Avatar
NickJunes
f714be81ac0e60093ffbd67819e2557bc0bcb311b013dfe3934d4133813dd711
NickJunes on TikTok

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.

How does he see all of this as a good thing? A police nanny state where every possible infraction is reported. People will be afraid to live.

If you wanted to make an client just for video (which I am) and you don't want to miss out on all the kind=1 video attachments then you have to filter on both. If you have an app that only filters on kind=1, but it is perfectly capable of displaying videos then you don't want to miss out on all the video content. If you can have a list of supported kinds then you don't have to leave out all the apps that can readily support your post with no changes. For instance kind NIP71, 34235 and kind 34236 are fully encompassed subsets of kind 1. If a kind one app were to bring these kinds in they would display just as well with no changes. This means anyone choosing kind 34235 or kind 34236 need to make the decision to leave a significant portion of the ecosystem just to have something as simple as "preferential orientation". I can't see anyone wanting to make that tradeoff. So in practice most people will simply choose to crate kind 1 posts with video attachments as to not risk being ignored by most nostr apps.

Replying to Avatar fiatjaf

If I remember correctly they contacted me and I had a call with a guy from Twitter where he told me Bluesky's goals were to build a protocol for which Twitter could become a client in the future, to which I said Nostr was a perfect match, then he asked me if I would consider becoming the lead Bluesky person they would pick for leading the effort, and I said ok but asked if it would be acceptable if I just used Nostr as it was as "the Bluesky" without considering the other proposals and he didn't know what to say.

Then he put me in a secret group chat with some other people including SSB people, Mastodon people, the GUN guy and people from a bunch of useless IPFS projects. Supposedly the group was gathered to work together in creating this Bluesky protocol, but I read the entire conversation and it was 100% people just shilling their own projects, so I talked a little about Nostr and the first feedback I got was: "how do we ban people? it looks like it would be very hard to ban", so I said that was the idea and the conversation ended. Maybe Jay Graber was in this chat, but I don't remember reading any messages from her.

Some time after that supposedly this group produced a "report" containing all decentralized protocols in existence and a comparison between them, but it didn't include Nostr. I think the group didn't produce anything and this was likely a solo effort from Jay. The group continued its useless, sparse conversation and Bluesky the company was created through some other means of communication.

I reviewed all the protocols before I started building and Blue Sky (AT Protocol) is a similar concept except much less flexible, more centralized in development and significantly and unnecessarily verbose as a protocol. I immediately started building my new app Etch on top of it. That's also why I wrote ERC-7847 on Ethereum to be compatible with Nostr. Nostr is the most elegant solution to e-publishing.

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. https://ethereum-magicians.org/t/eip-7832-nostr-and-nft-compatible-social-media-publishing-standard/22280 #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