New ideas for metaframes

[dionjwa]

Local file system metaframe

Imagined user flow:

1. Start a deno server somewhere on your local file system, this would be the "root" of the exposed file system.
2. The local-fs metaframe communicates with this server, exposing the file structure downstream.

Another possibility is the local server talks to e.g. a glitch.com remote server with a random hash, and prints the metaframe URL for the user to copy in the metapage. This would allow others to share, at the cost of more setup and security risk.

Since files can easily be large blobs (that's the point), interacting with the metaframe would be via a kind of API:

flowchart LR
    subgraph metapage
        direction LR

        style mf1 fill:#fff,stroke:#32AEE4,stroke-width:2px
        style mf2 fill:#fff,stroke:#32AEE4,stroke-width:2px

        mf2["fs consumer"]
        mf1["fs"]
        mf2 --> |ls| mf1
        mf1 --> |file list| mf2
        
    end

Loading

flowchart LR
    subgraph metapage
        direction LR

        style mf1 fill:#fff,stroke:#32AEE4,stroke-width:2px
        style mf2 fill:#fff,stroke:#32AEE4,stroke-width:2px

        mf2["fs consumer"]
        mf1["fs"]
        mf2 --> |get file X| mf1
        mf1 --> |file blob ref| mf2
        
    end

Loading

Cloud file system

This is an iteration of the Local file system metaframe

Using some authorization mechanism, users can create a cloud fs (file system), and share it with select others.

Likely this makes sense to integrate into app.metapage.io directly to take advantage of sharing/groups etc.