

Login to reply
Replies (10)
Like my kind 0? I have to keep updating it?
๐ profiles so hard ๐
profiles should be included in every. single. note.
What do you mean ๐ค?
Gotcha, yeah that's what I was thinking. So going offline for a bit can cause kind 0 to drain from relays?
Yeah. My set up is messed up half the time. I frankly have no idea what I am doing with relays. Right now I just want to see updates from and talk to interesting people.
I don't care if I miss out on a global view but the limited state I am interested in. My own data and my follow's data, should be fairly predictable without having to study all the nips and setting up my own relay accordingly.
Yeah, relays are document stores, tho, so documents that haven't been retrieved in a while fall further back and don't get pulled in timed queries.
That's not a problem on Alex, as it has a local profile cache. Might have to add one to Jumble, as it's annoying.
What a relay wants to store and what a client wants to retrieve are not well aligned.
A relay just wants to avoid cache misses. But a client wants certain infrequently accessed data to always available. This make things like profile data grow stale and get removed even though it is still logically pertainate while a note with the same access pattern is not.
It also isn't as simple as just holding all the kind 0 information forever. If you do fiatjaf will make a bot to spool up tons of kind 0 records.
Yeah, that's why I need more caching. The client should be able to show you, quickly, what you have already seen.