aboutsummaryrefslogtreecommitdiffstats
path: root/tools/feed-wheel-reverse-test.js
diff options
context:
space:
mode:
authorAdam Soltys <[email protected]>2026-10-11 23:04:15 -0700
committerAdam Soltys <[email protected]>2026-10-11 23:04:15 -0700
commit2b83c3f46c0dc2da1bbd9854443d57de54b979ea (patch)
tree44cf2eb1b315f798894d81504248874a67297b71 /tools/feed-wheel-reverse-test.js
parent6eda01863920ae45d56a65563a7f956a429fced8 (diff)
downloadcoinosv3-2b83c3f46c0dc2da1bbd9854443d57de54b979ea.tar.gz
coinosv3-2b83c3f46c0dc2da1bbd9854443d57de54b979ea.zip
Feed: your newest post is in Following from the first ask, and a new post goes to the feeds it belongs to. Adam posted from the laptop with the #photography feed open and found the post in #photography (untagged) but not in Following, on either device, until a later refresh. Two causes. The feed's opening ask (prefetchFeed, and seedOtherFeeds) took only the first 400 of its authors, and your own key was added after the follows — with 898 follows it sat in the third chunk, so the opening ask never named you; the later refresh (feedPass, every chunk) did. Your key now leads the author list, and the opening ask covers every author, a chunk per ask. And publishPost put the provisional post at the top of whatever feed was open: now it goes to the feeds it would reach — the open feed and Following when they carry your posts (Following, a people feed with you in it, Everything) or a topic the post wears — swapped for the signed event or withdrawn in each. The hashtags in the text go out as t tags (NIP-24, up to the hashtag-spam count), so topic feeds here and elsewhere find the post. tools/own-post-feeds-test.js (450 follows: every one asked, your key first; a post from Following; an untagged post from a topic feed stays out of it; a tagged one lands in both).
Co-Authored-By: Claude Fable 5.1 <[email protected]>
Diffstat (limited to 'tools/feed-wheel-reverse-test.js')
0 files changed, 0 insertions, 0 deletions