Jul (they/she)

But why are the patches kept separate at all. Especially if it’s a copyleft licensed code they’re patching. Many of those require release of the code. And the spirit of that was to make companies who profit off of the code release anything they add as they add it. Otherwise, they’re welcome to instead of taking open source code and patching it, creating closed source code from scratch without using any of the code from the open source version and selling that. It’s very simple. The license says, you want this code, you’re welcome to it, but release any fixes or improvements you make do we all benefit, not just developers, but users all benefit. If they keep it locked up, even if they release it as a patch that’s not accessible to the large majority of users, then it’s violating the spirit if in some cases not the letter of the license.

Exactly. But the corporations do it because it benefits them more than starting from scratch. They should release all changes to the central repository for all to consume as part of the agreement to get the benefit of the already created software. Not hold onto the patches to give them to their customers and people who pay them with their personal information.

Same they did before or red hat does or every other corporation who has benefitted from the labor of open source developers. Services built on those things or built around them. Not the things themselves. Their corporate customers benefit from the stuff they produce, but they didn’t produce most of it,so either start from scratch with, propriety software, or they need to give the content to everyone at the same time, not hold onto it for some time. That’s against the whole idea of open source and probably technically violates some copyleft licenses, but definitely violates the spirit of them. Even if they fix some bugs or add some features, they didn’t come up with the ideas, build the thing while it wasn’t producing income, or build the communities that they collaborate with. They just add what benefits them to the existing content.

Ubuntu has that dumb subscription to get security updates that pushed me away. Sure it was free for personal use, but I don’t want to have to give my personal information to get updates that are created primarily by volunteer open source developers anyway.

Cool. I activate all of the public ones. They come and go and rate limit and such. So just use them all. Unless you want to pay or try to find an invite to a free private one. That I can’t help with. But it works for me. Takes a little longer to search all of them, but it’s usually in the background so no big deal for me.

Try prowlarr.

It’s usually the opposite that’s the issue for me. If it’s not free, OK, let’s pay, but if it’s not a reasonable price for the product (including both the content, usability, and reusability, in case of media), then I’ll go out of my way to get it free or totally give up on it depending on how much I want it. That’s why I switched from piracy to Netflix for many years and now am back to piracy because I like shows in the background while working on projects, for example, or piracy, then Steam, then, fuck gaming as much because I found other hobbies.

Often the content is available without masking for a very short time so scrapers can access them or similar tricks to allow them access immediately after posting. But that requires that you hit the server immediately after the story is posted and there is no masking at all usually in those cases. That’s how things like archive.is get a copy for example. But none of that is client/browser side anymore, at least on the major sites. Otherwise it’s easy to defeat if the content is already provided to the browser and just masked with JavaScript or something that runs locally and can be blocked.

Hasn’t worked on most sites in a long time. The obscuring is now done on the server side so the text never gets to the browser. Otherwise it used to be easy to just use the developer console or uBlock to just remove the components that concealed the text or prevent the browser refreshing to prevent the concealing.

X11 is way, way older than that. But it also was more actively developed for most of that time.

Wayland is still too new for a lot of complex functionality. It works well enough for the vast majority of use cases, but X11 is still superior in terms of functionality. But like many systems, control means higher learning curve due to various quirks and complex configurations.

Because the random alterations create variations that allow survival of the species, not the individual, in changing conditions. For an example of what happens without that, just look at bananas. Without any evolution through DNA alteration during procreation, a single disease van wipe them out across the globe. Happened once and the current strain is being wiped out by disease, though more slowly due to human intervention, as we speak.

That future might not be far off considering what Trump did today. Balance of power is seriously about to shift.

If it’s POSIX compliant then it will work on all versions of Linux/Unix. Otherwise it depends on specific implementations that have branched for decades.