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",
"blurhash": "toot:blurhash",
"focalPoint": {
"@container": "@list",
"@id": "toot:focalPoint"
}
}
],
"id": "https://woof.tech/users/crashtestdev/statuses/114776728777008152/replies",
"type": "Collection",
"first": {
"id": "https://woof.tech/users/crashtestdev/statuses/114776728777008152/replies?page=true",
"type": "CollectionPage",
"next": "https://woof.tech/users/crashtestdev/statuses/114776728777008152/replies?only_other_accounts=true&page=true",
"partOf": "https://woof.tech/users/crashtestdev/statuses/114776728777008152/replies",
"items": [
{
"id": "https://woof.tech/users/crashtestdev/statuses/114776784130128061",
"type": "Note",
"summary": null,
"inReplyTo": "https://woof.tech/users/crashtestdev/statuses/114776728777008152",
"published": "2025-07-01T07:25:38Z",
"url": "https://woof.tech/@crashtestdev/114776784130128061",
"attributedTo": "https://woof.tech/users/crashtestdev",
"to": [
"https://www.w3.org/ns/activitystreams#Public"
],
"cc": [
"https://woof.tech/users/crashtestdev/followers"
],
"sensitive": false,
"atomUri": "https://woof.tech/users/crashtestdev/statuses/114776784130128061",
"inReplyToAtomUri": "https://woof.tech/users/crashtestdev/statuses/114776728777008152",
"conversation": "tag:woof.tech,2025-07-01:objectId=18328633:objectType=Conversation",
"content": "<p>But... it was a bit strange, reading through the schematic <a href=\"https://stardot.org.uk/forums/download/file.php?id=83573&sid=77daf7ba2622193fe0fea6e1c22f1eee\" target=\"_blank\" rel=\"nofollow noopener noreferrer\" translate=\"no\"><span class=\"invisible\">https://</span><span class=\"ellipsis\">stardot.org.uk/forums/download</span><span class=\"invisible\">/file.php?id=83573&sid=77daf7ba2622193fe0fea6e1c22f1eee</span></a> and the datasheet for the VIDC chip <a href=\"https://bitsavers.org/pdf/acorn/VIDC_Datasheet_Sep86.pdf\" target=\"_blank\" rel=\"nofollow noopener noreferrer\" translate=\"no\"><span class=\"invisible\">https://</span><span class=\"ellipsis\">bitsavers.org/pdf/acorn/VIDC_D</span><span class=\"invisible\">atasheet_Sep86.pdf</span></a> I couldn't find anything particularly noticeably wrong about the generated signals</p><p>You know what's hard, finding a bug when there are no bugs</p><p>I was lucky enough that someone in a group chat recognised the scrambled text that I was getting, and recalled it from an info video on the Acorn Archimedes A310 from 1987 about common faults, and was able to link me to the correct section of a YouTube video <a href=\"https://www.youtube.com/watch?v=d0C-jce6f0k&t=1158s\" target=\"_blank\" rel=\"nofollow noopener noreferrer\" translate=\"no\"><span class=\"invisible\">https://www.</span><span class=\"ellipsis\">youtube.com/watch?v=d0C-jce6f0</span><span class=\"invisible\">k&t=1158s</span></a></p><p>The jist of it is that we need to perform a reset to force the video generation into the correct mode, which is done by pressing R on the keyboard and turning on the power</p><p>The issue there of course is that it's not seeing the keyboard, both as reported from the RISC OS prompt and also the status lights and master reset button were all non-functional; looking at the schematic, I heavily suspected that it is IC20, a hex inverting schmitt trigger chip, this was because IOC (the IO processor chip) did seem to be working for the floppy drive, and ALL of the keyboard functions were being buffered by this chip, including the master reset which doesn't go via IOC, there was also a chance that since +12v is going to the keyboard that the blown tantalum could have done some damage to the keyboard itself, so to be sure about the condition of the keyboard, I removed the top cover...</p>",
"contentMap": {
"en": "<p>But... it was a bit strange, reading through the schematic <a href=\"https://stardot.org.uk/forums/download/file.php?id=83573&sid=77daf7ba2622193fe0fea6e1c22f1eee\" target=\"_blank\" rel=\"nofollow noopener noreferrer\" translate=\"no\"><span class=\"invisible\">https://</span><span class=\"ellipsis\">stardot.org.uk/forums/download</span><span class=\"invisible\">/file.php?id=83573&sid=77daf7ba2622193fe0fea6e1c22f1eee</span></a> and the datasheet for the VIDC chip <a href=\"https://bitsavers.org/pdf/acorn/VIDC_Datasheet_Sep86.pdf\" target=\"_blank\" rel=\"nofollow noopener noreferrer\" translate=\"no\"><span class=\"invisible\">https://</span><span class=\"ellipsis\">bitsavers.org/pdf/acorn/VIDC_D</span><span class=\"invisible\">atasheet_Sep86.pdf</span></a> I couldn't find anything particularly noticeably wrong about the generated signals</p><p>You know what's hard, finding a bug when there are no bugs</p><p>I was lucky enough that someone in a group chat recognised the scrambled text that I was getting, and recalled it from an info video on the Acorn Archimedes A310 from 1987 about common faults, and was able to link me to the correct section of a YouTube video <a href=\"https://www.youtube.com/watch?v=d0C-jce6f0k&t=1158s\" target=\"_blank\" rel=\"nofollow noopener noreferrer\" translate=\"no\"><span class=\"invisible\">https://www.</span><span class=\"ellipsis\">youtube.com/watch?v=d0C-jce6f0</span><span class=\"invisible\">k&t=1158s</span></a></p><p>The jist of it is that we need to perform a reset to force the video generation into the correct mode, which is done by pressing R on the keyboard and turning on the power</p><p>The issue there of course is that it's not seeing the keyboard, both as reported from the RISC OS prompt and also the status lights and master reset button were all non-functional; looking at the schematic, I heavily suspected that it is IC20, a hex inverting schmitt trigger chip, this was because IOC (the IO processor chip) did seem to be working for the floppy drive, and ALL of the keyboard functions were being buffered by this chip, including the master reset which doesn't go via IOC, there was also a chance that since +12v is going to the keyboard that the blown tantalum could have done some damage to the keyboard itself, so to be sure about the condition of the keyboard, I removed the top cover...</p>"
},
"attachment": [
{
"type": "Document",
"mediaType": "image/png",
"url": "https://cdn.woof.tech/media_attachments/files/114/776/768/571/644/624/original/6aa18ba9b0ece27b.png",
"name": "A screenshot of the Acorn Archimedes A310 schematic showing all the inputs and outputs from the keyboard buffered by inverting schmitt triggers from IC20. ",
"blurhash": "U5Rysgay%M00RjD%M{D%-;t7xuIUD%xuj[t7",
"focalPoint": [
0,
0
],
"width": 469,
"height": 495
}
],
"tag": [],
"replies": {
"id": "https://woof.tech/users/crashtestdev/statuses/114776784130128061/replies",
"type": "Collection",
"first": {
"type": "CollectionPage",
"next": "https://woof.tech/users/crashtestdev/statuses/114776784130128061/replies?min_id=114776792576021355&page=true",
"partOf": "https://woof.tech/users/crashtestdev/statuses/114776784130128061/replies",
"items": [
"https://woof.tech/users/crashtestdev/statuses/114776792576021355"
]
}
},
"likes": {
"id": "https://woof.tech/users/crashtestdev/statuses/114776784130128061/likes",
"type": "Collection",
"totalItems": 3
},
"shares": {
"id": "https://woof.tech/users/crashtestdev/statuses/114776784130128061/shares",
"type": "Collection",
"totalItems": 0
}
}
]
}
}