this repo has no description
Just an id
Signed-off-by: strawmelonjuice <mar@strawmelonjuice.com>
+8
+8
notes/notification resolver.md
+8
notes/notification resolver.md
···
1
+
> This is a far-future todo.
2
+
3
+
I notice on other social media platforms that when an edit or upload had unforseen consequences, this usually results in broken push notifications.
4
+
Notifications that lead to a 404.
5
+
6
+
Obviously, when creating a push notification for something we know nothing about this is what it is. But in Lumina these notifications lead to a postview using a json string after the # in the url (url hash).
7
+
8
+
That json string can obviously just contain a post or notification id, but we generate a preview of a post, and that preview should be pushed but not saved once again in the database. Instead, we add to the json object. Client holds an absolute reference to the post id, but also requests a post by both id and a part of it's preview. Lumina client should be smart enough to figure out what post this is even when the ID leads to a 404.