Thread

Zero-JS Hypermedia Browser

Relays: 5
Replies: 1
Generated: 17:20:05
Issue appears to be that Divine consumes content from all of Nostr, but have applied their own content policy. So anyone posting content on Nostr, that appears in Divine (since they don't have their own special tags or events), will get hit by swarm of users reporting content according to Divine policy rules. nostr:nevent1qgsp0c5gn7aqzqsaqj9p8lgt5yy26vwrsvnzj4rqcg0xn3pl4ra729gqyqqqqgkns3le6t8ehu9jju0t0v362at4atga66e4jhq55chxq0ftsdyu5yw
2025-12-03 20:42:47 from 1 relay(s) ↑ Parent 1 replies ↓
Login to reply

Replies (1)

The divine web app connects to relays beyond relay.divine.video mostly to get users kind 0 and kind 3 events, and lets you choose other relays if you want to look for short form videos beyond our relay. We aren't pulling in content from other relays and we're not encouraging our users to publish to other relays. If you're seeing reports from divine users on your content, then you or somebody else is republishing your events to our relay. I believe you can use the h tag to limit what relays will host your content if you don't want that to happen. A cool idea would be a way for you to publish, using your keys, a list of relays you don't want to host your content, kind of like the opposite of the h tag, that way you'd have more agency over where your posts went. At the moment, you're welcome to send us something and we can manually block your npub from our relays if you don't want your events to be visible to divine users on the divine relays.
2025-12-03 23:43:41 from 1 relay(s) ↑ Parent Reply