In this post, I explore the potential of the File System Access API to create local-only web experiences. I discuss how this API, combined with tools like Logseq, allows for on-device data storage outside the browser sandbox. While exciting, I also acknowledge the current limitations, such as the need to re-grant file access on refresh, the lack of a visual indicator for local-only sites, and the difficulty of preventing data exfiltration entirely. Despite these challenges, I believe this area holds significant potential and deserves further exploration.
Persistent Storage Options
This API provides database persistence via localStorage/sessionStorage and, in compatible browsers, the Origin-Private FileSystem.
Local PDS - Storing your data on your machine
This project aims to store your data on your device. The current implementation uses Chrome localstorage. View the README for more details while I work on this site...
LocalSend: Share files to nearby devices
LocalSend is a free, open-source, cross-platform file sharing tool that allows you to share files to nearby devices.
wander
A tiny, decentralised tool you can host with just two files to explore the small web
Wildland (@WildlandIO) on X
An open protocol for data management that allows users to have sole ownership of their data. Join us! https://t.co/AqwplMcG9u Developed by @GolemFoundation
Intent to Prototype: Isolated Web Apps
https://github.com/reillyeon/isolated-web-apps/blob/main/README.md
Local-first software: you own your data, in spite of the cloud
As part of the Digital Library's transition to Open Access, new features for researchers are available in the Premium Edition. Click here to learn more.
Web dev is fun again with ATproto · Web Dev Challenge S3.E4
Local-first software: You own your data, in spite of the cloud
A new generation of collaborative software that allows users to retain ownership of their data.
Local-first software: You own your data, in spite of the cloud
A new generation of collaborative software that allows users to retain ownership of their data.
Local-First Software: Taking Back Control of Our Data | a mini-doc
@same.supply
↩️ reply to @same.supply: also kinda works with local files, but file management and sync are making me question if the benefits of "web distribution" are worth the headache of web permissions
new data diary! this is the most in the weeds yet, all revolving around our proposed URI structure for permissioned data. turns out you can figure out a lot about a protocol from the uri! as always, let me know what you think :)
Permissioned Data Diary 5: What’s in a Name?
dholms.leaflet.pubOnce again looking at bring your own user-data storage options (for my malleable software experiment this time). What do people think are some user friendly options that don't require any OAuth apps to be created on the server? ie. no Dropbox, Google Drive, One Drive & other services like that.
Web Files
Interoperable web-files and ejectable apps.
DASL: Web Tiles
Web Tiles
Nothing new under the sun: everything is a file
A Social Filesystem — overreacted
File Over App: A Philosophy for Digital Longevity
Ejectable Apps
