![](https://slrpnk.net/pictrs/image/488cd980-b7a8-40c2-870f-7af8ec40eff4.jpeg)
![](https://lemmy.ml/pictrs/image/q98XK4sKtw.png)
Installing Linux on most hardware became really easy maybe 5 years ago.
Admin on the slrpnk.net Lemmy instance.
He/Him or what ever you feel like.
XMPP: povoq@slrpnk.net
Avatar is an image of a baby octopus.
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.
Lead acid can boil over and fill a badly ventilated room with flammable hydrogen and other toxic gasses.
A well maintained LiFePO4 battery that some modern UPS use it probably less risky, but I think the risk for both is very low.
Well I guess !climate@slrpnk.net !energy@slrpnk.net and !technology@slrpnk.net are already quite well known.
!balconygardening@slrpnk.net and !inperson@slrpnk.net are kinda cool as well. In general have a look at our community list, we have some good ones that are at least reasonably active.
There is a special .iso archive for all past releases.
Yes, don’t expose Windows to the internet 😒
https://opnsense.org/ is a good system if you want an easy to install and open-source firewall.
Edit: no need to buy their official hardware. Any x86 system with two network ports will do.
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).
The historical Nazi Germany was actually quite supportive of zionist efforts and interestingly the reverse was also true for some time before the holocaust got into full swing.
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.
If you can install a second gigabit NIC into the optiplex it can work very nicely with OPNSense as the main gateway. Then you can connect the LAN side to a simple un-managed switch and branch out to anything further from there.
Edit: OpenWRT is a bit of a pain to manage on x86, so I would try to avoid it for that.
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.
They have been talking about how creators want to own their platform and I could imagine that they don’t mind allowing a few such people to migrate off Threads to facilitate that. In the end what matters to them is that the large audience stays on their platform where they can serve them personalized advertisements.
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.
Nothing specifically, just nice improvements cumulating over the years.