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://floss.social/users/HerraBRE/statuses/109239947836041298",
"type": "Note",
"summary": null,
"inReplyTo": "https://floss.social/users/HerraBRE/statuses/109239934709440034",
"published": "2022-10-27T11:15:21Z",
"url": "https://floss.social/@HerraBRE/109239947836041298",
"attributedTo": "https://floss.social/users/HerraBRE",
"to": [
"https://www.w3.org/ns/activitystreams#Public"
],
"cc": [
"https://floss.social/users/HerraBRE/followers"
],
"sensitive": false,
"atomUri": "https://floss.social/users/HerraBRE/statuses/109239947836041298",
"inReplyToAtomUri": "https://floss.social/users/HerraBRE/statuses/109239934709440034",
"conversation": "tag:floss.social,2022-10-27:objectId=23475106:objectType=Conversation",
"content": "<p>... as far as I know *nobody* is using <a href=\"https://floss.social/tags/Duppy\" class=\"mention hashtag\" rel=\"tag\">#<span>Duppy</span></a> yet, including me - I have yet to deploy it. For shame!</p><p>It's quite functional though, and I think it's super neat - it's both a <a href=\"https://floss.social/tags/DNS\" class=\"mention hashtag\" rel=\"tag\">#<span>DNS</span></a> server and an HTTP web-API server in one <a href=\"https://floss.social/tags/Python\" class=\"mention hashtag\" rel=\"tag\">#<span>Python</span></a> process. The idea is for it to handle all your dynamic-DNS-update-API-server needs in one codebase.</p><p>I wonder if anyone in Fedi would like to take a look?</p>",
"contentMap": {
"en": "<p>... as far as I know *nobody* is using <a href=\"https://floss.social/tags/Duppy\" class=\"mention hashtag\" rel=\"tag\">#<span>Duppy</span></a> yet, including me - I have yet to deploy it. For shame!</p><p>It's quite functional though, and I think it's super neat - it's both a <a href=\"https://floss.social/tags/DNS\" class=\"mention hashtag\" rel=\"tag\">#<span>DNS</span></a> server and an HTTP web-API server in one <a href=\"https://floss.social/tags/Python\" class=\"mention hashtag\" rel=\"tag\">#<span>Python</span></a> process. The idea is for it to handle all your dynamic-DNS-update-API-server needs in one codebase.</p><p>I wonder if anyone in Fedi would like to take a look?</p>"
},
"attachment": [],
"tag": [
{
"type": "Hashtag",
"href": "https://floss.social/tags/Duppy",
"name": "#Duppy"
},
{
"type": "Hashtag",
"href": "https://floss.social/tags/DNS",
"name": "#DNS"
},
{
"type": "Hashtag",
"href": "https://floss.social/tags/Python",
"name": "#Python"
}
],
"replies": {
"id": "https://floss.social/users/HerraBRE/statuses/109239947836041298/replies",
"type": "Collection",
"first": {
"type": "CollectionPage",
"next": "https://floss.social/users/HerraBRE/statuses/109239947836041298/replies?min_id=109240162911419546&page=true",
"partOf": "https://floss.social/users/HerraBRE/statuses/109239947836041298/replies",
"items": [
"https://floss.social/users/HerraBRE/statuses/109240162911419546"
]
}
},
"likes": {
"id": "https://floss.social/users/HerraBRE/statuses/109239947836041298/likes",
"type": "Collection",
"totalItems": 1
},
"shares": {
"id": "https://floss.social/users/HerraBRE/statuses/109239947836041298/shares",
"type": "Collection",
"totalItems": 0
}
}