This is great news, and I might be tempted to use it if I had some reassurance that the mail servers (and the organisation that controls them) weren’t subject to U.S. jurisdiction.

I’m quite happy with EuroDNS. They even include free email housing if you want it.

Fascinating! Thanks for sharing. I’m not sure I’d be happy in a fully remote role where you’ve got hundreds of employees voting on how you build stuff, but I know that there are lots of people who dig this pattern, and they’re clearly doing Good work.

True, but the mere existence of an AGPL project that follows the MIT one might be enough to convince would-be contributors to choose our version instead.

It may also be more likely to be adopted by non-corporate Linux distros that favour the AGPL over MIT (Debian for example) which in turn could help make the AGPL version the dominant one.

The best example I could point to would be BSD. Unlike Linux, the BSD kernel was BSD (essentially MIT) -licensed. This allowed Apple to take their code and build OSX and a multi-billion dollar company on top of it, giving sweet fuck all back the community they stole from.

That’s the moral argument: it enables thievery.

The technical argument is one of practicality. MIT-licensed projects often lead to proprietary projects (see: Apple, Android, Chrome, etc) that use up all the oxygen in an ecosystem and allow one company to dominate where once we had the latitude to use better alternatives.

• Step 1 is replacing coreutils with uutils.
• Step 2 is Canonical, Google, or someone else stealing uutils to build a proprietary “fuutils” that boasts better speeds, features, or interoperation with $PROPRIETARY_PRODUCT, or maybe even a new proprietary kernel.
• Steep 3 is where inevitably uutils is abandoned and coreutils hasn’t been updated in 10 years. Welcome to 1978, we’re back to using UNIX.

The GPL is the tool that got us here, and it makes these exploitative techbros furious that they can’t just steal our shit for their personal profit. We gain nothing by helping them, but stand to lose a great deal.

Here’s a fun idea, let’s fork these MIT-based projects and licence them under the AGPL :-)

Absolutely. I’ve been running Debian for literally decades both personally & professionally (on servers) and it’s rock-solid.

On the desktop, it’s also very stable, but holy-fuck is it old. I’m happy to accept the occasionally bug in exchange for modern software though, so I use Arch (btw) on the desktop.

Ubuntu is literally just Debian unstable with a bunch of patches. Literally every time I’ve been forced to use it, it’s been broken in at least a few obvious places.

I have zero interest in anything Microsoft has to say about Free software.

It’s a rather brilliant idea really, but when you consider the environmental implications of forcing web requests to ensure proof of work to function, this effectively burns a more coal for every site that implements it.

I find Croc to be rather just good for this.

A fascinating take on an old idea. I wish they’d spent more time covering the economics of mass producing these things.

Looking at it now, they haven’t linked to the source code anywhere so… yeah I wouldn’t trust it.

This looks really cool actually. I’ve created an account. Thanks for sharing!

Now I just have to find a #solarpunk “pub” :-)

I’ve used pdfkit to considerable success. It has a few system-level dependencies, but the instructions are pretty straightforward:

# apt-get install wkhtmltopdf
$ pip install pdfkit

I’ve been using Linux for 25 years. I started with SuSe, switched to RedHat after a couple months, and after a few more months switched to Gentoo… for 10 years, then did Arch for the remainder.

Frankly, I think that distro hopping is a bad idea because it means you don’t get enough time really understanding how to fix things. As a long time Arch user, it would never occur to me to throw out 10+years of tooling and scripts, muscle memory and shorthand to fix a driver issue. I would read the wiki top to bottom and then go spelunking through other sources until I find the solution (then update the wiki) before I’d switch to something foreign with its own set of problems and unknowns.

My advice is to find a distro that makes sense to you, and that has a deployment pattern you like and commit to it for a few years. Don’t switch unless you find something that fulfills those two requirements even better, and even then do so cautiously. Your experience and understanding is hard-won.

This is pretty slick, but doesn’t this just mean the bots hammer your server looping forever? How much processing do you do of those forms for example?

Also Ctrl+D to exit any shell and Ctrl+R for reverse searching your history!

Just be careful with files with spaces in the name. There’s an incantation with xargs that I always have to look up when I want to use it safely.

Not in and of itself, but I find that I have a handful of common tricks that I can put into aliases. Also, there’s ffmpeg.app!