Personas have walls their followers write on
Owner decision of 2026-10-06 (G-0009, FEP-400e). A persona's actor names its wall (…/graffiti, sm:wall) and, in
Smithereen's privacySettings, that its followers may write on it. A public post that is not a reply, sent with the wall
as its target by an account following the persona, is hosted: the persona is notified, it reaches the persona's and its
followers' homes, and the followers' servers and the author's are told with Add{Note}. The persona deletes it with
DELETE /api/v1/statuses/:id, which sends Remove{Note}; Smithereen deletes the post then. The wall lists the persona's
public posts that start a thread and what was written on it.
Elsewhere: an account's Add{Note} on its own wall shows the post to its followers here as on that wall (privapub.wall on
the status), and its Remove takes it away. An Add or Remove naming a collection of the account's own server PrivaPub
does not know has its document read again first, at most hourly: accounts kept before walls were read had none.
Checked live: Smithereen 40 checks (G-0009 closed); GoToSocial and Mastodon unchanged (121).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01LsXgEaXee4GCU1hwYgPJXw
This commit is contained in:
1 parent
e0682fa868
commit
c47b6e5533
26 files changed
+582
-36
No files matched your search
@@ -608,8 +608,9 @@ tools/pasture/run.sh down # removes e
|
||||
`log_bin_trust_function_creators`, and a first start that failed there leaves the database without triggers (drop it
|
||||
and start again). Accounts come from its signup form (opened, with a short description, which its NodeInfo needs) and
|
||||
are renamed in its database; its API is VKontakte's (`/api/method/<name>?v=1.0`), with a password grant for a local
|
||||
application the peer script inserts. `scenarios/smithereen.sh`, 30 checks and one known gap (G-0009, posts on
|
||||
someone else's wall).
|
||||
application the peer script inserts. `scenarios/smithereen.sh`, 40 checks, walls both ways (alice's profile is
|
||||
told again first, so Smithereen reads her `sm:wall`; `servers.features & 1` says it took PrivaPub for a server with
|
||||
walls). Its scenario texts avoid apostrophes: `p_home_has` puts them inside a Python string.
|
||||
- **Load (`load.sh`, needs the `flood` peer):** `flood` (`flood/flood.cs`, published once into `.flood`) answers as
|
||||
twenty fake servers and sends signed activities at a set rate; `load.sh --rate=N --seconds=N` measures the answers,
|
||||
the queue's wait and processing times, its drain, and a persona's home timeline meanwhile, and keeps each run in
|
||||
|
||||
Reference in new issue
Block a user