Skip to content

never accept reposts that embed protected events inside#176

Merged
hoytech merged 1 commit into
hoytech:masterfrom
fiatjaf:protected-reposted
Mar 5, 2026
Merged

never accept reposts that embed protected events inside#176
hoytech merged 1 commit into
hoytech:masterfrom
fiatjaf:protected-reposted

Conversation

@fiatjaf

@fiatjaf fiatjaf commented Mar 4, 2026

Copy link
Copy Markdown
Contributor

Following nostr-protocol/nips#2251.
This is important to create a good environment for nostr-protocol/nips#2156, among other things.

@fiatjaf fiatjaf force-pushed the protected-reposted branch from 557021c to 8251f9b Compare March 4, 2026 04:02
@hoytech

hoytech commented Mar 4, 2026

Copy link
Copy Markdown
Owner

Possibly better handled with a write policy plugin?

@fiatjaf

fiatjaf commented Mar 5, 2026

Copy link
Copy Markdown
Contributor Author

I don't think so. I think plugins are for opinionated policies, while this should be the standard behavior for all relays, otherwise "private Nostr" (as jb55 said once in a talk) -- or people's right to talk different things in different relays and don't get them mixed -- won't be a thing.

(Of course any relay can work around this and become a hub of content the original authors didn't want to publish there, but I think we should assume that relays do want to respect authors' preferences, that's the point of NIP-70, and relays that don't do that should be considered "pirate" and ostracized.)

Let me know if you think this makes no sense.

@hoytech

hoytech commented Mar 5, 2026

Copy link
Copy Markdown
Owner

Makes sense to me! As discussed separately, we can simplify this a bit. I'll merge and do that.

@hoytech hoytech merged commit 2c27303 into hoytech:master Mar 5, 2026
1 check failed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants