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",
"Hashtag": "as:Hashtag"
}
],
"id": "https://c.im/users/dtauvdiodr/statuses/113269001211339104",
"type": "Note",
"summary": null,
"inReplyTo": null,
"published": "2024-10-08T00:36:36Z",
"url": "https://c.im/@dtauvdiodr/113269001211339104",
"attributedTo": "https://c.im/users/dtauvdiodr",
"to": [
"https://www.w3.org/ns/activitystreams#Public"
],
"cc": [
"https://c.im/users/dtauvdiodr/followers"
],
"sensitive": false,
"atomUri": "https://c.im/users/dtauvdiodr/statuses/113269001211339104",
"inReplyToAtomUri": null,
"conversation": "tag:c.im,2024-10-08:objectId=213883727:objectType=Conversation",
"content": "<p>I need to rant. Maybe I have a few Resilience friends out there who can sympathize.</p><p>It's not OK to cut people off from complexity.</p><p>First of all, it's insulting. The action infuses itself with distrust. It is some sort of disgusting us-vs-them holdover from like 2005.</p><p>Second of all, the dogma of "the developer sits and works on their little piece and knows nothing about what goes on around them" doesn't work anymore. Interactions matter, sharing knowledge matters, working together to understand each other's limitations and where we can find adaptive capacity, that all matters. It's not stuff you can put on a pre-flight checklist or a runbook, it's relationship building.</p><p>When we build relationships across the boundaries of the technologies we're building, we learn how to see the interactions between them. If we are only on one side of the equation, we're missing the interaction. And that's where the learning happens, witnessing how the system interacts and updating our mental models.</p><p>When we share this activity, we form a more complete picture of the system between a more broadly trained set of people. We discover new ways of doing things because new perspectives are added. Diversity makes these interactions come alive.</p><p>So when leaders pull out their managerspeak dialectic and say to me "devs don't need to know anything about the orchestration system" ... that isn't what I'm hearing.</p><p>I'm hearing: "Control and simplification is more important than learning."</p><p><a href=\"https://c.im/tags/SRE\" class=\"mention hashtag\" rel=\"tag\">#<span>SRE</span></a> <a href=\"https://c.im/tags/Resilience\" class=\"mention hashtag\" rel=\"tag\">#<span>Resilience</span></a> <a href=\"https://c.im/tags/Reliability\" class=\"mention hashtag\" rel=\"tag\">#<span>Reliability</span></a></p>",
"contentMap": {
"en": "<p>I need to rant. Maybe I have a few Resilience friends out there who can sympathize.</p><p>It's not OK to cut people off from complexity.</p><p>First of all, it's insulting. The action infuses itself with distrust. It is some sort of disgusting us-vs-them holdover from like 2005.</p><p>Second of all, the dogma of "the developer sits and works on their little piece and knows nothing about what goes on around them" doesn't work anymore. Interactions matter, sharing knowledge matters, working together to understand each other's limitations and where we can find adaptive capacity, that all matters. It's not stuff you can put on a pre-flight checklist or a runbook, it's relationship building.</p><p>When we build relationships across the boundaries of the technologies we're building, we learn how to see the interactions between them. If we are only on one side of the equation, we're missing the interaction. And that's where the learning happens, witnessing how the system interacts and updating our mental models.</p><p>When we share this activity, we form a more complete picture of the system between a more broadly trained set of people. We discover new ways of doing things because new perspectives are added. Diversity makes these interactions come alive.</p><p>So when leaders pull out their managerspeak dialectic and say to me "devs don't need to know anything about the orchestration system" ... that isn't what I'm hearing.</p><p>I'm hearing: "Control and simplification is more important than learning."</p><p><a href=\"https://c.im/tags/SRE\" class=\"mention hashtag\" rel=\"tag\">#<span>SRE</span></a> <a href=\"https://c.im/tags/Resilience\" class=\"mention hashtag\" rel=\"tag\">#<span>Resilience</span></a> <a href=\"https://c.im/tags/Reliability\" class=\"mention hashtag\" rel=\"tag\">#<span>Reliability</span></a></p>"
},
"updated": "2024-10-08T00:37:09Z",
"attachment": [],
"tag": [
{
"type": "Hashtag",
"href": "https://c.im/tags/sre",
"name": "#sre"
},
{
"type": "Hashtag",
"href": "https://c.im/tags/resilience",
"name": "#resilience"
},
{
"type": "Hashtag",
"href": "https://c.im/tags/reliability",
"name": "#reliability"
}
],
"replies": {
"id": "https://c.im/users/dtauvdiodr/statuses/113269001211339104/replies",
"type": "Collection",
"first": {
"type": "CollectionPage",
"next": "https://c.im/users/dtauvdiodr/statuses/113269001211339104/replies?only_other_accounts=true&page=true",
"partOf": "https://c.im/users/dtauvdiodr/statuses/113269001211339104/replies",
"items": []
}
},
"likes": {
"id": "https://c.im/users/dtauvdiodr/statuses/113269001211339104/likes",
"type": "Collection",
"totalItems": 11
},
"shares": {
"id": "https://c.im/users/dtauvdiodr/statuses/113269001211339104/shares",
"type": "Collection",
"totalItems": 4
}
}