@itsfoss I miss a #virtualFS (#openvfs)approach like nextcloud, dropbox and onedrive use on Windows. In best case it is independet usable on all kind of network storage like sftp, nfs or smb.
I miss,
- the possibility to have auto cached network files
- the possibility to have some files or directory permanently in sync
I hate it that a linux laptop even with VPN is not able to stay connected to a network folder especialy if you work with hibernation.
@gnulinux
Ich finde es schade, dass es auf Linux kein #VirtualFS gibt. #OpenVFS hat es nie in den Relase von #NextcloudClient geschafft:
https://github.com/dragotin/openvfs
Zur Dateisynchronisierung gibt es wohl ein Zuschaltbares performance Backend.
https://help.nextcloud.com/t/setting-up-files-high-performance-backend/108651
Bei den Bildern bin ich auch voll dabei. Mich stört vor allem, dass die Galerie nicht konfigurierbar ist. Es gibt bei mir Ordner, die nicht indexiert werden dürften.
#ReleaseWednesday Just pushed a new version of https://thi.ng/block-fs, now with additional multi-command CLI tooling to convert & bundle a local file system tree into a single block-based binary blob (e.g. for bundling assets, or distributing a virtual filesystem as part of a web app, or for snapshot testing, or as bridge for WASM interop etc.)
Also new, the main API now includes a `.readAsObjectURL()` method to wrap files as URLs to binary blobs with associated MIME types, thereby making it trivial to use the virtual filesystem for sourcing stored images and other assets for direct use in the browser...
(Ps. For more context see other recent announcement: https://mastodon.thi.ng/@toxi/114264980961483146)
#ThingUmbrella #BlockStorage #FileSystem #BlockFS #VirtualFS #CLI #TypeScript #JavaScript #OpenSource
#ThingUmbrella #ReleaseTuesday... New package (initial alpha release):
https://thi.ng/block-fs provides highly customizable & extensible block-based storage with an optional hierarchical filesystem layer. This is useful everywhere you might need virtual filesystem, though the storage providers can also be used without the filesystem layer (e.g. for #Forth-style block data/editors).
The default configuration provides:
- arbitrarily nested directories
- filenames (UTF-8) of max. 31 bytes per directory level
- max. 32 owner IDs
- file locking
- creation/modification timestamps (64 bit)
- efficient append writes
Currently included storage providers: TypedArray-based in-memory and host filesystem based file storage (one block per file). More are planned (e.g. IndexedDB, remote endpoint)...
The readme is currently still lacking various diagrams to illustrate the filesystem internals. I will add those ASAP...
