LinuxSBC

No, they know that a message has been received, but the phone is what decrypts the message. Beeper can't see it.

No. This is much more impressive, useful, secure, and sustainable because it's totally different internally.

The app itself is closed-source, but they use PyPush, which also has a blog post explaining how it works.

The problem is that breaking it will also break a lot of Apple devices.

That's a good point.

I like bottom right the most, but it does't really feel like a default wallpaper as much as top left. Middle right feels like part of a tiling WM with custom colors more than a default for a DE.

Why does him being rich mean that his opinion on LLMs is invalid? If anything, LLMs require such vast amounts of money that he has more experience in that area because of his riches, not less.

First, they do have senses. For example, many LLMs can "see" images. Second, they're actually pretty good at describing things. What they're really bad at is analysis and logic, which is not related to senses at all.

Think of it like email. You need a client (like Gmail or Outlook), which for Matrix is usually Element, Schildichat (a fork of Element), or Fluffychat. You also need a server (like gmail.com). The most popular one is matrix.org, though it doesn't have any bridges. To get bridges, you either need to run your own server (much easier than it sounds with this) or use a server with bridges built in. Bridges are tied to the server. You also get an address, of the form @name:example.com, where example.com is the homeserver.

If you want to do it the easy (but slightly proprietary) way, Beeper is basically commercialized Matrix with preinstalled bridges and a slightly better UI. Some of their stuff is proprietary, but they contribute a lot to FOSS (several bridges I use are by them), and most of the internals are FOSS.

People try to upload CP and get the admin arrested for hosting it.

Yeah, MacOS wasn't originally intended for x86 CPUs.

He's pretty much the quintessential QA tester. He wants to do things his way, regardless of whether or not the OS wants him to do that. He's usually skilled enough to fix anything he messes up, but he doesn't know enough about Linux to do that, so he ends up breaking things. I feel like most people have a better experience than he did, but his technique uncovered a ton of bugs and usability issues that significantly improved the Linux desktop to have fixed.