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.
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.
I chose Bookstack for the same situation. It’s dead simple in usage and maintenance. No issues yet!
I will have an OG Xiaomi Mi Box and it’s absurd how over the years it went from a purely functional media device to a complete shit show covered ads. Genuinely disgusted me every time I turned the TV on. I couldn’t stand it anymore, I had to tear out the launcher with ADB and replace it with FLauncher.
I wish Kodi wasn’t such a pain in the ass to deal with, especially for YouTube. We really need a new FOSS media center application. Until then, at least FLauncher works for now as a simple app switcher for a handful of Android apps.
Recently started using Tempo with Navidrome. Haven’t had more than a few days of use yet, but everything has worked exactly as expected! Can’t ask for much more than that.
If I were to list every FOSS project that has lasted longer, I’d have to spend all day writing the post. winRAR is unique in that it’s one of the only pieces of long-lasting proprietary software that didn’t die or turn to crap. Such things are not unique or even rare in FOSS.
WinRAR will either die, or be sold and squeezed by its new owners. Nobody lives forever and no asset goes unflipped in this market. You can say you won’t update, but that just leaves you vulnerable.
It’s not an opinion that proprietary for-profit software will betray you, it is an inevitability. It has happened every single time. If it was FOSS, we could salvage it. It’s proprietary, so we can’t. When it fails it must simply be abandoned. I just hope you learn the right lesson when this happens.
I’d argue it’s pretty stupid to use FOSS but then depend on a proprietary server that only one for-profit company is allowed to run to deliver all that software, trusting them to just never do wrong or leave you high and dry. I’d also argue it fits the analogy perfectly, because the analogy was about saying “I haven’t had a problem yet” in response to being shown the potential problems of the action.
Me reacting to analogies with “Did you know these two things are not completely identical?”, completely unburdened by the knowledge that I’m supposed to explain how the differences invalidate the comparison.
Presumably they are going to do more than simply rebrand it.
Most people do not care about their init system. Fewer still care about your init system. Use what you want, just quit shouting about it.
I very recently started using borgbackup. I’m extremely impressed with how much it compressed the data before sending, and how well it detects changes and only sends the difference. I have not yet attempted a proper restore from backup, though.
I have much less data I’m currently securing (~50gb) and much more uplink bandwidth (~115mbps) so my situation isn’t nearly as dire. But it was able to compress that down to less than 25gb before sending, and after the initial upload, the next week’s backup only required about 100mb of data transfer.
If you can find a way to seed your data from a faster location, reduce the amount you need to back up, and/or break it up into multiple smaller transfers, this might be an effective solution for you.
Borgbase’s highest plan has an upper limit of 8TB, which you would be brushing right up against, but Hetzner storage boxes go up to 20TB and officially support Borg.
Outside of that, if you don’t expect the data to change often, you might be looking for some sort of cheap S3 storage from AWS or other similar large datacenter company. But you’ll still need to find a way to actually get them the data safely, and I’m not sure if they support differential uploads like Borg does.
It’s far better than it used to be. They didn’t get the reputation for no reason. There were lots of Nvidia-specific bugs that have been slowly sorted out over the years. I’m told Wayland is even in a roughly usable state now. But it takes a lot of time to regain the lost trust. Let’s see how long it takes them to support HDR, and what that support looks like.
The goal here is to make it difficult to link to things uploaded to discord from outside of discord. The malware reason is BS. If they wanted to curb malware it would be as easy as making it a nitro feature. What that doesn’t fix is all the people piggybacking on discord as a free CDN.
Discord isn’t even wrong for doing this. I just resent their dishonesty.
This sucked, but shouldn’t happen anymore now the the flatpak is official.
This is the most important takeaway. There’s a lot of people whining about Wayland, but Wayland devs are currently the only people actually willing to put in the work. Nobody wants to work on X and nobody wants to make an alternative to Wayland, so why do we keep wasting time on this topic?