I want to build it into Habla but without requiring the publisher to do anything, thought about using a public list for user subscriptions (could be pubkey or hashtag) and send them a DM whenever someone from the list publishes a new poast. Weekly digests sound great too, usually long form are low frequency so probably good to send one DM per publication, perhaps make it configurable?

Replies (6)

Interesting so users have lists with "subscribed" publications, you'd need to query for all lists that contain publisher X, is this possible? DMs leak metadata but are still more private than public lists
I don't understand why involve DMs at all in this. If the entire flow involves a client asking relays for events, why not just ask directly for the articles?
HoloKat's avatar
HoloKat 2 years ago
This would be cool! I would like a weekly summary instead of individual updates, though configurable is probably best.
Here are my 2 cents (long post, sorry): Current status: - Long form posts today on Nostr are difficult to discover because most clients don't support it and instead you need to go to a Nostr enabled web site like Habla.news to see who has posted something lately. This is very suboptimal - Outside of Nostr, subscribers to newsletters receive them via email. They don't need a new client. They discover the new issue of the newsletter as part of their existing habit of checking their email - The key here is that it's an existing habit on an existing client. No need to do anything new to discover new issues of the newsletter you subscribed yourself to. Possible solutions: - When a publisher posts a new issue on their newsletter, Habla.news could simultaneously create a kind 1 event with the summary and the URL to the issue. This will allow the publisher's followers to discover the new issue through their existing habit and client, even if the client doesn't support long form notes - DM to all followers of the publisher. Could be considered obtrusive but let's face it, you're following that person for a reason. - Using a public list for user subscriptions like @verbiricha suggests above will work. But, doesn't this defeat the purpose of Nostr? I have always thought of Nostr as a way to follow a person and all the content this person produces. Would the public list require me to take a second step of subscribing to the publisher on top of already following him/her?
Great feedback, as you suggest there is no one size fits all solution. Perhaps the DM approach (with ability to opt out if you don't want it) is the way so you don't miss long form posts by people you follow. The idea behind subscriptions is to not only follow but also set up a recurring payment to the authors you want to support, I'm looking at NWC subscriptions and lists as a possible way to implement this but is still early and need to think about it more. I think we'll dedicate the next Habla design meeting to this topic, is the next big milestone for Habla.