Excellent analysis. Especially this part:
It will be much more productive to try to solve this with the handful of Browser vendors than trying to regulate each and every consent banner.
Early cookie banners were a bad experience but they were manageable. But now thing have transitioned into content-blocking modals, dark patterns, forced individual consent/rejection for each and every one of the 943 partners they’re selling your data to, sites that refuse to serve content if you reject tracking and other ways to frustrate the end user.
I’m done with every piece of shit predatory actor inventing their own way of malicious compliance with the GDPR. You either implement the user-friendly consent API or you get no more tracking at all. Paywall your shit for all I care, at least then you’ll have a sustainable business model.
I hate the fact that none of the big names support CalDAV natively. DAVx5 is cool and all, but app developers really need to step up their shit and support CalDAV already. Not just Microsoft Exchange and Google Calendar but CalDAV as well. It’s not like they need to rebuild their apps from scratch.
At this point you might just be better served using a web app instead of a native mobile app. Maybe K-9 Mail transformation into Thunderbird Mobile might bring some good news, but I’m not holding high hopes.
Maybe we should, under the EU’s DMA, force anyone that bundles a calendar/note app with their phone OS to support CalDAV as well as any proprietary protocol of their choice.