nip-10: fix duplicate replies in feed
#60
Merged
offbyn
merged 1 commits from duplicate-replies
into master
1 year ago
Loading…
Reference in New Issue
There is no content yet.
Delete Branch 'duplicate-replies'
Deleting a branch is permanent. It CANNOT be undone. Continue?
some replies rendered twice in different positions, seems to be
related to deprecated positional event tags and a regression
introduced in
a596121821
added 2 new functions to get reply to and replies of an event.
these functions are not pretty but should follow nip-10 with
correct fallback.
example event that had some replies rendered twice:
22e4ea80161ac591059da611d3ab63c583cb1d47a706826db2fc6955ac0a70b5
@ -697,0 +736,4 @@
// nip-10: fallback to deprecated positional 'e' tags
return eventTags.at(-1)[1] === evt.id;
}
);
so ugly 🙈
now it does that on every render. thinking about it again, it would be better to read and transform the data when receiving events, instead.
nip-10: fix duplicate replies in feedto draft: nip-10: fix duplicate replies in feed 1 year ago522f117d82
tof33639fa60
1 year agof33639fa60
to2e40a273c4
1 year agodraft: nip-10: fix duplicate replies in feedto nip-10: fix duplicate replies in feed 1 year ago2e40a273c4
into master 1 year ago2e40a273c4
.Step 1:
From your project repository, check out a new branch and test the changes.Step 2:
Merge the changes and update on Gitea.