a) Hardware/software failure
b) Accidental SQL modifications
If you care about a), you can do streaming replication to another Postgres server, so you get a near-real-time backup. However, if a wrong DELETE or UPDATE happens (b), it doesn't help
That's what periodic DB dumps help with
Streaming replication is kinda hard to setup tho, a bit of an arcane area of Postgres imo
@Hascobe @angristan @Chocobozzz Yo, on Mastodon, you get a thumbnail preview and a "play" button. Only upon clicking the "play" button any content is loaded from the original server. So when you click on it, without autoplay, you see a 2nd "play" button, this time from the original server. That's why autoplay is useful in this case. To skip the second button. Discord and Twitter also do this.
Downloaded archive of all FB activity from 2007-now. Surprised to see SMS and voice logs! Massive metadata. Fuck this. Script is now wiping all FB posts older than 90 days.
@Technowix @TheKinrar @slipstream @marsxyz Okay, so I think the thing here is... If it was a peertube embed, anybody could keep the page open and with some JS magic (or wireshark) know exactly which IP addresses (so how many people and where from) are visiting joinmastodon.org. So it's like analytics for everybody instead of analytics just for google. I think that is more dangerous in this case.