I’m using Fedora 43 Plasma under Wayland, with the regular Discord flatpak. Vesktop works, but I recall some oddly hacky things I had to do to make it work

It works and has worked for a while. Application specific sharing for audio is an oddity though, since it can’t seem to isolate and you get all desktop audio excluding discord

Interviews do typically count, it just has to be citable. Videos are sufficient in that regard as well, not just articles or books. It would be different if Torvalds had edited his own wikipedia page, but an editor who updates the page and cites this video would not be in the wrong.

I mean, I feel like he outright confirms it in the video. It’s his distro of choice since it allows him to easily use his own compiled kernels in testing. Anything else is an inconvenience to his work.

How’s the overall health of the drives? You might want to get a quick SMART report.

Otherwise, this sounds like pretty normal drive activity. It could be the result of anything from indexing tools to casual background processes doing a read.

If it’s periodic in a way that’s consistent, then it’s almost definitely something in software. What docker services are you running? Do you have any auditing tools or security processes that might be actively logging activity?

It’s pretty unlikely you’ve contracted malware unless you’ve gone out of your way to expose the server to outside sources, so I think you can alay those concerns.

If this is based on the GamersNexus videos, those are pretty absurd hit pieces that seemed to come from some bizarre place of resentment. They’ve had process issues when it comes to how they benchmark hardware, but never anything paid or purposefully misleading.

I’m honestly wondering if you’ve confused it with something else.

Brother you have eaten the onion

Something KDE has done seems to have resolved the issues I used to have with DPI related scaling problems in Wayland. Once Plasma 6 hit, it’s been nothing but rapid improvements with Wayland as a focus and man does it feel nice.

That said, there’s virtually no downside to still using X unless you have explicit display features you need from Wayland like HDR or the per-display scaling. Xfce is stupid lightweight and still my default for anything where battery life is a benefit.

That’s not really fair, I think. Smaller organizations are especially dispositioned here. Think small businesses, charities, local municipal services, etc. Small IT budgets, low staff (if any) and just enough to pad out a subscription cost to a service provider that fits their needs.

AWS is an incredibly low cost solution, and it’s probably where most of these low cost services point themselves at when building platforms at scale. Not everyone can build and maintain a datacentre or home server for their every need.

This isn’t to say that there are definitely idiots who pad their resume by chanting a prayer to SaaS and boasting about having moved their company to the “cloud” via a cheap and unreliable AWS rehoster, before failing upwards though.

Using the old interface seems to yield better results there. It appears to be their newer API model that’s suffering.

In my experience, they come in waves. They come either as data centres seek to replace or renew existing drives, but as a result, there aren’t as many lower capacity drives available. Lately, I’ve only seen 10+TB drives under a recertified banner, though you can find lower capacity drives that are “refurbished” instead. They will have the power-on hours to match though, as these are the refuse from those sorts of drive replacements.

You may find better luck with local used marketplaces if you only need cheap storage. Otherwise, they do seem less common if you don’t need large capacity drives.

Fair enough. I missed this push amidst every other AI related enshittification tactict at the time I guess. That said, this is how it should work. An organization proposes a change and the change is withdrawn or halted after the userbase is able to weigh in. I’m pleased that they didn’t barrel ahead with it despite the outcry.

I feel for the Wikimedia foundation right now. They’re under mounting pressure to compete with corporations that hold a monopoly on how people access their sites and subsequently the information on them. The goal is to provide open information, but that information is no less open to the AI that aims to scrape, rehost, and re-use the work of individuals who have volunteered their time to it.

I think it would have been easy for them to effectively do what Reddit did, and lock down the access to the site and its content in order to develop their own AI tools to perform similar tasks trained on their dataset exclusively. Instead, they’ve listened and I hope they continue to listen to their dedicated members who believe in the foundation’s original goals.

Not all AI use is bad, and it sounds to me like you didn’t read that article itself. They have no desire or intention to use AI in a way that directly effects the information on the site, how it’s presented to visitors or to use it in a way that would manipulate how articles are edited.

The only potential note is translation, but translation is such a massive undertaking that by providing a means to discuss and interact between languages, the information becomes more broadly available and open to correction as needed by native speakers.

Also, Britannica does employ the use of AI within their own system as well, even providing a chatbot by which to ask questions and search for information. It is, in this way, more involved than Wikipedia’s goals.

Echoing the sentiment of the other commenter. A link would be great!

To add, Apple has actually been making amends regarding repairability. It’s small steps, but leagues ahead of what’s offered for popular android manufacturers, while still maintaining their IP68 ratings on most devices.

I can’t speak to how they make their parts available to third parties (seems to be a grey area), but there has been a reasonable focus with the last couple generations of iPhones that ensures the device can be repaired from either side.

Overall, the tide seems to have shifted. If you’re going to be at the mercy of a corporate giant in order to keep up with modernity, then Apple is currently holding the dimly lit torch of consumer rights.

The crazy part is this may make iOS the better alternative when considering the emergence of third-party app stores and Apple’s loosening grip on their ecosystem.

LineageOS is still a good option too, for anyone who would prefer to keep the phone they have

I’m not sure about the coins but I’ve been using it for a few months now and have been thoroughly enjoying the service. I think the coins are literally just their store wallet, and whether you keep some store credit there or not doesn’t matter. It’s equivalent to buying an iTunes gift card or something. You can just pay for whatever you want outright.

I’m going to assume you’re looking for a solution in a personal context, not organizational so I won’t suggest local group policy.

Instead, I’d recommend removing the msstore source from “Winget”. The Microsoft Store uses this source to push updated for installed third party applications. It may not solve the issue entirely, but I find that as Microsoft expands the use of winget as a package manager for Windows (especially Windows 11), the store itself seems to use it for update provisioning.

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.