It would be desirable to have Rostra allow a user to share small config files through some Rostra Events

[vishalxl]

(I'm thinking in terms of Nostr, where we have events, and a user writes signed events. I understand that even Rostra works on similar principle, though details may be different. )

If a user were to share a file as a base64 data in payload, with meta data for file shared in event type ( meta data would be file extension, file name, size in bytes, last modified, and other such details), then Rostra could be used to share files by the user.

Since a rostra client is also a server, the server can allow a user to download a file too.

This would be useful if I wanted to share some small config files, files less than 1000 bytes, and such.

Of course, nothing precludes a user from sharing larger files.

Also, its also then possible to present a 'html' file as a page in its own right.

All this requires work, I am just presenting an idea....

[dpc]

If a user were to share a file as a base64 data in payload,

Why base64? Rostra uses binary encoding, so can encode arbitrary binary payloads with no overheads, and even guarantee incremental verification during transmission using verified streaming using BAO.

This would be useful if I wanted to share some small config files, files less than 1000 bytes, and such.

It's possible to share even huge files. Default client has limits because it's currently used for social media only, but underlying code is meant to handle use cases like this just fine.

All this requires work, I am just presenting an idea....

The use case here is unclear to me though.

I want to support file sharing/publishing, so e.g. attachmenets could be added to social posts, but also was thinking about any other form of sharing larger payloads.

But what you seem to describe seem more like just pasting a snippet of code, which can already be accomplished using three backticks Markdown syntax, like this: https://rostra.me/ui/post/rse1okfyp4yj75i6riwbz86mpmbgna3f7qr66aj1njceqoigjabegy/QK7FZ4NZCZFAX5RM24DNJT5VEA

[vishalxl]

Usecase of what I mentioned as 'config files' is when you have an application that you use on two computers, which work on same 'config file'.

For example, I have a fluent RSS reader. It has a .opml config file, which can be read from, and written to by the reader.

I want to use the same file on two laptops, or even an android app. And both endpoints may want to update it.

There are many such applications which need such 'file synchronization solutions' for their files. They use WebDav, even DropBox ( SuperProductivity uses Dropbox).

If they could use Rostra, many such open source applications could be changed to use Rostra files.

The simplest way to start is to make it read-only initially. Lets say I want to share some .torrent file or .opml file with some people I know.

[dpc]

Usecase of what I mentioned as 'config files' is when you have an application that you use on two computers, which work on same 'config file'.

For example, I have a fluent RSS reader. It has a .opml config file, which can be read from, and written to by the reader.

I want to use the same file on two laptops, or even an android app. And both endpoints may want to update it.

I use Syncthing for these sort of things, I highly recommend. I generally revision all my dotfiles and config files in a git repo, and then use dot file linker to put links in the right places, but it can be lined directly too.

If they could use Rostra, many such open source applications could be changed to use Rostra files.

I don't think this mixes well with Rostra's social-aspects. As in - events are supposed to be somewhat time-based, and forming a graph, and then copied between social graph. In practice, it would appear somewhat unreliable and confusing.

The simplest way to start is to make it read-only initially. Lets say I want to share some .torrent file or .opml file with some people I know.

How the UX here work? In particular contrasted with sharing such files over email or posting them as an attachment to a Rostra social post? Is automatic change syncing expected, etc.?

Notably with Syncthing one could achieve something like that - a shared folder between friends, with live sync.