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://mastodon.social/users/rgdd/statuses/113305466713404918",
"type": "Note",
"summary": null,
"inReplyTo": "https://mastodon.social/users/rgdd/statuses/113305462898606190",
"published": "2024-10-14T11:10:16Z",
"url": "https://mastodon.social/@rgdd/113305466713404918",
"attributedTo": "https://mastodon.social/users/rgdd",
"to": [
"https://www.w3.org/ns/activitystreams#Public"
],
"cc": [
"https://mastodon.social/users/rgdd/followers",
"https://follow.agwa.name/users/agwa",
"https://abyssdomain.expert/users/filippo"
],
"sensitive": false,
"atomUri": "https://mastodon.social/users/rgdd/statuses/113305466713404918",
"inReplyToAtomUri": "https://mastodon.social/users/rgdd/statuses/113305462898606190",
"conversation": "tag:abyssdomain.expert,2024-10-13:objectId=1957607:objectType=Conversation",
"content": "<p><span class=\"h-card\" translate=\"no\"><a href=\"https://follow.agwa.name/users/agwa\" class=\"u-url mention\">@<span>agwa</span></a></span> <span class=\"h-card\" translate=\"no\"><a href=\"https://abyssdomain.expert/@filippo\" class=\"u-url mention\">@<span>filippo</span></a></span> My crude sketch is that I just want to run the monitor as if it was a daemon; but force it into a schedule that fits e.g. a CI pipeline. So more or less something like: start running every T time units, stop and restart (or similar) if it doesn't finish on time, and of course stop if the monitor managed to catch up with all logs. While the monitor is still catching up with a slow log, just continue running for the other logs.</p>",
"contentMap": {
"en": "<p><span class=\"h-card\" translate=\"no\"><a href=\"https://follow.agwa.name/users/agwa\" class=\"u-url mention\">@<span>agwa</span></a></span> <span class=\"h-card\" translate=\"no\"><a href=\"https://abyssdomain.expert/@filippo\" class=\"u-url mention\">@<span>filippo</span></a></span> My crude sketch is that I just want to run the monitor as if it was a daemon; but force it into a schedule that fits e.g. a CI pipeline. So more or less something like: start running every T time units, stop and restart (or similar) if it doesn't finish on time, and of course stop if the monitor managed to catch up with all logs. While the monitor is still catching up with a slow log, just continue running for the other logs.</p>"
},
"attachment": [],
"tag": [
{
"type": "Mention",
"href": "https://follow.agwa.name/users/agwa",
"name": "@agwa@agwa.name"
},
{
"type": "Mention",
"href": "https://abyssdomain.expert/users/filippo",
"name": "@filippo@abyssdomain.expert"
}
],
"replies": {
"id": "https://mastodon.social/users/rgdd/statuses/113305466713404918/replies",
"type": "Collection",
"first": {
"type": "CollectionPage",
"next": "https://mastodon.social/users/rgdd/statuses/113305466713404918/replies?min_id=113305468430771357&page=true",
"partOf": "https://mastodon.social/users/rgdd/statuses/113305466713404918/replies",
"items": [
"https://mastodon.social/users/rgdd/statuses/113305468430771357"
]
}
},
"likes": {
"id": "https://mastodon.social/users/rgdd/statuses/113305466713404918/likes",
"type": "Collection",
"totalItems": 0
},
"shares": {
"id": "https://mastodon.social/users/rgdd/statuses/113305466713404918/shares",
"type": "Collection",
"totalItems": 0
}
}