Issue: Sometimes same information/profile is shown in one account , but not shown to another login/account

[vishalxl]

Create an account A. Change its profile to spell its name as Aname. ( This I did on localhost)

Then on rostra.me login through your own account, and check A's profile. You should be shown Aname.

Then open In-private browser, and login to rostra.me only using A's pubkey. Then A's name is not shown by rostra.me

[dpc]

Does this persist? Circulation of proofs between accounts can take sometime, especially when they are new.

[vishalxl]

So problem here was rostra.me was showing name to one account, but not to another account logged in from another browser.

It got resolved, but i don't see why the same server should show different values for same info.

[dpc]

Data in Rostra is not collocated. Every identity keeps its own database and replicates events. One account might have something that another didn't get yet.

[vishalxl]

I would like to know/understand why that is so. If you are running a server ( on localhost or rostra.me), and you have 100 people/accounts using it, and they want a public event, we would want the server to go fetch that event once. Why do we want the server to fetch the same event 100 times?

I guess one answer is that you expect a single server to be used by ONE person, who is running it. Because we do not want to give our private keys to random/other servers.

However, even if 99 people logged in to rostra.me using their public keys only, and asked that given event, then the server should fetch it only once, no?

[dpc]

The core reason is: the database architecture was written assuming a single user, and multiple users were added later by just starting multiple clients, each with its own database.

Actually joining data together adds a lot of subtle but potentially nasty problems too. E.g. we need to track the disk usage of data of people you follow, then prune and gc according to some quota policies, but this becomes much harder if the same data is mixed between multiple owner accounts.

It can be done, but I just never got to it. AFAICT Rostra is largely empty so far, so it was not worrying me too much. I'm hosting Rostra.me on some $7/mo VPS and Rostra never gave me any disk issues yet.