akm.longyap.name.my usual stuff, actually asked to be added to the blocklist


re: fediblock 

@host Is there just one 'federation' in Mastadon?

re: fediblock 

@StuffByBez @host

The Fediverse is bigger than just Mastodon, so it's more the other way around. :)

The way I understand it, there is one fediverse and Mastodon instances effectively are connected to a subset of it (primarily by blocking out the bits they don't want to interact with). In principle groups of instances could form their own separate federation groupings, but I don't know to what extent that happens (if at all).

re: fediblock 

@StuffByBez @host
I hope you don't mind me answering on this sort of thing - I'm kinda testing my understanding and very much open to being corrected.

re: fediblock 

@harperrob @StuffByBez I very much appreciated you jumping in, and I you are correct.

I'll have a go at answering is there 1 federation?

Conceptually: yes.
Practically: yes but it is a complex picture.

So the fediverse is made of software that speak different protocols, so not all software speak to all the software.

If yoir software can only do OSstatus, you will not see stuff from software that only ActivityPub.
Mastodon support both the above


re: fediblock 

@harperrob @StuffByBez beside the protocol aspect, there is the values aspect.

At the begining, the fediverse was not that complex, and very much some open source people and some nazi, with a sizeable overlap.

Mastodon arrived and eventually added more protocol. It was driven by minorities and other people that were getting shadowbaned etc. from birdsite and also open source people.

The moderation tool such as blocking instances allowed admin to make value based judgment.


re: fediblock 

@harperrob @StuffByBez that values/ethics is still a hot topic.

In the past blocking instances was just hidding stuff. So a blocked nazi instance would still see the content, comment and reply, just the blocking instance(s) wouldn't see it

Of course it is not what is needed.
Eventually an authorized fetch option was introduced so blocked instances would get no data at all, stoping them from seeing and interacting at all.


re: fediblock 

@harperrob @StuffByBez now, with the (very crude) capacity to block, it is not an every one talk to everyone scenario.

It is now looking more like clusters, of very close instances, and some link between big instances, mostly because they get more connection to more other instances by virtue of having more people.

So 1 fediverse, many protocol, and many cluster that continue to define themselves as time goes on.

Is this helpful?


re: fediblock 

@host @harperrob Thank you for the explanations.

Sign in to participate in the conversation
Tabletop Social

We are an inclusive Mastodon community for everything tabletop (and more).