Edit messages about oasis

[cinnamon-bun]

We have a responsibility to let users know this is only cosmetic; their old message will still be available in the feed. Otherwise they might think that e.g. editing away personal information will be effective.

But overall I'm excited to try this! I have a lot of questions but that doesn't mean I'm opposed:

This would be the first client using the edit plugin? https://github.com/fraction/ssb-edit/network/dependents

Is there a spec for these edit messages? The ssb-edit code looks like a view for indexing them but doesn't describe the format for publishing them, and the expected semantics around them. Has this format been discussed w/ the community?

What types of messages can be edited?

Can anyone edit a message or is it limited to the original author?

I think the index uses the last edit message in the order provided by flume. If using ssb-ooo, could the messages be out of order so that the wrong one is chosen?

It looks like editing is done by publishing a type: edit message which is expected to supersede the original. Those messages will be invisible in most clients. Could it be more backwards-compatible to publish the edits as regular message types, with an additional key like replaces: "%abc... ", so that they will visible in older clients (graceful degradation style).

Some other message types are already editable e.g. the last one is considered to supersede the previous ones (about, gathering, contact). Do they have a uniform format for referring back to the thing they're replacing?

(sorry for the wall of questions, this feels like an ecosystem-level decision to make with care)

[jedahan]

How about a delayed post plugin? Make it all client-side. One implementation could post to your local feed, but filter that message in gossips until post time + (1 hour? 15 minutes?). If a post is edited, roll back, recalculate hashes, and re-add to feed.

[christianbundy]

How about a delayed post plugin?

We could safe it as a pending draft, but once you introduce a message to the flumedb views you can't remove it without rebuilding all of your indexes. What do you think about having the ability to edit?

[cinnamon-bun]

How about a delayed post plugin? Make it all client-side. One implementation could post to your local feed, but filter that message in gossips until post time + (1 hour? 15 minutes?). If a post is edited, roll back, recalculate hashes, and re-add to feed.

If the user posts and then turns off their computer, their message won't get published. This could be ok if the delay is very short (10 seconds?) and there's clear communication about this in the UI.