With so many files, notes, and photos scattered across devices, cloud services, and forgotten hard drives. Most of us just ignore the mess until something goes wrong. After attending the PKM Summit and talking with experts and power users, I reworked Heaper around four core principles that I believe every digital workspace should follow: Local-First Access: Your data lives on your device by default, always available, even offline. No more "I don't have that with me right now." Conflict-Free Syncing: Using CRDTs (conflict-free replicated data types), edits merge across devices without overwriting your work. No sync conflicts, no lost notes. Flexible Linking Over Folders: Folders force everything into one place. Heaper uses mentions, tags, and backlinks so anything can exist in multiple contexts without duplicates. True Ownership: Self-host on your own hardware with Docker, or use the hosted EU cloud. No vendor lock-in. If Heaper disappears tomorrow, your data is still yours. Heaper is available now on iOS, Android, Windows, Linux, and Mac. The offline version is completely free, no account required. 🔗 Links Website: https://janlunge.de Download: https://heaper.de Self-Hosting Guide: https://docs.heaper.de/docs/self-hosting Discord: https://discord.gg/dNB4QsPBnu Feature Roadmap & Voting: https://heaper.de/roadmap 📚 Resources Mentioned PKM Summit: https://pkmsummit.com/ Linking Your Thinking (Nick Milo): https://www.youtube.com/@linkingyourthinking Restic Backup Tool: https://restic.net/ Chat Control / EU Privacy Info: https://fightchatcontrol.eu/ CRDTs for Developers: https://yjs.dev/ Thanks again to Herman Kopinga for introducing me to the PKM Summit.
Folders Are Broken, So I Built Heaper
Heaper: One home for files, photos, notes, tasks, and media
Heaper is a private, local-first home for files, photos, notes, tasks, and media that you own. Use built-in or user-defined types to shape one connected digital world around your life.
Understanding new Cloud Storage hierarchical namespace | Google Cloud Blog
The new hierarchical namespace capabilities bring file system optimizations to Cloud Storage buckets.
Rethinking Digital Storage for Community-Based Archives
Over the last few decades, the standard procedure for storing and backing up data has been ‘put it in the cloud.’ Many of us use cloud…
File Over App: A Philosophy for Digital Longevity
My take on the 'file over app' philosophy and why it’s essential for keeping my data resilient and built to last.
Three schemes for shared-private storage - Paul's Leaflets
Peter van Hardenberg - Ink and Switch, Automerge
Comment on: Permissioned Data Diary 2: Buckets - Daniel&#...
"a bucket doesn’t necessarily imply a physical container sitting on one PDS. Consider how threads ..." The distributed-vs-centralized storage question is where this gets really interesting. If buc...
durability-labs/archivist-desktop
Cross-platform desktop client for Archivist decentralized storage - built with Tauri v2, React, and Rust
iCloud Drive - Apple iCloud
Store, organize and collaborate on files and folders with iCloud Drive. Easily upload, delete or recover files. Changes will sync across your devices with iCloud.
iCloud Drive - Apple iCloud
Store, organize and collaborate on files and folders with iCloud Drive. Easily upload, delete or recover files. Changes will sync across your devices with iCloud.
Plan B: an operating system for ubiquitous computing environments
The conventional approach for building pervasive environments relies on middleware to integrate different systems. Instead, we have built a system that can deal with these environments by exporting system resources through distributed virtual file systems. This requires no middleware, simplifies interoperation, and permits applying general purpose tools to any system resource. A constraint-based file system import mechanism allows the system to adapt to changes in the environment and permits users to customize the environment and tailor adaptation according to their needs. The system has been in use for over a year to carry out our daily work and is underlying the smart space that we built for our department
Personal sync servers for composable data
Exploring the possibilities of interoperability and composability for local-first software & data by using a personal sync server tied to an atproto identity
Personal sync servers for composable data
Exploring the possibilities of interoperability and composability for local-first software & data by using a personal sync server tied to an atproto identity
I was looking at an older version of the software I'm yet again working on from what, 15 years ago, and I can't believe we're still mostly stuck with the same private blob storage options that can serve as user-data storage. S3-compatible storage + Dropbox was the list: github.com/icidasset/ongaku-ryoho-v1?tab…
