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",
"Hashtag": "as:Hashtag"
}
],
"id": "https://corteximplant.com/users/Sirs0ri/statuses/110650371910877488",
"type": "Note",
"summary": null,
"inReplyTo": null,
"published": "2023-07-03T13:24:44Z",
"url": "https://corteximplant.com/@Sirs0ri/110650371910877488",
"attributedTo": "https://corteximplant.com/users/Sirs0ri",
"to": [
"https://www.w3.org/ns/activitystreams#Public"
],
"cc": [
"https://corteximplant.com/users/Sirs0ri/followers"
],
"sensitive": false,
"atomUri": "https://corteximplant.com/users/Sirs0ri/statuses/110650371910877488",
"inReplyToAtomUri": null,
"conversation": "tag:corteximplant.com,2023-07-03:objectId=6412419:objectType=Conversation",
"content": "<p>Ooooooh, I figured out why my <a href=\"https://corteximplant.com/tags/HomeAssistant\" class=\"mention hashtag\" rel=\"tag\">#<span>HomeAssistant</span></a> instance's been so powerhungry lately! </p><p>A couple of versions ago they split the \"states\" database table in two, with all the states' attributes being in another table, which meant that my sensors running on the <a href=\"https://corteximplant.com/tags/database\" class=\"mention hashtag\" rel=\"tag\">#<span>database</span></a> for newest / oldest / most updated entities now needed a JOIN between the <code>states</code> and <code>state_attributes</code> tables (as described in <a href=\"https://www.home-assistant.io/integrations/sql#configuration-by-yaml\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">the docs</a>). </p><p>The split has allowed HA to run a lot more performant (apparently), but in turn the updated queries I used with the JOIN statements would cause my poor raspi's CPU to spike to 100% usage every time the sensors were updated. Because apparently a LEFT JOIN on a db with about 2 million states is a bit much for the poor little thing.</p><p>I disabled the expensive SQL Queries and the CPU usage dropped instantly from ~33% down to 8-ish.</p><p>In case anyone's interested in the queries, I'll add them below, maybe some <a href=\"https://corteximplant.com/tags/SQL\" class=\"mention hashtag\" rel=\"tag\">#<span>SQL</span></a> wizard has some ideas for optimizations?</p>",
"contentMap": {
"en": "<p>Ooooooh, I figured out why my <a href=\"https://corteximplant.com/tags/HomeAssistant\" class=\"mention hashtag\" rel=\"tag\">#<span>HomeAssistant</span></a> instance's been so powerhungry lately! </p><p>A couple of versions ago they split the \"states\" database table in two, with all the states' attributes being in another table, which meant that my sensors running on the <a href=\"https://corteximplant.com/tags/database\" class=\"mention hashtag\" rel=\"tag\">#<span>database</span></a> for newest / oldest / most updated entities now needed a JOIN between the <code>states</code> and <code>state_attributes</code> tables (as described in <a href=\"https://www.home-assistant.io/integrations/sql#configuration-by-yaml\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">the docs</a>). </p><p>The split has allowed HA to run a lot more performant (apparently), but in turn the updated queries I used with the JOIN statements would cause my poor raspi's CPU to spike to 100% usage every time the sensors were updated. Because apparently a LEFT JOIN on a db with about 2 million states is a bit much for the poor little thing.</p><p>I disabled the expensive SQL Queries and the CPU usage dropped instantly from ~33% down to 8-ish.</p><p>In case anyone's interested in the queries, I'll add them below, maybe some <a href=\"https://corteximplant.com/tags/SQL\" class=\"mention hashtag\" rel=\"tag\">#<span>SQL</span></a> wizard has some ideas for optimizations?</p>"
},
"updated": "2023-07-03T13:29:37Z",
"attachment": [],
"tag": [
{
"type": "Hashtag",
"href": "https://corteximplant.com/tags/homeassistant",
"name": "#homeassistant"
},
{
"type": "Hashtag",
"href": "https://corteximplant.com/tags/database",
"name": "#database"
},
{
"type": "Hashtag",
"href": "https://corteximplant.com/tags/sql",
"name": "#sql"
}
],
"replies": {
"id": "https://corteximplant.com/users/Sirs0ri/statuses/110650371910877488/replies",
"type": "Collection",
"first": {
"type": "CollectionPage",
"next": "https://corteximplant.com/users/Sirs0ri/statuses/110650371910877488/replies?min_id=110669529489323567&page=true",
"partOf": "https://corteximplant.com/users/Sirs0ri/statuses/110650371910877488/replies",
"items": [
"https://corteximplant.com/users/Sirs0ri/statuses/110650383899177880",
"https://corteximplant.com/users/Sirs0ri/statuses/110669529489323567"
]
}
},
"likes": {
"id": "https://corteximplant.com/users/Sirs0ri/statuses/110650371910877488/likes",
"type": "Collection",
"totalItems": 8
},
"shares": {
"id": "https://corteximplant.com/users/Sirs0ri/statuses/110650371910877488/shares",
"type": "Collection",
"totalItems": 5
}
}