ActivityPub Viewer

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.

Open in browser →
{ "@context": [ "https://www.w3.org/ns/activitystreams", { "ostatus": "http://ostatus.org#", "atomUri": "ostatus:atomUri", "inReplyToAtomUri": "ostatus:inReplyToAtomUri", "conversation": "ostatus:conversation", "sensitive": "as:sensitive", "toot": "http://joinmastodon.org/ns#", "votersCount": "toot:votersCount", "blurhash": "toot:blurhash", "focalPoint": { "@container": "@list", "@id": "toot:focalPoint" }, "Hashtag": "as:Hashtag" } ], "id": "https://social.wildeboer.net/users/jwildeboer/statuses/114516287015424952", "type": "Note", "summary": null, "inReplyTo": null, "published": "2025-05-16T07:17:47Z", "url": "https://social.wildeboer.net/@jwildeboer/114516287015424952", "attributedTo": "https://social.wildeboer.net/users/jwildeboer", "to": [ "https://www.w3.org/ns/activitystreams#Public" ], "cc": [ "https://social.wildeboer.net/users/jwildeboer/followers" ], "sensitive": false, "atomUri": "https://social.wildeboer.net/users/jwildeboer/statuses/114516287015424952", "inReplyToAtomUri": null, "conversation": "tag:social.wildeboer.net,2025-05-16:objectId=11318904:objectType=Conversation", "content": "<p>I am totally sure (sarcasm included) that <a href=\"https://social.wildeboer.net/tags/Google\" class=\"mention hashtag\" rel=\"tag\">#<span>Google</span></a> has totally overseen that their planned changes to their root program requirements will cause a lot of problems for mailserver owners like me who in future might run into weird problems with <a href=\"https://social.wildeboer.net/tags/Letsencrypt\" class=\"mention hashtag\" rel=\"tag\">#<span>Letsencrypt</span></a> certificates for SMTP. I am sure that Google is absolutely not trying to make running your own mailserver even more complicated just to protect their gmail business. That would be totally not how Google thinks, amirite? <a href=\"https://letsencrypt.org/2025/05/14/ending-tls-client-authentication/\" target=\"_blank\" rel=\"nofollow noopener noreferrer\" translate=\"no\"><span class=\"invisible\">https://</span><span class=\"ellipsis\">letsencrypt.org/2025/05/14/end</span><span class=\"invisible\">ing-tls-client-authentication/</span></a></p>", "contentMap": { "en": "<p>I am totally sure (sarcasm included) that <a href=\"https://social.wildeboer.net/tags/Google\" class=\"mention hashtag\" rel=\"tag\">#<span>Google</span></a> has totally overseen that their planned changes to their root program requirements will cause a lot of problems for mailserver owners like me who in future might run into weird problems with <a href=\"https://social.wildeboer.net/tags/Letsencrypt\" class=\"mention hashtag\" rel=\"tag\">#<span>Letsencrypt</span></a> certificates for SMTP. I am sure that Google is absolutely not trying to make running your own mailserver even more complicated just to protect their gmail business. That would be totally not how Google thinks, amirite? <a href=\"https://letsencrypt.org/2025/05/14/ending-tls-client-authentication/\" target=\"_blank\" rel=\"nofollow noopener noreferrer\" translate=\"no\"><span class=\"invisible\">https://</span><span class=\"ellipsis\">letsencrypt.org/2025/05/14/end</span><span class=\"invisible\">ing-tls-client-authentication/</span></a></p>" }, "updated": "2025-05-16T18:49:46Z", "attachment": [ { "type": "Document", "mediaType": "image/png", "url": "https://cdn.masto.host/socialwildeboernet/media_attachments/files/114/516/285/604/835/823/original/ca265e09b0772f23.png", "name": "After this change is complete, only TLS Server Authentication will be available from Let’s Encrypt.\n\nThis change is prompted by changes to Google Chrome’s root program requirements, which impose a June 2026 deadline to split TLS Client and Server Authentication into separate PKIs. Many uses of client authentication are better served by a private certificate authority, and so Let’s Encrypt is discontinuing support for TLS Client Authentication ahead of this deadline.", "blurhash": "UGQ,L1M{xuRj~qayRjj[%Mj[Rjj[Rjofj[j[", "focalPoint": [ 0, 0 ], "width": 1184, "height": 394 } ], "tag": [ { "type": "Hashtag", "href": "https://social.wildeboer.net/tags/google", "name": "#google" }, { "type": "Hashtag", "href": "https://social.wildeboer.net/tags/letsencrypt", "name": "#letsencrypt" } ], "replies": { "id": "https://social.wildeboer.net/users/jwildeboer/statuses/114516287015424952/replies", "type": "Collection", "first": { "type": "CollectionPage", "next": "https://social.wildeboer.net/users/jwildeboer/statuses/114516287015424952/replies?min_id=114516429319640686&page=true", "partOf": "https://social.wildeboer.net/users/jwildeboer/statuses/114516287015424952/replies", "items": [ "https://social.wildeboer.net/users/jwildeboer/statuses/114516429319640686" ] } }, "likes": { "id": "https://social.wildeboer.net/users/jwildeboer/statuses/114516287015424952/likes", "type": "Collection", "totalItems": 69 }, "shares": { "id": "https://social.wildeboer.net/users/jwildeboer/statuses/114516287015424952/shares", "type": "Collection", "totalItems": 90 } }