It doesn’t explicitly, but because all subsequent forks and software that makes use of GPL licensed code must also adhere to the GPL license, the original developer more naturally becomes the sole maintainer unless you can build a community of like-minded developers. Free and open source software doesn’t have much incentive for maintenance outside of those passionate about it.

With an MIT license, attribution is sufficient and a business that finds value in that code may repackage, redistribute or sell that code without making their whole product strictly open source. In this way, you end up with larger business investment in your works because there’s an inherent value in keeping it maintained that has a direct return.

Seeing as you’re running this from a laptop, was this speed test performed on a wired connection?

For self-hosting services you want to access remotely, you may find this to be exceptionally limiting. It may not be too bad if you live alone, and you’re sure no one else is using your network when you’re gone, but other devices performing routine updates may be enough to disrupt your outgoing connection. Additionally, that ping would indicate the speed test is being run from somewhere quite far from you. Latency that bad isn’t a great time for applications that might expect a consistent response time.

As for streaming those FLACs from your server while at home: You’re not going to struggle loading these files, because your local network is likely running at least at gigabit speeds. That speed test isn’t representative of your network as a whole, but just your internet connection.

This isn’t the first time you’ve approached this problem like it’s supposedly a relatable aging one. None of the symptoms you describe are things that come with age unless there is an underlying health issue.

Please keep seeking medical assistance. Search for second opinions, or specialists who target sleep disorders.

Well, morons bought it and the device is directly connected to a data harvesting company. I think that has more to do with it. One lone weirdo with a hidden camera and a home server isn’t the same kind of boogeyman

The only thing I’ve missed, like truly missed about old Reddit was Secret Santa. There was something so fun about it, and the system was so good. I know it’s logistically challenging, even more so for a federated platform, but it was one of the things that made the site feel unique.

Seems like it’s specific to Piefed after looking for more examples. Something baked into the code for that particular fediverse host?

What’s up with the þ symbol in your comment? Odd thing to go out of your way to use?

If I remember right, that post wasn’t designed to highlight a practical use-case, but rather to set up a simple task as a “how could I apply this?” type of experimentation. The guy got roasted for it, but I think it’s a very reasonable thing to try because it’s a simple task you can see the direct result of in practice.

The cost problem was highlighted as well, because if such a simple task is a problem, it can’t possibly scale well.

Audio hasn’t worked for me or my friends across Linux or Windows. Been kind of a pain.

It also seems to suffer the XWayland issue in Linux that Discord did for quite some time where it just flat out fails to get screen capture in the desktop app, but works in the browser. Electron pains

Paying for journalism is ideal, but unfortunately makes it difficult to cite/link to a source the way Wikipedia needs as a way to ensure the information remains open and accessible.

Admittedly, I’m not familiar with these outlets enough to know if those paywalls are significant, but the problem with direct article links is that those links can change. Archival services (I suppose not archive[.]is) are important for ensuring those articles remain accessible in the format they were presented in.

I’ve come across a number of older Wikipedia articles about more minor or obscure events where links lead to local new outlet websites that no longer exist or were consumed by larger media outlets and as a result no longer provide an appropriate citation.

Both are great, and I think complement eachother nicely. Qobuz mostly focuses on label offered music catalogues, while Bandcamp has always catered to indies. If an artist offers their music through Bandcamp, I still prefer to make my purchases there, but if the artist is signed to a label then it’s a good shot Qobuz has it.

Either service offers the music in the highest quality provided, though lossless versions through Qobuz do tend to be priced a few dollars higher than the regular album.

I’ve settled for Qobuz. Its discovery features are terrible, but it’s basically a music storefront with a streaming library. High-quality, had basically my whole library and I can buy albums directly for download.

You can use slsk-batchdl alongside a CSV of your Spotify Playlists to make quicker work of this.

People say it because it was a Windows limitation, not a computing limitation. Windows Server had support for more, but for consumers, it wasn’t easily doable. I believe there’s modern workarounds though. The real limit is how much memory a single application can address at any given time.

I don’t feel like this is a terribly recent attitude. It’s definitely one I’ve encountered repeatedly over a decade or more of dipping my toes in the pool. It’s not incorrect in a lot of circumstances, but it’s very difficult to find support when no one wants to help you improve. There’s always been a significant degree of ego in Linux user communities.

Well that’s a strangely deep cut Ken Ashcorp ref

Flatpaks are basically containers, allowing applications to maintain their own dependencies separate from your system. It’s similar to a Windows program shipping with its own precompiled DLLs, helping prevent dependenct conflicts when you go to update something you installed with pacman or yay.

Arc support was added after release to Linux Kernel 6.2 and it’s steadily improved since. Older Linux distros, or “LTS” oriented distros that favour stability may still not have support for them. I know Unraid was very slow to pick up on it and I had to settle for passing the pcie device through to a VM to get it working. Intel is keen to made these viable though, and I love having the AV1 encoder from my A380.

That’s not an equivalency. From written paper to typewriters and then to computers, writing has remained a product of the author. A typewriter repair shop would transition from mechanical to electronic typewriters and potentially then to computer repair. This is because it supports an evolving technology.

An author cannot transition to becoming a machine, because they cannot author what they don’t write, but a publisher can continue to publish anything that would make them money. So when human experience is boiled down to nothing more than the probabalistic order of the words written by authors who gave no consent to have their work absorbed and mutilated by an LLM, the only winner is a publishing house seeking cheaper labour than the human.

That one sounds squarely on Nvidia. Any driver that uses undocumented workarounds to gain kernel level access or utilizes an access loophool for system hooks is a bad driver. I’d assume Debian, or likely more accurately the Linux kernel itself was updated following some matter of CVE that Nvidia was quietly abusing.

Frustrating, but a good example of why those kinds of proprietary drivers are such a nightmare. You really just don’t know what techniques they’re using.