Nostr Relay for the Russian-Language Audience on Anubiz Offshore

Russian intermediary law requires registration with Roskomnadzor for services with significant Russian-language reach, mandates data localization, and historically responds to content takedown demands with broad scope. A Nostr relay inside Russia would be either non-compliant and risk blocking or compliant and unable to credibly serve as a censorship-resistant venue.

The operational pattern is offshore hosting (Finland is closest in network terms) with Tor onion fallback for users behind DPI throttling.

Helsinki to Saint Petersburg: 12-15 ms. To Moscow: 25-30 ms. Section 10 telecoms privacy at the operator level. Strfry on a V tier handles tens of thousands of concurrent WS connections. Tor onion mirror on the same instance for resilience.

WSS on standard 443 generally passes Russian DPI without issue most of the time. During heightened enforcement periods WSS over 443 can be intermittently throttled. Tor onion fallback is the mitigation: publish the .onion alongside the clearnet WSS in your relay metadata; Tor-capable Nostr clients use the onion automatically when clearnet fails.

You moderate. CSAM at infrastructure layer on credible notice. For Russian-language content specifically, plan for higher volume of political content and have a clear policy on what kinds of moderation (if any) you apply. Pseudonymous Nostr keys make user-level enforcement harder than fediverse models.

Finland VPS via VPS lineup, related anonymous hosting, dedicated tier.