-
-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Read reciepts are not actually sent toward hangouts #44
Comments
Ether |
Got it, so then this is more of a support question instead of an actual bug. I'll try ephemeral_events and let you know (I didn't really know what it did before). |
Hmm, nope. ephemeral_events doesn't seem to do anything.
|
Did you regenerate the registration and restart synapse after enabling ephemeral events? |
I'm not quite sure if this is related, but with ephemeral events I get this in the log:
|
Same, i just regenerated my registration and was greeted by these errors. FWIW this bug is still ongoing, my hangouts still has bolded rooms. |
The features checklist mentions
Matrix → Hangouts
/[x] Read receipts
.But I don't think this is working:
Whenever I read a recieved hangouts message from matrix, while my matrix client will have "seen" the message (matrix room no longer bolded), I don't see the same for the my avatar from hangouts (no
Seen by $MyName (Hangouts) (@hangouts_5454543:example.com)
).If i load up the official hangouts, the room that I just "seen" in matrix is still bolded. My hangout friends will always think I never read their messages, despite sometimes replying.
If I "read" the new message there it will of course unbold itself in hangouts. And then in matrix I also notice my hangouts avatar update its read reciept.
Seen by $MyName (Hangouts) (@hangouts_5454543:example.com)
moves the last message.Read reciepts seem to work perfectly fine toward matrix, but they don't really work toward hangouts. It's as if
Seen by $MyName
should perfectly follow my matrix user that it's representing.The text was updated successfully, but these errors were encountered: