When trying to login to near.org, the authentication is being rejected by Firebase.
I'm being advised this is a 'local storage' issue and if it is, you've got an issue that is going to have a significant impact.
Impact
If the 'local storage' is being used for the basis of authorizing, then you've got a problem with this, as your authoring isn't taking into account 'local storage' session based use, which is what I use and all my browsers are set to clear out 'local storage' upon closing and so will only store data on a 'session basis'.
I also clean my systems fully every Q, as I'm sure many of you will know, that the impact of developing, creates a massive loop of over used resources and logs and so eventually slows your machine down.
So with both scenarios, local storage is a problem if the local storage isn't being refreshed on authentication and relied upon for authorization.
Description
When trying to login to near.org, the authentication is being rejected by Firebase.
I'm being advised this is a 'local storage' issue and if it is, you've got an issue that is going to have a significant impact.
Impact
If the 'local storage' is being used for the basis of authorizing, then you've got a problem with this, as your authoring isn't taking into account 'local storage' session based use, which is what I use and all my browsers are set to clear out 'local storage' upon closing and so will only store data on a 'session basis'.
I also clean my systems fully every Q, as I'm sure many of you will know, that the impact of developing, creates a massive loop of over used resources and logs and so eventually slows your machine down.
So with both scenarios, local storage is a problem if the local storage isn't being refreshed on authentication and relied upon for authorization.