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"
}
],
"id": "https://mathstodon.xyz/users/seano/statuses/113244990484680024/replies",
"type": "Collection",
"first": {
"id": "https://mathstodon.xyz/users/seano/statuses/113244990484680024/replies?page=true",
"type": "CollectionPage",
"next": "https://mathstodon.xyz/users/seano/statuses/113244990484680024/replies?only_other_accounts=true&page=true",
"partOf": "https://mathstodon.xyz/users/seano/statuses/113244990484680024/replies",
"items": [
{
"id": "https://mathstodon.xyz/users/seano/statuses/113245072862762551",
"type": "Note",
"summary": null,
"inReplyTo": "https://mathstodon.xyz/users/seano/statuses/113244990484680024",
"published": "2024-10-03T19:11:19Z",
"url": "https://mathstodon.xyz/@seano/113245072862762551",
"attributedTo": "https://mathstodon.xyz/users/seano",
"to": [
"https://www.w3.org/ns/activitystreams#Public"
],
"cc": [
"https://mathstodon.xyz/users/seano/followers"
],
"sensitive": false,
"atomUri": "https://mathstodon.xyz/users/seano/statuses/113245072862762551",
"inReplyToAtomUri": "https://mathstodon.xyz/users/seano/statuses/113244990484680024",
"conversation": "tag:mathstodon.xyz,2024-10-03:objectId=117213039:objectType=Conversation",
"content": "<p>To be clear, this is meant to be read as a bottom-to-top backwards-reasoning rule. The vision I have is that these kinds of name constraints flow upwards, so there's never any issue with incompatible constraints. I think any left rule for negative types should be amenable to this kind of approach, including function application which might be even more cursed lmao.</p>",
"contentMap": {
"en": "<p>To be clear, this is meant to be read as a bottom-to-top backwards-reasoning rule. The vision I have is that these kinds of name constraints flow upwards, so there's never any issue with incompatible constraints. I think any left rule for negative types should be amenable to this kind of approach, including function application which might be even more cursed lmao.</p>"
},
"attachment": [],
"tag": [],
"replies": {
"id": "https://mathstodon.xyz/users/seano/statuses/113245072862762551/replies",
"type": "Collection",
"first": {
"type": "CollectionPage",
"next": "https://mathstodon.xyz/users/seano/statuses/113245072862762551/replies?only_other_accounts=true&page=true",
"partOf": "https://mathstodon.xyz/users/seano/statuses/113245072862762551/replies",
"items": []
}
},
"likes": {
"id": "https://mathstodon.xyz/users/seano/statuses/113245072862762551/likes",
"type": "Collection",
"totalItems": 0
},
"shares": {
"id": "https://mathstodon.xyz/users/seano/statuses/113245072862762551/shares",
"type": "Collection",
"totalItems": 0
}
}
]
}
}