Unified/shared storage + fields e.g. for guest names

[nickvergessen]

E.g. guest name was chosen to be localStorage.getItem('nick') in the past and we decided it should e.g. persist over apps, so the same value should be used in Talk, Deck, Text, etc.
Since all apps use a scoped browser storage, we need a fixed scope for shared data like this, so all apps can use the same scope.

Proposal would be server or shared and in there we use nick or guest-name?

After we agreed on this, it should be documented in the readme.

cc @juliushaertl @ChristophWurst

PS: would a getUnscopedItem function make sense, so you don't need 2 stores, one for the guest name and one for your apps data?

[ChristophWurst]

I'm not sure about this. What you are describing is a shared global variable in fact. I do not think we want to embrace this.

Things like these are easy to add but pain to debug and maintain. Can we add that into OCP of server or one of the existing npm packages?

[rullzer]

I tend to agree with @ChristophWurst here.
I mean a dedicated npm package would make sense I guess. This can of course in the background use this browser-storage. But the logic should be hidden

'getGuestName' 'setGuestName' or something like that is enough.
Then everybody can use it. But it doesn't do 💥 so easily. And we can have proper debugigng and tracing in that package.

[nickvergessen]

Okay, then let's do that instead.