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/da_667/statuses/111109191465278888/replies",
"type": "Collection",
"first": {
"id": "https://infosec.exchange/users/da_667/statuses/111109191465278888/replies?page=true",
"type": "CollectionPage",
"next": "https://infosec.exchange/users/da_667/statuses/111109191465278888/replies?only_other_accounts=true&page=true",
"partOf": "https://infosec.exchange/users/da_667/statuses/111109191465278888/replies",
"items": [
{
"id": "https://infosec.exchange/users/da_667/statuses/111109271098182858",
"type": "Note",
"summary": null,
"inReplyTo": "https://infosec.exchange/users/da_667/statuses/111109191465278888",
"published": "2023-09-22T14:28:50Z",
"url": "https://infosec.exchange/@da_667/111109271098182858",
"attributedTo": "https://infosec.exchange/users/da_667",
"to": [
"https://www.w3.org/ns/activitystreams#Public"
],
"cc": [
"https://infosec.exchange/users/da_667/followers"
],
"sensitive": false,
"atomUri": "https://infosec.exchange/users/da_667/statuses/111109271098182858",
"inReplyToAtomUri": "https://infosec.exchange/users/da_667/statuses/111109191465278888",
"conversation": "tag:infosec.exchange,2023-09-22:objectId=96945971:objectType=Conversation",
"content": "<p>I would also like to note that all of these points apply to the "privacy minded individual", and not necessarily to "Enterprise Ops/Security".</p><p>When I first started talking shit about DoH being bad, I got told that I'm not cypherpunk. Sounds pretty fuckin' cypherpunk, giving corporate entities who have proven they give zero fucks about you even more of your data.</p><p>But I digress. From the point of view of systems administration and support, its also a fucking nightmare for enforcing policy, and troubleshooting connectivity problems, because the web browser now believes it has the right to be handling DNS resolutions independent of your operating system settings.</p><p>On top of that, you have no idea what domains are being resolved, how they're being resolved, or where to even start to troubleshooting the problem.</p><p>From a network security perspective, its pretty much the same can of worms. DoH providers are allowed to have your DNS queries, but you aren't allowed to have that for trying to figure out if any of your hosts are infected, and calling back to a C2 somewhere in the middle of Russia.</p><p>DNS logs have always been a troubleshooting tool. The fact is, you're making them opaque, and given them to an external entity. "Its always DNS" is a joke until it isn't and you have to figure out whats wrong. Only the DNS queries are opaque now, making this shit much more difficult than it needs to be.</p>",
"contentMap": {
"en": "<p>I would also like to note that all of these points apply to the "privacy minded individual", and not necessarily to "Enterprise Ops/Security".</p><p>When I first started talking shit about DoH being bad, I got told that I'm not cypherpunk. Sounds pretty fuckin' cypherpunk, giving corporate entities who have proven they give zero fucks about you even more of your data.</p><p>But I digress. From the point of view of systems administration and support, its also a fucking nightmare for enforcing policy, and troubleshooting connectivity problems, because the web browser now believes it has the right to be handling DNS resolutions independent of your operating system settings.</p><p>On top of that, you have no idea what domains are being resolved, how they're being resolved, or where to even start to troubleshooting the problem.</p><p>From a network security perspective, its pretty much the same can of worms. DoH providers are allowed to have your DNS queries, but you aren't allowed to have that for trying to figure out if any of your hosts are infected, and calling back to a C2 somewhere in the middle of Russia.</p><p>DNS logs have always been a troubleshooting tool. The fact is, you're making them opaque, and given them to an external entity. "Its always DNS" is a joke until it isn't and you have to figure out whats wrong. Only the DNS queries are opaque now, making this shit much more difficult than it needs to be.</p>"
},
"updated": "2023-09-22T14:32:41Z",
"attachment": [],
"tag": [],
"replies": {
"id": "https://infosec.exchange/users/da_667/statuses/111109271098182858/replies",
"type": "Collection",
"first": {
"type": "CollectionPage",
"next": "https://infosec.exchange/users/da_667/statuses/111109271098182858/replies?only_other_accounts=true&page=true",
"partOf": "https://infosec.exchange/users/da_667/statuses/111109271098182858/replies",
"items": []
}
},
"likes": {
"id": "https://infosec.exchange/users/da_667/statuses/111109271098182858/likes",
"type": "Collection",
"totalItems": 54
},
"shares": {
"id": "https://infosec.exchange/users/da_667/statuses/111109271098182858/shares",
"type": "Collection",
"totalItems": 9
}
}
]
}
}