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://mastodon.top/users/lispi314/statuses/110130279511931153",
"type": "Note",
"summary": null,
"inReplyTo": "https://mastodon.top/users/lispi314/statuses/110130259188733740",
"published": "2023-04-02T16:58:24Z",
"url": "https://mastodon.top/@lispi314/110130279511931153",
"attributedTo": "https://mastodon.top/users/lispi314",
"to": [
"https://www.w3.org/ns/activitystreams#Public"
],
"cc": [
"https://mastodon.top/users/lispi314/followers",
"https://borg.social/users/9bs4r64e74"
],
"sensitive": false,
"atomUri": "https://mastodon.top/users/lispi314/statuses/110130279511931153",
"inReplyToAtomUri": "https://mastodon.top/users/lispi314/statuses/110130259188733740",
"conversation": "tag:merveilles.town,2023-04-02:objectId=23925884:objectType=Conversation",
"content": "<p>@zens@merveilles.town <span class=\"h-card\" translate=\"no\"><a href=\"https://borg.social/@rq\" class=\"u-url mention\">@<span>rq</span></a></span> The next better thing would be to use <a href=\"https://mastodon.top/tags/Usenet\" class=\"mention hashtag\" rel=\"tag\">#<span>Usenet</span></a> / <a href=\"https://mastodon.top/tags/NNTP\" class=\"mention hashtag\" rel=\"tag\">#<span>NNTP</span></a>, such that taking down a single given host for the list server doesn't have any impact at all because your developer base doesn't rely on a single server, rather than just a mitigated impact.</p><p>Of course setting up a new mailing list server is possible too, but it involves a lot more coordination.</p>",
"contentMap": {
"en": "<p>@zens@merveilles.town <span class=\"h-card\" translate=\"no\"><a href=\"https://borg.social/@rq\" class=\"u-url mention\">@<span>rq</span></a></span> The next better thing would be to use <a href=\"https://mastodon.top/tags/Usenet\" class=\"mention hashtag\" rel=\"tag\">#<span>Usenet</span></a> / <a href=\"https://mastodon.top/tags/NNTP\" class=\"mention hashtag\" rel=\"tag\">#<span>NNTP</span></a>, such that taking down a single given host for the list server doesn't have any impact at all because your developer base doesn't rely on a single server, rather than just a mitigated impact.</p><p>Of course setting up a new mailing list server is possible too, but it involves a lot more coordination.</p>"
},
"attachment": [],
"tag": [
{
"type": "Mention",
"href": "https://borg.social/users/9bs4r64e74",
"name": "@rq@borg.social"
},
{
"type": "Hashtag",
"href": "https://mastodon.top/tags/usenet",
"name": "#usenet"
},
{
"type": "Hashtag",
"href": "https://mastodon.top/tags/nntp",
"name": "#nntp"
}
],
"replies": {
"id": "https://mastodon.top/users/lispi314/statuses/110130279511931153/replies",
"type": "Collection",
"first": {
"type": "CollectionPage",
"next": "https://mastodon.top/users/lispi314/statuses/110130279511931153/replies?only_other_accounts=true&page=true",
"partOf": "https://mastodon.top/users/lispi314/statuses/110130279511931153/replies",
"items": []
}
},
"likes": {
"id": "https://mastodon.top/users/lispi314/statuses/110130279511931153/likes",
"type": "Collection",
"totalItems": 4
},
"shares": {
"id": "https://mastodon.top/users/lispi314/statuses/110130279511931153/shares",
"type": "Collection",
"totalItems": 1
}
}