Curious about the event semantics and architecture. What event kinds are you using?
Does relay.nostr.band only store events directly written to it by clients, or does it also fetch events from other relays?
Why are topics retarded? What do you mean by “topics”?
it's not really based on topic but based on npubs, but i think that's the closest we have right now
This starter pack website is great not only because it can help some with onboarding, but also because it's the first non-kind-1 app to have enough usage to become useless in its normal form of "just display all lists by anyone", and now some anti-spam or curation mechanism will have to be invented.
It's even better that, since it's made to be used by people who have just joined Nostr, using their follows as a filter can't be a good solution because they simply do not follow anyone.
I just hope whatever solution nostr:nprofile1qqs9pk20ctv9srrg9vr354p03v0rrgsqkpggh2u45va77zz4mu5p6ccytv72v comes up with isn't centralizing and specific, but something more generic and interoperable (like relying on relays).
I think the client is nice not only for newcomers. Right now I believe it's the best implementation I've encountered for viewing notes filtered by specific topics.
i think zapping/liking/commenting on packs would be nice
u can just drop 'em in chat
https://cdn.nostrcheck.me/4075ee229923ff096ee6eec2f226269c7f0f7ed16606235d35746e8d1bb9585c.mov
That was fast 💨
Introducing Following._ — a simple way to create and share follow packs on Nostr!
Finding interesting people to follow has always been one of the biggest challenges for new users on Nostr. Even experienced users often struggle to discover new communities and voices.
Following._ makes it easy to curate lists of users and share them with anyone on the web. Whether you're helping newcomers get started or building a niche community, Following._ allows you to grow connections on Nostr.
You can create your own follow pack in minutes and share it anywhere. Here’s an example:
https://following.space/d/d27a91a4-6155-4089-b4de-377e24dde08d
I spent months complaining that someone should build this... and eventually realized that someone had to be me. So here we are.
I also leaned heavily on AI during the process — it’s never been easier (or more fun) to create apps for open platforms like Nostr. If you have an idea, you really can just build it. No gatekeepers, no permission needed. Just ship it.
Peace

amazing! what event kinds are being used?
I opened a few PRs that should allow me to retrofit relay-based groups onto NIP 29:
https://github.com/nostr-protocol/nips/pull/1604
https://github.com/nostr-protocol/nips/pull/1601
Are you planning a tgfn episode about relay-based groups?
https://github.com/nostr-protocol/nips/pull/1589
But I'm moving towards compatibility with NIP 29, so take it as a historical artifact.
Are you suggesting NIP-29 should support both traditional nip-29 groups and relay-based groups? These seem like fundamentally different concepts. Aren’t they?
Very interesting. I like it very much. It seems like the most simple approach to do groups on nostr. Makes nip29 kinda look like nip72🤣.
It seems like it would be harder to migrate a group though, or maybe not?
What are the cons of relays-as-groups in your opinion?
Kind 20 as per nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z ‘s recent NIP
But I’m debating whether that’s a good idea or just use kind 1
I think I will introduce a way for users to choose based on what type of audience they want to reach with each post; it’s a new approach pretty unique to nostr so I think it’s worth exploring whether that UX makes sense
I love nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6's solution c in nostr:naddr1qvzqqqr4gupzqwlsccluhy6xxsr6l9a9uhhxf75g85g8a709tprjcn4e42h053vaqqyxxepcvdjnyc3ht2lc7s
(“Publish different things as different kinds, and reference them in kind:1 notes”).
The disadvantages of using kind-1 for this instagram type of posts are quite big, aren’t they?
Let’s say the whole world goes nostr. There are billions of active npubs. I want to find the outbox/inbox relays of someone. How does nostr go about this?
I cannot query all the possible 10002-kind relays (partly because it’s inefficient but mainly because I just don’t know them all).
DHT over pubkeys ? Are there other solutions?
Test


