| How is GDPR ugly? It's easy to build websites, even interactive ones, that comply. If you build a mobile app, you are also supposed to only ask for permissions once you actually need them. Replace interactive embeds with a dumb replacement of the actual content and e.g., "we want to show you an embedded tweet here, [allow once] [allow always]". Don't use CDNs for delivering assets, they've long stopped being useful anyway. Don't use Google Analytics. In general, build websites like we used to in the early 2000s. And yes, you can even do cloud-y stuff like that. You can run k8s on your hetzner dedicated servers, you can run MinIO as your s3 store, none of that is stopped at all by these rules. You can even run an interactive website like HN without any GDPR violation or cookie prompts at all. |
Hard on Android, where "did my wifi go away" means asking "can I have access to your phone's internal state including call logs and if you're in a call right now?"
> replace interactive embeds with a dumb replacement
Sucks when you depend on that content or the content has to be interactive under the TOS of the service you're using.
> [CDNs have] stopped being useful
Not at all. In many a corporate network as well as situations where you're paying for transit (e.g. AWS) they still make sense.
> build websites like we used to in the early 2000s
Ah yes with Flash for our interactivity, __Just throw an executable format that has a hard to render, proprietary ISA running unsupervised__, that worked for us then it should work fine today?
I'd say "Let's build more websites like we did in 2010". That's right around when Javascript peaked.
> Minio
due to their licensing change, a lot of legal departments have banned minio.