#1 items should be backups. (Well maybe #2 so that you have something to back up, but don't delete the source data until the backups are running.)
You need offsite backups, and ideally multiple locations.
This is not funny, it is mildly infuriating.
That isn't what that document says. It says that they can impersonate you in non-E2EE scenarios. The clients I use warn me when a message isn't properly encrypted so someone without E2EE keys can't impersonate someone in an E2EE room.
That being said the general concept is a problem. I would love to see progress where all events from a user are signed by a device key and non-forgable. There is some thinking about this with portable identities (such as MSC2787) where you server is basically just storing and forwarding events but the root of trust is your identity and keys that you control. But none of this will land soon, not for many years.
Probably yes, it depends on your threat model.
If you are using E2EE on a matrix.org account then your message content, attachments (images) and most other traffic isn't accessible to anyone but the people in the chat. However Matrix isn't the most private option, it has a number of leaks such as reactions and chat topics (these are being worked on but aren't close to happening).
For most people Matrix is a very private and secure option and the fact that it is federated is a huge plus. If you want something more secure you are probably looking at Signal (which you don't want to use and isn't federated) or Simplex Chat (which doesn't have multi-device support).
There are local readers, that fetch the feed directly from your device, but many use backend servers for the feed fetching. There are a handful of possible reasons:
- Cross-device syncronization.
- Save battery by checking on the server and only waking the device with a push notification when there are actually new items.
- Obey platform background activity restrictions (especially on iOS)
- Privacy by hiding your IP from the feed operators.
- Avoid missing items on busy feeds when your client goes offline by checking constantly from the server.
Yup, first-past-the-post strongly pushes two primary parties polarizing politics to just the right and left with no nuance on individual issues. Then both sides end up being corrupt anyways and doing what they want, but no reasonable parties can make their way up the ranks due to strategic voting to avoid the spoiler effect. So the crap just festers.
Ah yes, recompressing JPEG's as PNG. Gotta losslessy preserve those artifacts at triple the file size. Perfection.
I'm pretty sure every microwave just splits the input in to the last to digits as a number of seconds and the digits before that as minutes. Then runs for 60 * minutes + seconds. So 0:99 is equivalent to 1:39 and 1:80 is equivalent to 2:20. I mean it is a little weird that the seconds can be >59 and extra weird that you can do 6:66 but it isn't exactly wizardry.
Closed-source software that sends home tons of information about your system without consent. All communication accessible to a VC funded company that has huge pressure to make as much money as possible.
I've been doing this from Firefox forever...
But "with audio" is actually a new feature. Previously I was manually sending the audio through my voice channel which worked pretty well but it would be nice to have a separate stream for the streaming audio.
Probably not enough for me to install the spyware though, I'll keep using Discord via Firefox.
those disks were not spinning for maybe 3 weeks total
This is actually a good thing for longevity. Start up and stopping is the hardest part of a drive's life. So you will see more failures on a personal PC that you turn off every night than a server drive running 24/7. Laptop drives will typically fare the worst as they may be power cycled many times a day, often fully stop when idle for power saving and get shaken much more than other drives.
It would be nice if there was a shortcut to go "back to previous site". Because on one hand using back to navigate around map moves is often very convenient, but sometimes I want to go to the site before the map. Having a two-level history with page and site would be super useful.