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://mastodon.social/users/blaine/statuses/100570761019831564",
"type": "Note",
"summary": null,
"inReplyTo": "https://mastodon.me.uk/users/symroe/statuses/100570654176400336",
"published": "2018-08-18T10:27:08Z",
"url": "https://mastodon.social/@blaine/100570761019831564",
"attributedTo": "https://mastodon.social/users/blaine",
"to": [
"https://www.w3.org/ns/activitystreams#Public"
],
"cc": [
"https://mastodon.social/users/blaine/followers",
"https://mastodon.me.uk/users/symroe",
"https://mastodon.me.uk/users/Floppy"
],
"sensitive": false,
"atomUri": "https://mastodon.social/users/blaine/statuses/100570761019831564",
"inReplyToAtomUri": "https://mastodon.me.uk/users/symroe/statuses/100570654176400336",
"conversation": "tag:mastodon.me.uk,2018-08-18:objectId=694993:objectType=Conversation",
"content": "<p><span class=\"h-card\" translate=\"no\"><a href=\"https://mastodon.me.uk/@symroe\" class=\"u-url mention\">@<span>symroe</span></a></span> <span class=\"h-card\" translate=\"no\"><a href=\"https://mastodon.me.uk/@Floppy\" class=\"u-url mention\">@<span>floppy</span></a></span> my recommendation would be to ignore or bend the spec (I say that having been involved with large parts of it in the past). The problem with a lot of the specification processes to date is that they've operated in a vacuum, so don't necessarily reflect what's needed, and can't react quickly enough.</p><p>e.g., For DMs, an auto-reply saying "non-encrypted DMs are dropped and not stored" would be a compliant but rule-bendy approach to start.</p>",
"contentMap": {
"en": "<p><span class=\"h-card\" translate=\"no\"><a href=\"https://mastodon.me.uk/@symroe\" class=\"u-url mention\">@<span>symroe</span></a></span> <span class=\"h-card\" translate=\"no\"><a href=\"https://mastodon.me.uk/@Floppy\" class=\"u-url mention\">@<span>floppy</span></a></span> my recommendation would be to ignore or bend the spec (I say that having been involved with large parts of it in the past). The problem with a lot of the specification processes to date is that they've operated in a vacuum, so don't necessarily reflect what's needed, and can't react quickly enough.</p><p>e.g., For DMs, an auto-reply saying "non-encrypted DMs are dropped and not stored" would be a compliant but rule-bendy approach to start.</p>"
},
"attachment": [],
"tag": [
{
"type": "Mention",
"href": "https://mastodon.me.uk/users/symroe",
"name": "@symroe@mastodon.me.uk"
},
{
"type": "Mention",
"href": "https://mastodon.me.uk/users/Floppy",
"name": "@floppy@mastodon.me.uk"
}
],
"replies": {
"id": "https://mastodon.social/users/blaine/statuses/100570761019831564/replies",
"type": "Collection",
"first": {
"type": "CollectionPage",
"next": "https://mastodon.social/users/blaine/statuses/100570761019831564/replies?only_other_accounts=true&page=true",
"partOf": "https://mastodon.social/users/blaine/statuses/100570761019831564/replies",
"items": []
}
},
"likes": {
"id": "https://mastodon.social/users/blaine/statuses/100570761019831564/likes",
"type": "Collection",
"totalItems": 2
},
"shares": {
"id": "https://mastodon.social/users/blaine/statuses/100570761019831564/shares",
"type": "Collection",
"totalItems": 0
}
}