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/resingm/statuses/111337414282011785",
"type": "Note",
"summary": null,
"inReplyTo": "https://fosstodon.org/users/winfried/statuses/111337367252941551",
"published": "2023-11-01T21:28:39Z",
"url": "https://infosec.exchange/@resingm/111337414282011785",
"attributedTo": "https://infosec.exchange/users/resingm",
"to": [
"https://www.w3.org/ns/activitystreams#Public"
],
"cc": [
"https://infosec.exchange/users/resingm/followers",
"https://fosstodon.org/users/winfried"
],
"sensitive": false,
"atomUri": "https://infosec.exchange/users/resingm/statuses/111337414282011785",
"inReplyToAtomUri": "https://fosstodon.org/users/winfried/statuses/111337367252941551",
"conversation": "tag:infosec.exchange,2023-11-01:objectId=107156261:objectType=Conversation",
"content": "<p><span class=\"h-card\" translate=\"no\"><a href=\"https://fosstodon.org/@winfried\" class=\"u-url mention\" rel=\"nofollow noopener noreferrer\" target=\"_blank\">@<span>winfried</span></a></span> - for sure the endpoint gives it away, but I doubt that an ISP handshakes with every IP that shows up in their TCP/443 upstream to see if it runs a resolver which responds to DoH. Yes, you can filter out known DNS revolvers, but its hard to believe to do that with all IPs. And thats, why I asked for fingerprinting techniques. I found some nice papers, that I'll work through next week. I might post a follow-up afterwards</p>",
"contentMap": {
"en": "<p><span class=\"h-card\" translate=\"no\"><a href=\"https://fosstodon.org/@winfried\" class=\"u-url mention\" rel=\"nofollow noopener noreferrer\" target=\"_blank\">@<span>winfried</span></a></span> - for sure the endpoint gives it away, but I doubt that an ISP handshakes with every IP that shows up in their TCP/443 upstream to see if it runs a resolver which responds to DoH. Yes, you can filter out known DNS revolvers, but its hard to believe to do that with all IPs. And thats, why I asked for fingerprinting techniques. I found some nice papers, that I'll work through next week. I might post a follow-up afterwards</p>"
},
"attachment": [],
"tag": [
{
"type": "Mention",
"href": "https://fosstodon.org/users/winfried",
"name": "@winfried@fosstodon.org"
}
],
"replies": {
"id": "https://infosec.exchange/users/resingm/statuses/111337414282011785/replies",
"type": "Collection",
"first": {
"type": "CollectionPage",
"next": "https://infosec.exchange/users/resingm/statuses/111337414282011785/replies?only_other_accounts=true&page=true",
"partOf": "https://infosec.exchange/users/resingm/statuses/111337414282011785/replies",
"items": []
}
},
"likes": {
"id": "https://infosec.exchange/users/resingm/statuses/111337414282011785/likes",
"type": "Collection",
"totalItems": 0
},
"shares": {
"id": "https://infosec.exchange/users/resingm/statuses/111337414282011785/shares",
"type": "Collection",
"totalItems": 0
}
}