Edit message

[erlend-sh]

Editable posts will be a nice little win that goes a long way to show that ‘we’re not your regular Bluesky app’, hehe.

Eventually we might wanna keep revisions of edits as well, if the storage is light enough.

[zicklag]

Eventually we might wanna keep revisions of edits as well, if the storage is light enough.

We don't have a choice actually. 😄 Everything in automerge is remembered. The overhead is less than making another chat, so no biggie at all. We can actually support edits right now, all we need is the UI!

[zeucapua]

@zicklag How would I implement a function to know whether or not a message has been edited? And will the autodoc be remembered every time channel.change((doc) => {}) is called and the doc changed?

[zicklag]

There are two ways to respond to changes.

• You can use the channel.view in a svelte $effect() and it will re-run the effect when the doc changes.
• The autodoc is an event emitter, so you can use channel.addEventListener('change', event => {}) and channel.removeEventListener().

And yes the autodoc is automatically saved and synced every time that we change it.

So editing shouldn't need any special handling. Just use channel.change to modify the doc and everything else should be handled.

[jshnjovu]

Is roomy opensource, can I contribute ? *Joshua Njovu* AI/ML Platform Engineer Senior Software Engineer +254 751 098722 |+254 751 098722 | LinkedIn <https://www.linkedin.com/in/njovu-joshua/>|StackOverflow <https://stackoverflow.com/users/3384760/joash> ***@***.*** ***@***.*** ***@***.***

…

On Sun, Feb 9, 2025 at 6:32 PM Zicklag ***@***.***> wrote: There are two ways to respond to changes. - You can use the channel.view in a svelte $effect() and it will re-run the effect when the doc changes. - The autodoc is an event emitter, so you can use channel.addEventListener('change', event => {}) and channel.removeEventListener(). And yes the autodoc is automatically saved every time that we change it. So editing shouldn't need any special handling. Just us channel.change to modify the doc and everything else should be handled. — Reply to this email directly, view it on GitHub <#39 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BL74KSF635LJ3WV2OOJQA432O5YHXAVCNFSM6AAAAABWPQ2QBKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNBWGM2TQNJRGQ> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[zicklag]

@jshnjovu Yes roomy is Open Source, and yes you can contribute!

Let us know if there's something specific you'd like to work on. We've also got a Discord channel or a Matrix room if you want to chat. ( We don't have public chat on Roomy just yet, but it's coming. 😀 )

[verdverm]

Will Roomy support full deletes, like posts from Bluesky on ATProto?

(such that you cannot go into the CRDT history to recover deleted messages)

[zicklag]

Will Roomy support full deletes, like posts from Bluesky on ATProto?

Good question. Once Beelay comes out for Automerge and we start using that, we are considering making each chat message it's own automerge document. If that works out, then it should be possible for us to request that a chat message be deleted, but just like on AtProto, nothing can force all clients or subscribers to actually delete it permanently. The official app would respect the request, of course.

Since the chat message itself would be in a different automerge document, the chat won't be in the Roomy channel's CRDT so we don't have to worry about the CRDT history. The history will just show the ID of the message that was there, and, when deleted, it could replace the message with a marker that requests client no longer retain the automerge document for the chat message.