eleijeep

what licence can we use to force any entity using a library to make their project open-source

GPL requires this, since linking with a library is considered a derivative work even if the library is dynamically loaded.

This is why the LGPL exists, which makes the library copyleft but does not extend the derivative work classification to programs linking with the library.

Interesting, but ultimately a roundabout justification for why the author chose a non-FOSS license for their startup Slack-clone built on ATProto.

They talk about “pro-labor licensing” but what they mean is pro- their -labor, not pro- anyone else’s -labor.

GPL is already the most pro-labor licensing since it respects the work of anyone who contributes in equal measure, and does not hold the “original” founding author in higher regard.

It’s really quite something to rail so unequivocally against the “fascistic mega-corps” and “autocratic corpostates” in your licensing justification blog post and then build your commercial product on top of Bluesky .

The GPL doesn’t place any restrictions on selling or profiting from GPL licensed works. It only requires that anyone distributing the work provides the recipients with the same rights under the GPL, ie. the right to view, modify and redistribute the source code.

This means that a company cannot take a GPL licensed work and turn it into a proprietary product.

GPL is the only thing standing between us and Embrace-Extend-Extinguish.

There’s a reason that “Stallman was right” is a meme in the FOSS world.

Do you think IBM wouldn’t make Red Hat completely proprietary if they had the chance? They already tried to use their customer licensing to restrict source access!

It only takes one successful proprietary product to gain mind-share and market-share and become a new de-facto standard, and then all of the original FOSS has to play catch-up and stay compatible to stay relevant.

See Jabber/XMPP for an example.

The post is about NixOS. The intro paragraph about Arch is just a preamble to provide the motivation for switching.

> Joined 3 hours ago
> first post is concern trolling

You wrote this shit with an LLM, didn’t you?

This is the post that made me unsubscribe. Bye.

the broadcom module is always significantly behind the kernel

Right, but if it’s not unmaintained then you only have to wait a finite amount of time before you get to update your kernel again yes?

but held packages like your kernel impact other software as well

Well… I’d be interested to hear what user-space impacts you’ve experienced from running a kernel that’s “weeks or even months behind the latest kernel .”

Oh it’s the transphobic billionaire’s game. Nice 👍

The FreedomBox project started in 2010, and it’s a Debian-based plug and play device that lets you easily self-host useful network services.

This is just an ad for “Viduli, The AI-native cloud platform”

The discussion itself is off-topic for this community anyway. Who would even think about using “serverless” for self-hosting?

Ah, docker compose makes it easy! Thanks.

I just configure them to use the network stack from that container.

Can you explain how you do this (or link to a guide that you found useful)? Thanks

You need to learn about e and E motions, but also $ will take you to the end of the line.

if you click on it, the link in your browser’s address bar will more likely render properly.

The default on librewolf (and possibly Firefox?) is to show the punycode in the URL bar since rendering the international characters can be used as a way to create phishing URLs that look similar (and sometimes identical) to characters in the latin alphabet. This is a very dangerous feature since the URL bar of the phishing site can look identical to the real website address.

To enable the display of the alternate character sets represented by the punycode URLs, you have to set network.IDN_show_punycode to false in about:config.

Form over function. They probably have aspirations of getting VC funding and for that you need to look like every other web app.

You get incremental backups (snapshots) by using

--link-dest=DIR         hardlink to files in DIR when unchanged

To use this you pass in the previous snapshot location as DIR and use a new destination directory for the current snapshot. This creates hard links in the new snapshot to the files which were unchanged from the previous snapshot, so only the new files are transferred, and there is no duplication of data on disk (for whole-file matches).

This does of course require that all of the snapshots exist in the same filesystem, since you cannot hard-link across filesystems.

I checked your Mastodon timeline but I don’t see the post, only the one where you relate the story.