With hardware like that the main issues are power inefficiency and (often) lack of UEFI support making it hard to install modern distros on them.

Otherwise there should be mitigations for the CPU issues, so unlikely that it will be a real issue from the security perspective.

It still seems to be under heavy discussion. see this recent article: https://netzpolitik.org/2024/eu-council-discusses-digital-euro-and-how-much-privacy-should-it-be/

I assume the end result will be more privacy preserving than current commercial offers like Visa or Mastercard, but it will be a trade-off between what commercial data-brokers will be able to see and what the central bank will be able to see. Pick your poison I guess 😒

Realistically it might also become so bureaucratic that it will see limited uptake, but specifically for GNU Taler it might make it possible for a Taler intermediatory to exchange digital Euros for tokens in your Taler wallet without having a banking license, which could help Taler adoption a lot. But I guess the latter would depend on how usable the former is. Like if it is too bureocratic, then a separate payment system based on it could thrive, but if it is easy to use, then too few people would probably see the benefit of GNU Taler as an extra step.

The one at the top could also be a connector for a serial port for debugging or so.

https://github.com/fatedier/frp seems to be designed for such cases, but I have not tried it myself.

Nothing specifically, just nice improvements cumulating over the years.

Installing Linux on most hardware became really easy maybe 5 years ago.

Gnome works quite well on a larger touch-screen. Edit: ah, Ubuntu should have that by default.

There is a special .iso archive for all past releases.

When you are actively charging the batteries off a solar panel for example, it will be even higher, up to 17V 14.5V or so I think. The automotive PicoPSUs only cost a little more and will smooth it out up to 24V I think… there are even some models that go up to 48V.

Edit: why the down-votes? Is this incorrect?

Some people want to be able to reach their server via SSH when they are not at home, but yes I agree in general that is not necessary when running a real home server.

Get a PicoPSU for automotive use (there are two varieties, one that needs stable 12v and another that can run directly off a battery with varying voltage).

Don’t leave SSH on port 22 open as there are a lot of crawlers for that, otherwise I really can’t say I share your experience, and I have been self-hosting for years.

This is nonsense. A small static website is not going to be hacked or DDOSd. You can run it off a cheap ARM single board computer on your desk, no problem at all.

Well then, your assertion that Matrix gives it freely is false.

My point is that it should never give out that data, or even store it permanently in the first place. This is just a fundamentally bad design from a privacy perspective, and other messengers don’t do that.

This is false, too. Historical event visibility is controlled by a room setting. (And if you don’t trust admins of a sensitive room to configure for privacy, then you’re going to have bigger problems, no matter what platform it’s on.)

This is not false, what you mean only hides it for normal users, but it still ends up in the database of all participating homeservers and all the admins of those have full access to it. I happen to run a Matrix homeserver myself…

Obviously you need someone joining the room for the room metadata to be shared between homeservers. But that is really only a minor barrier and once that has happened the worst case scenario takes place immediately. On other messengers (federated or not) a newly joining member has very limited access to past room metadata. Not so with Matrix, where a joining homeserver get full retroactive access to all the room metadata since the room’s creation. If you can’t see the problem with that, you really need to stop privacy LARPing 🙄

lol, why are you even posting on a privacy community then? And using Tor doesn’t help at all in that case.

Yes it is a problem for both public and private rooms as this info is stored and shared retroactively. Lets say one of the participants of a private room gets compromised or you invite someone that has their account on a compromised homeserver. This then results in the entire room meta-data history (since the room was created) being shared with that compromised homeserver which can then easily analyse it in detail.

No, because Matrix stores all this info and gives it freely to other servers retroactively(!). Also with network layer sniffing (which is anyway much harder to do) you can only see which home-server talked to with other homeserver and what clients talked to their homeserver. If you have the full room meta-data you can easily make a social graph of which account talked to whom when and where.

There is a lot more metadata than just avatars and reactions. Accounts and their room membership over time, timing of messages (and thus online times), individual interactions between specific users (based on the timing of their messages) and so on. That is all in the unencrypted metadata of a Matrix room and can’t be moved to the encrypted message part like avatars and reactions.

Like all of it. It is not a “leak” if it is working as intended.

Anyone can spin up a Matrix server, join a room with it and the Matrix network will happily push a complete copy of the room metadata (all the way back to the point the room was first created) to that new homeserver.