this post was submitted on 19 Dec 2023
227 points (91.3% liked)

Fediverse

17698 readers
3 users here now

A community dedicated to fediverse news and discussion.

Fediverse is a portmanteau of "federation" and "universe".

Getting started on Fediverse;

founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 10 points 10 months ago* (last edited 10 months ago) (14 children)

Pre-0.19 I assume you would need to be on an instance that is blocking them.

Post-0.19 you can block them as an instance, meaning "any posts from communities which are hosted on that instance are hidden"

So, the answer still varies depending on your goals for blocking.

[–] [email protected] 12 points 10 months ago (12 children)

yes, on Mastodon when a user block an instance, it's more like a mute than a block. Your posts will still be available to them, but you won't see their content.

The only solution if you want to protect your content from being shared on an instance is to block it at the instance level AND that the instance use Authorised Fetch.

Not all instances have this feature on.

[–] [email protected] 5 points 10 months ago (11 children)

Isn’t “protecting content” on a public platform kinda moot?

[–] [email protected] 1 points 10 months ago* (last edited 10 months ago) (1 children)

protecting your content from being pushed to an instance that you though your blocked.
protecting your content from being shared where you though it won't because of the way things are worded.

[–] [email protected] 1 points 10 months ago (1 children)

And what’s stopping these people and these instances from spreading that content using just the publicly available link? Instead of just clicking “share” they’ll have to open an anonymous browser window and copy paste the link from there, the horror!

[–] [email protected] 1 points 10 months ago* (last edited 10 months ago) (1 children)

define these people. define these instances. etc etc

what's your point? anyone can do a screen shot and share it too.

if you want to have a conversation about the content of my post, please keep it on topic : without authorised fetch and a domain blocked at the instance level, the content is pushed.

if you have technical knowledge to add to this or can correct me about the protocol I'm glad to hear it. if not I'm not interested.

[–] [email protected] 1 points 10 months ago

That was exactly my point. Blocking instances because “that way my content can’t be seen there” doesn’t make sense, because it’s trivial to bypass it. Yes, even a screenshot will do the job if nothing else, so why talk about protocols in the first place?

Somebody (maybe you maybe not, can’t check while replying) said that blocking instances was useful so that “my content doesn’t get seen / shared / pushed / etc to people and instances I don’t want”. That doesn’t make sense because of the line above. If you need clarification on who are those people and what are those instances ask them, not me.

I hope I’m somehow conveying my message. If there is a subtlety in the subject that I didn’t catch feel free to help me understand.

load more comments (9 replies)
load more comments (9 replies)
load more comments (10 replies)