Digital identity
Some content published by DYWEB Solutions (articles) is digitally signed with an OpenPGP (GPG) key. This signature does not protect against copying, but it lets any reader independently verify that an article was indeed published and signed by Teddy JEAN-BAPTISTE, and that its content has not been modified since signing.
This signature attests
- ✓Provenance: the content genuinely comes from the holder of the private key (Teddy JEAN-BAPTISTE).
- ✓Integrity: the content has not been modified since the moment of signing.
- ✓Human review and validation: several articles are co-written with AI agents. The signature certifies that Teddy JEAN-BAPTISTE reviewed and validated the final content before publication — AI may have contributed to the drafting, editorial responsibility remains human.
Public key
Key fingerprint
1B9B FDBE 03A5 173D 3939 3924 3F52 DB76 391A 52EDIdentity
Teddy JEAN-BAPTISTE <contact@dyweb-solutions.com>
Verification
From an article's authenticity block, download the .mdx source and .asc signature, then:
- 1. Import the public key
gpg --keyserver hkps://keys.openpgp.org --recv-keys 1B9BFDBE03A5173D393939243F52DB76391A52ED - 2. Download the source article and its signature (links in the authenticity block)
- 3. Verify
gpg --verify fr.mdx.asc fr.mdx
A valid signature only proves the file's content and origin at the time of signing — it does not certify the accuracy of the article's content.
Scope and limits
Only articles displaying a signature block are covered. Pages without this block are not signed.
Site version : 0.3.1