Server-side grouped notifications #528

Open
opened 2024-08-15 02:13:56 +00:00 by shadowfacts · 1 comment
Owner

Mastodon 4.3+

Mastodon 4.3+
shadowfacts added the
enhancement
label 2024-08-15 02:13:56 +00:00
shadowfacts added this to the 2025.2 milestone 2024-08-15 02:21:16 +00:00
Author
Owner

Some API changes necessary to have feature parity, see https://github.com/mastodon/mastodon/discussions/31618.

Client-side grouping will continue to exist indefinitely to support old instances/other software.

Server-side grouping interferes with #245 and #235, possibly have a preference for client vs. server. I'm not sure which should be the default.

Only fav/reblog notifications are server-side grouped currently. We want to keep grouping follows, so need some sort of hybrid approach. Would also help with #245 and #235.

Some API changes necessary to have feature parity, see https://github.com/mastodon/mastodon/discussions/31618. Client-side grouping will continue to exist indefinitely to support old instances/other software. Server-side grouping interferes with #245 and #235, possibly have a preference for client vs. server. I'm not sure which should be the default. Only fav/reblog notifications are server-side grouped currently. We want to keep grouping follows, so need some sort of hybrid approach. Would also help with #245 and #235.
Sign in to join this conversation.
No Milestone
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: shadowfacts/Tusker#528
No description provided.