#relays

unattributed 𓂃✍︎ @unattributed@gotosocial.social · Jun 28, 2026

Since @evan@cosocial.ca seems unable (or unwilling) to understand that many users desire the #FediVerse to be a place where opt-in is the normal and expected implementation for features such as #relays I propose that #fedidevelopers take up this call. The problem: the implementation of relays lacks sufficient user-based controls. While users may (at least on platforms such as GotoSocial) add relays they desire to have their content sent to, there are no user based controls over relays configured at the instance level. The current implementation appears to have unintended, and unconsidered consequences associated with it. Ban evasion can likely be achieved through chaining relays together. We have already seen the unintended consequence of a relay following tags.pub leading to content being relayed non-consensually. Something that has not been considered is potential damages to users in regions where political, social, or religious beliefs are sensitive topics need to maintain tight controls over where their content is sent. This is a case where the handling and relaying of posts needs to be 100 percent bulletproof. The Solution: all platforms in the Fediverse should implement instance level relays in the following manner: Instance level relays are disabled for all users on that instance.User settings provide a list of the relays provided at the instance level.Users can opt to leave the relay(s) disabled, orThey can choose to enable the relays they trust their content being sent to. Through this implementation we avoid clunky workarounds like adding hashtags to profiles. Also, we make this feature more discoverable for new users who are unfamiliar with the conventions of the FediVerse. I am unfamiliar with the #FEP submission process and requirements. Anyone willing to work with me on this, I would like to see this brought forth as a FEP. #fedideveloperverse #fedideveloper #mastodon #gotosocial #misskeyworld #misskey #pixelfed #microdotblog #pleroma #sharkeydev @alice@lgbtqia.space @admin@gotosocial.social @gotosocial@gts.superseriousbusiness.org @Gargron@mastodon.social

0

Olivia Vespera @OliviaVespera@spacey.space · Jun 28, 2026

Replying to @OliviaVespera@spacey.space

I think one way it could work is through opt-in chains. Secondary relay(SR) identifies as relay and makes request to primary relay(PR) to relay PR's content. PR asks source instance (SI) for permission. SI either grants permission or not. If granted, PR grants permission to SR. SR relays SI content via PR. #Tagspub #relays #R2R #Fediverse #OptIn

1

0

1

0

Olivia Vespera @OliviaVespera@spacey.space · Jun 28, 2026

Replying to @OliviaVespera@spacey.space

This can also be placed inside a closed registration-esque structure where only secondary relays which the primary relay has registered with can make the request to relay PR's content. thereby reducing the number of requests to an SI to only SRs that are trusted by the PR. But perhaps opt-in needs to be propagated further to individual user accounts. #Tagspub #relays #R2R #Fediverse #OptIn

0

Olivia Vespera @OliviaVespera@spacey.space · Jun 28, 2026

Boosted by

Furbland's Very Value = 71 Account™ @GroupNebula563@mastodon.social

Replying to @OliviaVespera@spacey.space

The other alternative is to delegate opt-in responsibilities to the primary relay. Source Instances could set an option that says, you don't have to ask me for permission, I will leave it to you to decide whom to share my content with. Reducing the number of requests to users. Or Source Instances could set a flag in the primary relay that says do not relay to secondary relays. (and don't ask me for permission because I won't ever grant it) #Tagspub #relays #R2R #Fediverse #OptIn

0

1

0

Olivia Vespera @OliviaVespera@spacey.space · Jun 28, 2026

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?🧵 #TagsPub #Relays #Fediverse #OptIn

1

0

3

0

Olivia Vespera @OliviaVespera@spacey.space · Jun 28, 2026

Boosted by

Furbland's Very Value = 71 Account™ @GroupNebula563@mastodon.social

Replying to @OliviaVespera@spacey.space

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? #Tagspub #relays #R2R #Fediverse #OptIn

0

1

0

Jason Parker (he/they) @north@xn--8r9a.com · Jun 28, 2026

When you're a Very Important user on the #Fediverse, and you spend 3+ hours writing dozens of responses about how something is opt-in actually (it isn't), and that you understand consent (after-the-fact), maybe you should take the next 3 hours to reflect on how wrong you are. #subtoot #hashtags #bots #relays #ConsentIsSexy

21

3

15

0

About This Hashtag

#relays

Related