Open Source Software Community - it's about ethics in Code of Conducts

  • Want to keep track of this thread?
    Accounts can bookmark posts, watch threads for updates, and jump back to where you stopped reading.
    Create account
dame dudi jench said:
Also, in many circumstances software patents are easy to work around
Click to expand...
Yes, just move out of the US. As mentioned above US (IP) law is fucking retarded and unsalvageable, and the only reason it has been getting worse elsewhere is US influence and overt pressure.

There's a reason openbsd developers traveled outside the US to implement crypto stuff, videolan insisting on staying in France (as well as ffmpeg being written by a fr*nch in the first place), mplayer hosting on handcranked hardware in Hungary, etc.
 
volatile puar said:
FFMPEG, btw, uses the LGPL because by allowing corponiggers to link it with their nonfree software they cause people to be more free.
Click to expand...
Hannibalistique said:
as well as ffmpeg being written by a fr*nch in the first place), mplayer hosting on handcranked hardware in Hungary, etc.
Click to expand...
Moving out of the US doesn't work if you want to sell your product there. You can't run form US IP law, activists need to engage with it and steer it in good directions. But yeah one of the biggest ironies in open source is that ffmpeg doesn't warn people that h264 and 265 are patented so they've generated millions of dollars in revenue for IP lawyers and Sony, Mitsubishi and the other corps in the mpegla patent portfolio when ppl innocently start using h264 for their product. they only talk about the issue obliquely in a blurb tucked away at the end of a FAQ many ppl never see. At least the last of the patents burn off in a year or two iirc, not completely sure.
 
Last edited:
Hannibalistique said:
Yes, just move out of the US. As mentioned above US (IP) law is fucking retarded and unsalvageable, and the only reason it has been getting worse elsewhere is US influence and overt pressure.

There's a reason openbsd developers traveled outside the US to implement crypto stuff, videolan insisting on staying in France (as well as ffmpeg being written by a fr*nch in the first place), mplayer hosting on handcranked hardware in Hungary, etc.
Click to expand...
Staying out of the US is not a get-out-of-hell-free card. For example, witness the mental contortions done by the britfags to make the unpatentable patentable. Note that all of these mental gymnastics result from the notion that while software can be regarded as pure math and logic and therefore lay outside the realm of patentable subject-matter, a "software patent" may nevertheless relate to some improvement of a technical character which is nevertheless patentable. This is why there are still software patents in europe, and once again you shouldn't listen to gnufags (but especially eurofags, since they seem to be especially ignorant).
 
The people you find on mailing lists are top tier content.
Schimon Jehudah is a lawyer (or AI) who wants Xlibre to rename Xforms because it's not doing its proper job—styling his blog's XML for RSS readers.
[xlibre] Renaming XForms
  • From: Schimon Jehudah <sch@fedora.email>
  • To: xlibre@xxxxxxxxxxxxx
  • Date: Fri, 20 Feb 2026 13:12:57 +0200
Greetings.

My name is Schimon, and I am very glad of the X11Libre (XLibre)
initiative.


Introduction
------------

I am a criminal lawyer, and one of the prime electronical concerns of
criminal lawyers here, is "safe hardware and software", which is also
having open source operating system, and a normal init system (e.g.
OpenRC, runit, s6-rc, et cetera).

This is required for privacy, instead of the state to utilize designed
"backdoors" of proprietary systems against lawyers.

Several law firms with which I am working as a lawyer have informed me
of their potential savings of costs due to the continuation of the
XLibre project, and their refusal to adopt the other "solution".


About
-----

In the recent year, I have been developing an XML based publication
software which is both a CMS and Journal platform.

Unlike other publication platforms with different "templating engines"
(e.g. Django, ERuby, Jinja, Smarty, et cetera), this platform utilizes
XSLT, which is standard.

As I intend to make this publication available with RSS Readers, I
replaced the "login" form with "HTTP Authentication"; and I further
consider to utilize the standard XForms to handle forms, instead of
creating a special XSLT stylesheet to create forms.

https://git.xmpp-it.net/sch/Rivista


Concern
-------

As I further study and explore more of XML, I have found XForms which
is an XML format for the collection and management of inputs.

Apparently, there is a "toolkit" which is also called XForms, and I
deem it to be a deliberate attempt of FDO to subtly censor XForms

Just as HTML5 and the "browser war" were an orchestrated operation to
facilitate spying by perpetuating HTML (invalid XML) patched by JS
(ECMAScript) over HTTP, and to advance the impossibility of competing
with a few organiztaions; instead of merely utilizing several XML
formats to exchange data over any protocol, including eD2k and Gnutella.

http://git.savannah.gnu.org/cgit/xforms.git

I do not know whether XLibre is or can be related with XForms; yet, if
at all possible, I would advise to rename project XForms to something
else, in order to avoid the cesoring of the XForms XML format.


Kind reagrds,
Schimon


Other related posts:​

Click to expand...
 
I do have one thing to say about ladybird moving to rust.

I know it's the popular thing right now to hate rust. But why is it a big deal that a new project that hasn't even had a proper release yet is moving to rust? Especially when Ladybird is on so many of the tranny "nazi bar" shit lists.

It's not someone suddenly forcing rust into a giant 20 year old C project, and it's not a tranny shoving rust down your throats. It seems like people have completely lost sight of what the actual problem is with rust. It's not the language itself, and someone deciding to use rust for something isn't a bad thing or a good thing. (Although someone trannies hate using rust is a good thing).

Especially when the language they are moving from was kind of a shit choice in the first place because it was apples fairly platform specific swift that rust is taking the place of. Maybe if they picked go it would have made less sense to move to rust but in this case it seems fine. Along with the c++ they're using
 
prollyanotherlurker said:
I do have one thing to say about ladybird moving to rust.

I know it's the popular thing right now to hate rust. But why is it a big deal that a new project that hasn't even had a proper release yet is moving to rust? Especially when Ladybird is on so many of the tranny "nazi bar" shit lists.

It's not someone suddenly forcing rust into a giant 20 year old C project, and it's not a tranny shoving rust down your throats. It seems like people have completely lost sight of what the actual problem is with rust. It's not the language itself, and someone deciding to use rust for something isn't a bad thing or a good thing. (Although someone trannies hate using rust is a good thing).

Especially when the language they are moving from was kind of a shit choice in the first place because it was apples fairly platform specific swift that rust is taking the place of. Maybe if they picked go it would have made less sense to move to rust but in this case it seems fine. Along with the c++ they're using
Click to expand...
It's just pointless churn, they had good C++ code and now they have weird translated rust code. It's equivalent in functionality and looks weird. It didn't reveal any insights into anything the old code might've been doing wrong. No regressions, no improvements, nothing.
We will continue developing the engine in C++, and porting subsystems to Rust will be a sidetrack that runs for a long time.
Click to expand...
What's the point of that. What does the process of porting unlock in that case? They're still going to write it without any of the rust's guarantees and safety nets, develop test cases, fix bugs, and then when it's all ironed out, transpile it with AI into weird C++-like rust that's 100% equivalent but somehow better? I just don't get it.

You can write safe c++, they are already doing it, using a whole bespoke standard library even. It just feels like change for the sake of change, ill-defined progress to chase after.

They weren't using Swift, they said they would but they never did, it just fizzled out. They made their own language, they tried Swift, they stayed with C++, all to not go with rust. They're ripping out the cool rebellious hand-made spirit of the project, the legacy of SerenityOS, the cheeky "skill issue? just git gud with C++" approach for nothing

The soul is gone

i may be acting a little melodramatic
 
prollyanotherlurker said:
I do have one thing to say about ladybird moving to rust.

I know it's the popular thing right now to hate rust. But why is it a big deal that a new project that hasn't even had a proper release yet is moving to rust? Especially when Ladybird is on so many of the tranny "nazi bar" shit lists.

It's not someone suddenly forcing rust into a giant 20 year old C project, and it's not a tranny shoving rust down your throats. It seems like people have completely lost sight of what the actual problem is with rust. It's not the language itself, and someone deciding to use rust for something isn't a bad thing or a good thing. (Although someone trannies hate using rust is a good thing).

Especially when the language they are moving from was kind of a shit choice in the first place because it was apples fairly platform specific swift that rust is taking the place of. Maybe if they picked go it would have made less sense to move to rust but in this case it seems fine. Along with the c++ they're using
Click to expand...
I was more concerned with AI/otherwise automated translation, but they went about it the smart way:
The requirement from the start was byte-for-byte identical output from both pipelines. [...] We’ve verified that every AST produced by the Rust parser is identical to the C++ one, and all bytecode generated by the Rust compiler is identical to the C++ compiler’s output. Zero regressions across the board[.]
Click to expand...
The other worrying part is this:
This is not becoming the main focus of the project. We will continue developing the engine in C++, and porting subsystems to Rust will be a sidetrack that runs for a long time. New Rust code will coexist with existing C++ through well-defined interop boundaries.
Click to expand...
The pessimist in me reads this as "Rust is just tacked on to the side and we'll be doing the same work twice, writing code in C++ then rewriting it in Rust later".


Edit to not double-post:
Hacker News, 1k+ points, 620 comments
Lobsters, reaction is exactly what you'd expect.
 
Last edited:
Max Weber said:
Lobsters, reaction is exactly what you'd expect.
Click to expand...
seething.png
It's nice to not care when it's not you the one they want dead, gone, plus your friends and family too.
Click to expand...
"When we win, do not forget that these people want you broke, dead, your kids raped and brainwashed, and they think it's funny"
 
You must log in or register to reply here.
Back
Top Bottom