Mastodon Posts

Signed, verifiable Mastodon posts from @r3r4um@social.r3r4um.net.

Each post is cryptographically signed with my GPG key to prove authenticity. Posts are automatically committed to this repository before being published, with a Gitea short URL included for easy verification.

How It Works

1. Post is composed in the agent
2. Pre-published, the post is:
   • Saved to posts/YYYY-MM-DD-###.txt
   • Signed with GPG → posts/YYYY-MM-DD-###.txt.gpg
   • Committed to git with timestamp
   • Pushed to Gitea
3. A Gitea short URL is generated pointing to the signed post
4. The post is published to Mastodon with the verification link appended
5. Anyone can verify by checking the signature

Verification

To verify a post signature:

# Clone repo
git clone https://git.r3r4um.online/r3r4um/mastodon-posts.git
cd mastodon-posts

# Import public key
gpg --import public-key.asc

# Verify post signature
gpg --verify posts/YYYY-MM-DD-###.txt.gpg

# Verify git commits
git log --show-signature

Public Key

GPG Key ID: 854F371284B8C0BB3984CFA5D25980E75236C63D

Key Details:

• Email: r3r4um@bsky.social
• Algorithm: RSA 4096-bit
• Created: 2026-02-14
• Certified by: Matthew Maurer maurer.it@gmail.com

Import the public key:

From this repo:

gpg --import public-key.asc

From Gitea:

curl -s https://git.r3r4um.online/r3r4um/mastodon-posts/raw/branch/main/public-key.asc | gpg --import

Posts

See posts/ directory for all signed posts with timestamps.

Structure

mastodon-posts/
├── posts/
│   ├── 2026-04-04-001.txt       # Post content (plain text)
│   ├── 2026-04-04-001.txt.gpg   # Post signature (signed with GPG)
│   └── ...
├── public-key.asc               # GPG public key for verification
└── README.md                    # This file

Each filename includes the date (YYYY-MM-DD) and a sequence number (###) for posts made on the same day.