If people do bad stuff on internet and use you as exit node, you might be investigated. Similar to TOR exit nodes and VPN…

This sounds very promising! Is there a github repo or similar where we can follow the development?

Just remember that you do _not_ want to be someone else exit node without fully grokkin the risks.

Nostr doesnt solve this, because Nostr isnt p2p, its not onion routed and the incentivesXcost of running relays is not proper.

Its fixable, but then dev needs to wake up.

Nostr does not solve this.

#Nostr tries to do #duplex, even though its #simplex. Separating messages from transport layer is key to success.

Lets modularize the transport/content, and create content that can be used on many social media! We could do it for user profiles and notes… I mean… JPEG proved it possible :-D

nostr:note1974f0y3ekf8pjheua6n3yt8e6shz4kdn7zy490rcxx7xgq9yf4dq6k938s

Pear/Keet is confused about the transport layer and the content packaging.

nostr:note1kkryp4vetgy93nsk279gfy0yaqjhymspwlnsgpf9zfu5dd9s7afs90te7r

#Nostr is confused about the transport protocol and the data packaging. These are two different things. One is a propagation/messaging protocol the other more of a schema for data. #few

(Nostr eating the world, lets decentralize all social graphs) LinkedIn is a website that leverages peoples trust and reputation. Basically its Web-of-Trust (#WoT) on a centralized server. #Nostr is also a foundational piece of WoT and I think it could be used to create a decentralized alternative to LinkedIn.

Thanks! I tool a brief look at the Nostr code and believe basically all of my ideas are applicable and can be implemented without any changes to the Nostr protocol. Could even be done using a proof-of-concept “peercuration”-relay. nostr:npub12vkcxr0luzwp8e673v29eqjhrr7p9vqq8asav85swaepclllj09sylpugg could for instance do it.

Great observation. By leveraging common interests and high quality of peers, we can mitigate spam AND accidentally we also fixed the “decentralized the relays” problem. I outlined part of the solution here: https://github.com/baumbit/peercuration?tab=readme-ov-file#peercuration

#Nostr should integrate #Keet for group chats, streaming radio… Pear should embrace Nostr user profiles. “One privkey to rule them all”. Protocols should not diverge, they should solve different problems and be used together. You never build a house using only a hammer.

sometimes best defense is offense

nostr:note1zkkngaqf94u4d6sfw0mg256rwxvrp8ad3kagv4fesg2wdjrtna2sva44z8

its because they dont know how to fix it. I have a proposal for how to fix it, but no one believe in me lol.. (not 100% true because giacomo has vetted my idea and think its worth testing).

check out my profile/notes and IF you think there is something to it, you can use ur status as influencer to help get attention.

Pear is using censorship/moderation in chats. Its not public. Its both a feature and a bug. Different use-cases. I love both Nostr and Pear, but they cant replace eachother.

Yes! “But will everyone store all content?” Nope… we will use #peercuration

Here is someone who gets it! Make nodes, not war.

nostr:note1qatxpzv7kaegvyyzr3l0y0q2s94ss5df72lfwtudhcj98xugrgsqeywe2z

Nostr needs an upgrade for it to happen though… the hub n spoke topology can be improved upon. #peercuration

You have an incentive to run your own relay, to ensure your own content doesn’t disappear, to ensure you get the best content etc. In the #protocolSociety you have an incentive to not be owned by someone else, because it’s actually possible.