Post AW6FbEdh38MHqfoLrM by lauren@mastodon.laurenweinstein.org
(DIR) More posts by lauren@mastodon.laurenweinstein.org
(DIR) Post #AW67kCjehLC0uuMjtg by lauren@mastodon.laurenweinstein.org
2023-05-28T01:04:40Z
0 likes, 0 repeats
So it seems like there's a pretty clear enhancement needed to the #Mastodon blocking paradigm. When a remote user (or the instance a remote user is on) is blocked system-wide by a local admin, any users on that local system who currently follow that now blocked user (or any other users on a now blocked instance), should be *notified* of this action, so they can determine if they wish to stay on that local instance given the policy decision of its admin. If they aren't informed, they cannot make informed decisions, and may simply assume remote users that they follow have stopped posting.
(DIR) Post #AW6819brZYRg95nrAO by stcwhite@historians.social
2023-05-28T01:07:51Z
0 likes, 0 repeats
@lauren Bloody hell. That's absurd. Agree that a better process is needed.
(DIR) Post #AW68QGRlI0VWae3H5U by cazabon@mindly.social
2023-05-28T01:12:19Z
0 likes, 0 repeats
@lauren I sense a need for a #tool.It should retrieve a list of the people you follow, and then check their origin instances for their latest post. If it doesn't show up (within a reasonable period of time) in your feed, you've detected silent blockage.I wrote a small client using the #Mastodon API for posting my epic-length threads; most of this is easy. I don't remember seeing anything in the #API to find "messages in my feed from user X", but I wasn't looking for that either.
(DIR) Post #AW68YMkviS7UTSsfey by jab01701mid@universeodon.com
2023-05-28T01:13:42Z
0 likes, 0 repeats
@lauren This seems exactly right to me. If I followed someone from another instance, and the admin of that site had blocked that person, I'd hope #Universeodon would let me know.Got a notify today about a suspicious follower request.It's better than being at the mercy of Elon Musk, I can say that for sure.
(DIR) Post #AW68dNZg6GuUSd0Znc by lauren@mastodon.laurenweinstein.org
2023-05-28T01:14:43Z
0 likes, 0 repeats
@cazabon This should not require "checking" by a user. The user should be informed by their instance if the instance is now blocking a user that they've been following. No action by the user should be necessary to check status.
(DIR) Post #AW68pJylIGfamiR3dQ by lauren@mastodon.laurenweinstein.org
2023-05-28T01:16:51Z
0 likes, 0 repeats
@jab01701mid In fact, when my block was dropped today at that site (after I discovered the block today, months after it was imposed), I shortly thereafter today got a note from a follower there telling me he had been wondering why I "hadn't been posting." Yep.
(DIR) Post #AW6AQrTzn3M1MbVdZI by jab01701mid@universeodon.com
2023-05-28T01:19:23Z
0 likes, 0 repeats
@lauren But it does beg the question, why would someone be on an instance that blocked them ? Can't they move to another instance ?I'm not sure I completely understand, but I think we mostly agree. I don't want anyone muted, without an audit trail and notifications.
(DIR) Post #AW6AQvVYpAyzqcGwYy by lauren@mastodon.laurenweinstein.org
2023-05-28T01:34:50Z
0 likes, 0 repeats
@jab01701mid OK. Here we go. User A is on instance A. User A follows user B on instance B. Admin of instance A either system-wide blocks user B or blocks system-wide the entire instance B. User A doesn't know that this block has been put in place by their instance A admin, and assumes user B isn't posting anymore. Since user A wasn't informed of the block, they don't suspect anything is amiss, and don't realize that they might want to leave instance A.
(DIR) Post #AW6AUZW4Wzg2neFXjk by cazabon@mindly.social
2023-05-28T01:35:28Z
0 likes, 0 repeats
@lauren Oh, I agree with you 100%.I'm thinking this tool would be useful for users who aren't positive that their instance is actually giving them these "we blocked X" notifications."Trust, but verify" kind-of-thing. The question isn't "Am I paranoid?". As always, it's "Am I paranoid *enough*?"
(DIR) Post #AW6Af0R9IPAvBjvFOC by ike@pkm.social
2023-05-28T01:37:22Z
0 likes, 0 repeats
@lauren Agreed. Server-wide changes of most any sort that affect content should be published in a must-acknowledge notification.I want transparency on who was server-blocked, who my server isnt federated with, etc. Not that it is a problem for my server - we have pretty lowkey community and our admins are chill.But if my admin takes a unilateral action, I want to know it and view a changlog history of past actions. Seems like tooling tor admins should be on the Mastodon roadmap.
(DIR) Post #AW6BFXwgBnDhXR5uUq by pgcommunication@vis.social
2023-05-28T01:43:59Z
0 likes, 0 repeats
@lauren Agreed! I also deeply appreciate it when an instance publicly lists all of its blocks along with the reason for blocking (qoto.org comes to mind).
(DIR) Post #AW6BMG5wxHocCedBhY by lauren@mastodon.laurenweinstein.org
2023-05-28T01:45:14Z
0 likes, 0 repeats
@pgcommunication Right, but notifications are necessary so that relevant users on the instance are informed of new blocks that affect users they follow. Users can't be expected to keep checking that list.
(DIR) Post #AW6CIB8FZ6MfbgKELI by leadegroot@bne.social
2023-05-28T01:55:30Z
0 likes, 0 repeats
@lauren I resepctfully suggest that suggestions like this should be sent here:https://github.com/mastodon/mastodon/issuesNo value in yelling into the void :( )(by all means then post here that you've done so, so we can vote it up.)Valid call though!
(DIR) Post #AW6CZOwpS3odNXCBoe by lauren@mastodon.laurenweinstein.org
2023-05-28T01:58:47Z
0 likes, 0 repeats
@leadegroot Thanks. Frankly, I don't have the time nowadays to be pulled into the ongoing debates over such suggested changes in a formal sense. Been there, done that!
(DIR) Post #AW6DD0P47w7Wq2HuAS by breakfastmtn@calckey.social
2023-05-28T02:03:46.089Z
0 likes, 1 repeats
@lauren@mastodon.laurenweinstein.org You're in luck! It's already "planned" on the roadmap."Notify users when relationships are severed due to domain block"https://joinmastodon.org/roadmap
(DIR) Post #AW6DD1AZHK7NDMVqD2 by lauren@mastodon.laurenweinstein.org
2023-05-28T02:05:56Z
0 likes, 0 repeats
@breakfastmtn That's encouraging, but it needs to be extended to notifications when an admin blocks individuals from an instance, not just when entire instances are blocked.
(DIR) Post #AW6FVpOBV9ty5Yyjg0 by leadegroot@bne.social
2023-05-28T02:31:43Z
0 likes, 0 repeats
@lauren :nods: your choice, but nothing will happen if you only mention it here!I would suggest that your audience is broad enough here if you post the issue and then mention it here, the resulting upvote might well be enough without you doing anything further :)
(DIR) Post #AW6FbEdh38MHqfoLrM by lauren@mastodon.laurenweinstein.org
2023-05-28T02:32:44Z
0 likes, 0 repeats
@leadegroot Apparently one aspect of this is on the roadmap. Which may mean something. Or not.
(DIR) Post #AW6NtLqZmzEN35zDnc by tokyo_0@mas.to
2023-05-28T04:05:36Z
0 likes, 0 repeats
@lauren Agreed. Is there a Github issue for it? Will follow and support if so đź‘Ť
(DIR) Post #AW6OYbOgsWqN9Mc4TQ by solomon@masto.ai
2023-05-28T04:12:55Z
0 likes, 0 repeats
@lauren Could these be done in an interoperable way with other fedi implementations?
(DIR) Post #AW6OgbRKbVfdbBfBS4 by lauren@mastodon.laurenweinstein.org
2023-05-28T04:14:34Z
0 likes, 0 repeats
@solomon One would think so.
(DIR) Post #AW6gsyGFNaDZ1lWfQ0 by harriettmb@mastodon.ie
2023-05-28T07:38:20Z
0 likes, 0 repeats
@lauren Don’t the various #fediverse sites publish a lot of this information which you will see if you follow them. Ones like #feditips Then there’s people like Chris Trottier and others who provide information on how to move yourself and your followers to another instance.
(DIR) Post #AW7HmE3NxewyHg9mXA by lauren@mastodon.laurenweinstein.org
2023-05-28T14:31:52Z
0 likes, 0 repeats
@harriettmb You need to be *notified* when blocks occur that affect people you follow. Just having lists available that you have to keep checking is next to useless.