This is a local test publish with an image.

I discovered while digging through the irisdb code that they use a social graph for the feed system. If your nostr app is still using a social graph for the feed system then it’s creating echo chamber and orphaning legitimate users trying to use the network. Social graphs distance should not be used to create feeds with the exception of your direct follows. Social networks are more like news feeds. They are global. A good feed isn’t just made up of your “in-group”. A good feed is made up of high quality content regardless of the author. This is how new authors get recognized and how people can see what’s going on in their world outside their immediate bubble. Social graph prioritized feeds are relic from Facebook, a network that was never designed to be a news feed. That network was designed to be simple friends update app and mostly private. That is not what social networks are today. Today social networks are a place for people to discover content from around the world and that is actually unrelated to who is a friend of a friend of a friend. I’m rebuilding the feed algorithm from scratch on etch.social.

After digging through the iris codebase I discovered that unless someone follows you then you will essentially be hidden from a social graph based feed system. Unless Damus is different the chances of anyone seeing this are very small.

If your feed system is sorting people by follow distance then it’s a bad feed system. I’m fixing this with etch.social.

I'm building a Nostr client and I have a couple questions if anyone can help: Can an event be more than one kind? Can you have like a secondary kind? I've noticed some of the kinds are redundant or add more functionality, but could still show up in another kind. For instance NIP-71 has kind 34235 but if clients aren't listening for that kind it could still show up as kind 1, but just won't have some auto video rotation. Is there a NIP or any way to announce to the world that a key has been compromised? This seems like it would be really useful if you know your key is compromised and you want to make an announcement before or even after something bad has already happened. Then you don't have to worry as much about someone pretending to be you because a smart client would be able to figure out that a key has announced it's breach at some point. #asknostr

Any ethereum devs out there? I’d love your input on my draft for Nostr compatible NFTs for blockchain posts. Thank you.

Fellowship of Ethereum Magicians

ERC-7847: Social Media NFTs

eip: 7847 title: Social Media NFTs description: Create a social media post or publication in the form of an NFT. author: Nick Juntilla (@nickjun...

#ethereum #nfts #blockchain #nostr

What’s up guys I’m a blockchain developer, founder of Ownerfy, NFTs, ordinals, and smart contracts are my jam. No offense to all the btc maxis. The world is big enough for everyone 😊 #introductions