ΔC
https://cascade.engineer network wars clone
https://talos.nostr.xyz openclaw bot
https://drss.io -- bringing back the republic of blogs. and onramp for bringing RSS content, including podcasts, into NOSTR
https://npub.dev -- configure your outbox
I don't enjoy having to say this, but @River your emails and notifications constantly jamming offers at me is not something sovereign people tolerate much of. your service and app have been incredibly useful. I'd really not like to have to block all notifications from your app or emails from you. but that is the next step if the panhandling doesn't stop.
most of the insights of The Wealth of Networks have since diffused into our awareness. it sees mostly positive feedbacks and not much negative, but still worth a look for those working on snd thinking about the protocol.
https://cyber.harvard.edu/wealth_of_networks/Main_Page
a funny aspect of getting the coding agent to write meaningful tests around #nostr functionality is the understanding that secret key -> pubkey cannot be faked. I see so many "npub123-abc" in its tests. no matter how often I explicitly instruct it otherwise. I have a rule in CLAUDE.md which points out that we have a keys.md with a markdown table with 10 secret keys, pubkeys, and npubs for use in tests, and it always forgets and just makes things up.
I keep coming back to making lists of lists, or more accurately, set of sets. is there a reason why it doesn't exist in the NIPS? just hasn't been a need so far, or was it discussed and discarded? I ask because I've looked and did not find anything.
thinking of using 30100 for that kind. I like the idea of a hierarchical list of lists than can link in lists owned and maintained by others. if you hang follow sets from those lists, it becomes a nice way to subscribe to a feed, if there are clients that allow it.