😊 make 200 into 201
https://github.com/nosdav/spec/commit/b3804ea763c7d7e8727e275ee99649c2ab2ea298
Inflation..
Planned obsolescence 😉
I only use a single twitter list on occasion now. No main feed, DMs.. nothing.
TLDR has a typo 🙂
In my spare time I’m playing with ideas like a p2p layer. Likely with super peers. Early days..
Yep. I meant more for the contact lists, than the EOL relay meta content.
0/3/10002 are the most important events to be the latest version, without clients updating old state and publishing over an unknown newer event.
Ideally it could be dynamic too - likely based on a pubkey AUTH.
In theory it could then be like a paywall or gated community (like you can comment using kind1, but not publish blog posts).
Kind 3 may be useful adding to the list. You can do a lot with 0/3/10002.
Where is the Nostr PR for Nostr++ - the exact same but without p tag support.
👀
I agree. Getting bots to somehow include an (one click) unsubscribe filter in events (maybe that’s mute or block already), or even identify them as an automated account is a tough ask, given how easy it is to accidentally leaves shell command running and spam into global feeds.
Some bits need to be visible, like an adhoc game between two random participants. Others could defer to DMs - but public events are marketing in a way.
Maybe client apps can rank automated as low value. But again, means relying on some algo. Some automated messages are valuable.
I think this will be the kind 1’s biggest problem. It will be the default dumping ground forever. The trick will be managing it the best we can.
This is where POW could come in.
It’s funny how no Nostr clients I’ve seen have added a ‘location’ profile field. Even if just free text. It’s on every other social network profile.
Looking forward!
https://chatbot-nostr.vercel.app/
It tried so hard:
{
"id": "6d35c6f8-cb89-4676-94aa-f07de81a0678",
"type": "follow",
"publisher": "03b8afb3d381c046beada3f96bc2b3718e3f0abe4e4d24760f2aebb8f0dab7aaf5",
"created_at": 1632425439,
"payload": {
"target": "030afe03b81c2f717df7605c35e1b450f9efa0005d5ba5e5fff5f704bbe8ff2d81"
},
"signature": "b24952813d3e60bc4d4ff0482ad275a4f57cd7d84a75ba1c7e53e157057e946f235405d527da280afa46785b626f0d3c0b569be763392b2bb22f49e21303105"
}
Paging the patent infringement office! The Nostr CEO is furious about this inferior clone-tocol.
Someone suggested even filtering nip05 domains too. Ha.
Luckily I have less to block on Nostr than I did on Twitter. That will change over time no doubt.
I’ve learned on Nostr that people can be very protective of their feed and notifications - to the point where inclusions they can’t reject/filter can cause great anxiety.
It’s like allowing some kind of invasion into their space.
Weirdly ads somehow slipped through as normal on other platforms without this same degree of anxiety.
#ThereWasAnAttempt
Is anyone currently using phoenix wallet https://phoenix.acinq.co? I’ve heard it’s non-custodial so it’s safe. But does it support zaps? Is it good for NOSTR?
I use it casually. It doesn’t support inbound zaps, however invoices should work.


