Synchronization of notifications

[dschrempf]

Hi!

I can pull notifications, list them, and change their status. In particular, I set some notifications in the inbox to done.

However, these state changes (e.g., unread -> done), do not propagate to the upstream forge (GitHub in my case), and I fail to find a function that "pushes notification chagnes" (similar to forge-post-submit).

Also, when I pull notifications again (after locally marking unreads as done), they become unread again (which is expected, in a way, since the changes were not propagated to the forge).

Is there a way to push notification state changes to the forge?

Thank you!

[tarsius]

I am painfully aware of this. I have drafted many rants about it but was wise enough to not publish them. However, it does seem like I erred too much on the side of caution, or at least I couldn't find anything about it in the manual in a minute or two.

This is the fault of managers at Github/Microsoft. I always had troubles attributing this to incompetence because it reeks of malice. A few days ago, someone finally published what to me is the smoking gun. It appears they intentionally do not provide the necessary functionality in the API to keep an edge over third-party clients. Some developer at Github was not aware of this and implemented it anyway, but that tactical error was quickly corrected.

[dschrempf]

This is so sad. Thanks a lot for all your great work!

[dschrempf]

Not sure if that helps, but there seem to be REST endpoints that could achieve this (at leat for GitHub):
https://docs.github.com/en/rest/activity/notifications?apiVersion=2022-11-28#mark-a-thread-as-done

[dschrempf]

Also maybe relevant: https://github.com/meiji163/gh-notify/blob/556df2eecdc0f838244a012759da0b76bcfeb2e7/gh-notify#L508C1-L509C1