@r000t That's an oof π―. I wonder what the thinking was behind that decision
@terryenglish Remember, Mastodon's developers put all of their effort into **enforcing** suspensions, bans and the like. They put zero effort into lifting them.
And bugs related to that (I've run into two huge ones now) sit undiscovered for years, because no Mastodon admin would ever *lift* a suspension.
@terryenglish @r000t that doesnt mean that it goes away *forever*. it just means that instances dont spend time trying to connect to dead servers. theyll happily start talking and youll "rejoin" the fediverse if the server goes live again. servers talk both ways. they both request and push. theyll just stop pushing from servers that stop answering is all.
@wagesj45 @terryenglish Nope. I literally tested this. Neither machine would so much as create a delivery job, even when explicitly told to do so by sending DMs between each other.
@r000t sounds like a bug then
@r000t @terryenglish I need to learn Elixir to fix that. Does it at least have an issue?
@terryenglish Software.
The software, by default, won't talk to a server it hasn't seen in a week. It will start talking again when it hears from the remote server.
Which is following the exact same logic.