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://discuss.systems/users/ocratato/statuses/113049108246803257",
"type": "Note",
"summary": null,
"inReplyTo": "https://discuss.systems/users/xand/statuses/113045981162046973",
"published": "2024-08-30T04:34:56Z",
"url": "https://discuss.systems/@ocratato/113049108246803257",
"attributedTo": "https://discuss.systems/users/ocratato",
"to": [
"https://www.w3.org/ns/activitystreams#Public"
],
"cc": [
"https://discuss.systems/users/ocratato/followers",
"https://discuss.systems/users/xand"
],
"sensitive": false,
"atomUri": "https://discuss.systems/users/ocratato/statuses/113049108246803257",
"inReplyToAtomUri": "https://discuss.systems/users/xand/statuses/113045981162046973",
"conversation": "tag:discuss.systems,2024-08-29:objectId=24241097:objectType=Conversation",
"content": "<p><span class=\"h-card\" translate=\"no\"><a href=\"https://discuss.systems/@xand\" class=\"u-url mention\">@<span>xand</span></a></span> I think I prefer the term "sub-projects".</p><p>Large projects are rarely successful, so they need to be subdivided. However this can introduce even more complexity if the sub-projects are interdependent.</p><p>My hypothesis is that the architect should define the interfaces between the modules and they should be implemented as a set of test harnesses prior to beginning main development.</p><p><a href=\"https://discuss.systems/tags/Softwarearchitecture\" class=\"mention hashtag\" rel=\"tag\">#<span>Softwarearchitecture</span></a></p>",
"contentMap": {
"en": "<p><span class=\"h-card\" translate=\"no\"><a href=\"https://discuss.systems/@xand\" class=\"u-url mention\">@<span>xand</span></a></span> I think I prefer the term "sub-projects".</p><p>Large projects are rarely successful, so they need to be subdivided. However this can introduce even more complexity if the sub-projects are interdependent.</p><p>My hypothesis is that the architect should define the interfaces between the modules and they should be implemented as a set of test harnesses prior to beginning main development.</p><p><a href=\"https://discuss.systems/tags/Softwarearchitecture\" class=\"mention hashtag\" rel=\"tag\">#<span>Softwarearchitecture</span></a></p>"
},
"attachment": [],
"tag": [
{
"type": "Mention",
"href": "https://discuss.systems/users/xand",
"name": "@xand"
},
{
"type": "Hashtag",
"href": "https://discuss.systems/tags/softwarearchitecture",
"name": "#softwarearchitecture"
}
],
"replies": {
"id": "https://discuss.systems/users/ocratato/statuses/113049108246803257/replies",
"type": "Collection",
"first": {
"type": "CollectionPage",
"next": "https://discuss.systems/users/ocratato/statuses/113049108246803257/replies?only_other_accounts=true&page=true",
"partOf": "https://discuss.systems/users/ocratato/statuses/113049108246803257/replies",
"items": []
}
},
"likes": {
"id": "https://discuss.systems/users/ocratato/statuses/113049108246803257/likes",
"type": "Collection",
"totalItems": 0
},
"shares": {
"id": "https://discuss.systems/users/ocratato/statuses/113049108246803257/shares",
"type": "Collection",
"totalItems": 0
}
}