[Groxx]

Importantly, during this entire multi-year gap, nearly all of them worked just fine but it was gated behind an AMO account for... I don't know what reason.

If it was just an experience issue because like 5% failed weirdly or had bad performance but they couldn't validate them all: that's basically fine! Hide it behind an about:config flag! The AMO requirement was a privacy-invading piece of nonsense that had no business existing.

[KennyBlanken]

Privacy-invading requirements that delay implementation of plugins that would enable plugins providing better privacy and ad-blocking functionality?

Hmmmmmmm, now what major Mozilla sugar daddy would be interested in that /s

[account42]

Why the sarcasm tag?