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",
"litepub": "http://litepub.social/ns#",
"directMessage": "litepub:directMessage"
}
],
"id": "https://60228.dev/users/leo/statuses/109320379435010240",
"type": "Note",
"summary": null,
"inReplyTo": "https://60228.dev/users/leo/statuses/109320365737050416",
"published": "2022-11-10T16:10:10Z",
"url": "https://60228.dev/@leo/109320379435010240",
"attributedTo": "https://60228.dev/users/leo",
"to": [
"https://www.w3.org/ns/activitystreams#Public"
],
"cc": [
"https://60228.dev/users/leo/followers",
"https://infosec.exchange/users/tinker"
],
"sensitive": false,
"atomUri": "https://60228.dev/users/leo/statuses/109320379435010240",
"inReplyToAtomUri": "https://60228.dev/users/leo/statuses/109320365737050416",
"conversation": "tag:infosec.exchange,2022-11-10:objectId=20747057:objectType=Conversation",
"content": "<p><span class=\"h-card\" translate=\"no\"><a href=\"https://infosec.exchange/@tinker\" class=\"u-url mention\" rel=\"nofollow noopener noreferrer\" target=\"_blank\">@<span>tinker</span></a></span> many instances incl. yours (and mine), especially smaller ones, run the glitch-soc/mastodon fork, it's closely tied to upstream development but includes several features that the lead dev is against. this includes both being much more lenient with incoming formatting, and allowing posts to be composed in HTML or Markdown<br>in addition to changing the default from your Settings, in the web app you can enable changing the setting per-post in the App Settings dialog (I think the reason they're in different places is that Settings will also affect posts made via the API that don't specify the format)</p>",
"contentMap": {
"en": "<p><span class=\"h-card\" translate=\"no\"><a href=\"https://infosec.exchange/@tinker\" class=\"u-url mention\" rel=\"nofollow noopener noreferrer\" target=\"_blank\">@<span>tinker</span></a></span> many instances incl. yours (and mine), especially smaller ones, run the glitch-soc/mastodon fork, it's closely tied to upstream development but includes several features that the lead dev is against. this includes both being much more lenient with incoming formatting, and allowing posts to be composed in HTML or Markdown<br>in addition to changing the default from your Settings, in the web app you can enable changing the setting per-post in the App Settings dialog (I think the reason they're in different places is that Settings will also affect posts made via the API that don't specify the format)</p>"
},
"attachment": [],
"tag": [
{
"type": "Mention",
"href": "https://infosec.exchange/users/tinker",
"name": "@tinker@infosec.exchange"
}
],
"replies": {
"id": "https://60228.dev/users/leo/statuses/109320379435010240/replies",
"type": "Collection",
"first": {
"type": "CollectionPage",
"next": "https://60228.dev/users/leo/statuses/109320379435010240/replies?only_other_accounts=true&page=true",
"partOf": "https://60228.dev/users/leo/statuses/109320379435010240/replies",
"items": []
}
},
"likes": {
"id": "https://60228.dev/users/leo/statuses/109320379435010240/likes",
"type": "Collection",
"totalItems": 9
},
"shares": {
"id": "https://60228.dev/users/leo/statuses/109320379435010240/shares",
"type": "Collection",
"totalItems": 1
}
}