Skip to content

Feat/block and report - #9

Merged
nogringo merged 10 commits into
mainfrom
feat/block-and-report
Aug 31, 2026
Merged

Feat/block and report#9
nogringo merged 10 commits into
mainfrom
feat/block-and-report

Conversation

@nogringo

Copy link
Copy Markdown
Owner

No description provided.

A block lives on the device first: `openspecs:blocked` holds the keys, the
comment ids and the document addresses a reader chose not to see, and the
changes no signed list carries yet. Listings, search, the variants under a
name, the tallies, the row counts and the bell all read it; a blocked comment
folds to one line and keeps its replies; a blocked document or account page
stands behind a notice with Unblock and Show anyway. A Settings tab lists it
all. Nothing offers the block yet, and nothing publishes it: both follow.
Loading the picture would call on a server the blocked key chose, from the
one page a reader visits to stop seeing them, and the picture may be the
reason they are here. The mark is computed from the key alone.
… your own

A reader with no key can now report, and a reader with one can choose not
to sign with it: the event is signed by a key generated for it and thrown
away, so nothing ties it to them. The form says what that is worth, since
most relays weigh such a report at nothing, and the report also goes to the
relay this site runs, where it is read whatever its weight. The row that sent
a keyless reader to connect is gone.
It explained a protocol detail the reader can do nothing with. The code
comment on `editMuteList` already says it, for the reader who can.
@nogringo
nogringo merged commit a3bbcbf into main Aug 31, 2026
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant