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",
"litepub": "http://litepub.social/ns#",
"directMessage": "litepub:directMessage",
"Hashtag": "as:Hashtag"
}
],
"id": "https://infosec.exchange/users/australeo/statuses/109385108337663009",
"type": "Note",
"summary": null,
"inReplyTo": null,
"published": "2022-11-22T02:31:34Z",
"url": "https://infosec.exchange/@australeo/109385108337663009",
"attributedTo": "https://infosec.exchange/users/australeo",
"to": [
"https://www.w3.org/ns/activitystreams#Public"
],
"cc": [
"https://infosec.exchange/users/australeo/followers"
],
"sensitive": false,
"atomUri": "https://infosec.exchange/users/australeo/statuses/109385108337663009",
"inReplyToAtomUri": null,
"conversation": "tag:infosec.exchange,2022-11-22:objectId=23333756:objectType=Conversation",
"content": "<p>Hard to overstate how useful the `nom` crate is for building parsers. One of the first things I usually do when researching a new target is build a POC client/server program, and nom makes it incredibly easy to mock-up new protocols. If you are still doing everything with Python struct.unpack(), maybe check out nom instead next time? <a href=\"https://github.com/Geal/nom\" target=\"_blank\" rel=\"nofollow noopener noreferrer\" translate=\"no\"><span class=\"invisible\">https://</span><span class=\"\">github.com/Geal/nom</span><span class=\"invisible\"></span></a> <a href=\"https://infosec.exchange/tags/rust\" class=\"mention hashtag\" rel=\"tag\">#<span>rust</span></a> <a href=\"https://infosec.exchange/tags/rustlang\" class=\"mention hashtag\" rel=\"tag\">#<span>rustlang</span></a></p>",
"contentMap": {
"en": "<p>Hard to overstate how useful the `nom` crate is for building parsers. One of the first things I usually do when researching a new target is build a POC client/server program, and nom makes it incredibly easy to mock-up new protocols. If you are still doing everything with Python struct.unpack(), maybe check out nom instead next time? <a href=\"https://github.com/Geal/nom\" target=\"_blank\" rel=\"nofollow noopener noreferrer\" translate=\"no\"><span class=\"invisible\">https://</span><span class=\"\">github.com/Geal/nom</span><span class=\"invisible\"></span></a> <a href=\"https://infosec.exchange/tags/rust\" class=\"mention hashtag\" rel=\"tag\">#<span>rust</span></a> <a href=\"https://infosec.exchange/tags/rustlang\" class=\"mention hashtag\" rel=\"tag\">#<span>rustlang</span></a></p>"
},
"attachment": [],
"tag": [
{
"type": "Hashtag",
"href": "https://infosec.exchange/tags/rust",
"name": "#rust"
},
{
"type": "Hashtag",
"href": "https://infosec.exchange/tags/rustlang",
"name": "#rustlang"
}
],
"replies": {
"id": "https://infosec.exchange/users/australeo/statuses/109385108337663009/replies",
"type": "Collection",
"first": {
"type": "CollectionPage",
"next": "https://infosec.exchange/users/australeo/statuses/109385108337663009/replies?only_other_accounts=true&page=true",
"partOf": "https://infosec.exchange/users/australeo/statuses/109385108337663009/replies",
"items": []
}
},
"likes": {
"id": "https://infosec.exchange/users/australeo/statuses/109385108337663009/likes",
"type": "Collection",
"totalItems": 6
},
"shares": {
"id": "https://infosec.exchange/users/australeo/statuses/109385108337663009/shares",
"type": "Collection",
"totalItems": 0
}
}