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"
}
],
"id": "https://macaw.social/users/thinkingfish/statuses/110648626782439680",
"type": "Note",
"summary": "birdsite",
"inReplyTo": "https://macaw.social/users/thinkingfish/statuses/110648574943049805",
"published": "2023-07-03T06:00:56Z",
"url": "https://macaw.social/@thinkingfish/110648626782439680",
"attributedTo": "https://macaw.social/users/thinkingfish",
"to": [
"https://www.w3.org/ns/activitystreams#Public"
],
"cc": [
"https://macaw.social/users/thinkingfish/followers"
],
"sensitive": true,
"atomUri": "https://macaw.social/users/thinkingfish/statuses/110648626782439680",
"inReplyToAtomUri": "https://macaw.social/users/thinkingfish/statuses/110648574943049805",
"conversation": "tag:macaw.social,2023-07-03:objectId=10830714:objectType=Conversation",
"content": "<p>I also think if they are really counting tweets, then they are seriously out of infra engineers especially TFE/T3 expertise. Because in the history of Twitter load was almost always shed at the earliest possible place, which is the reverse proxy returning a 500. But this time load is shed somewhere in the Core Services (TFE doesn't count tweets) which is suboptimal (multiple services doing work for nothing). It implies Twitter is likely quite vulnerable to various types of DDoS attacks.</p>",
"contentMap": {
"en": "<p>I also think if they are really counting tweets, then they are seriously out of infra engineers especially TFE/T3 expertise. Because in the history of Twitter load was almost always shed at the earliest possible place, which is the reverse proxy returning a 500. But this time load is shed somewhere in the Core Services (TFE doesn't count tweets) which is suboptimal (multiple services doing work for nothing). It implies Twitter is likely quite vulnerable to various types of DDoS attacks.</p>"
},
"updated": "2023-07-03T06:25:57Z",
"attachment": [],
"tag": [],
"replies": {
"id": "https://macaw.social/users/thinkingfish/statuses/110648626782439680/replies",
"type": "Collection",
"first": {
"type": "CollectionPage",
"next": "https://macaw.social/users/thinkingfish/statuses/110648626782439680/replies?only_other_accounts=true&page=true",
"partOf": "https://macaw.social/users/thinkingfish/statuses/110648626782439680/replies",
"items": []
}
},
"likes": {
"id": "https://macaw.social/users/thinkingfish/statuses/110648626782439680/likes",
"type": "Collection",
"totalItems": 35
},
"shares": {
"id": "https://macaw.social/users/thinkingfish/statuses/110648626782439680/shares",
"type": "Collection",
"totalItems": 9
}
}