#fossdrama — Public Fediverse posts

The @Codeberg FOSS Drama continues as predicted with @bizzfed

https://codeberg.org/rhamdorf/BizzFed/issues/37

🍿

I predict this blog clause will be pleaded by the defendant: "Projects who have an active community that cares about and maintains the software". With my bet for the plaintiff to be pleading the "Projects written and maintained with heavy use of LLMs" clause.

#bizzfed #codeberg #fossdrama #opensorce #llm #aiassisted #forgejo

The @Codeberg FOSS Drama continues as predicted with @bizzfed

🍿

I predict this blog clause will be pleaded by the defendant: "Projects who have an active community that cares about and maintains the software". With my bet for the plaintiff to be pleading the "Projects written and maintained with heavy use of LLMs" clause.

#bizzfed #codeberg #fossdrama #opensorce #llm #aiassisted #forgejo

Looks like Flatpak discovery will move from one mostly generally accepted hub to a gazillion of repos since the performative LLM complaints have befallen the possible single hub. (Partially half-understandable arguments, partially performative fluff for my taste)

Which is ok as it triggers competition that might lead to better outcomes. (bazaar vs cathedral and all, rite? 😏 )
And removes a possible single point of failure.

Now what I'd like to see is an approach that does discovery of those repos and enables search across those repos without a single point of failure. As e.g. a single, centrally hosted index for repos to register to would be.

Flatpak already uses a reverse-dns-namespace structure internally. Anything that would leverage that? Wouldn't help with enumeration though.

Something something DHT/Gossip/...? (as the cool thing from the past)

Clearly a problem that will arise with more of the expectable decentralized systems that need uniform discovery and search.

What's the Fedis wisdom on current academic approaches that might be interesting around this?
Or bastardized routing tech, yet another idea on how to twist DNS into a pretzel, etc? Dare I say: Blockchain (as the unpopular thing before the LLMs 🤣 )

Throw you best Arxiv posts etc. at me. I'm just curious about the state-of-the-art techn for now, all smirk and sarcasm aside.

#discovery #search #decentralized #routing #dns #fedimeta #flathub #dht #cooltechfromthepast #llm #selfhosting #fossdrama #spof #singlepointoffailure #arxiv #academicchatter #academic #computerscience

Looks like Flatpak discovery will move from one mostly generally accepted hub to a gazillion of repos since the performative LLM complaints have befallen the possible single hub. (Partially half-understandable arguments, partially performative fluff for my taste)

Which is ok as it triggers competition that might lead to better outcomes. (bazaar vs cathedral and all, rite? 😏 )
And removes a possible single point of failure.

Now what I'd like to see is an approach that does discovery of those repos and enables search across those repos without a single point of failure. As e.g. a single, centrally hosted index for repos to register to would be.

Flatpak already uses a reverse-dns-namespace structure internally. Anything that would leverage that? Wouldn't help with enumeration though.

Something something DHT/Gossip/...? (as the cool thing from the past)

Clearly a problem that will arise with more of the expectable decentralized systems that need uniform discovery and search.

What's the Fedis wisdom on current academic approaches that might be interesting around this?
Or bastardized routing tech, yet another idea on how to twist DNS into a pretzel, etc? Dare I say: Blockchain (as the unpopular thing before the LLMs 🤣 )

Throw you best Arxiv posts etc. at me. I'm just curious about the state-of-the-art techn for now, all smirk and sarcasm aside.

#discovery #search #decentralized #routing #dns #fedimeta #flathub #dht #cooltechfromthepast #llm #selfhosting #fossdrama #spof #singlepointoffailure

More fork drama ensuing as was to be expected:

https://github.com/flathub-infra/documentation/pull/641

Also, thanks for highlighting the existence of
https://flatpark.org/

People hosting their own flatpak repos for their apps is increasing as it appears to me too.

Luckily the format, tooling and docs for this are pretty useful and enable easy publication straight from Github actions or the likes. Compared to Flathub a rather pleasant experience.

Now what'd be great would be a (forge based) discovery mechanism for self hosted flatpak repos.

#fossdrama #flatpak #flatpark #flathub #foss #opensource #llm #selfhosting #fork #github #githubactions

More fork drama ensuing as was to be expected:

https://github.com/flathub-infra/documentation/pull/641

Also, thanks for highlighting the existence of
https://flatpark.org/

People hosting their own flatpak repos for their apps is increasing as it appears to me too.

Luckily the format, tooling and docs for this are pretty useful and enable easy publication straight from Github actions or the likes. Compared to Flathub a rather pleasant experience.

Now what'd be great would be a (forge based) discovery mechanism for self hosted flatpak repos.

#fossdrama #flatpak #flatpark #flathub #foss #opensource #llm #selfhosting #fork #github #githubactions

Here's an interesting one around all the "no projects with the LLM taint wanted here" discussion, taking Codeberg as example:

• Codeberg offers to host binary releases

• Current (FOSS) software contains hundreds or thousands of individual works as dependencies in deep dependency trees

• It can be regarded as nearly certain that a substantial amount of those projects will fall under the exclusion or problematic class as per the rules above

• Once complied to a release binary those "tainted" works are often included in the binary and will thus be uploaded to the forge as a release.

• Hence, the forge will be hosting ToS violating material on behalf of the project subjecting the otherwise possibly compliant project to possible sanctions.

Now what do we make of that thought experiment? And how do we resolve it?

#codeberg #llm #sca #foss #compliance #fossdrama #opensource #fossdrama #drama #aiassistedcoding

Here's an interesting one around all the "no projects with the LLM taint wanted here" discussion, taking Codeberg as example:

• Codeberg offers to host binary releases

• Current (FOSS) software contains hundreds or thousands of individual works as dependencies in deep dependency trees

• It can be regarded as nearly certain that a substantial amount of those projects will fall under the exclusion or problematic class as per the rules above

• Once complied to a release binary those "tainted" works are often included in the binary and will thus be uploaded to the forge as a release.

• Hence, the forge will be hosting ToS violating material on behalf of the project subjecting the otherwise possibly compliant project to possible sanctions.

Now what do we make of that thought experiment? And how do we resolve it?

#codeberg #llm #sca #foss #compliance #fossdrama #opensource #fossdrama #drama #aiassistedcoding

@Codeberg Hackernews called it, the internet delivered: https://vibeberg.org/

🤣

#lol #vibecoding #vibeberg #codeberg #forgejo #thatescalatedquickly #llm #ai #fossdrama #foss #opensource

@Codeberg Hackernews called it, the internet delivered: https://vibeberg.org/

🤣

#lol #vibecoding #vibeberg #codeberg #forgejo #thatescalatedquickly #llm #ai #fossdrama #foss #opensource

Todays FOSS Drama served to you by @Codeberg

Tl;dr: Codeberg wants to exclude "vibed"/" LLM'd projects from its platform by means of TOU, hilarity ensues.

https://codeberg.org/Codeberg/org/pulls/1253#issuecomment-19820434

https://news.ycombinator.com/item?id=49003386 (via, also some discussion)

Adding one here: Burden of proof and how do you sufficiently prove or refute the "vibed" nature of any given work without falling to arbitrary / unpredictable results.
One more argument for self-hosting.

Also interesting to projects such as #bizzfed or #nolto both of which would likely or clearly be banned from the platform now.

#fossdrama #foss #hackernews #opensource #LLMs #tos #codeberg #intellectualproperty #selfhosting

Todays FOSS Drama served to you by @Codeberg

Tl;dr: Codeberg wants to exclude "vibed"/" LLM'd projects from its platform by means of TOU, hilarity ensues.

https://codeberg.org/Codeberg/org/pulls/1253#issuecomment-19820434

https://news.ycombinator.com/item?id=49003386 (via, also some discussion)

Adding one here: Burden of proof and how do you sufficiently prove or refute the "vibed" nature of any given work without falling to arbitrary / unpredictable results.
One more argument for self-hosting.

Also interesting to projects such as #bizzfed or #nolto both of which would likely or clearly be banned from the platform now.

#fossdrama #foss #hackernews #opensource #LLMs #tos #codeberg #intellectualproperty #selfhosting

One fresh FOSS drama coming right up: https://bbhtt.in/posts/flathub-leave/

Whatever has really happened there - the review and update process of Flathub clearly is cumbersome to ineffective or at least inefficient in my view. As are some policies.

Very unfortunate for such a seemingly central piece of desktop Linux app distribution.

Let's hope for a better evolution over time...

#fossdrama #foss #opensource #flathub #flatpak

@littlealex @cR0w Yup. That is exactly the rule of the game. Very publicly known since ages. BDFL and all.
Everyone who is even modestly involved in it knows Mr Torvalds approach to things past his threshold of fucks to be given.

To summarize: High qualify FOSS 🍿 drama. More in news at eleven. 😂

Here's the relevant actual LKML link: https://lore.kernel.org/linux-media/CA[email protected]/

#lkml #linux #torvalds #foss #fossdrama #ai #llm #opensource

@littlealex @cR0w Yup. That is exactly the rule of the game. Very publicly known since ages. BDFL and all.
Everyone who is even modestly involved in it knows Mr Torvalds approach to things past his threshold of fucks to be given.

To summarize: High qualify FOSS 🍿 drama. More in news at eleven. 😂

Here's the relevant actual LKML link: https://lore.kernel.org/linux-media/CA[email protected]/

#lkml #linux #torvalds #foss #fossdrama #ai #llm #opensource

@adamsdesk

I have no way of actually verifying this, but it seems (according to certain parties' accusations) that whoever is calling the shots at The Document Foundation (i.e. the LibreOffice org) is pulling a Gnome Foundation and deciding to jettison whoever they don't like.

...but like... ten times worse?

Umm... egad. #FOSSDrama #ArentWeAllAdultsHere?

@adamsdesk

I have no way of actually verifying this, but it seems (according to certain parties' accusations) that whoever is calling the shots at The Document Foundation (i.e. the LibreOffice org) is pulling a Gnome Foundation and deciding to jettison whoever they don't like.

...but like... ten times worse?

Umm... egad. #FOSSDrama #ArentWeAllAdultsHere?

Mmmmkay, a Collabora <--> LibreOffice public online grudgematch sounds like a very odd and un-original #AprilFools joke, but it's somehow... not??

https://www.collaboraonline.com/blog/tdf-ejects-its-core-developers/

https://blog.documentfoundation.org/blog/2026/04/01/comment-about-collabora-blog-post/

What the heck? XD

#Collabora #LibreOffice #FOSSDrama

Mmmmkay, a Collabora <--> LibreOffice public online grudgematch sounds like a very odd and un-original #AprilFools joke, but it's somehow... not??

https://www.collaboraonline.com/blog/tdf-ejects-its-core-developers/

https://blog.documentfoundation.org/blog/2026/04/01/comment-about-collabora-blog-post/

What the heck? XD

#Collabora #LibreOffice #FOSSDrama

RE: https://fosstodon.org/@ONLYOFFICE/116323756094840918

Quite the interesting fresh FOSS drama.
Curious to see how this will turn out. Two 🍺 on settlement.

Also, should the verdict go towards the Euro-Office fork will we see any precendence for other cases effectively weaking FOSS legal protection? Will distributors or integrators be impacted?

@Karlitschek being a clear FOSS native will surely have a proper strategy & plan forward laid out for this with his legal counsel. Or so one would hope.

Technically a pleasant product that one could only hope to be continued and advanced, ideally on combined man power of both parties.

#fossdrama #fosscompliance #onlyoffice #eurooffice #drama #foss #opensource

Quoting Alan Cox [@etchedpixels] at Twitter:

>> Mike McGrath for Red Hat: “We will always send our code upstream and abide by the open source licenses our products use, which includes the GPL.”
> https://www.redhat.com/en/blog/red-hats-commitment-open-source-response-gitcentosorg-changes

Meanwhile:

>> Magnus Glantz of Red Hat: “I guess some people just still have not understood that free software (which open source originally was called), refers to free as in freedom, not free as in free beer, free labor or free money.”
> https://www.linkedin.com/pulse/problem-rocky-linux-free-beer-magnus-glantz/

It's all puff pieces about fear and freeloading that are old Microsoft grade.

And it speaks to the point. IBMHat thinks it “sells Red Hat Linux”, no it sells support and services. The code isn't really theirs to sell.

(Not when it's “100% Open Source”. ~ed.)

___

🐦: https://twitter.com/EtchedPixels/status/1673610472224899072 / https://nitter.net/EtchedPixels/status/1673610472224899072

#RedHat vs #RockyLinux #IBMHat #FOSSdrama #DistroDrama #LinuxDrama #SourceCodeGatekeeping