yes this is the current update I am working on. but will take a while as I want to allow users to use the old method if they want and its taking me a while to sort out the best way to do this.

def agree send delay feature is needed

thank you rob! glad you find it useful.


I am currently in the process of completely revamping the relay strategy to be more targeted (kinda frozen with indecision atm), and hopefully make UI less busy as well. in theory the targeted relay strategy should be faster and less data intensive, the hard part will be supporting the legacy relay strategy as well to continue to provide a smooth experience.

lists are meant to be flexible enough to hold anything, though rn only have lists for users, hashtags, and events defined, I also think lists of relays or lists of other's lists should be added.


lists are essentially tag lists and can be public and/or private. user tag lists can also hold the relay hint field so you can specify which relay to use for which user in a list.


my idea was users can create their own feeds by pulling in the lists they have saved. so you could create a feed by pulling in a list of hashtags queried against a list of relays. or a list of hashtags from a list of users (using the relay listed for each user).


what do you think @nostrich ?

correct, this is what kind 2 does. but this pr may make kind 2 irrelevant


@nostrich

I have an open pr for this: https://github.com/nostr-protocol/nips/pull/182

discussion of new long form posts pr by @nostrich 
https://github.com/nostr-protocol/nips/pull/220

@nostrich

yeah have no idea about the legal side. but damus means nothing outside of the context of nostr so hard to image those domains would be used for something completely unrelated.

but having to spend limited resources fighting trademark infringement will surely make damus better and better no???

of course! thank you!

wow things really getting interesting now

I feel like ppl using 'notes'