For all the #Mastodon #selfhosting folks out there, any idea what I should be looking at as far as backoff timers or whatever from other instances coming back down, after something like a week of downtime?

[north@xn--8r9a.com]

For all the #Mastodon #selfhosting folks out there, any idea what I should be looking at as far as backoff timers or whatever from other instances coming back down, after something like a week of downtime? Several instances, most notably infosec.exchange, still haven't been sending me new messages, some 18 hours later.

I didn't even get one when I tagged myself in a new post - https://infosec.exchange/@north/116199899292856762 - until I searched for it¹. Any insight maybe, @jerry ?

Curiously, Threads and brid.gy started sending me messages within about 15 minutes of coming back online. That seems bad.

¹ at that point, it became a pull, not a push

Edit: A boost from the other side does not appear to have been correctly pushed.

[jerry@infosec.exchange]

@north Mastodon stops delivery attempts after 7 days of failures. it resumes once it starts receiving messages from the remote site. Since you sent this, it should start delivering again

[north@xn--8r9a.com]

@jerry Does it have to specifically tag that instance? I sent a bunch of stuff yesterday.

[jerry@infosec.exchange]

@north I am not 100% sure. the message needs to be sent in a way that it is delivered to the instance that has stopped trying. It appears that it started again now (since we are conversing here), so maybe it does require tagging someone.