Implement /_matrix/client/v3/notifications #707
Labels
No labels
Blocked
Bug
Cherry-picking
Database
Dependencies
Dependencies/Renovate
Difficulty
Easy
Difficulty
Hard
Difficulty
Medium
Documentation
Enhancement
Good first issue
Help wanted
Inherited
Matrix/Administration
Matrix/Appservices
Matrix/Auth
Matrix/Client
Matrix/Core
Matrix/E2EE
Matrix/Federation
Matrix/Hydra
Matrix/MSC
Matrix/Media
Matrix/T&S
Meta
Meta/CI
Meta/Packaging
Priority
Blocking
Priority
High
Priority
Low
Security
Status
Confirmed
Status
Duplicate
Status
Invalid
Status
Needs Investigation
Support
To-Merge
Wont fix
old/ci/cd
old/rust
No milestone
No project
No assignees
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
continuwuation/continuwuity#707
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
Hello! Thanks for the amazing work :)
I hope I'm not doing something wrong. I have the server running. I can federate. Everything is good!
Except notifications. They are a bit unstable/inconsistent. And I'm trying to check if it's some configuration I have wrong.
When I curl
https://chat.filipesm.eu/_matrix/client/v3/notifications, I get the{"errcode":"M_UNRECOGNIZED","error":"M_UNRECOGNIZED: Not Found"}response. I think delegation is working becausehttps://chat.filipesm.eu/_matrix/federation/v1/version(for example) works.Am I doing something wrong?
Thanks!
We simply don't implement the endpoint at the moment.
Aha that sounds about right. Feel free to close this if you want :) Thanks!
Would be nice to get this one implemented at some point but im not aware of a client outside of cinny that uses this endpoint
Element has a lab for it but it's disabled by default, and they're not enabling it soon as it doesn't work well with e2ee
There is a grapevine MR open for this: https://gitlab.computer.surgery/matrix/grapevine/-/merge_requests/180/diffs
Might be worth taking a look at and seeing if we can implement a similar structure.
Olivia mentioned that there's an issue with pushers:
Unsure if we're affected by that
/_matrix/client/v3/notifications#1345