A publication is a collection of content from various authors/creators, usually with the permission of the author for their content to appear in it. Personally, I would not call user-curated collections like e.g. on Flipboard a "publication", since the idea of a publication is for content to be first published, not merely shared, listed, or linked.

The potential censorship risks of DNS have absolutely nothing to do with publications not publishing everyone's articles. Not sure what you meant to say there. I meant that when events are spread across multiple relays to begin with, it's much harder for people to lose access to content, when a single relay goes down for whatever reason (can also just be infrastructure issues).

Reply to this note

Please Login to reply.

Discussion

I honestly don't get what a publication is, in essence. If it's not curation then it is what? Is it like a movement by which various people are gathered and they all agree to write articles specifically to be published on that place? That would make sense.

If I am right about this then the relay specific for the publication is what makes more sense to me:

Considering an example on the internet of 20 years ago, we could have Bob and his blog at bob.blog and a publication at xfiles.pub. Bob generally writes about politics on bob.blog, but on xfiles.pub he only writes about the X-Files.

Normal Bob followers will naturally connect to bob.blog and read his politics stuff and never see his X-Files articles and X-Files fans will read Bob's articles on xfiles.pub and may or may not be inclined to look for other Bob articles on bob.blog.

Of course, anyone is free to copy-paste Bob's articles from xfiles.pub or from bob.blog and rehost them elsewhere without mentioning where they were taken from, but that is of little relevance to most users.

I want to implement multi-author blogs on Nostr. For example for our opensource co-op. The authors should be able to tag posts for one or more blogs, and the co-op key should publish who's allowed to post. When our relay goes down or loses DNS connectivity for whatever reason, everything can still be accessible from other relays. Clients can also cache whatever they want.