tags.pub has unsubscribed from all open relays.
-
tags.pub has unsubscribed from all open relays. Evan recognises there's a mismatch of expectations on what Relay 2 relay, R2R connections should be like.
It should not have taken as long as it did but it's done. However this is ultimately a stop gap and not a full solution. What was asked for was an opt-in solution because there is value in having relays of relays.
So on the tags.pub issue, how should R2R relays gain consent?🧵
-
tags.pub has unsubscribed from all open relays. Evan recognises there's a mismatch of expectations on what Relay 2 relay, R2R connections should be like.
It should not have taken as long as it did but it's done. However this is ultimately a stop gap and not a full solution. What was asked for was an opt-in solution because there is value in having relays of relays.
So on the tags.pub issue, how should R2R relays gain consent?🧵
@OliviaVespera it seems to me that it was Evan's expectations that did not match much of Fedi's.
I appreciate that my push has (eventually) resulted in tags.pub (temporarily) ceasing its opt-out model of consent. I'll take that as a promising step.
But what is the problem this service is actually solving, and is it really a problem, or is this a "tech fix for tech fix's sake"?
I understand that single-user instances can't follow hashtags the way larger instances can. How many single-user instances—which are, by definition, one (likely more tech-savvy) user—are there?
Evan's "solution" pissed off a *lot* of people on established instances. Like, I haven't seen a defed response that swift and unified since the Japanese hacker group Discord bot attacks I fought a couple years ago.
We already have a workable solution (that anyone who runs their own instance should be able to implement), and I've been opted-in to it for years. A Fedi directory of accounts who post on specific hashtags. I'm listed for like a dozen different tags with a couple different directories, and people find me (and others) through those follow-lists that can be easily imported.
-
So how should Opt-in work with R2R?
Should it be that the source instance must explicitly register or give permission to the secondary relay?
Should it be the job of the primary relay to explicitly register with the secondary relay?
Should it be the job of the secondary relay to explicitly flag itself as a relay to the primary relay and send a relay request message to the primary relay?
How should the primary relay handle that permission?
@OliviaVespera From my point of view this can only be achieved by looking at the actor's profile. There are (often) already the two fields
discoverableandindexable. When at least one these is set tofalse, then one can safely assume that they don't want their content to be spread out.Also I suggest a new XEP that defines a field where users can directly control whether their content should be distributed by relay services at all. And in the absence of this field the other two can be used. Then the users are in control and don't need some quirky solutions like placing a tag in their bio.
Ciao! Sembra che tu sia interessato a questa conversazione, ma non hai ancora un account.
Stanco di dover scorrere gli stessi post a ogni visita? Quando registri un account, tornerai sempre esattamente dove eri rimasto e potrai scegliere di essere avvisato delle nuove risposte (tramite email o notifica push). Potrai anche salvare segnalibri e votare i post per mostrare il tuo apprezzamento agli altri membri della comunità.
Con il tuo contributo, questo post potrebbe essere ancora migliore 💗
Registrati Accedi