bear

One of those two will be president no matter what you do. They will then be in a position capable of inflicting great damage. Trump will use that position to hurt more people than Biden. The math here isn't complicated, and it continually astounds me how many people on the left cannot actually solve the trolly problem when faced with it for real. It really shows which people are engaged in politics as a means to an end rather than as personal expression or a hobby.

You should play it. It's such a pleasant experience. In fact, I might play it again now that I've remembered it.

Maintaining multiple SKUs with major differences is quite expensive and time consuming, plus confusing for the customer on a global Internet trying to look things up. I expect that this would make at least some manufacturers ship these to other countries, so we would have some options.

The full details are complex but I'll give you the basic gist. The original GPL licenses essentially say that if you give somebody the compiled binary, they are legally entitled to have the source code as well, along with the rights to modify and redistribute it so long as they too follow the same rules. It creates a system where code flows down freely like water.

However, this doesn't apply if you don't give them the binary. For example, taking an open source GPL-licensed project and running it on a server instead. The GPL doesn't apply, so you can modify it and do whatever, and you aren't required to share the source code if other people access it because that's not specified in the GPL.

The AGPL was created to address this. It adds a stipulation that if you give people access to the software on a remote system, they are still entitled to the source code and all the same rights to modify and redistribute it. Code now flows freely again, and all is well.

The only "issue" is that the GPL/AGPL are only one-way compatible with the Apache/MIT/BSD/etc licenses. These licenses put minimal requirements on code sharing, so it's completely fine to add their code to GPL projects. But themselves, they aren't up to GPL requirements, so GPL code can't be added to Apache projects.

Most Snaps have apt or Flatpak alternatives.

I'm simply not going to support a distro that creates a proprietary service and ships it as the default source of software. I will support and use distros that open source their code so that everyone can benefit from it. Whether workarounds or alternatives exist is unimportant, my prime issue with Ubuntu and Canonical is with their principles, not Ubuntu's quality as a product to be consumed by me.

Look, I'm usually first in line to shit on Canonical, but I can't get mad at them adopting AGPL. This is objectively the best license for server software. Incus should also switch to AGPL for all Canonical code, and seek to have contributors license their code as AGPL as well.

I will however point out the hypocrisy and inconsistency of it, because the Snap server is still proprietary after all of this time. If this is their "standard for server-side code" then apply it to Snaps or quit lying to us.

The only difference between Tumblr and Facebook is size. Facebook isn't uniquely evil; it does exactly what any corporation would do at that scale. The systems that molded Facebook into what it is would also mold Tumblr or anything else into the same abomination.

I would respect principled opposition to megacorps even if I think it's still misguided in this instance, because at least that's overall based. But all of the discourse focuses on the specific wrongdoings of Facebook as if any other corporation wouldn't have done exactly the same thing in their position. It feels very kneejerk.

I want to federate and use it to destroy their platform. The biggest problem with the periodic social media "migrations" that always fail is that it creates a fragmented diaspora. Take Twitter as an example. When the big migration off Twitter was supposed to happen, some went to the Fediverse, some went to Threads, some went to BlueSky.

You know what happened? After a few weeks, most of them went back to Twitter, because that was the only common place between them, where they knew they could all meet and communicate. If Twitter was forced to federate with all other platforms, it would have been snuffed out by now. But if that was even proposed, everybody would have a kneejerk reaction, because Twitter bad. Nobody is thinking of the big picture.

I find it kind of strange that people seem so hesitant about it

I simply want the Fediverse to be a proper alternative option for social media access, not just another secret nerd club. We have enough of those already. That requires not completely closing off access to the things the typical person will want to access. I want all social media to eventually be interoperable like email is, preferably on the ActivityPub standard and not whatever centralized bullshit BlueSky is trying to cook up. That is the only way we're going to break the corporate stranglehold on social media.

Put simply, if you make people choose between our platform and the large corporate-backed platform with orders of magnitude more users, they will choose the corporate platform almost every time. And I think that's a bad outcome for all involved.

If you're waiting for Jellyfin to run some kind of relay like Plex, you'll be waiting a long time. That takes a lot of money to upkeep, and the demand for people who self-host FOSS and then want to depend on an external service is very minimal, certainly not enough to sustain such a service. I'd recommend just spending a weekend afternoon learning how to set up Nginx Proxy Manager and being done with it, the GUI makes it very easy.

If Linux was that easy, adoption would be higher

People use what comes on the computer. OS usage on the Steam Deck is overwhelmingly Linux because that's what comes on it. This indicates that Linux is perfectly fine for the average person, it just needs to come pre-installed. Very few people install their own OS either way, Linux or Windows.

I assume doog is the opposite of good, in which case I agree

I chose Bookstack for the same situation. It's dead simple in usage and maintenance. No issues yet!