• n2usenet - pseudonymous identity + anti-impersonation for Usenet posts

    From Gabx@victor@virebent.invalid to alt.privacy,alt.privacy.anon-server,alt.cypherpunks on Mon Aug 3 12:35:13 2026
    From Newsgroup: alt.privacy.anon-server

    https://n2usenet.virebent.art is a small web gateway for posting to Usenet through Nym Network without a local news client.

    Beyond the basic post form, it has a pseudonymous identity system built to stop impersonation: generate an Ed25519 keypair entirely client-side (nothing leaves your browser), save it as a portable JSON file, and reload it on any device.

    Every post you send while using that identity carries an X-Ed25519-Pub/-Sig headers pair signing the body,
    plus a Face: header, a 48x48 base64-encoded PNG identicon
    deterministically derived from username + email + your public key.

    The point: same key, same identicon, every time.

    Anyone can visually verify post-to-post continuity of a handle without a central authority,
    and nobody can forge your identicon without also forging your signature.

    Optional SHA256 fingerprint of the identity string is shown alongside it for exact verification.

    On the transport side, the web server itself keeps no logs, and outbound delivery
    is routed through the Nym mixnet, so anonymity doesn't rely on trusting us,

    it's a property of the infrastructure.

    Posting is anti-spam gated with hashcash PoW client-side before submission.

    Best regards

    Gabx

    --- Digital Signature --- hDKQBOii9VDUSwCAeqv9XCyxm8zCPkQQI7iJtdC1L5ZblzrJQxu8LcDV4pzJlk2j0FLtSeKElg20KJHXMEgMBA==

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Gabx@victor@virebent.invalid to alt.privacy.anon-server on Mon Aug 3 15:20:16 2026
    From Newsgroup: alt.privacy.anon-server

    Just shipped a small but overdue fix to n2usenet.

    Until now, messages composed through the web form were sent exactly as
    typed, with no reflow. Fine on a modern wide screen, but it ignores the
    old Usenet convention (RFC 1855, Netiquette Guidelines) of wrapping
    plain-text body lines at roughly 65-70 columns, for compatibility with
    classic terminal-based newsreaders (slrn, tin, trn, and similar). It was overdue, so today I fixed it.

    The change lives entirely client-side, in a new wrapUsenetText()
    function that runs in the browser right before the message is signed:

    - Greedy word-wrap at 72 columns.
    - Blank lines and lines already starting with '>' (quotes) are left
    untouched.
    - It runs *before* the Ed25519 signature is computed, not after, so the signature covers exactly the wrapped bytes that end up posted to the
    group. Wrapping server-side, after verification, would have silently
    broken signature checks for anyone verifying it against the posted
    body.

    Ok?

    Gabx

    --- Digital Signature --- X1SCGAkKMVznyAgrOCqcJeNDNPzRA6Cc4T09wdH6R2GVtMxDjy50t/iCi9ULgxTHm1tp9wXKg3HKLCnOgYGPBA==

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Gabx@victor@virebent.tcpreset to alt.privacy,alt.privacy.anon-server,alt.cypherpunks on Mon Aug 3 22:05:57 2026
    From Newsgroup: alt.privacy.anon-server

    Gabx wrote:
    https://n2usenet.virebent.art is a small web gateway for posting to Usenet through Nym Network without a local news client.


    Just shipped a small but overdue fix to n2usenet.

    Until now, messages composed through the web form were sent exactly as
    typed, with no reflow. Fine on a modern wide screen, but it ignores the
    old Usenet convention (RFC 1855, Netiquette Guidelines) of wrapping
    plain-text body lines at roughly 65-70 columns, for compatibility with
    classic terminal-based newsreaders (slrn, tin, trn, and similar). It was overdue, so today I fixed it.

    The change lives entirely client-side, in a new wrapUsenetText()
    function that runs in the browser right before the message is signed:

    - Greedy word-wrap at 72 columns.
    - Blank lines and lines already starting with '>' (quotes) are left
    untouched.
    - It runs *before* the Ed25519 signature is computed, not after, so the signature covers exactly the wrapped bytes that end up posted to the
    group. Wrapping server-side, after verification, would have silently
    broken signature checks for anyone verifying it against the posted
    body.

    Ok?

    Gabx
    --
    https://contact.virebent.art
    https://www.virebent.art
    https://news.tcpreset.net
    https://jabber.tcpreset.net
    https://virebent.noblogs.org/
    https://infosec.exchange/@virebent
    --- Synchronet 3.22a-Linux NewsLink 1.2