file-system-access VS notabase

You can read about the privacy concerts the community group published [1].

[1]: https://wicg.github.io/file-system-access/#privacy-considera...

WHATWG File System Standard provides a means to write directories and files to the private origin storage associated with a Web page origin. If you want you can use WICG File System Access API to write data directly to your filesystem in the browser. WHATWG File System Standard uses the same FileSystemDirectoryHandle and FileSystemFileHandle defined by File System Access API.

Chromium-based browsers support File Systeam Access API.

We have stopped using the file system access API: https://github.com/WICG/file-system-access/issues/401

Where file handling is concerned, there are at least

- File System Access API, https://wicg.github.io/file-system-access/

- File Handling, https://github.com/WICG/file-handling/blob/master/explainer....

- Origin Private File System, https://github.com/WICG/file-system-access/blob/main/AccessH...

There was also Storage Foundation API to which the reaction was "I don't think it's an acceptable outcome for the web platform to have that many ways to work with files" :) https://github.com/mozilla/standards-positions/issues/481 This one never saw the light of day.

Huh. Disregard what I wrote entirely, then. Reading through https://github.com/WICG/file-system-access/blob/main/AccessH..., I can see how they’ve bypassed most of the problems I saw—I was making unnecessary assumptions.

Thank you for correcting me.

> Browsers have never let anything (not even JS) have raw access to the host FS

I'm not sure what you mean by "raw access", but the File System Access API certainly allows web applications to do a lot of things.

> The File System Access API (formerly known as Native File System API and prior to that it was called Writeable Files API) enables developers to build powerful web apps that interact with files on the user's local device, like IDEs, photo and video editors, text editors, and more.

https://web.dev/file-system-access/

> After a user grants a web app access, this API allows the app to read or save changes directly to files and folders on the user’s device. Beyond reading and writing files, this API provides the ability to open a directory and enumerate its contents. Additionally, web apps can use this API to store references to files and directories they’ve been given access to, allowing the web apps to later regain access to the same content without requiring the user to select the same file again.

> Additionally this API also makes it possible for websites to get access to some directory without having to first prompt the user for access.

https://wicg.github.io/file-system-access/

It's not just a draft, it's been part of Chrome since version 78 in 2019.

> After a user grants access, this API allows web apps to read or save changes directly to files and folders on the user's device. It does all this by invoking the platform's own open and save dialog boxes.

https://blog.chromium.org/2019/09/chrome-78-beta-new-houdini...

Discussion at the time:

https://news.ycombinator.com/item?id=21032537

In the post, the Vite webserver is only used to serve the HTML and JS static files to the browser. When the user saves or opens text files, the code uses the web File System Access API (https://wicg.github.io/file-system-access/) to interact with the user file system.

Have you heard of Project Fugu and their idea of a File System Access API in the browser? https://wicg.github.io/file-system-access/

I don't know a C++ equivalent of HTML , prompt(), or File System Access API (https://wicg.github.io/file-system-access/; https://web.dev/file-system-access/) using JavaScript in the browser window.

https://notabase.io - a note-taking app for networked thinking.

It supports page stacking, linked references, block references, a graph view, and all that good stuff. Think of it as similar to Roam Research / Obsidian.

It's also open source so you can self-host it. Here's the code: https://github.com/churichard/notabase

I'm hoping to add support for shareable links soon. Open to other ideas or feedback!

you can check out this page https://alternativeto.net/software/joplin/?platform=online but the best I could find are - https://www.taskade.com/ https://standardnotes.com/ https://notesnook.com/ https://bundlednotes.com/ https://diaroapp.com/ https://notabase.io/ https://boostnote.io/ etc.

When evaluating rich text editors for the note-taking app I started about a year ago (https://notabase.io), I ended up going with Slate because of its flexible schema and customizable plugin architecture.

I sort of regret that choice now. I ran into a lot of bugs when integrating it which I had to manually work around; issues go months without being addressed; and there still isn't good cross-platform support, especially for Android. With a more active contributor base, Slate could be a fantastic library, but I get the feeling that it's in maintenance mode now, with not many major changes in the past year and a v1.0 still far in the future.

Tiptap looks like it might be a good choice now, but I find it off-putting that I can't insert links in the demo editor on Tiptap's website (https://tiptap.dev), especially for my use case (a note-taking app whose core concept revolves around links).

I'm working on an open source note-taking app called Notabase [1]. It's built primarily for my use - I just never liked most existing note-taking apps and wanted to make one that fit the way that I think. I made it open source [2] so other people can build on top of my ideas, and released a hosted version so that other people can use it if they like it. It would be nice if other people found it helpful, but regardless it's something that I intrinsically enjoy working on.

[1]: https://notabase.io

You can try Notabase https://notabase.io/, which is better for self-hosting.

if you prefer mdSilo, need to toggle the Offline mode false in code and use the third-part services: vercel and supabase