wireapp / wireapp/wire-webapp

Delivered Status Gone After Update 2024-04-11-production.0

Open
#17,276 11 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

status: in-process type: bug / fix 🐞
Dominant language
TypeScript
Stars
1.2k
Forks
307
Avg merge
17h 44m
Merged PRs (30d)
256

Description

Hello,

Before Update 2024-04-11-production.0 there was a "Delivered" status next to each message and now it's gone.

There's nothing in the changelog about it, so I'm guessing that it's a bug (probably related to the new 100% width of the messages) or it was moved to the "Read Receipts" code, which works only if activated by each contact.

In either case - please bring it back, because this is a complete downgrade.
If it has become part of the "Read Receipts" - that is not the right place for it.

I do not really care if someone has read a message or when they've read it (in case such info is provided (I've never used this option)), but I do really care whether the message has been delivered or something happened during delivery.

For example I'm often sending messages that do not require an answer, but I still need to know that the other party has received them (and search for other means of communication with them if they haven't received them after a certain period).

It's not realistic to ask each of my contacts to enable read receipts and if you're worried about spamming - make the "Delivered" status available only for people in our contacts list.

In case it matters - this happens both in a browser and the latest for the moment version of the desktop client.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the missing “Delivered” status in the browser and desktop client, then compare message delivery indicators with the Read Receipts behavior introduced around 2024-04-11-production.0. Done means restoring a distinct delivered indicator without requiring contacts to enable read receipts, and confirming it works in both clients.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
frontend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.