Hacker News with Generative AI: Data Ownership

Owning my own data, part 1: Integrating a self-hosted calendar solution (emilygorcenski.com)
The first part of what I hope to be an ongoing series about repatriating and owning my own data and tech. In this post, I describe how I integrated my own self-hosted calendar solution.
A Synchronization Engine for Everyone (greenvitriol.com)
I love storing user data on the client. It helps with privacy, data ownership (which prevents enshittification), and allows users to run mundane computations (like indexing) on their devices instead of sharing a sliver of a server's CPU time. Also, if the backend fails, UX degrades like an escalator, not an elevator: users temporarily lose the ability to run server-side computations on their data but still retain access. This is the basis of local-first software, as defined by Ink & Switch.
Local-First and Ejectable (thymer.com)
An important requirement to ensure you can fully access your data in cloud apps forever is making the backend sync server available for local self-hosting. That's what EJECTABLE apps are about.
EyeEm will license users' photos to train AI if they don't delete them (techcrunch.com)