notifications are no longer being marked as read on GitHub

[benthamite]

Unfortunately, after a notification is read with gh-notify, it won’t be marked as read on GitHub, as used to be the case. I'm unsure whether this is linked to the recent forge changes or is unrelated to that issue. I tentatively think the latter, since I noticed this particular problem a couple of weeks after the forge problems.

[anticomputer]

Digging into this now, I noticed today also with the latest forge that a topic visit no longer marks things as read on the GitHub side.

[anticomputer]

So I'm seeing some beta endpoints being used for the unread/read marking on GitHub (/notifications/beta/mark and /notifications/beta/unmark). It looks like those SHOULD support bulk status changes through an array of topic IDs but not sure how/if we can leverage that clientside since it's undocumented. To that end I'm going to hold off on kludging together remote marking support for now. Presumably Forge is also in a similar posture, and ideally this gets implemented on the forge visit end once GitHub gets out of beta with the notification endpoints. I'll leave this open to track progress.