Rather than running a Tor relay, running a simple Tor bridge (e.g. via the browser add-on Snowflake as suggested by @[email protected]) is probably the best thing to do with one’s home hardware.

Actual relays must suffice certain requirements, according to the Tor project:

Requirements for Tor relays depend on the type of relay and the bandwidth they provide. ==== Bandwidth and Connections ====

A non-exit relay should be able to handle at least 7000 concurrent connections. This can overwhelm consumer-level routers. If you run the Tor relay from a server (virtual or dedicated) in a data center you will be fine. If you run it behind a consumer-level router at home you will have to try and see if your home router can handle it or if it starts failing. Fast exit relays (>=100 Mbit/s) usually have to handle a lot more concurrent connections (>100k).

It is recommended that a relay have at least 16 Mbit/s (Mbps) upload bandwidth and 16 Mbit/s (Mbps) download bandwidth available for Tor. More is better. The minimum requirements for a relay are 10 Mbit/s (Mbps). If you have less than 10 Mbit/s but at least 1 Mbit/s we recommend you run a [/wiki/doc/PluggableTransports/obfs4proxy bridge with obfs4 support]. If you do not know your bandwidth you can use http://beta.speedtest.net/ to measure it.

As for exit relays aka exit nodes, the obligatory advice is of course to not run them at all unless you know exactly what you are doing both legally and technically, and probably only if you’re a foundation or something.

There are word filters for Lemmy?

Matrix/Element

Some local libraries (e.g. in Heidelberg) or ecological initiatives lend devices to measure electricity consumption at the power plug. In particular, this is useful to measure other appliances as well.

Specifically for computers, they probably have some means to tell you their own consumption, but they may not be accurate or complete and will most certainly omit any peripherals, e.g. external hard drives.

Yeah, the Android alternatives I have in mind are LineageOS, GrapheneOS and /e/OS, but I’m not sure on how good their privacy is. Most importantly though, they’re often not available for older/non-mainstream smartphones.

So policy-wise, a useful step could be to get wider standardization of smartphone hardware, to reduce the efforts needed to port alternative OSs there.

Thank you, that’s very insightful and useful.