With the new Chrome filesystem API it should be possible to make a full browser implementation.
Let's just hope they don't have annoying GDPR and other popups when you're trying to edit a file.
Let's just hope they don't have annoying GDPR and other popups when you're trying to edit a file.
Your remark about GDPR is kind of strange ... not sure what that would have to do with anything ... GDPR applies to people and organisations, not their tools.
To a lesser extent, there are people that are concerned about "all the extra work" this entails, and the cost it adds to their bottom line. But this stuff is important nowadays. You really should be taking care of it.
There is some scaremongering about small firms being blown out of the water for noncompliance, but really, unless you're doing something you shouldn't be doing you should be fine. The terms of GDPR though still not completely clearly specified are flexible and reasonable. The main thing is now, that you can't say you weren't aware of it.
OP is saying that Emacs-as-website would be frustrating if it had those popups.
The cookies warning is all about notifying the casual reader who might otherwise believe they were passively browsing static content.
Logging in means you get a single cookie (a login/session cookie), that cookie is necessary and thus a functional cookie that you can't say no to. All other cookies (and basically every form of tracking) still isn't allowed without consent.
You know that GDPR doesn't require pop ups unless the service is doing something that isn't otherwise lawful?