Live data from Hacker News

Show HN: Capsule – Single-file web apps that save their data into SQLite

withcapsule.app

171–178 of 178 posts

Re: Show HN: Capsule – Single-file web apps that save their data into SQLite

#171
post #165

Neat! Another way to achieve something like this is Cosmopolitan C Compiler, Actually Portable Executables. For example, Redbean. (Jart, all of your certs are bad! I can't open your websites any more!) http://justine.lol/ It's a binary that can run on Windows, Mac, Linux, and it is also a zip file. The application can read the zip file and on several systems (not Windows), it can self-modify the zip file. Including h…

I have been meaning to use Justine's RedBean to build a "project app" (kind of like what the OP describes, but leaning more towards something like Datasette). It would contain the data, the paper(s), and the UI for interacting with the data (and supporting scripts or R that can be run with other tools). I just like the idea of a portable single-file scientific artifact. (also another call for jart to fix their certs!…

I'm kind of exhausted...

I want to sick Claude on porting tsnet to a C/C++ library that can run in a fat binary Actually Portable Executable.

And then I want to use tailscale share / tailscale funnel APEs for... everything...

Like... everything. So many things.

Re: Show HN: Capsule – Single-file web apps that save their data into SQLite

#173
post #159
post #60

> but trying to save data required hosting it somewhere With the File System Access API, webpages nowadays can read and write local files just like desktop applications: https://developer.chrome.com/docs/capabilities/web-apis/file... Try this text editor for example: https://googlechromelabs.github.io/text-editor/ It works nicely on Desktop and Mobile.

it's not only about saving data but easily sharing too. I think the capsule file is great for sharing one's work without the hassle of hosting.

Ease of backup too. One of the issues I take with browsers allowing web apps to save data locally is that they don’t also expose a way to easily locate the data in the filesystem or export it, and to my knowledge on-disk format isn’t standardized and so portability between browsers is also a concern.

The effect of this is that unless the user uses migration assistants or similar when upgrading to a new computer is that they’ll lose all local web app data. To me to this feels like a serious problem but when it’s brought up it tends to be hand waved away.

Re: Show HN: Capsule – Single-file web apps that save their data into SQLite

#175

Earlier quoted context omitted.

It's not using the File System Access API, on Firefox it uses for file-picking, and the save just downloads it. It's not synchronizing anything with your filesystem.

Do you know the reason for that? The File System API does seem to be well supported on Firefox: https://developer.mozilla.org/en-US/docs/Web/API/File_System...

[dead]

Re: Show HN: Capsule – Single-file web apps that save their data into SQLite

#176
post #169
post #158

Earlier quoted context omitted.

> Firefox unfortunately does not support the File System Access API. I would not call it unfortunate. Browsers should not have access to the file system, USB ports, etc. Perhaps in "PWA"s, if the user has a way of giving and withdrawing consent.

Why shouldn’t browsers have these capabilities..?

It's unsafe and allows for even more privacy invasion.

Re: Show HN: Capsule – Single-file web apps that save their data into SQLite

#177

I love this idea! One of the fallouts from widespread AI adoption that I've seen: They're very good at creating visual artifacts, but if you ever have to provide data in those artifacts, you don't really have a great way to share it without hard coding it. > One downside with this approach is that multiple people working on it will create different copies. To make it possible to merge different copies of the same fil…

Each document record is saved with UUID and timestamps. When deleting a record the data is removed but the record keeps a tombstone so only the ID remains. For conflicts currently the newest one is used, but there will be a merge like UI in the future to confirm which one to use.

[dead]
Post reply on HN