π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«π«
All clients should do these things automatically. I think it's bug in the nostr ecosystem :D
By the time you can do that, your brain is not needed anymore.
I don't want to select relays to pay. I want my client to do it automatically.
One easy way to pay for relays is to be able to know how to do it. I would happily pay, but there's no ,,pay for relays'' button in my client. It could just distribute money to all relays that I'm following and take a part of it, and it would be a subscription.
Also I want half ads for that money!
More fun is coming on rbr.bio, I'm constantly improving threading, showing comments and likes. I want to make it perfect before adding ,,view as'' support (which is basically the following page). What's fun is that I really don't want to do a client, but I feel that it's easier than hacking on another.
I just wanted to do my own ranking for nostr, but there are lots of requesites to get ranking right. If it works well, I'd like to make a ,,nostr rendering engine'' available as a library for clients, as I'm trying hard not to go on the full client route.
https://rbr.bio/npub1sg6plzptd64u62a878hep2kev88swjh3tw00gjsfl8f237lmu63q0uf63m
Also nostr-relaypool-ts has an API where it just gets the write relays automatically and sends the requests to the good relays. That's why rbr.bio web client demo is super fast (also of course it doesn't load as much data as other clients)
sorry, I didn't see your reply in Iris :(
It has a ,,writerelays'' API, I created a special 10003 event type for it until we all use 10002 starndard.
It contains metadata, contacts and write relays so far, I have to add all 10002 as well.
It's fast because it is all in RAM.
Can you add me in Telegram?
It works actually, I just had too many Nostr tabs open
Hey #[1] , sure, if you want a nice demo application to see how to use it, you can check out https://rbr.bio/npub107jk7htfv243u0x5ynn43scq9wrxtaasmrwwa8lfu2ydwag6cx2quqncxg (it's open source https://github.com/adamritter/light-nostr-client ). Also feel free to add me on telegram (@AdamRitter)
Cool, #[2] your profile doesn't work, I need to fix it :)
https://github.com/adamritter/nostr-relaypool-ts Nostr relaypool TS is a RelayPool implementation on top of nostr-tools' SimpleRelayPool. Implements subscription batching and deduplication and also has optional caching. Probably worth exploring using it in your nostr apps if you are implementing all of this yourself, i want to give it a spin for Habla although I'm not sure if it implements nip-33.
Hey #[1] , sure, if you want a nice demo application to see how to use it, you can check out https://rbr.bio/npub107jk7htfv243u0x5ynn43scq9wrxtaasmrwwa8lfu2ydwag6cx2quqncxg (it's open source https://github.com/adamritter/light-nostr-client ). Also feel free to add me on telegram (@AdamRitter)
rbr.bio initial data loading is much faster now. Check out https://rbr.bio/npub1sg6plzptd64u62a878hep2kev88swjh3tw00gjsfl8f237lmu63q0uf63m and start browsing. It's still not perfect (still relying on info.json somewhat), but writerelays and metadata for user are loaded first, and cached (using caching of RelayPool).
I also added merging of posts with replies that are in the same thread. This will help a lot when viewing more complex interations in the future.
Hey Vitor, rbr.bio already does it, check out https://rbr.bio/npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z . I wrote to you DM some time ago about it, but you didn't write back.
Haha, build the service / microapp, ask for money
Great, chipped in a bit for the beer haha :)
Wow, it must be cool...I'd love to play chess, but at the same time there's just too many interesting people there, so it would be a very hard pass probably :)
I went in the evening, it was all women actually at the party :)
