v3 work log: Oct 28
First entry in a running log of v3 work. Oct 28 in short: posting for the first time got easier, Account and Users were rebuilt, Activity got much faster, and removals share one receipt format. That was 82 commits on main and about 9,200 lines across code, tests and plan docs.
FIRST POST
No more browser dialogs. Every signed composer has a name field, and your key stays in your browser until your first post, reply or Like. That first action shows "Creating your account…" and then goes through. If it fails, Retry appears next to the composer and your draft is kept.
Readers who never post no longer publish a key to the server just by visiting. Late in the day the "Post as" row came back out of the composers, and on phones the ··· menu now sits beside Post.
ACCOUNT
Rebuilt around how v3 works: your user is your name, and keys are cheap. The page opens in the right state (guest, waiting for approval, or approved). You can name or rename in place, save a copy of an approved key so another device skips re-approval, use a key from another device, and remove a key with Undo. Fingerprints and storage details are under Advanced.
USERS AND PERSON PAGES
Users is a compact, searchable list. Approved members also see a Waiting tab. Each person has one page with Message, their threads and replies, and their keys, which show in the short form openpgp-0168ff20e…
SIGN-IN
Coming back to the site no longer reloads the page under you. Sign-in finishes quietly and leaves your typing, scroll position and open menus alone.
PHONE TAB BAR
It hides when you scroll down and comes back when you scroll up, hit the top or bottom, or tab into it. It also stays out of the way while you type, so it can't cover Post.
ACTIVITY SPEED
Activity pages took 4 to 8.5 seconds on the live site, and one request timed out. They now read data saved when posts are written instead of recomputing it each time. In local tests, database time per page dropped from 7.5 ms to 1.5 ms, and from about 5 ms to under 0.3 ms for Forte and detail views. The real check is the live site after deploy.
REMOVALS
An author's signed retraction and an operator's cleanup now leave the same readable receipt. A signed one keeps the original signature; an operator one doesn't pretend to have one.
PROCESS
Every feature above went through Railspike, now pinned at v0.4.0. The plans, debug logs and effort estimates are in docs/plans/ if you want the reasoning.
Sources:
https://github.com/gulkily/v3/commits/main
https://github.com/gulkily/v3/tree/main/docs/plans
#v3 #worklog #meta
#
FIRST POST
No more browser dialogs. Every signed composer has a name field, and your key stays in your browser until your first post, reply or Like. That first action shows "Creating your account…" and then goes through. If it fails, Retry appears next to the composer and your draft is kept.
Readers who never post no longer publish a key to the server just by visiting. Late in the day the "Post as" row came back out of the composers, and on phones the ··· menu now sits beside Post.
ACCOUNT
Rebuilt around how v3 works: your user is your name, and keys are cheap. The page opens in the right state (guest, waiting for approval, or approved). You can name or rename in place, save a copy of an approved key so another device skips re-approval, use a key from another device, and remove a key with Undo. Fingerprints and storage details are under Advanced.
USERS AND PERSON PAGES
Users is a compact, searchable list. Approved members also see a Waiting tab. Each person has one page with Message, their threads and replies, and their keys, which show in the short form openpgp-0168ff20e…
SIGN-IN
Coming back to the site no longer reloads the page under you. Sign-in finishes quietly and leaves your typing, scroll position and open menus alone.
PHONE TAB BAR
It hides when you scroll down and comes back when you scroll up, hit the top or bottom, or tab into it. It also stays out of the way while you type, so it can't cover Post.
ACTIVITY SPEED
Activity pages took 4 to 8.5 seconds on the live site, and one request timed out. They now read data saved when posts are written instead of recomputing it each time. In local tests, database time per page dropped from 7.5 ms to 1.5 ms, and from about 5 ms to under 0.3 ms for Forte and detail views. The real check is the live site after deploy.
REMOVALS
An author's signed retraction and an operator's cleanup now leave the same readable receipt. A signed one keeps the original signature; an operator one doesn't pretend to have one.
PROCESS
Every feature above went through Railspike, now pinned at v0.4.0. The plans, debug logs and effort estimates are in docs/plans/ if you want the reasoning.
Sources:
https://github.com/gulkily/v3/commits/main
https://github.com/gulkily/v3/tree/main/docs/plans
#v3 #worklog #meta