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://epistolary.org/users/vees/statuses/114009366789850299",
"type": "Note",
"summary": null,
"inReplyTo": null,
"published": "2025-02-15T18:41:19Z",
"url": "https://epistolary.org/@vees/114009366789850299",
"attributedTo": "https://epistolary.org/users/vees",
"to": [
"https://www.w3.org/ns/activitystreams#Public"
],
"cc": [
"https://epistolary.org/users/vees/followers"
],
"sensitive": false,
"atomUri": "https://epistolary.org/users/vees/statuses/114009366789850299",
"inReplyToAtomUri": null,
"conversation": "tag:epistolary.org,2025-02-15:objectId=24068346:objectType=Conversation",
"content": "<p>I managed to corrupt the <a href=\"https://epistolary.org/tags/AREDN\" class=\"mention hashtag\" rel=\"tag\">#<span>AREDN</span></a> config file so bad the user interface wouldn’t load the <a href=\"https://epistolary.org/tags/Wireguard\" class=\"mention hashtag\" rel=\"tag\">#<span>Wireguard</span></a> section. I did a too-full reset but I need to put the firmware back on again now. Should be a quicker process now that the rest of my network is configured correctly for the VLANs it expects.</p>",
"contentMap": {
"en": "<p>I managed to corrupt the <a href=\"https://epistolary.org/tags/AREDN\" class=\"mention hashtag\" rel=\"tag\">#<span>AREDN</span></a> config file so bad the user interface wouldn’t load the <a href=\"https://epistolary.org/tags/Wireguard\" class=\"mention hashtag\" rel=\"tag\">#<span>Wireguard</span></a> section. I did a too-full reset but I need to put the firmware back on again now. Should be a quicker process now that the rest of my network is configured correctly for the VLANs it expects.</p>"
},
"attachment": [],
"tag": [
{
"type": "Hashtag",
"href": "https://epistolary.org/tags/aredn",
"name": "#aredn"
},
{
"type": "Hashtag",
"href": "https://epistolary.org/tags/wireguard",
"name": "#wireguard"
}
],
"replies": {
"id": "https://epistolary.org/users/vees/statuses/114009366789850299/replies",
"type": "Collection",
"first": {
"type": "CollectionPage",
"next": "https://epistolary.org/users/vees/statuses/114009366789850299/replies?only_other_accounts=true&page=true",
"partOf": "https://epistolary.org/users/vees/statuses/114009366789850299/replies",
"items": []
}
},
"likes": {
"id": "https://epistolary.org/users/vees/statuses/114009366789850299/likes",
"type": "Collection",
"totalItems": 2
},
"shares": {
"id": "https://epistolary.org/users/vees/statuses/114009366789850299/shares",
"type": "Collection",
"totalItems": 1
}
}