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",
"Hashtag": "as:Hashtag"
}
],
"id": "https://mast.hpc.social/users/ProjectPhysX/statuses/114676822514898881",
"type": "Note",
"summary": null,
"inReplyTo": "https://mast.hpc.social/users/ProjectPhysX/statuses/114659148482693321",
"published": "2025-06-13T15:44:05Z",
"url": "https://mast.hpc.social/@ProjectPhysX/114676822514898881",
"attributedTo": "https://mast.hpc.social/users/ProjectPhysX",
"to": [
"https://www.w3.org/ns/activitystreams#Public"
],
"cc": [
"https://mast.hpc.social/users/ProjectPhysX/followers"
],
"sensitive": false,
"atomUri": "https://mast.hpc.social/users/ProjectPhysX/statuses/114676822514898881",
"inReplyToAtomUri": "https://mast.hpc.social/users/ProjectPhysX/statuses/114659148482693321",
"conversation": "tag:mast.hpc.social,2025-06-10:objectId=18266339:objectType=Conversation",
"content": "<p>Interesting take from an <a href=\"https://mast.hpc.social/tags/Nvidia\" class=\"mention hashtag\" rel=\"tag\">#<span>Nvidia</span></a> engineer I met at <a href=\"https://mast.hpc.social/tags/ISC25\" class=\"mention hashtag\" rel=\"tag\">#<span>ISC25</span></a>: "Do you need IEEE-754 compliant <a href=\"https://mast.hpc.social/tags/FP64\" class=\"mention hashtag\" rel=\"tag\">#<span>FP64</span></a>, or do you need digits? Digits we can get you through FP64 emulation."</p><p>Not sure what to make of that. Things were an absolute mess before the IEEE-754 standard, and I wouldn't want to ever go back to that. No standards means you cannot at all port software between hardware architectures even from within the same vendor. Having to re-architect software for each and every new chip is not gonna happen.</p>",
"contentMap": {
"en": "<p>Interesting take from an <a href=\"https://mast.hpc.social/tags/Nvidia\" class=\"mention hashtag\" rel=\"tag\">#<span>Nvidia</span></a> engineer I met at <a href=\"https://mast.hpc.social/tags/ISC25\" class=\"mention hashtag\" rel=\"tag\">#<span>ISC25</span></a>: "Do you need IEEE-754 compliant <a href=\"https://mast.hpc.social/tags/FP64\" class=\"mention hashtag\" rel=\"tag\">#<span>FP64</span></a>, or do you need digits? Digits we can get you through FP64 emulation."</p><p>Not sure what to make of that. Things were an absolute mess before the IEEE-754 standard, and I wouldn't want to ever go back to that. No standards means you cannot at all port software between hardware architectures even from within the same vendor. Having to re-architect software for each and every new chip is not gonna happen.</p>"
},
"attachment": [],
"tag": [
{
"type": "Hashtag",
"href": "https://mast.hpc.social/tags/nvidia",
"name": "#nvidia"
},
{
"type": "Hashtag",
"href": "https://mast.hpc.social/tags/isc25",
"name": "#isc25"
},
{
"type": "Hashtag",
"href": "https://mast.hpc.social/tags/fp64",
"name": "#fp64"
}
],
"replies": {
"id": "https://mast.hpc.social/users/ProjectPhysX/statuses/114676822514898881/replies",
"type": "Collection",
"first": {
"type": "CollectionPage",
"next": "https://mast.hpc.social/users/ProjectPhysX/statuses/114676822514898881/replies?only_other_accounts=true&page=true",
"partOf": "https://mast.hpc.social/users/ProjectPhysX/statuses/114676822514898881/replies",
"items": []
}
},
"likes": {
"id": "https://mast.hpc.social/users/ProjectPhysX/statuses/114676822514898881/likes",
"type": "Collection",
"totalItems": 7
},
"shares": {
"id": "https://mast.hpc.social/users/ProjectPhysX/statuses/114676822514898881/shares",
"type": "Collection",
"totalItems": 3
}
}