A small tool to view real-world ActivityPub objects as JSON! Enter a URL
or username from Mastodon or a similar service below, and we'll send a
request with
the right
Accept
header
to the server to view the underlying object.
{
"@context": "https://www.w3.org/ns/activitystreams",
"type": "Note",
"id": "https://snac.daltux.net/daltux/p/1744383247.497785",
"published": "2025-04-11T14:54:07Z",
"attributedTo": "https://snac.daltux.net/daltux",
"summary": "",
"content": "\"The <b>treta</b> has been planted.\"<br><br>@ :debian: Sid<br><br><pre>apt-listchanges: News<br>---------------------<br><br>gnupg2 (2.4.7-4) experimental; urgency=medium<br><br> The upstream GnuPG project now explicitly and deliberately diverges from<br> the OpenPGP standard. Debian's own workflows rely heavily on OpenPGP,<br> and we ship several different OpenPGP implementations, so<br> interoperability via standardization is a priority for the project.<br><br> While Debian still has significant dependencies on GnuPG, the version of<br> GnuPG shipped in Debian will default to emitting only OpenPGP-compatible<br> artifacts if at all possible. As of 2.4.7-4, the default<br> is --compliance=openpgp, and we apply several patches to ensure that<br> this mode is respected.<br><br> If you observe GnuPG in Debian emitting a non-OpenPGP artifact in a<br> scenario where a standard OpenPGP artifact is intended or expected,<br> please open a critical bug report in the Debian BTS.<br><br> If you want Debian's GnuPG to emit non-standardized artifacts, in line<br> with upstream's deliberate divergence, you can explicitly pass<br> --compliance=gnupg (or set the corresponding option in<br> ~/.gnupg/gpg.conf). If you revert to compliance with upstream defaults,<br> do not expect the material you produce to be interoperable with other<br> OpenPGP implementations.<br><br> -- Daniel Kahn Gillmor <dkg@fifthhorseman.net> Fri, 07 Feb 2025 23:35:29 -0500<br></pre><a href=\"https://snac.daltux.net?t=debian\" class=\"mention hashtag\" rel=\"tag\">#Debian</a> <a href=\"https://snac.daltux.net?t=gnupg\" class=\"mention hashtag\" rel=\"tag\">#GnuPG</a> <a href=\"https://snac.daltux.net?t=gpg\" class=\"mention hashtag\" rel=\"tag\">#GPG</a> <a href=\"https://snac.daltux.net?t=openpgp\" class=\"mention hashtag\" rel=\"tag\">#OpenPGP</a> <a href=\"https://snac.daltux.net?t=gnu\" class=\"mention hashtag\" rel=\"tag\">#GNU</a><br>",
"context": "https://snac.daltux.net/daltux/p/1744383247.497785#ctxt",
"url": "https://snac.daltux.net/daltux/p/1744383247.497785",
"to": [
"https://www.w3.org/ns/activitystreams#Public"
],
"cc": [],
"inReplyTo": null,
"tag": [
{
"id": "https://snac.daltux.net/daltux/s/debian.png",
"type": "Emoji",
"name": ":debian:",
"updated": "2025-04-11T14:54:07Z",
"icon": {
"type": "Image",
"mediaType": "image/png",
"url": "https://snac.daltux.net/daltux/s/debian.png"
}
},
{
"type": "Hashtag",
"href": "https://snac.daltux.net?t=debian",
"name": "#debian"
},
{
"type": "Hashtag",
"href": "https://snac.daltux.net?t=gnupg",
"name": "#gnupg"
},
{
"type": "Hashtag",
"href": "https://snac.daltux.net?t=gpg",
"name": "#gpg"
},
{
"type": "Hashtag",
"href": "https://snac.daltux.net?t=openpgp",
"name": "#openpgp"
},
{
"type": "Hashtag",
"href": "https://snac.daltux.net?t=gnu",
"name": "#gnu"
}
],
"sourceContent": "\"The **treta** has been planted.\"\n\n@ :debian: Sid\n\n```\napt-listchanges: News\n---------------------\n\ngnupg2 (2.4.7-4) experimental; urgency=medium\n\n The upstream GnuPG project now explicitly and deliberately diverges from\n the OpenPGP standard. Debian's own workflows rely heavily on OpenPGP,\n and we ship several different OpenPGP implementations, so\n interoperability via standardization is a priority for the project.\n\n While Debian still has significant dependencies on GnuPG, the version of\n GnuPG shipped in Debian will default to emitting only OpenPGP-compatible\n artifacts if at all possible. As of 2.4.7-4, the default\n is --compliance=openpgp, and we apply several patches to ensure that\n this mode is respected.\n\n If you observe GnuPG in Debian emitting a non-OpenPGP artifact in a\n scenario where a standard OpenPGP artifact is intended or expected,\n please open a critical bug report in the Debian BTS.\n\n If you want Debian's GnuPG to emit non-standardized artifacts, in line\n with upstream's deliberate divergence, you can explicitly pass\n --compliance=gnupg (or set the corresponding option in\n ~/.gnupg/gpg.conf). If you revert to compliance with upstream defaults,\n do not expect the material you produce to be interoperable with other\n OpenPGP implementations.\n\n -- Daniel Kahn Gillmor <dkg@fifthhorseman.net> Fri, 07 Feb 2025 23:35:29 -0500\n```\n\n#Debian #GnuPG #GPG #OpenPGP #GNU"
}