<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Topics tagged with r2r]]></title><description><![CDATA[A list of topics that have been tagged with r2r]]></description><link>https://citiverse.it/tags/r2r</link><generator>RSS for Node</generator><lastBuildDate>Wed, 08 Jul 2026 16:20:01 GMT</lastBuildDate><atom:link href="https://citiverse.it/tags/r2r.rss" rel="self" type="application/rss+xml"/><pubDate>Sun, 28 Jun 2026 15:33:02 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[So how should Opt-in work with R2R?]]></title><description><![CDATA[@oliviavespera@spacey.space why does a secondary relay need explicit permission from the source instance to have their content relayed?
If the source content is public then there's no discussion to be had, there are no grey areas, the post is public.
It sounds like you're trying to add in layers of privacy to a visibility scheme ("public") that does not have any.
]]></description><link>https://citiverse.it/topic/cb7e9c37-6fff-4d23-9cab-b504737db3c5/so-how-should-opt-in-work-with-r2r</link><guid isPermaLink="true">https://citiverse.it/topic/cb7e9c37-6fff-4d23-9cab-b504737db3c5/so-how-should-opt-in-work-with-r2r</guid><dc:creator><![CDATA[julian@activitypub.space]]></dc:creator><pubDate>Sun, 28 Jun 2026 15:33:02 GMT</pubDate></item></channel></rss>