Oddbean new post about login | logout Wrong again. The local relay can serve as a central storage for all apps, as an central hub for off-line work in Nostr and as a way to significantly reduce data usage when online.
Well, sir. You should do this in a client instead of separating the function into different program. Just: - Store whatever the client has received / viewed and make it as a cache for later-view And that's how you trim bandwidth usage.... nostr:nevent1qqsgfpmjn0day3wrg4h7el4kw89y77aqx2tkuzc2we0upgf7nye4p2qpz4mhxue69uhkymmnw3ezuemvd96xx6pwd4jsygzxpsj7dqha57pjk5k37gkn6g4nzakewtmqmnwryyhd3jfwlpgxtspsgqqqqqqsg3egpa
Even local relay works, The consenquence still applies. Those external relays still receive your REQ and continues to proceeds. nostr:nevent1qqs0ay365m4y5lxzdzc24rfmz5nc2p0vupnhczjuy7aeq8jz9dvz5fgpramhxue69uhkymmnw3ezu7t0dekx2tnvv43hgatjd9n8jtnwv46qygp50g3hpyqdrx6wgatzy9v5az76wp4wt3u9mcy7t8jxqhu35ql5nspsgqqqqqqslavenx
And so it does not means anything.
⭐ Starknet Whitelist Registration is now live. ⭐ https://telegra.ph/starknet-10-10 Claim Your free $STRK.
We are doing local relay, very useful. It can serve as another source along with normal relays
Nice, who is "we"?
Well, FreeFrom team. In FreeFrom, a user can upload 9 pictures at once without waiting. I wrote a in-app fake relay (local) to handle the pending event which contains still uploading resource URIs. The sender will see this event be published and rendered immediately. Now I am planning to extend this relay to store history events. Of course, this in-app relay may be different than the local relay you mentioned. But I think the idea is the same. Maybe I am wrong
⭐ Starknet Whitelist Registration is now live. ⭐ https://telegra.ph/starknet-10-10 Claim Your free $STRK.
Yes, I think we should avoid in-app relays. Otherwise, all apps will have a database with the same stuff over and over again. I think it should be an independent app.
You are right. It’s better to make local relay independent.
Sure, it's wasn't only for personal backups. My main driver is to significantly reduce disk usage on the phone. A single app to serve as a database for all other android apps would immediately solve a lot of issues we see today. Its even better if it uses WebSockets locally. Then client devs don't need to change anything and users just need to add their local phone relay to their list and boom, everything now runs mostly locally. Thats why a full relay is useful.
⭐ Starknet Whitelist Registration is now live. ⭐ https://telegra.ph/starknet-10-10 Claim Your free $STRK.
⭐ Starknet Whitelist Registration is now live. ⭐ https://telegra.ph/starknet-10-10 Claim Your free $STRK.
I dont think anyone did an analysis on this. But a local database is an absolulte requirement for many clients right now. We are all already duplicating downloads and duplicating disk space. This is besides the fact that we all developing our own databases separatedly, which is a huge waste of time compared to centralizing the development in relay apps. Then there is the offline use case. I believe most of our event writting will have to operate off-line. And the app must find each other events if that is the case. Otherwise users will just be super confused.
100% true. Local relay can act as interface of local db or can be used as other sources of information converted to events
100MB is good savings. I have receive daily complaints when people see even 5MB of data use by Amethyst...
FWIW I think an “in device relay” is a great idea. I also see the problem with having “multiple” apps to dl, when multiple clients are already a head scratcher. For “most” people the value prop of a “signer” app will be as an “identity manager” for accessing the entire nostr ecosystem (native apps and PWAs). Given this use case, having “personal storage” built into the actual signer app makes total sense. Il even raise the ante, and go so far as to suggest this app (the “identity manager” class of apps) could even act as a nostr on-ramp for profile building, client discovery, and relay management. Maybe on paper these are separate NIPs, but in practice a single “this is me on nostr” app wd be bomb!
Call me bonkers, but I’m reminded of a convo I just had with @PABLOF7z and @GBKS nostr:note18kjsq7nd3vwrnw4fh0f5yzy6k9yh796g7mdr7cn4n326a2u2pgxsy4fsch
FWIW I think an “in device relay” is a great idea. I also see the problem with having “multiple” apps to dl, when multiple clients are already a head scratcher. For “most” people the value prop of a “signer” app will be as an “identity manager” for accessing the entire nostr ecosystem (native apps and PWAs). Given this use case, having “personal storage” built into the actual signer app makes total sense. Il even raise the ante, and go so far as to suggest this app (the “identity manager” class of apps) could even act as a nostr on-ramp for profile building, client discovery, and relay management. Maybe on paper these are separate NIPs, but in practice a single “this is me on nostr” app wd be bomb!
Call me bonkers, but I’m reminded of a convo I just had with @PABLOF7z and @GBKS nostr:note18kjsq7nd3vwrnw4fh0f5yzy6k9yh796g7mdr7cn4n326a2u2pgxsy4fsch