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"
}
],
"id": "https://infosec.exchange/users/tasket/statuses/113370227214204685",
"type": "Note",
"summary": null,
"inReplyTo": null,
"published": "2024-10-25T21:39:43Z",
"url": "https://infosec.exchange/@tasket/113370227214204685",
"attributedTo": "https://infosec.exchange/users/tasket",
"to": [
"https://www.w3.org/ns/activitystreams#Public"
],
"cc": [
"https://infosec.exchange/users/tasket/followers"
],
"sensitive": false,
"atomUri": "https://infosec.exchange/users/tasket/statuses/113370227214204685",
"inReplyToAtomUri": null,
"conversation": "tag:infosec.exchange,2024-10-25:objectId=206595107:objectType=Conversation",
"content": "<p>Its odd how we expect society to be pro-literacy, but then in IT we constantly make arguments against computer literacy because checking things like addresses gets in the way of instant, constant gratification. So most of you get upset when I suggest that YOU should remind users to actually check the spelling of who the f*ck they are actually accessing.</p><p>But no, that's too much rocket science.</p><p>\"Oh but the domain spelling doesn't matter because...\" stupid excuse consisting of exceptional incidents. Or saying that users can't know the difference between microsoft.com and edge-update.com. Or suggesting that we'll get the phishing problem licked one day without any bothersome checks by the user – this is literally impossible on an open network, so your ultimate solution would have to be the equivalent of closing the net and/or converting all endpoints to dumb terminals.</p><p>🙃 I now return you to our regularly scheduled phishing stories...</p>",
"contentMap": {
"en": "<p>Its odd how we expect society to be pro-literacy, but then in IT we constantly make arguments against computer literacy because checking things like addresses gets in the way of instant, constant gratification. So most of you get upset when I suggest that YOU should remind users to actually check the spelling of who the f*ck they are actually accessing.</p><p>But no, that's too much rocket science.</p><p>\"Oh but the domain spelling doesn't matter because...\" stupid excuse consisting of exceptional incidents. Or saying that users can't know the difference between microsoft.com and edge-update.com. Or suggesting that we'll get the phishing problem licked one day without any bothersome checks by the user – this is literally impossible on an open network, so your ultimate solution would have to be the equivalent of closing the net and/or converting all endpoints to dumb terminals.</p><p>🙃 I now return you to our regularly scheduled phishing stories...</p>"
},
"updated": "2024-10-28T15:43:41Z",
"attachment": [],
"tag": [],
"replies": {
"id": "https://infosec.exchange/users/tasket/statuses/113370227214204685/replies",
"type": "Collection",
"first": {
"type": "CollectionPage",
"next": "https://infosec.exchange/users/tasket/statuses/113370227214204685/replies?min_id=113862756103919003&page=true",
"partOf": "https://infosec.exchange/users/tasket/statuses/113370227214204685/replies",
"items": [
"https://infosec.exchange/users/tasket/statuses/113862756103919003"
]
}
},
"likes": {
"id": "https://infosec.exchange/users/tasket/statuses/113370227214204685/likes",
"type": "Collection",
"totalItems": 3
},
"shares": {
"id": "https://infosec.exchange/users/tasket/statuses/113370227214204685/shares",
"type": "Collection",
"totalItems": 1
}
}