→ @[email protected]

SO JUST A PSA FOR EVERYONE

BE CAREFUL WHAT YOU POST - TREAT IT LIKE IT IS PERMANENT

"Oh but there's a delete button."

INSTANCES DON'T HAVE TO OBEY IT.

UNLESS YOU KNOW 100% OF YOUR FOLLOWERS AND TRUST THEM TO HONOUR IT, ASSUME IT'S PERMANENT

A HACKED INSTANCE CAN IGNORE THE DELETE REQUEST AND ARCHIVE IT.

IT CAN BE USED AS BLACKMAIL AGAINST YOU OR SOMETHING FUCKO LIKE THAT.

Apr 18, 2017 at 4:02amWeb
Show thread🌈 A. Wilcox delicatelyApr 18, 2017

@Elizafox it is permanent.

Sites like archive.is have proven this. They even have some secret mod-only Reddit posts. And those are fairly provable, unlike screenshots.

Show threadUncommon Raven (Corvus stultissimus)Apr 18, 2017
@awilfox @Elizafox how did they get there?
Show thread🌈 A. Wilcox delicatelyApr 18, 2017
@luciferMysticus @Elizafox a mod would have to leak them.
Show threadUncommon Raven (Corvus stultissimus)Apr 18, 2017
@awilfox @Elizafox hmm
Show threadChris OApr 18, 2017
@Elizafox I wonder if it makes any practical difference, as you can use birdsite API to archive posts, and many people do
Show threadConrad PankoffApr 18, 2017
@Elizafox yup, this is totally correct. I was actually confused by the delete messages that I was getting at the start - didn't realise there was even provision for it in the protocol. It's probably useful to think of it more as a fix for "oops I made a typo" than "oops I posted something sensitive".
Show threadArchaemeApr 18, 2017
@deoxxa @elizafox Also worth noting GS doesn't properly handle delete requests from Mastodon and vice versa.
Show threadConrad PankoffApr 18, 2017
@archaeme @Elizafox yeah, it's tricky. I'm yet to read about the logic involved there. Presumably it's just "purge object with id ...", but there's a bunch of validation you'd want to do around that. Understandable that it might be a bit flimsy between different implementations.