Follow

This (accidental, temporary) blocking also hit me. It even cut me off from my spouse! (Fortunately, she's right across the breakfast table.)

Is there any way to reconnect (or even enumerate) these severed connections? Nobody on either end was notified.

@trinsec @freemo @stux
QT: qoto.org/@trinsec/110264801634

Trinsec @Qoto  
Always fun to see the side-effect of a server-wide suspension. :P mstdn.social blocked qoto.org for a bit, so everybody from there that I was follo...

@peterdrake

Sadly no, as you've noticed even accidental suspensions cause harm to the users of both instances.

@trinsec @stux

@freemo @peterdrake

Qoto has a little workaround where you can 'keep' those connections from your end. Follow _and_ subscribe to them. If there's a brief (accidental) suspension, you're still seeing them via subscription. They won't be following you anymore, of course. But at least you could see who you're not following anymore (as the follow icon won't be colored).

I'm contemplating doing that to all I follow. :P You won't be seeing stuff double or anything that I've seen.

@trinsec @freemo I don't suppose there's a way to do this in bulk, or at least without individually opening the profile of each of the hundreds of people I follow.

@peterdrake you could script it using Mastodon.py. First you’ll need an instance of the Mastodon class set up with your credentials - mine is called qoto in the below snippet. Then loop over your followers, get each’s id, and call the following internal function (since Mastodon.py doesn’t know about QOTO’s nonstandard subscribe feature):

qoto._Mastodon__api_request('POST', f'/api/v1/accounts/{id}/subscribe').

@peterdrake I did it manually. But the way I did it was going to my profile, click on 'Following', and then just click on the subscribe buttons of everyone in that list down there (except those on Qoto, I skip those as that's not necessary, unless Freemo manages to fuck up something royally with this codebase. :D)

@freemo

@peterdrake @trinsec @freemo @stux The only thing you can do to really is make sure to join an instance that does its best to not perform unnecessary instance blocks. That's the #1 thing I look for in new instances.

@freemo @peterdrake @trinsec @stux Instances that rarely block tend also not to block other instances accidentally

@realcaseyrollins @peterdrake @trinsec @stux

Yes but the issue isnt that QOTO accidentally blocked someone.. the issue was someone accidentally blocked us. So even though QOTO doesnt block at all it is still an issue for us.

@freemo @realcaseyrollins@social.freetalklive.com @peterdrake @trinsec Yup.. it creates a lot of mess.. :sadlinux:

Working on the solution to not let it happen again :blobcatgiggle:

Yes, maintain your own node. The fediverse is built for owner operators who are tired of all sorts of agenda by control freaks.
Why would you and your spouse be on different instances, unless you don't talk to eachother?

@Corfiot

QOTO is a STEM-exclusive instance. Its common for people to be on here and separate from their friends or family on other instances.

@stux @peterdrake @trinsec

@Corfiot @stux @freemo @trinsec I got onto Mastodon significantly earlier than her. When we both left the birdsite after Elongate, she picked a different instance.

Sign in to participate in the conversation
Qoto Mastodon

QOTO: Question Others to Teach Ourselves
An inclusive, Academic Freedom, instance
All cultures welcome.
Hate speech and harassment strictly forbidden.