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",
"type": "Note",
"summary": null,
"inReplyTo": null,
"published": "2023-09-22T14:08:35Z",
"url": "https://infosec.exchange/@da_667/111109191465278888",
"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/111109191465278888",
"inReplyToAtomUri": null,
"conversation": "tag:infosec.exchange,2023-09-22:objectId=96945971:objectType=Conversation",
"content": "<p>Time for me to reiterate why I think DOH is fucking garbage. This is the cliffnotes version:</p><p>-If you read the RFC, never once is privacy listed as a goal for the protocol<br />-Ostensibly, you get some privacy on the first hop, but from there, you have zero guarantees on literally anything. You have promises from various companies, but that doesn't mean jack shit.<br />-I'd like you to consider that cloudflare doesn't have a good track record of policing abuse of their platforms, they tacitly support white supremecists and terrorists, they've been known to forward abuse requests containing personal information of those who have submitted them to their abusers, and they have zero financial incentive to stop the flow of traffic. THIS INCLUDES MALWARE, THERE IS SO MUCH FUCKING MALWARE USING CLOUDFLARE. They are a default DoH provider choice in the major browsers that support it.<br />-Transaction ID is always set to zero for DoH requests to improve caching. This is actually written into the protocol. Y'all know why the transaction ID/DNS ID exists, right? This opens up attack paths for man in the middle attacks. Think QUANTUM and PRISM-type bullshit, where the answer to your DNS query is changed but you'll never know.<br />-The only goal of the protocol was to move DNS resolution to the browser, so that the browser is cognizant of how domains are being resolved. Its anti-adblocking tech. <br />-Think about who the major players are behind DoH - It was driven by Cloudflare, Mozilla, and Google. and while I like Firefox, they all have financial incentive to see how domain resolution is occuring and ensure ads are delivered to clients. Y'all are aware of google's Web Integrity web DRM shit, right? How much you wanna bet that if it becomes a standard, there will be websites popping up whereby resolution via DoH is required for viewing the content? I wonder why that would be?<br />-Flow analysis easily reveals which HTTPS traffic is likely to be DoH traffic. You can't hide connection metadata.<br />-Several tools have been developed to used DoH as C2, and even file storage, if you're brave enough.</p>",
"contentMap": {
"en": "<p>Time for me to reiterate why I think DOH is fucking garbage. This is the cliffnotes version:</p><p>-If you read the RFC, never once is privacy listed as a goal for the protocol<br />-Ostensibly, you get some privacy on the first hop, but from there, you have zero guarantees on literally anything. You have promises from various companies, but that doesn't mean jack shit.<br />-I'd like you to consider that cloudflare doesn't have a good track record of policing abuse of their platforms, they tacitly support white supremecists and terrorists, they've been known to forward abuse requests containing personal information of those who have submitted them to their abusers, and they have zero financial incentive to stop the flow of traffic. THIS INCLUDES MALWARE, THERE IS SO MUCH FUCKING MALWARE USING CLOUDFLARE. They are a default DoH provider choice in the major browsers that support it.<br />-Transaction ID is always set to zero for DoH requests to improve caching. This is actually written into the protocol. Y'all know why the transaction ID/DNS ID exists, right? This opens up attack paths for man in the middle attacks. Think QUANTUM and PRISM-type bullshit, where the answer to your DNS query is changed but you'll never know.<br />-The only goal of the protocol was to move DNS resolution to the browser, so that the browser is cognizant of how domains are being resolved. Its anti-adblocking tech. <br />-Think about who the major players are behind DoH - It was driven by Cloudflare, Mozilla, and Google. and while I like Firefox, they all have financial incentive to see how domain resolution is occuring and ensure ads are delivered to clients. Y'all are aware of google's Web Integrity web DRM shit, right? How much you wanna bet that if it becomes a standard, there will be websites popping up whereby resolution via DoH is required for viewing the content? I wonder why that would be?<br />-Flow analysis easily reveals which HTTPS traffic is likely to be DoH traffic. You can't hide connection metadata.<br />-Several tools have been developed to used DoH as C2, and even file storage, if you're brave enough.</p>"
},
"updated": "2023-09-22T14:13:28Z",
"attachment": [],
"tag": [],
"replies": {
"id": "https://infosec.exchange/users/da_667/statuses/111109191465278888/replies",
"type": "Collection",
"first": {
"type": "CollectionPage",
"next": "https://infosec.exchange/users/da_667/statuses/111109191465278888/replies?min_id=111109271098182858&page=true",
"partOf": "https://infosec.exchange/users/da_667/statuses/111109191465278888/replies",
"items": [
"https://infosec.exchange/users/da_667/statuses/111109271098182858"
]
}
},
"likes": {
"id": "https://infosec.exchange/users/da_667/statuses/111109191465278888/likes",
"type": "Collection",
"totalItems": 207
},
"shares": {
"id": "https://infosec.exchange/users/da_667/statuses/111109191465278888/shares",
"type": "Collection",
"totalItems": 130
}
}