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.

Reply to this note

Please Login to reply.

Discussion

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

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

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.