Yes, or like we saw in the demo, someone’s arm disappears, a ball becomes a blurry shapeless blob, and many others.

This tech is the same tech that powers other ““Generative AI””, meaning exact the issues with asking for a hand and getting one with 7.5 fingers can now happen in real time, in video games supporting DLSS 5.

It is straight up an AI slop filter over top of a game. There’s not much more to say about it.

The exact numbers for when it messes something up, but keeps running, are unknown and highly ubpredictable.

According to above post, about 10% of firefox crashes (more numbers found in the post) are caused by this stuff. It’s not unreasonable to say those crashes could’ve had the bitflip happen on content instead, changing maybe a character on the page or something.

Note that it’s not 10% of users, as that’s reslly hard to figure out. Someone with bad RAM will likely crash more often.

Simple stuff like a calculator can be just as broken by a bitflip as more complex things. You wouldn’t want your calculator to say 1 + 1 = 2049.

If you want to rely on your computer, ECC RAM is required.

I use whatsapp for communicating with a few groups of people who are refusing to switch over. I’m not getting them to move, they’re a mix of tech illiterate, ignorant, or just unwilling. These groups have important annoucements in them, that I’m unable to receive any other way. Sometimes there’s just no way around services like these.

I do my best to protect myself (no proprietary facebook code ever runs on my main device), and keep personal information I provide to a minimum (as I don’t trust Facebook’s E2EE claims). There’s not much more I can do besides not receiving important announcements.

There’s always the option of gathering device info first, then using the appropriate driver. Either the SSD is in a “known supported models” list, or it reports support for whatever feature the new driver needs.

It’s technically possible that straight up trying an unsupported driver can cause physical damage, but this can be avoided by carefully selecting the driver. From MS pov, they’d have to extensively test this driver on a bunch of SSDs and configurations, but it would lead to a performance improvement.

And obviously, there’s been no possible way to try loading the modern driver and if that fails, falling back to the legacy one.

This is once again Microsoft refusing to improve performance, because that doesn’t directly increase profits.

This used to be an issue, but has been resolved in most major applications. Are you on an “app” version of slack? Try updating it, or try using an up to date webbrowser like Firefox, or anything based on Chromium if you prefer.

I’m going to assume you’re unable to see the embedded image. I didn’t add alt text, that’s my mistake.

Below “Besides”, there is a screenshot of a tweet by user @haydendevs stating “this is who you’re arguing with online” and an attached image of a series of dots connected by lines. This is the (overused) visual representation of a “neural network” in machine learning. The meaning of the image in this context is to state you are arguing with bots or AI online. I used this twitter screenshot as an attempt to make a joke of the fact the OP reads like AI-generated text.

I will edit the alt text in my comment above.

MPV is great, I use it all the time. It’s fully replaced VLC on my desktop.

It is not an “alternative to Jellyfin”. It does not offer many “comfort features” like (synced ootb) watch tracking. It does not transcode at all, and it doesn’t even run on devices that need transcoding most, like smart TVs.

These two applications fall into two different categories, and they will never replace each other. One is a media player, you throw mpv any video file, it puts it up on screen, great. The other is a media server, it allows you to sign in, browse your nicely organized library, and click play on the movie of your choice, very cool.

Even the idea of opening SMB or NFS to the entire internet just so your most technical of friends can manually download and watch a movie is insane compared to setting up Jellyfin. Reminder, not everyone has the connection to stream a full 4k bluray rip, transcoding allows those users to watch at all.

Besides,

With a custom, very restrictive license. Builds are not reproducible, and code from the project cannot be used elsewhere. For the purposes of security, transparency, and advancing development of (proper) FOSS YouTube clients, Grayjay is effectively closed source.

There is no justification. The “Ends” in E2EE mean the initial sender, and intended recipient. The “transport” should have zero insight into the content. Encrypting a message to the servers is standard even for “non-private” messaging services, it’s usually done with SSL (part of HTTPS).

Lets compare it to traditional mail. If you send something, the postal company can always just open your mail and read it. With computers, we have black magic (E2EE) that physically prevents the postal company from doing that. In this hypothetical, Facebook (owner of WhatsApp) is the company that provides you with the pen and paper (the app), and is a postal company (their servers). They promise that the black magic on the paper prevents them from reading what you wrote, but then they clearly read the content of your letter to send you a summary of the conversation.

Mid-message quick edit: They could’ve also done something to the pen (other parts of the app) to have it tell them what you wrote. This would mean the black magic (E2EE) is applied, but is completely useless. (End of edit)

If the process for making the pen and paper (the app) was publicly known (open source), you could make your own, and be sure the black magic (E2EE) is applied properly. That way you can be certain the postal company (servers) can’t read your letter, only the recipient can.

If the postal company gives you the pen and paper without telling you how to make it, it’s nearly impossible to tell if the black magic was applied properly.

The concept of “End to End Encryption” (E2EE) is that one end encrypts the data, it passes through transport, and the only person who can read the decrypted data is the intended receiver.

In the case of WhatsApp, this should mean:

• Your phone (WhatsApp app) encrypts a message
• Your phone sends the encrypted (“unreadable”) message to Facebook
• Facebook sends the message to the intended receiver
• The receiver decrypts the message

The whole “Meta AI summaries” thing has to run on their servers. Large language models small enough to fit on a phone don’t produce sensible output yet, and your phones battery would drain very quickly. Since each message is (supposed to be) encrypted with different keys, no human nor computer can make sense of the encrypted data without the keys to decrypt it. For their servers to provide a “summary of your chats”, they have to be able to read the content of the messages. Thus proving that the whole “end to end encryption” in WhatsApp is either false, or made entirely useless with them sending all messages to themselves without E2EE.

The only proof that would invalidate this is evidence of the LLM running locally on device. Even then, the way some of WhatsApp’s services work (like notifications, WhatsApp Web) creates some serious doubt on the “E2EE” claim.

It is absolutely essential that any communications platform claiming “E2EE” proves this by making the client-side code (the stuff running on your device) fully open source. A proprietary app, like WhatsApp, by definition makes it harder to fully understand its inner workings, and thus fully verify the E2EE claim.

It’s actually not within their rights (I am NOT a lawyer)

GPL code is still owned by the person who wrote it, that includes contributors who have made a PR. Unless they all signed CLAs (Contributor License Agreements) to hand over their copyright to the repository owner, the repository owner does not hold copyright for this code, and as such can’t legally change the license. They can use and distribute it as specified in the license terms of the GPL, but that excludes changing the license.

Surely there wasn’t an exploit on the half a year out of date kernel (Article screenshots from April 2025, uname kernel release from a CBL-Mariner released September 3rd 2024).

transmitting over 125,000 gigabytes of data per second over 1,120 miles (1,802 kilometers).

Please include usable metrics in the title

XMPP is significantly less decentralized, allowing them to “”“cut corners”“” compared to Matrix protocol implementation, and scale significantly better. (In heavy quotes, as XMPP isn’t really cutting corners, but true decentralization requires more work to achieve seemingly “the same result”)

An XMPP or IRC channel with a few thousand users is no problem, wheras Matrix can have problems with that. On the other hand, any one Matrix homeserver going down does not impact users that aren’t specifically on that homeserver, whereas XMPP is centralized enough that it can take down a whole channel.

Meanwhile IRC is a 90s protocol that doesn’t make any sense in the modern world of mainly mobile devices.

XMPP also doesn’t change much, the last proper addition to the protocol (from what I can tell, on the website) was 2024-08-30 https://xmpp.org/extensions/xep-0004.html

Why the downvotes? Apple silicon ARM is not the same ISA as any existing ARM. There’s extra undocumented instructions and features. Unless you want to reverse engineer all that, and make your own ARM CPU, you cannot run (all of) macOS on an off the shelf ARM chip. Making it effectively “impossible”.

I own a OnePlus 6 with postmarketOS. My daily driver is a Pixel 7 with CalyxOS and microg turned off.

Despite having effectively only FOSS apps on my Android daily driver, I can’t daily drive postmarketOS. It’s making great progress, but isn’t nearly stable enough as a modern smartphone, and several other issues hold it back;

• Sleep states. Currently you get to choose between your phone going to sleep (~ a day battery life) but without notifications, incoming calls, alarms, etc. Or your phone “staying awake”, where you’ll have those features but only ~4 hours battery.
• Hardware video decoding, which “can work” but only in select apps, and they’re not great for mobile.
• Audio issues, such as no audio from the earpiece, microphone not working, or no audio at all.

If you rely on non-foss Android apps, there is Waydroid, but it’s not a perfect solution and might have issues.

It’s not a “waste of money” if you want a device to experiment or tinker with, or if you want to follow progress of Linux mobile, but it is extremely unlikely to replace your daily driver.

Mint under the hood is still Linux, but for basic tasks like webbrowsing, it’s very similar to or easier than Windows.