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://social.coop/users/eob/statuses/109320777639960907",
"type": "Note",
"summary": "Infrastructure engineering question about Mastodon",
"inReplyTo": null,
"published": "2022-11-10T17:51:26Z",
"url": "https://social.coop/@eob/109320777639960907",
"attributedTo": "https://social.coop/users/eob",
"to": [
"https://social.coop/users/eob/followers"
],
"cc": [
"https://www.w3.org/ns/activitystreams#Public",
"https://hayu.sh/users/dscl",
"https://mastodon.ar.al/users/aral",
"https://social.coop/users/brecht"
],
"sensitive": true,
"atomUri": "https://social.coop/users/eob/statuses/109320777639960907",
"inReplyToAtomUri": null,
"conversation": "tag:social.coop,2022-11-10:objectId=40954678:objectType=Conversation",
"content": "<p>@mairin@fosstodon.org <span class=\"h-card\" translate=\"no\"><a href=\"https://hayu.sh/users/dscl\" class=\"u-url mention\">@<span>dscl</span></a></span> <span class=\"h-card\" translate=\"no\"><a href=\"https://mastodon.ar.al/@aral\" class=\"u-url mention\">@<span>aral</span></a></span> <span class=\"h-card\" translate=\"no\"><a href=\"https://social.coop/@brecht\" class=\"u-url mention\">@<span>brecht</span></a></span> I'm intrigued by this in the article:</p><p>'ActivityPub and Mastodon are designed the same way Big Tech/Big Web is: to encourage services that host as many “users” as they can.'</p><p>Is this inherent in the ActivityPub protocol? And are there tweaks that could help?</p><p>Or does it come from the particular implementation of the standard Mastodon server? Is it just because it's overly complex?</p>",
"contentMap": {
"en": "<p>@mairin@fosstodon.org <span class=\"h-card\" translate=\"no\"><a href=\"https://hayu.sh/users/dscl\" class=\"u-url mention\">@<span>dscl</span></a></span> <span class=\"h-card\" translate=\"no\"><a href=\"https://mastodon.ar.al/@aral\" class=\"u-url mention\">@<span>aral</span></a></span> <span class=\"h-card\" translate=\"no\"><a href=\"https://social.coop/@brecht\" class=\"u-url mention\">@<span>brecht</span></a></span> I'm intrigued by this in the article:</p><p>'ActivityPub and Mastodon are designed the same way Big Tech/Big Web is: to encourage services that host as many “users” as they can.'</p><p>Is this inherent in the ActivityPub protocol? And are there tweaks that could help?</p><p>Or does it come from the particular implementation of the standard Mastodon server? Is it just because it's overly complex?</p>"
},
"attachment": [],
"tag": [
{
"type": "Mention",
"href": "https://hayu.sh/users/dscl",
"name": "@dscl@hayu.sh"
},
{
"type": "Mention",
"href": "https://mastodon.ar.al/users/aral",
"name": "@aral@mastodon.ar.al"
},
{
"type": "Mention",
"href": "https://social.coop/users/brecht",
"name": "@brecht"
}
],
"replies": {
"id": "https://social.coop/users/eob/statuses/109320777639960907/replies",
"type": "Collection",
"first": {
"type": "CollectionPage",
"next": "https://social.coop/users/eob/statuses/109320777639960907/replies?only_other_accounts=true&page=true",
"partOf": "https://social.coop/users/eob/statuses/109320777639960907/replies",
"items": []
}
},
"likes": {
"id": "https://social.coop/users/eob/statuses/109320777639960907/likes",
"type": "Collection",
"totalItems": 0
},
"shares": {
"id": "https://social.coop/users/eob/statuses/109320777639960907/shares",
"type": "Collection",
"totalItems": 0
}
}