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.jvns.ca/users/b0rk/statuses/113522523450205145",
"type": "Note",
"summary": null,
"inReplyTo": "https://fosstodon.org/users/ololduck/statuses/113522509039682183",
"published": "2024-11-21T19:10:39Z",
"url": "https://social.jvns.ca/@b0rk/113522523450205145",
"attributedTo": "https://social.jvns.ca/users/b0rk",
"to": [
"https://www.w3.org/ns/activitystreams#Public"
],
"cc": [
"https://social.jvns.ca/users/b0rk/followers",
"https://fosstodon.org/users/ololduck"
],
"sensitive": false,
"atomUri": "https://social.jvns.ca/users/b0rk/statuses/113522523450205145",
"inReplyToAtomUri": "https://fosstodon.org/users/ololduck/statuses/113522509039682183",
"conversation": "tag:jvns.ca,2024-11-21:objectId=786688:objectType=Conversation",
"content": "<p><span class=\"h-card\" translate=\"no\"><a href=\"https://fosstodon.org/@ololduck\" class=\"u-url mention\">@<span>ololduck</span></a></span> I guess the main differences with a pipe are that</p><p>a) if the second process crashes for some reason, the first process can't finish writing to the pipe? (it'll get sent a SIGPIPE signal)<br />b) pipes have a capacity, so if the second process is consuming the input from the pipe slowly, then the first process's writes will block until there's room in the pipe for more data</p><p>there are probably others I'm not thinking of though</p>",
"contentMap": {
"en": "<p><span class=\"h-card\" translate=\"no\"><a href=\"https://fosstodon.org/@ololduck\" class=\"u-url mention\">@<span>ololduck</span></a></span> I guess the main differences with a pipe are that</p><p>a) if the second process crashes for some reason, the first process can't finish writing to the pipe? (it'll get sent a SIGPIPE signal)<br />b) pipes have a capacity, so if the second process is consuming the input from the pipe slowly, then the first process's writes will block until there's room in the pipe for more data</p><p>there are probably others I'm not thinking of though</p>"
},
"attachment": [],
"tag": [
{
"type": "Mention",
"href": "https://fosstodon.org/users/ololduck",
"name": "@ololduck@fosstodon.org"
}
],
"replies": {
"id": "https://social.jvns.ca/users/b0rk/statuses/113522523450205145/replies",
"type": "Collection",
"first": {
"type": "CollectionPage",
"next": "https://social.jvns.ca/users/b0rk/statuses/113522523450205145/replies?only_other_accounts=true&page=true",
"partOf": "https://social.jvns.ca/users/b0rk/statuses/113522523450205145/replies",
"items": []
}
},
"likes": {
"id": "https://social.jvns.ca/users/b0rk/statuses/113522523450205145/likes",
"type": "Collection",
"totalItems": 1
},
"shares": {
"id": "https://social.jvns.ca/users/b0rk/statuses/113522523450205145/shares",
"type": "Collection",
"totalItems": 0
}
}