Sharing data #4

New issue

Open

opened 2026-05-25 13:45:43 +00:00 by erik · 0 comments

erik commented

2026-05-25 13:45:43 +00:00

Owner

In general settings, a user can configure credentials to their object storage service. Unlike the other simpler credentials that can be configured, this will be more involved: credentials, publish (bool), name (str), secret (str)
In general settings, a user can subscribe to multiple webbits cloud storage.
For webbits that want to participate in this kind of sharing, there is an actions menu option that loads a dialog that lists their subscribed storages. Clicking loads that data into user's localStorage but under a separate name so that both their items and their peer's items are shown.
When a peer's items are loaded, then we need to indicate the owner.
A user can import peer items into their own storage.
When remote storage is configured, there needs to be a "Save" action menu. Loading remote storage can simply use the existing "load from url" functionality. When saving, it needs to be namespaced to the user so that a single remote storage can work for multiple users.

The idea is that users will have a relatively small number of remote storages they subscribe to. The model is federation. Typical uses would be one person in a family sets up remote storage and grants access to family members, similar for a group of friends or colleagues.

For things like gear-closet & camp-jam, it would be nice if data could be shared so others can view and import into their local storage. The shared remote would also serve as a cloud backup. Object storage seems like the obvious choice, probably something like Cloudflare's R2. Brainstorming random thoughts: - In general settings, a user can configure credentials to their object storage service. Unlike the other simpler credentials that can be configured, this will be more involved: credentials, publish (bool), name (str), secret (str) - In general settings, a user can subscribe to multiple webbits cloud storage. - For webbits that want to participate in this kind of sharing, there is an actions menu option that loads a dialog that lists their subscribed storages. Clicking loads that data into user's localStorage but under a separate name so that both their items and their peer's items are shown. - When a peer's items are loaded, then we need to indicate the owner. - A user can import peer items into their own storage. - When remote storage is configured, there needs to be a "Save" action menu. Loading remote storage can simply use the existing "load from url" functionality. When saving, it needs to be namespaced to the user so that a single remote storage can work for multiple users. The idea is that users will have a relatively small number of remote storages they subscribe to. The model is federation. Typical uses would be one person in a family sets up remote storage and grants access to family members, similar for a group of friends or colleagues.

erik added the

labels