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://social.librem.one/users/eighthave/statuses/109977120584942308",
"type": "Note",
"summary": null,
"inReplyTo": null,
"published": "2023-03-06T15:48:04Z",
"url": "https://social.librem.one/@eighthave/109977120584942308",
"attributedTo": "https://social.librem.one/users/eighthave",
"to": [
"https://www.w3.org/ns/activitystreams#Public"
],
"cc": [
"https://social.librem.one/users/eighthave/followers"
],
"sensitive": false,
"atomUri": "https://social.librem.one/users/eighthave/statuses/109977120584942308",
"inReplyToAtomUri": null,
"conversation": "tag:librem.one,2023-03-06:objectId=40569365:objectType=Conversation",
"content": "<p>Interesting comparison between <a href=\"https://social.librem.one/tags/Google\" class=\"mention hashtag\" rel=\"tag\">#<span>Google</span></a> vs <a href=\"https://social.librem.one/tags/Apple\" class=\"mention hashtag\" rel=\"tag\">#<span>Apple</span></a> approaches at <a href=\"https://social.librem.one/tags/DMAWorkshop\" class=\"mention hashtag\" rel=\"tag\">#<span>DMAWorkshop</span></a>. They have very different methods of gatekeeping, and <a href=\"https://social.librem.one/tags/Android\" class=\"mention hashtag\" rel=\"tag\">#<span>Android</span></a> has been typically quite a lot more open <a href=\"https://social.librem.one/tags/iOS\" class=\"mention hashtag\" rel=\"tag\">#<span>iOS</span></a>. And Google has already added some improvements for other app stores. Google says, "hey, we're already trying to find ways to comply" while Apple seems to stick to its guns: "our way is the only way to trusted app stores."</p>",
"contentMap": {
"en": "<p>Interesting comparison between <a href=\"https://social.librem.one/tags/Google\" class=\"mention hashtag\" rel=\"tag\">#<span>Google</span></a> vs <a href=\"https://social.librem.one/tags/Apple\" class=\"mention hashtag\" rel=\"tag\">#<span>Apple</span></a> approaches at <a href=\"https://social.librem.one/tags/DMAWorkshop\" class=\"mention hashtag\" rel=\"tag\">#<span>DMAWorkshop</span></a>. They have very different methods of gatekeeping, and <a href=\"https://social.librem.one/tags/Android\" class=\"mention hashtag\" rel=\"tag\">#<span>Android</span></a> has been typically quite a lot more open <a href=\"https://social.librem.one/tags/iOS\" class=\"mention hashtag\" rel=\"tag\">#<span>iOS</span></a>. And Google has already added some improvements for other app stores. Google says, "hey, we're already trying to find ways to comply" while Apple seems to stick to its guns: "our way is the only way to trusted app stores."</p>"
},
"attachment": [],
"tag": [
{
"type": "Hashtag",
"href": "https://social.librem.one/tags/ios",
"name": "#ios"
},
{
"type": "Hashtag",
"href": "https://social.librem.one/tags/android",
"name": "#android"
},
{
"type": "Hashtag",
"href": "https://social.librem.one/tags/dmaworkshop",
"name": "#dmaworkshop"
},
{
"type": "Hashtag",
"href": "https://social.librem.one/tags/apple",
"name": "#apple"
},
{
"type": "Hashtag",
"href": "https://social.librem.one/tags/google",
"name": "#google"
}
],
"replies": {
"id": "https://social.librem.one/users/eighthave/statuses/109977120584942308/replies",
"type": "Collection",
"first": {
"type": "CollectionPage",
"next": "https://social.librem.one/users/eighthave/statuses/109977120584942308/replies?only_other_accounts=true&page=true",
"partOf": "https://social.librem.one/users/eighthave/statuses/109977120584942308/replies",
"items": []
}
}
}