coracle/flotilla
1
3
Fork 9
Code Issues 34 Pull Requests 1 Actions Packages Projects 5 Releases Wiki Activity

feat: show per-relay publish status on outgoing messages #290

Merged
hodlbod merged 1 commits from userAdityaa/flotilla:feat/per-relay-message-delivery-status into dev 2026-06-04 21:10:00 +00:00
Conversation 8 Commits 1 Files Changed 4
+83 -40
userAdityaa commented 2026-06-01 10:08:34 +00:00
Collaborator
Copy Link
Copy Source

Summary

Outgoing messages in DMs and rooms now show a delivery status row (sending, delivered, partial, failed) with colored icons and neutral text. Tapping a completed status opens a per-relay breakdown with errors and per-relay retry. Desktop chat views get bottom padding so the last message and status row clear the compose bar.

Closes #56.

Screenshots

Screenshot 2026-06-01 at 3.27.07 PM.pngScreenshot 2026-06-01 at 3.27.18 PM.pngScreenshot 2026-06-01 at 3.30.20 PM.png

### Summary Outgoing messages in DMs and rooms now show a delivery status row (sending, delivered, partial, failed) with colored icons and neutral text. Tapping a completed status opens a per-relay breakdown with errors and per-relay retry. Desktop chat views get bottom padding so the last message and status row clear the compose bar. Closes #56. ### Screenshots <img width="711" alt="Screenshot 2026-06-01 at 3.27.07 PM.png" src="attachments/465cd7e4-f164-44dd-aabb-71fe3462492d"><img width="711" alt="Screenshot 2026-06-01 at 3.27.18 PM.png" src="attachments/aafe735e-0044-4166-9402-ea616c5e3aaf"><img width="709" alt="Screenshot 2026-06-01 at 3.30.20 PM.png" src="attachments/95a2c80b-238c-4045-8a81-f659d41c1b37">
Screenshot 2026-06-01 at 3.27.07 PM.png
186 KiB
Screenshot 2026-06-01 at 3.27.18 PM.png
180 KiB
Screenshot 2026-06-01 at 3.30.20 PM.png
186 KiB
hodlbod commented 2026-06-01 15:52:46 +00:00
Owner
Copy Link
Copy Source

This is a regression of a lot of behavior that is subtle but deliberate. Biggest thing is that there should be no success messages — only pending and failure. So the restructure of ThunkStatus etc is unnecessary, this issue is pretty much just about changing how failure renders to show more information.

This is a regression of a lot of behavior that is subtle but deliberate. Biggest thing is that there should be no success messages — only pending and failure. So the restructure of ThunkStatus etc is unnecessary, this issue is pretty much just about changing how failure renders to show more information.
👍 1
userAdityaa force-pushed feat/per-relay-message-delivery-status from d2f2263676 to 39a58910f8 2026-06-02 05:57:13 +00:00 Compare
userAdityaa commented 2026-06-02 06:03:36 +00:00
Author
Collaborator
Copy Link
Copy Source

Yeah, I felt the same about not including all of those. However, from the discussion here, my understanding was that we had agreed to show those status messages, so I went ahead and implemented them. I've reverted those changes now, and currently only the pending and failed states are shown.

Yeah, I felt the same about not including all of those. However, from the [discussion here](https://gitea.coracle.social/coracle/flotilla/issues/56#issuecomment-2527), my understanding was that we had agreed to show those status messages, so I went ahead and implemented them. I've reverted those changes now, and currently only the pending and failed states are shown.
👍 1
hodlbod reviewed 2026-06-02 15:53:45 +00:00
hodlbod left a comment
Owner
Copy Link
Copy Source

Makes sense, I didn't even notice that change in the mockup.

  • On line 21 of ThunkFailure, the aborted urls are never relevant, because if the thunk was aborted its event will have been removed from the repository and it won't be visible.
  • I don't think the manual management of the popover is necessary, I think hiding on hide is probably the default behavior.
Makes sense, I didn't even notice that change in the mockup. - On line 21 of ThunkFailure, the aborted urls are never relevant, because if the thunk was aborted its event will have been removed from the repository and it won't be visible. - I don't think the manual management of the popover is necessary, I think hiding on hide is probably the default behavior.
👍 1
src/app/components/ChatMessage.svelte
@@ -125,6 +122,9 @@
<Content showEntire {event} />
</div>
</TapTarget>
{#if isOwn && thunk}
hodlbod commented 2026-06-02 15:49:23 +00:00
Owner
Copy Link
Copy Source

This check is redundant, there will never be a thunk for an event not by the current author.

This check is redundant, there will never be a thunk for an event not by the current author.
👍 1
hodlbod marked this conversation as resolved
src/app/components/RoomItem.svelte
@@ -128,3 +128,2 @@
<RoomItemContent {url} event={$innerEvent ?? event} />
{#if thunk}
<ThunkFailure showToastOnRetry {thunk} class="mt-2 text-sm" />
{#if event.pubkey === $pubkey && thunk}
hodlbod commented 2026-06-02 15:49:20 +00:00
Owner
Copy Link
Copy Source

This check is redundant, there will never be a thunk for an event not by the current author.

This check is redundant, there will never be a thunk for an event not by the current author.
👍 1
hodlbod marked this conversation as resolved
src/app/components/ThunkStatus.svelte
@@ -16,0 +31,4 @@
const successUrls = $derived(getThunkUrlsWithStatus(PublishStatus.Success, $thunk))
const failedUrls = $derived([
...getFailedThunkUrls($thunk),
...getThunkUrlsWithStatus(PublishStatus.Aborted, $thunk),
hodlbod commented 2026-06-01 15:50:20 +00:00
Owner
Copy Link
Copy Source

This isn't necessary, if a thunk is aborted the event is removed from the repo and will not appear.

This isn't necessary, if a thunk is aborted the event is removed from the repo and will not appear.
👍 1
hodlbod reviewed 2026-06-02 15:56:08 +00:00
src/app/components/ThunkStatusDetail.svelte
@@ -25,0 +70,4 @@
return
}
}
hodlbod commented 2026-06-02 15:56:06 +00:00
Owner
Copy Link
Copy Source

Why inline this instead of pass retry through?

Why inline this instead of pass retry through?
👍 1
userAdityaa force-pushed feat/per-relay-message-delivery-status from 39a58910f8 to fb3d9f3923 2026-06-03 17:14:04 +00:00 Compare
hodlbod reviewed 2026-06-03 17:27:00 +00:00
src/routes/spaces/[relay]/[h]/+page.svelte
@@ -471,3 +471,3 @@
onscroll={onScroll}
class={cx(
"flex-col-reverse pb-0! pt-4",
"flex-col-reverse pb-0! pt-4 md:pb-8!",
hodlbod commented 2026-06-03 17:27:00 +00:00
Owner
Copy Link
Copy Source

This breaks on small screens

This breaks on small screens
hodlbod reviewed 2026-06-03 17:27:08 +00:00
src/routes/spaces/[relay]/chat/+page.svelte
@@ -319,3 +319,3 @@
</SpaceBar>
<PageContent bind:element onscroll={onScroll} class="flex flex-col-reverse pt-4 pb-0!">
<PageContent bind:element onscroll={onScroll} class="flex flex-col-reverse pt-4 pb-0! md:pb-8!">
hodlbod commented 2026-06-03 17:27:08 +00:00
Owner
Copy Link
Copy Source

This breaks on small screens

This breaks on small screens
userAdityaa force-pushed feat/per-relay-message-delivery-status from fb3d9f3923 to caf3f620e4 2026-06-03 19:53:26 +00:00 Compare
hodlbod reviewed 2026-06-03 23:12:39 +00:00
src/app/components/ChatMessage.svelte
@@ -67,4 +67,1 @@
{#if thunk}
<ThunkFailure showToastOnRetry {thunk} class="mt-1" />
{/if}
hodlbod commented 2026-06-03 23:12:39 +00:00
Owner
Copy Link
Copy Source

I think moving this may be causing the problem in the screenshot below.

I think moving this may be causing the problem in the screenshot below.
Screenshot 2026-06-03 at 4.11.39 PM.png
14 KiB
Screenshot 2026-06-03 at 4.11.39 PM.png
hodlbod reviewed 2026-06-03 23:14:49 +00:00
hodlbod left a comment
Owner
Copy Link
Copy Source

Looks good, just one more thing

Looks good, just one more thing
src/app/components/RoomItem.svelte
@@ -128,3 +128,3 @@
<RoomItemContent {url} event={$innerEvent ?? event} />
{#if thunk}
<ThunkFailure showToastOnRetry {thunk} class="mt-2 text-sm" />
<ThunkFailure showToastOnRetry {thunk} class="mt-1 flex justify-end" />
hodlbod commented 2026-06-03 23:13:01 +00:00
Owner
Copy Link
Copy Source

Or maybe this

Or maybe this
userAdityaa force-pushed feat/per-relay-message-delivery-status from caf3f620e4 to 7365fb7a35 2026-06-04 05:07:17 +00:00 Compare
userAdityaa force-pushed feat/per-relay-message-delivery-status from 7365fb7a35 to 6255dc2d39 2026-06-04 05:13:26 +00:00 Compare
hodlbod added 1 commit 2026-06-04 21:09:54 +00:00
feat: show per-relay failure, pending breakdown on outgoing messages 32cf909d45
hodlbod force-pushed feat/per-relay-message-delivery-status from 6255dc2d39 to 32cf909d45 2026-06-04 21:09:54 +00:00 Compare
hodlbod merged commit 4d57e4e6ed into dev 2026-06-04 21:10:00 +00:00
hodlbod deleted branch feat/per-relay-message-delivery-status 2026-06-04 21:10:00 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
hodlbod
Labels
Clear labels
design
For issues related to design work. Development should be done in another issue and refer back to this one.
 dev
Issues related to development work
 easy
Issues that can be executed on by new contributors
 idea
For issues that aren't yet actionable
 priority
For issues related to high priority features and bugs
 usability
Issues that have to be validated with real live human beings.
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
AQB hodlbod (hodlbod) mplorentz (Matt Lorentz) sakshamjain (Saksham Jain) sondreb triesap userAdityaa (Aditya Chaudhary)
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: coracle/flotilla#290
Delete Branch "userAdityaa/flotilla:feat/per-relay-message-delivery-status"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?