Code and data for arewedecentralizedyet.online and related projects
Update after having conversations with people about this
+9
-6
+9
-6
BIndex.md
+9
-6
BIndex.md
···
142
142
143
143
* The number of entities that have to agree in order to get something on the
144
144
blocklist; in general, given the blocklists I am aware of, this is usually
145
-
the admins of n instances deciding to block the instance
145
+
the admins of n instances deciding to block the instance. For the blocklists
146
+
I've found that appear to be widely used, this number seems to be 10 or
147
+
more
146
148
* The number of instances that subscribe to these blocklists
147
149
148
150
To the best of my knowledge, the shared blocklists that do exist are at the
···
172
174
* PDS: A PDS can refuse to talk to a relay or an AppView
173
175
* Relay: A relay can refuse to include data from a particular DID or PDS
174
176
* AppViews: An AppView can refuse to include a particular DID; it can also refuse to contact a particular PDS. It is not clear to me at this time whether AppViews talk to only one relay; if they can talk to many, then blocking an individual relay is possible
177
+
* The PLC for did:plc; we might consider 'strong' and 'weak' hypothetical models here in the which we assume the PLC to be a truly neutral service that never under any circumstances ever blocks lookup of a DID, and a model under which it can (which is possible but maybe we can assume it won't)
175
178
176
179
Some questions I have that I don't the answers to:
177
-
178
-
It is not clear to me whether PLC would itself be considered a location where
179
-
blocking can occur: eg. if the PLC can refuse to interoperate with specific
180
-
relays, AppViews, etc. It is also unclear to me at this point whether it is
181
-
possible for there to be more than one PLC in practice.
182
180
183
181
Let's say that we have bluesky and blacksky, and each runs their own,
184
182
independent set of all services in the blocking list above. If bluesky blocks a
···
188
186
had to have somehow opted-in to blacksy's relay? If a bluesky user wants to
189
187
interact with a blacksky user who has been blocked from bluesky, does the bluesky
190
188
user need to use an appview not controlled by bluesky?
189
+
190
+
If a entity has an open, transparent, and truly independent process at the
191
+
blocking level, perhaps we can count it as more than one; eg. if you have
192
+
internal moderation, plus an external independent appeals board with binding
193
+
decisions, perhaps that can count as two in the B-Index, not one.
191
194
192
195
Note that bluesky's stackable moderation (labellers) and feeds are out of scope
193
196
for the B-Index, as they are not exactly blocking mechanisms; they are positive