Suggestion GM_setValueGlobal Global Scope

[TimidScript]

The ability to store information in a central database accessible by all scripts.

[tiansh]

Should this be global or namespace specified?

[TimidScript]

The namespace idea is good 👍

Any is better than none.

[jerone]

I don't think that is really needed. Script authors could provide their own namespace by using a prefix in the key if needed. This keeps the API the same as GM_[gs]etValue.

[TimidScript]

If it is only one database it can become bloated if several scripts are writing to it as the number of scripts utilising it increases.

Instead of having one global database allow the script to define a global database name(s).

Reading is not an issue but altering or amending a large database with high number of records really slows down the browser and causes irresponsiveness.

[janekptacijarabaci]

See also #1728

[TimidScript]

Please consider allowing the new databases locations to be a setting value. I would rather have them on a different drive and directory.