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",
{
"ostatus": "http://ostatus.org#",
"atomUri": "ostatus:atomUri",
"inReplyToAtomUri": "ostatus:inReplyToAtomUri",
"conversation": "ostatus:conversation",
"sensitive": "as:sensitive",
"toot": "http://joinmastodon.org/ns#",
"votersCount": "toot:votersCount",
"litepub": "http://litepub.social/ns#",
"directMessage": "litepub:directMessage",
"Hashtag": "as:Hashtag"
}
],
"id": "https://infosec.exchange/users/resingm/statuses/110939059680693293",
"type": "Note",
"summary": null,
"inReplyTo": "https://ipv6.social/users/doachs/statuses/110938981574474227",
"published": "2023-08-23T13:01:50Z",
"url": "https://infosec.exchange/@resingm/110939059680693293",
"attributedTo": "https://infosec.exchange/users/resingm",
"to": [
"https://www.w3.org/ns/activitystreams#Public"
],
"cc": [
"https://infosec.exchange/users/resingm/followers",
"https://ipv6.social/users/doachs"
],
"sensitive": false,
"atomUri": "https://infosec.exchange/users/resingm/statuses/110939059680693293",
"inReplyToAtomUri": "https://ipv6.social/users/doachs/statuses/110938981574474227",
"conversation": "tag:infosec.exchange,2023-08-23:objectId=89378499:objectType=Conversation",
"content": "<p><span class=\"h-card\" translate=\"no\"><a href=\"https://ipv6.social/@doachs\" class=\"u-url mention\" rel=\"nofollow noopener noreferrer\" target=\"_blank\">@<span>doachs</span></a></span> - as it should be the case. I don't see any reason for not handing out a /64 for each customer. That's been the case for all my public <a href=\"https://infosec.exchange/tags/IPv6\" class=\"mention hashtag\" rel=\"tag\">#<span>IPv6</span></a> addresses so far, no matter whether it was a cloud IP or a residential connection.</p>",
"contentMap": {
"en": "<p><span class=\"h-card\" translate=\"no\"><a href=\"https://ipv6.social/@doachs\" class=\"u-url mention\" rel=\"nofollow noopener noreferrer\" target=\"_blank\">@<span>doachs</span></a></span> - as it should be the case. I don't see any reason for not handing out a /64 for each customer. That's been the case for all my public <a href=\"https://infosec.exchange/tags/IPv6\" class=\"mention hashtag\" rel=\"tag\">#<span>IPv6</span></a> addresses so far, no matter whether it was a cloud IP or a residential connection.</p>"
},
"attachment": [],
"tag": [
{
"type": "Mention",
"href": "https://ipv6.social/users/doachs",
"name": "@doachs@ipv6.social"
},
{
"type": "Hashtag",
"href": "https://infosec.exchange/tags/ipv6",
"name": "#ipv6"
}
],
"replies": {
"id": "https://infosec.exchange/users/resingm/statuses/110939059680693293/replies",
"type": "Collection",
"first": {
"type": "CollectionPage",
"next": "https://infosec.exchange/users/resingm/statuses/110939059680693293/replies?only_other_accounts=true&page=true",
"partOf": "https://infosec.exchange/users/resingm/statuses/110939059680693293/replies",
"items": []
}
},
"likes": {
"id": "https://infosec.exchange/users/resingm/statuses/110939059680693293/likes",
"type": "Collection",
"totalItems": 0
},
"shares": {
"id": "https://infosec.exchange/users/resingm/statuses/110939059680693293/shares",
"type": "Collection",
"totalItems": 0
}
}