Step 1 in keeping communications private:

Don't send them to people for whom they are not intended.

"If Mastodon sends you a message you shouldn't get, it's your fault if you accept and federate it"


How about... no.

@maiyannah It's common sense to make sure it doesn't end up in the wrong place at all costs, even if it means the recepient isn't able to recieve it due to incompatibilites.  The implementation is a massive fail.

I don't think any of the devs working on it actually has taken the time and effort to set up some way to test compatibility with other servers.  A lot of these issues would be glaringly obvious to them if that was the case.

@archaeme @maiyannah Deliver securely > Fail gracefully > Fail ungracefully > Fail silently > Just deliver DMs to anyone, man, who cares?

In terms of outcomes, this is the worst one.

@archaeme @maiyannah There was obviously no care put so that it would fall down on the other steps along the way.

@guizzy @maiyannah Even if it just concerns Mastodon instances only, its not like an admin is prevented from simply ignoring the flags.  The code is right there.

@archaeme The magic envelope date is literally never seen by GNU social.  They chose a method to operate it entirely out of band from ostatus.  I told them this was a bad idea, but no one listened.  They never do.