Agenda
Performance Issues Update
Merged the sync prioritization- Syncing new content and updates should feel faster now
Fine-Grained Syncing Update
Profile Discovery In progress
Should use the /:profile URL format
Next up: /:comments ??
It would be nice to use these URLs for de-duplicating discovery streams in the middle end
Maybe we need a recursive URL format? hm://ACCOUNT_ID/path/*
hm://ACCOUNT_ID/:directory - maybe needs format for "direct children" vs "all children"
:directory-all ?? :directory:all ??
The push towards immediacy
hm://z6MkgYR76i3w2Xc2fcvgFJWfYjsop6YwUonDhQx3AdLmQ4BQ/:profile suggests to avoid highly fine-grained syncing, to avoid extra complexity with immediacy
Discovery will start supporting a PubSub p2p pattern
app-sync polling activity to trigger invalidations. Is polling okay?
Can we push to the peer when discovery has been called within 15 sec?
hm://z6MkgYR76i3w2Xc2fcvgFJWfYjsop6YwUonDhQx3AdLmQ4BQ/:profile to flesh out thoughts and produce a note, please!?
We do need Discord-level immediacy! 3 seconds is the goal!
hm://ACCOUNT_ID - references the home document
Is this a problem? hm://z6MkrbYsRzKb1VABdvhsDSAk6JK8fAszKsyHhcaZigYeWCou/:profile?v=bafy2bzacecoevvu2ebpntbrhm552uqp3ag5vrxvukpk7a4vvfmhazkk7smu5y&l thinks so.
Please include the user story in a note!
We don't know how comment discovery works. @eric and @burdi should investigate
Fixing Release Workflow - hm://z6Mkvz9TgGtv9zsGsdrksfNk1ajbFancgHREJEz3Y2HsAVdk/:profile?v=bafy2bzacebrehvt6ciku2flf23pbf4qm5o7ylje5iihoqir2ho3urr7vmbntg&l
Sentry step required more RAM causing windows build failure
Tag rollback workflow feels nasty
If one platform fails, it shouldn't cause everything to fail
Optimize failed build workflow
Agents Update
Deep seek experimentation by hm://z6Mkvz9TgGtv9zsGsdrksfNk1ajbFancgHREJEz3Y2HsAVdk/:profile?v=bafy2bzacebrehvt6ciku2flf23pbf4qm5o7ylje5iihoqir2ho3urr7vmbntg&l - demos on the way!
Do you like what you are reading? Subscribe to receive updates.
Unsubscribe anytime