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.coop/users/smallcircles/statuses/113542059725414972",
"type": "Note",
"summary": null,
"inReplyTo": "https://social.coop/users/smallcircles/statuses/113542032899291372",
"published": "2024-11-25T05:58:59Z",
"url": "https://social.coop/@smallcircles/113542059725414972",
"attributedTo": "https://social.coop/users/smallcircles",
"to": [
"https://www.w3.org/ns/activitystreams#Public"
],
"cc": [
"https://social.coop/users/smallcircles/followers",
"https://mastodon.social/users/dahukanna"
],
"sensitive": false,
"atomUri": "https://social.coop/users/smallcircles/statuses/113542059725414972",
"inReplyToAtomUri": "https://social.coop/users/smallcircles/statuses/113542032899291372",
"conversation": "tag:social.coop,2024-11-24:objectId=137033351:objectType=Conversation",
"content": "<p><span class=\"h-card\" translate=\"no\"><a href=\"https://mastodon.social/@dahukanna\" class=\"u-url mention\">@<span>dahukanna</span></a></span> </p><p>Also I see <a href=\"https://social.coop/tags/UX\" class=\"mention hashtag\" rel=\"tag\">#<span>UX</span></a> as a huge toolbox, where you find the proper tool to use. This makes "Implement UX of.." non-descriptive without context, or rather UX is something you can slap onto anything.</p><p>Theory (how we think we do UX) and practice are wildly different. Frustration ensues as the tools are used haphazardly in not well defined processes.</p><p>This last bit is where I feel SX coming into play. It acknowledges both project concerns and externalities, sees the broader picture still.</p>",
"contentMap": {
"en": "<p><span class=\"h-card\" translate=\"no\"><a href=\"https://mastodon.social/@dahukanna\" class=\"u-url mention\">@<span>dahukanna</span></a></span> </p><p>Also I see <a href=\"https://social.coop/tags/UX\" class=\"mention hashtag\" rel=\"tag\">#<span>UX</span></a> as a huge toolbox, where you find the proper tool to use. This makes "Implement UX of.." non-descriptive without context, or rather UX is something you can slap onto anything.</p><p>Theory (how we think we do UX) and practice are wildly different. Frustration ensues as the tools are used haphazardly in not well defined processes.</p><p>This last bit is where I feel SX coming into play. It acknowledges both project concerns and externalities, sees the broader picture still.</p>"
},
"attachment": [],
"tag": [
{
"type": "Mention",
"href": "https://mastodon.social/users/dahukanna",
"name": "@dahukanna@mastodon.social"
},
{
"type": "Hashtag",
"href": "https://social.coop/tags/ux",
"name": "#ux"
}
],
"replies": {
"id": "https://social.coop/users/smallcircles/statuses/113542059725414972/replies",
"type": "Collection",
"first": {
"type": "CollectionPage",
"next": "https://social.coop/users/smallcircles/statuses/113542059725414972/replies?min_id=113542081956304808&page=true",
"partOf": "https://social.coop/users/smallcircles/statuses/113542059725414972/replies",
"items": [
"https://social.coop/users/smallcircles/statuses/113542081956304808"
]
}
},
"likes": {
"id": "https://social.coop/users/smallcircles/statuses/113542059725414972/likes",
"type": "Collection",
"totalItems": 1
},
"shares": {
"id": "https://social.coop/users/smallcircles/statuses/113542059725414972/shares",
"type": "Collection",
"totalItems": 0
}
}