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/saraislet/statuses/109426852597881201/replies",
"type": "Collection",
"first": {
"id": "https://infosec.exchange/users/saraislet/statuses/109426852597881201/replies?page=true",
"type": "CollectionPage",
"next": "https://infosec.exchange/users/saraislet/statuses/109426852597881201/replies?only_other_accounts=true&page=true",
"partOf": "https://infosec.exchange/users/saraislet/statuses/109426852597881201/replies",
"items": [
{
"id": "https://infosec.exchange/users/saraislet/statuses/109431422536210250",
"type": "Note",
"summary": null,
"inReplyTo": "https://infosec.exchange/users/saraislet/statuses/109426852597881201",
"published": "2022-11-30T06:49:53Z",
"url": "https://infosec.exchange/@saraislet/109431422536210250",
"attributedTo": "https://infosec.exchange/users/saraislet",
"to": [
"https://www.w3.org/ns/activitystreams#Public"
],
"cc": [
"https://infosec.exchange/users/saraislet/followers"
],
"sensitive": false,
"atomUri": "https://infosec.exchange/users/saraislet/statuses/109431422536210250",
"inReplyToAtomUri": "https://infosec.exchange/users/saraislet/statuses/109426852597881201",
"conversation": "tag:infosec.exchange,2022-11-29:objectId=25209978:objectType=Conversation",
"content": "<p>How to secure a Content Distribution Network (CDN), Part 2.1: What are you protecting? — Availability!</p><p>1. The primary role of a CDN is to DISTRIBUTE content, so keep it up! Some nuances here:</p><p>1a. Performance: Operate efficiently—from Watts per content unit delivered, to operational support and maintenance burden on engineers. If the CDN isn't performant, why have a CDN?</p><p>1b. The Caching Problem: Give clients the content they're expecting to receive, not an outdated version.</p><p>1c. Reliability: Many people say Security shouldn't be the "Department of No", and yet we keep targeting "Five Neins". 🤷🏼♀️</p><p>1d. Latency: Deliver content to clients within stable thresholds for latency. (Not all CDN use cases require minimizing latency—but capacity and capability to achieve consistent delivery within a threshold seems IMO to be a common value. YMMV.)</p><p>*record scratch*</p><p>"Sarai, this is sounding like a classic engineering and reliability chat"<br />"That's right"<br />"Where's the security?"<br />*points at meme*: "They're the same picture. You're defending engineering and product goals, in order to maintain the ability to meet business outcomes. These should be no further from Security than Privacy is."</p><p>"Ahhh. Why are you writing this as a conversation?"<br />"Read too much Plato as a child."</p>",
"contentMap": {
"en": "<p>How to secure a Content Distribution Network (CDN), Part 2.1: What are you protecting? — Availability!</p><p>1. The primary role of a CDN is to DISTRIBUTE content, so keep it up! Some nuances here:</p><p>1a. Performance: Operate efficiently—from Watts per content unit delivered, to operational support and maintenance burden on engineers. If the CDN isn't performant, why have a CDN?</p><p>1b. The Caching Problem: Give clients the content they're expecting to receive, not an outdated version.</p><p>1c. Reliability: Many people say Security shouldn't be the "Department of No", and yet we keep targeting "Five Neins". 🤷🏼♀️</p><p>1d. Latency: Deliver content to clients within stable thresholds for latency. (Not all CDN use cases require minimizing latency—but capacity and capability to achieve consistent delivery within a threshold seems IMO to be a common value. YMMV.)</p><p>*record scratch*</p><p>"Sarai, this is sounding like a classic engineering and reliability chat"<br />"That's right"<br />"Where's the security?"<br />*points at meme*: "They're the same picture. You're defending engineering and product goals, in order to maintain the ability to meet business outcomes. These should be no further from Security than Privacy is."</p><p>"Ahhh. Why are you writing this as a conversation?"<br />"Read too much Plato as a child."</p>"
},
"attachment": [],
"tag": [],
"replies": {
"id": "https://infosec.exchange/users/saraislet/statuses/109431422536210250/replies",
"type": "Collection",
"first": {
"type": "CollectionPage",
"next": "https://infosec.exchange/users/saraislet/statuses/109431422536210250/replies?min_id=109431836960949104&page=true",
"partOf": "https://infosec.exchange/users/saraislet/statuses/109431422536210250/replies",
"items": [
"https://infosec.exchange/users/saraislet/statuses/109431836960949104"
]
}
},
"likes": {
"id": "https://infosec.exchange/users/saraislet/statuses/109431422536210250/likes",
"type": "Collection",
"totalItems": 23
},
"shares": {
"id": "https://infosec.exchange/users/saraislet/statuses/109431422536210250/shares",
"type": "Collection",
"totalItems": 4
}
}
]
}
}