Notices by Pieselpriemel (pieselpriemel@mastodon.de)

@jwildeboer What is unpopular about that opinion?

@tokyo_0 You say, we need a shared user mute list for .social? 😁

@tokyo_0 If something is written 8 times it's surely 8 times more convincing. :blobcat0_0:

@Foto_Graf
Das weis ich jetzt leider auch nicht.

@dansup is import from IG currently disabled on pixelfed.social for all users or just for this one?

@tokyo_0 @nm
As long as there is no list of instances that have Authorized Fetch activated I am fine with both approaches.
I guess it's not feasible from nodeinfo but maybe a instance could be setup that tries to unauthorized fetch a post from an instance and returns the status for that instance. 🤔

@tokyo_0 @jdp23 @foucaultwelles @arthunter @smitten Gargrons statement is missleading in the same way as the Mastodon User Interface is. There is no user level domain block. A user can only mute a whole instance.

@jdp23 @foucaultwelles @arthunter @smitten
cc @tokyo_0

Well, never trust no one.
I am totally confinced now. User level domain blocks are in fact only mutes. AF affects admin level domain blocks and user level blocks of other users.

https://universeodon.com/@deepfedi/111601813760539279

https://mastodon.social/@deepfedi/111601888467326795

@arthunter @smitten @jdp23
I tested it with two accounts and a friend in the middle. I 'blocked' the instance of the other account. The friend boosted a post of my main account and I could see it and comment under it with my test account. It is just muting and remove follows of an instance.

Tusky-App i.e. names it the right way.

@jdp23
AFAIK that is not depending on AUTHORIZED_FETCH
As a user you can only mute a whole instance. The nameing in the Mastodon UI is misleading. Note the headline.
https://docs.joinmastodon.org/user/moderating/#block-domain

@folkerschamel @tokyo_0 @Gargron @tay
https://hub.sunny.garden/2023/06/28/what-does-authorized_fetch-actually-do/