Don't you think it's a bit hypocritical to complain about mastodon.social cutting itself off when you've cut the nostr bridge off on the instance you admin (calckey.social) something even mastodon.social *hasn't* done?
nostr:npub1cdak4q4f3h3k3sgyh0rd5dj4w8k95f3mquzh6z3ew76vqkh60e3slyczgz What's this post in regards to?
Discussion
nostr:npub1grd6pp385tevd8psx9nxzjd4vutg7pycjj49cs3q8gujpg77sjps4752zz nostr:npub1cdak4q4f3h3k3sgyh0rd5dj4w8k95f3mquzh6z3ew76vqkh60e3slyczgz While Nostr isn't something that I, personally, have a problem with -- it's just a protocol -- the fellow who admins mostr.pub is not welcome in our community.
I understand that Alex isn't everyone's cup of tea but this is the sort of thing that should really be taken care of with individual defederations rather than instance/ bridge defeds. It's totally understandable that many users may not want to communicate with us for ideological or even aesthetic reasons due to the slightly offputting user id's, but it's better to empower the end user which calckey, like most other sw allows, leaving you to just worry about defedding csam, ddos and forkbomb instances.
lol i did not know about all this, i guess you guys are not gonna use bluesky bridge if #[4] made it