Also, this bridge is easier than you might think, you actually dont need to make a new client, all you need is for normal clients to "talk" pear links and you've completely changed the game. Its getting a "relay" running on a pear swarm that needs to be built, the rest is just integration with all your favorite clients already.
what makes a pear link unique? are there adequate libraries for the protocol? is there push to open up kind 1 to support it?
It wouldn't need "kind 1" support or anything like that. It would be in the relay list. You would simply need the pear stack running in the background and have it connecting to other pear nodes and pulling nostr notes from those as well. Then you could easily run and organize your own pear node however you wanted. Would make nostr load much faster too and customizations would become much simpler to implement, imo.
This sounds very promising! Is there a github repo or similar where we can follow the development?
Not yet, we're totally in the dark right now, but it's seriously very close. We are meeting Monday about potential alpha version. All of the code probably won't be public until the beta version though because i already know we have some breaking changes in the roadmap. Right now we just want to have it working with the core functionality so we can see how people interact with it and then we will have something to work off of when it comes to the design and UI. Ideas are great and all, but users are 100x more valuable than theories.
Oh.. I was hoping it would be more like a URI link, e.g. pear://ade0eea0938someidvalue.pear/resource
I still havent setup anything with pear due in part to massive time constraints but thanks for the feedback. im sure if there is enough viable demand and support itll take hold.
I don’t see why that wouldn’t be possible, but I think that takes a lot more work. It’s easier to just have a node that can be reached with one of those URI links that simply watches relays for any of your follows or notes, and then saves them, then you connect to it with the link from whatever client you like and you just load from your personal node.
yeah. the way you describe with a pear enabled relay is just transparent to nostr users and implementation specific
Fair. I always assumed there were two possible paths to go down:
1. regular Nostr relay with Pear backend
2. Pear client for Nostr that skips the HTTP part
1 is easy, 2 more complicated, depends on 1
I guess there's also 3: nostr client that injects notes into a Pear backend. Think of it like a bridge. you would probably need that to make 2 work and not wall itself off from most of Nostr.
I suspect it will naturally start with 1 and then end up at a combined 2 and 3 depending on whether the client in web based or an app.
Oddbean new post about login | logout