Googles new secret sharing scheme. It’s called plain text. Highly innovative and approved by Five Eyes. We need to get off this trash so badly.. View quoted note →

One risk with value for value public payment models is that people may see N amount of zapped sats, and think, “that’s received enough compensation”. Their internal model of what something is/was worth is in equilibrium - yet the global utility/value is still higher. It may translate into a deferred or more balanced zapping across content - however it’s likely to be a friction point too - where people internally question the above before contributing, and either zap other things or fewer things.

“Esteemed ladies and gentlemen, now is the time to take our assigned seats. It’s not the time to pack bags or search for a better seat. This is a fully booked flight.” 🤣

I wonder if anyone has analytics linked to their profile image. Like tracking image loads, location, time of day, etc… I considered in events before, but forgot profile images are likely a better way to do this. Sounds creepy, but literally it’s what Facebook and every crappy social does today without you knowing.. and then selling the data.

Everyone who joined the NostrGraph Dashboard waiting list now have access. Check your DMs.

RE: NIPs, implementations and compatibility. Specs are hard. They often are unclear and miss edge cases. It’s why the only Bitcoin consensus spec I trust is the Bitcoin core source code - no written documentation or alternative project. Nostr is moving at such a pace, and development individuals and teams are all self-funded, and frankly keeping up with their own development roadmap is hard enough - let alone trying to keep up with the latest NIPs; either draft NIP input, awareness around proposals, and where the most difficultly lies.. supporting NIPs that break user-space and create a negative user experience and feedback. Solutions.. not sure exactly. But here are some ideas. 1. A regular 7-14 day reoccurring NIPs updates and presenting via community open video call session. 2. Implement breaking changes in smaller isolated test/POC projects - and not directly into popular app beta builds. 3. Difficult to say.. but perhaps slow down. We have major fundamentals in Nostr that are not great today.. we scrape by. Building on rocky foundations is a future curse - much works pretty well too. 4. Understand that creating work for other devs who are already struggling to keep up, builds more stress and tension. I have around 500 TODO comments across my Nostr projects… some easy and some hard. It’s not easy to keep up.

Pro Tip: add an iOS (or android) shortcut for your favourite relays. wss: -> wss://relay.nostrgraph.net