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",
"https://akkomane.social/schemas/litepub-0.1.jsonld",
{
"@language": "und"
}
],
"actor": "https://akkomane.social/users/maegul",
"attachment": [],
"attributedTo": "https://akkomane.social/users/maegul",
"cc": [
"https://akkomane.social/users/maegul/followers"
],
"content": "<p><span class=\"h-card\"><a class=\"u-url mention\" data-user=\"Agh8AGbMLWdHsBQAnQ\" href=\"https://mastodon.social/@Gargron\" rel=\"ugc\">@<span>Gargron</span></a></span> <span class=\"h-card\"><a class=\"u-url mention\" data-user=\"Agmcum5Yl7aIBcxame\" href=\"https://mastodon.social/@ricmac\" rel=\"ugc\">@<span>ricmac</span></a></span> <span class=\"h-card\"><a class=\"u-url mention\" data-user=\"AgmyjrF5SIllybcG7k\" href=\"https://mastodon.social/@rabble\" rel=\"ugc\">@<span>rabble</span></a></span> </p><blockquote><p>Pixelfed and Mastodon are not isolated from each other. I have Pixelfed users in my home feed on Mastodon. That’s a very weird definition of isolated.</p></blockquote><p><strong>UI-mismatch</strong> is the issue there and as well as with the “promise” of the fediverse. A shared protocol isn’t the same as a shared UI.</p><p>Then there’s the whole <strong>data-model-mismatch</strong> problem, where platforms only implement parts of the protocol such that things get lost or misinterpreted between platforms.</p><p>And so, despite being technically “not isolated”, people have multiple accounts all over the place to reroute around these mismatch frictions, which are significant enough to create prohibitive separations.</p><hr/><p>Whether its a misinterpretation from users or an overzealous advocacy of the power of the protocol and fediverse … I think it’s absolutely fair enough to say that we’ve arrived at a point where the promise of multiple platforms and instances all in a single unifying space is a bad over promise.</p><p>The friction involved in trying to reach for that is bad enough that most just bounce off of it, either ditching the fediverse, or giving up on this so called promise and staying on their platform of choice, or just creating multiple accounts and tolerating the chaos.</p><p>At the root of it is this lack of mobile identity (as well as, IMO, some other general design decisions). Not least because bridging these gulfs is exactly the sort of thing necessary to make the fediverse realise its killer potential. At the moment to many, probably most, the fediverse is in practice “just” a sea of disparate platforms. Which is a shame TBH, but also shouldn’t be glossed over as a non-issue.</p>",
"contentMap": {
"en": "<p><span class=\"h-card\"><a class=\"u-url mention\" data-user=\"Agh8AGbMLWdHsBQAnQ\" href=\"https://mastodon.social/@Gargron\" rel=\"ugc\">@<span>Gargron</span></a></span> <span class=\"h-card\"><a class=\"u-url mention\" data-user=\"Agmcum5Yl7aIBcxame\" href=\"https://mastodon.social/@ricmac\" rel=\"ugc\">@<span>ricmac</span></a></span> <span class=\"h-card\"><a class=\"u-url mention\" data-user=\"AgmyjrF5SIllybcG7k\" href=\"https://mastodon.social/@rabble\" rel=\"ugc\">@<span>rabble</span></a></span> </p><blockquote><p>Pixelfed and Mastodon are not isolated from each other. I have Pixelfed users in my home feed on Mastodon. That’s a very weird definition of isolated.</p></blockquote><p><strong>UI-mismatch</strong> is the issue there and as well as with the “promise” of the fediverse. A shared protocol isn’t the same as a shared UI.</p><p>Then there’s the whole <strong>data-model-mismatch</strong> problem, where platforms only implement parts of the protocol such that things get lost or misinterpreted between platforms.</p><p>And so, despite being technically “not isolated”, people have multiple accounts all over the place to reroute around these mismatch frictions, which are significant enough to create prohibitive separations.</p><hr/><p>Whether its a misinterpretation from users or an overzealous advocacy of the power of the protocol and fediverse … I think it’s absolutely fair enough to say that we’ve arrived at a point where the promise of multiple platforms and instances all in a single unifying space is a bad over promise.</p><p>The friction involved in trying to reach for that is bad enough that most just bounce off of it, either ditching the fediverse, or giving up on this so called promise and staying on their platform of choice, or just creating multiple accounts and tolerating the chaos.</p><p>At the root of it is this lack of mobile identity (as well as, IMO, some other general design decisions). Not least because bridging these gulfs is exactly the sort of thing necessary to make the fediverse realise its killer potential. At the moment to many, probably most, the fediverse is in practice “just” a sea of disparate platforms. Which is a shame TBH, but also shouldn’t be glossed over as a non-issue.</p>"
},
"context": "tag:mastodon.social,2024-04-12:objectId=684076755:objectType=Conversation",
"conversation": "tag:mastodon.social,2024-04-12:objectId=684076755:objectType=Conversation",
"formerRepresentations": {
"orderedItems": [
{
"actor": "https://akkomane.social/users/maegul",
"attachment": [],
"attributedTo": "https://akkomane.social/users/maegul",
"cc": [
"https://akkomane.social/users/maegul/followers"
],
"content": "<p><span class=\"h-card\"><a class=\"u-url mention\" data-user=\"Agh8AGbMLWdHsBQAnQ\" href=\"https://mastodon.social/@Gargron\" rel=\"ugc\">@<span>Gargron</span></a></span> <span class=\"h-card\"><a class=\"u-url mention\" data-user=\"Agmcum5Yl7aIBcxame\" href=\"https://mastodon.social/@ricmac\" rel=\"ugc\">@<span>ricmac</span></a></span> <span class=\"h-card\"><a class=\"u-url mention\" data-user=\"AgmyjrF5SIllybcG7k\" href=\"https://mastodon.social/@rabble\" rel=\"ugc\">@<span>rabble</span></a></span> </p><blockquote><p>Pixelfed and Mastodon are not isolated from each other. I have Pixelfed users in my home feed on Mastodon. That’s a very weird definition of isolated.</p></blockquote><p><strong>UI-mismatch</strong> is the issue there and as well as with the “promise” of the fediverse. A shared protocol isn’t the same as a shared UI.</p><p>Then there’s the whole <strong>data-model-mismatch</strong> problem, where platforms only implement parts of the protocol such that things get lost or misinterpreted between platforms.</p><p>And so, despite being technically “not isolated”, people have multiple accounts all over the place to reroute around these mismatch frictions, which are significant enough to create prohibitive separations.</p><hr/><p>Whether its a misinterpretation from users or an overzealous advocacy of the power of the protocol and fediverse … I think it’s absolutely fair enough to say that we’ve arrived at a point where the promise of multiple platforms and instances all in a single unifying space is a bad over promise.</p><p>The friction involved in trying to reach for that is bad enough that most just bounce off of it, either ditching the fediverse, or giving up on this so called promise and staying on their platform of choice, or just creating multiple accounts and tolerating the chaos.</p><p>At the route of it is this lack of mobile identity (as well as, IMO, some other general design decisions). Not least because bridging these gulfs is exactly the sort of thing necessary to make the fediverse realise its killer potential. At the moment to many, probably most, the fediverse is in practice “just” a sea of disparate platforms. Which is a shame TBH, but also shouldn’t be glossed over as a non-issue.</p>",
"contentMap": {
"en": "<p><span class=\"h-card\"><a class=\"u-url mention\" data-user=\"Agh8AGbMLWdHsBQAnQ\" href=\"https://mastodon.social/@Gargron\" rel=\"ugc\">@<span>Gargron</span></a></span> <span class=\"h-card\"><a class=\"u-url mention\" data-user=\"Agmcum5Yl7aIBcxame\" href=\"https://mastodon.social/@ricmac\" rel=\"ugc\">@<span>ricmac</span></a></span> <span class=\"h-card\"><a class=\"u-url mention\" data-user=\"AgmyjrF5SIllybcG7k\" href=\"https://mastodon.social/@rabble\" rel=\"ugc\">@<span>rabble</span></a></span> </p><blockquote><p>Pixelfed and Mastodon are not isolated from each other. I have Pixelfed users in my home feed on Mastodon. That’s a very weird definition of isolated.</p></blockquote><p><strong>UI-mismatch</strong> is the issue there and as well as with the “promise” of the fediverse. A shared protocol isn’t the same as a shared UI.</p><p>Then there’s the whole <strong>data-model-mismatch</strong> problem, where platforms only implement parts of the protocol such that things get lost or misinterpreted between platforms.</p><p>And so, despite being technically “not isolated”, people have multiple accounts all over the place to reroute around these mismatch frictions, which are significant enough to create prohibitive separations.</p><hr/><p>Whether its a misinterpretation from users or an overzealous advocacy of the power of the protocol and fediverse … I think it’s absolutely fair enough to say that we’ve arrived at a point where the promise of multiple platforms and instances all in a single unifying space is a bad over promise.</p><p>The friction involved in trying to reach for that is bad enough that most just bounce off of it, either ditching the fediverse, or giving up on this so called promise and staying on their platform of choice, or just creating multiple accounts and tolerating the chaos.</p><p>At the route of it is this lack of mobile identity (as well as, IMO, some other general design decisions). Not least because bridging these gulfs is exactly the sort of thing necessary to make the fediverse realise its killer potential. At the moment to many, probably most, the fediverse is in practice “just” a sea of disparate platforms. Which is a shame TBH, but also shouldn’t be glossed over as a non-issue.</p>"
},
"context": "tag:mastodon.social,2024-04-12:objectId=684076755:objectType=Conversation",
"conversation": "tag:mastodon.social,2024-04-12:objectId=684076755:objectType=Conversation",
"inReplyTo": "https://mastodon.social/users/Gargron/statuses/112267982528757290",
"published": "2024-04-14T06:56:20.814855Z",
"sensitive": false,
"source": {
"content": "@Gargron@mastodon.social @ricmac@mastodon.social @rabble@mastodon.social \n\n> Pixelfed and Mastodon are not isolated from each other. I have Pixelfed users in my home feed on Mastodon. That's a very weird definition of isolated.\n\n**UI-mismatch** is the issue there and as well as with the \"promise\" of the fediverse. A shared protocol isn't the same as a shared UI.\n\nThen there's the whole **data-model-mismatch** problem, where platforms only implement parts of the protocol such that things get lost or misinterpreted between platforms.\n\nAnd so, despite being technically \"not isolated\", people have multiple accounts all over the place to reroute around these mismatch frictions, which are significant enough to create prohibitive separations.\n\n---\n\nWhether its a misinterpretation from users or an overzealous advocacy of the power of the protocol and fediverse ... I think it's absolutely fair enough to say that we've arrived at a point where the promise of multiple platforms and instances all in a single unifying space is a bad over promise.\n\nThe friction involved in trying to reach for that is bad enough that most just bounce off of it, either ditching the fediverse, or giving up on this so called promise and staying on their platform of choice, or just creating multiple accounts and tolerating the chaos.\n\nAt the route of it is this lack of mobile identity (as well as, IMO, some other general design decisions). Not least because bridging these gulfs is exactly the sort of thing necessary to make the fediverse realise its killer potential. At the moment to many, probably most, the fediverse is in practice \"just\" a sea of disparate platforms. Which is a shame TBH, but also shouldn't be glossed over as a non-issue.",
"mediaType": "text/markdown"
},
"summary": "",
"tag": [
{
"href": "https://mastodon.social/users/Gargron",
"name": "@Gargron@mastodon.social",
"type": "Mention"
},
{
"href": "https://mastodon.social/users/rabble",
"name": "@rabble@mastodon.social",
"type": "Mention"
},
{
"href": "https://mastodon.social/users/ricmac",
"name": "@ricmac@mastodon.social",
"type": "Mention"
}
],
"to": [
"https://mastodon.social/users/Gargron",
"https://www.w3.org/ns/activitystreams#Public",
"https://mastodon.social/users/rabble",
"https://mastodon.social/users/ricmac"
],
"type": "Note",
"updated": "2024-04-14T06:57:18.484078Z"
},
{
"actor": "https://akkomane.social/users/maegul",
"attachment": [],
"attributedTo": "https://akkomane.social/users/maegul",
"cc": [
"https://akkomane.social/users/maegul/followers"
],
"content": "<p><span class=\"h-card\"><a class=\"u-url mention\" data-user=\"Agh8AGbMLWdHsBQAnQ\" href=\"https://mastodon.social/@Gargron\" rel=\"ugc\">@<span>Gargron</span></a></span> <span class=\"h-card\"><a class=\"u-url mention\" data-user=\"Agmcum5Yl7aIBcxame\" href=\"https://mastodon.social/@ricmac\" rel=\"ugc\">@<span>ricmac</span></a></span> <span class=\"h-card\"><a class=\"u-url mention\" data-user=\"AgmyjrF5SIllybcG7k\" href=\"https://mastodon.social/@rabble\" rel=\"ugc\">@<span>rabble</span></a></span> </p><blockquote><p>Pixelfed and Mastodon are not isolated from each other. I have Pixelfed users in my home feed on Mastodon. That’s a very weird definition of isolated.</p></blockquote><p><strong>UI-mismatch</strong> is the issue there and with the “promise” of the fediverse. A shared protocol isn’t the same as a shared UI.</p><p>Then there’s the whole <strong>data-model-mismatch</strong> problem, where platforms’ only implement parts of the protocol such that things get lost or misinterpreted between platforms.</p><p>And so, despite being technically “not isolated”, people have multiple accounts all over the place to reroute around these mismatch frictions, which are significant enough to create prohibitive separations.</p><hr/><p>Whether its a misinterpretation from users or an overzealous advocacy of the power of the protocol and fediverse … I think it’s absolutely fair enough to say that we’ve arrived at a point where the promise of multiple platforms and instances all in a single unifying space is a bad over promise.</p><p>The friction involved in trying to reach for that is bad enough that most just bounce off of it, either ditching the fediverse, or giving up on this so called promise and staying on their platform of choice, or just creating multiple accounts and tolerating the chaos.</p><p>At the route of it is this lack of mobile identity (as well as, IMO, some other general design decisions). Not least because bridging these gulfs is exactly the sort of thing necessary to make the fediverse realise its killer potential. At the moment to many, probably most, the fediverse is in practice “just” a sea of disparate platforms. Which is a shame TBH, but also shouldn’t be glossed over as a non-issue.</p>",
"contentMap": {
"en": "<p><span class=\"h-card\"><a class=\"u-url mention\" data-user=\"Agh8AGbMLWdHsBQAnQ\" href=\"https://mastodon.social/@Gargron\" rel=\"ugc\">@<span>Gargron</span></a></span> <span class=\"h-card\"><a class=\"u-url mention\" data-user=\"Agmcum5Yl7aIBcxame\" href=\"https://mastodon.social/@ricmac\" rel=\"ugc\">@<span>ricmac</span></a></span> <span class=\"h-card\"><a class=\"u-url mention\" data-user=\"AgmyjrF5SIllybcG7k\" href=\"https://mastodon.social/@rabble\" rel=\"ugc\">@<span>rabble</span></a></span> </p><blockquote><p>Pixelfed and Mastodon are not isolated from each other. I have Pixelfed users in my home feed on Mastodon. That’s a very weird definition of isolated.</p></blockquote><p><strong>UI-mismatch</strong> is the issue there and with the “promise” of the fediverse. A shared protocol isn’t the same as a shared UI.</p><p>Then there’s the whole <strong>data-model-mismatch</strong> problem, where platforms’ only implement parts of the protocol such that things get lost or misinterpreted between platforms.</p><p>And so, despite being technically “not isolated”, people have multiple accounts all over the place to reroute around these mismatch frictions, which are significant enough to create prohibitive separations.</p><hr/><p>Whether its a misinterpretation from users or an overzealous advocacy of the power of the protocol and fediverse … I think it’s absolutely fair enough to say that we’ve arrived at a point where the promise of multiple platforms and instances all in a single unifying space is a bad over promise.</p><p>The friction involved in trying to reach for that is bad enough that most just bounce off of it, either ditching the fediverse, or giving up on this so called promise and staying on their platform of choice, or just creating multiple accounts and tolerating the chaos.</p><p>At the route of it is this lack of mobile identity (as well as, IMO, some other general design decisions). Not least because bridging these gulfs is exactly the sort of thing necessary to make the fediverse realise its killer potential. At the moment to many, probably most, the fediverse is in practice “just” a sea of disparate platforms. Which is a shame TBH, but also shouldn’t be glossed over as a non-issue.</p>"
},
"context": "tag:mastodon.social,2024-04-12:objectId=684076755:objectType=Conversation",
"conversation": "tag:mastodon.social,2024-04-12:objectId=684076755:objectType=Conversation",
"inReplyTo": "https://mastodon.social/users/Gargron/statuses/112267982528757290",
"published": "2024-04-14T06:56:20.814855Z",
"sensitive": false,
"source": {
"content": "@Gargron@mastodon.social @ricmac@mastodon.social @rabble@mastodon.social \n\n> Pixelfed and Mastodon are not isolated from each other. I have Pixelfed users in my home feed on Mastodon. That's a very weird definition of isolated.\n\n**UI-mismatch** is the issue there and with the \"promise\" of the fediverse. A shared protocol isn't the same as a shared UI.\n\nThen there's the whole **data-model-mismatch** problem, where platforms' only implement parts of the protocol such that things get lost or misinterpreted between platforms.\n\nAnd so, despite being technically \"not isolated\", people have multiple accounts all over the place to reroute around these mismatch frictions, which are significant enough to create prohibitive separations.\n\n---\n\nWhether its a misinterpretation from users or an overzealous advocacy of the power of the protocol and fediverse ... I think it's absolutely fair enough to say that we've arrived at a point where the promise of multiple platforms and instances all in a single unifying space is a bad over promise.\n\nThe friction involved in trying to reach for that is bad enough that most just bounce off of it, either ditching the fediverse, or giving up on this so called promise and staying on their platform of choice, or just creating multiple accounts and tolerating the chaos.\n\nAt the route of it is this lack of mobile identity (as well as, IMO, some other general design decisions). Not least because bridging these gulfs is exactly the sort of thing necessary to make the fediverse realise its killer potential. At the moment to many, probably most, the fediverse is in practice \"just\" a sea of disparate platforms. Which is a shame TBH, but also shouldn't be glossed over as a non-issue.",
"mediaType": "text/markdown"
},
"summary": "",
"tag": [
{
"href": "https://mastodon.social/users/Gargron",
"name": "@Gargron@mastodon.social",
"type": "Mention"
},
{
"href": "https://mastodon.social/users/rabble",
"name": "@rabble@mastodon.social",
"type": "Mention"
},
{
"href": "https://mastodon.social/users/ricmac",
"name": "@ricmac@mastodon.social",
"type": "Mention"
}
],
"to": [
"https://mastodon.social/users/Gargron",
"https://www.w3.org/ns/activitystreams#Public",
"https://mastodon.social/users/rabble",
"https://mastodon.social/users/ricmac"
],
"type": "Note"
}
],
"totalItems": 2,
"type": "OrderedCollection"
},
"id": "https://akkomane.social/objects/5e5931cd-f8bc-4b7a-a3b7-2f3365c78c01",
"inReplyTo": "https://mastodon.social/users/Gargron/statuses/112267982528757290",
"published": "2024-04-14T06:56:20.814855Z",
"repliesCount": 1,
"sensitive": false,
"source": {
"content": "@Gargron@mastodon.social @ricmac@mastodon.social @rabble@mastodon.social \n\n> Pixelfed and Mastodon are not isolated from each other. I have Pixelfed users in my home feed on Mastodon. That's a very weird definition of isolated.\n\n**UI-mismatch** is the issue there and as well as with the \"promise\" of the fediverse. A shared protocol isn't the same as a shared UI.\n\nThen there's the whole **data-model-mismatch** problem, where platforms only implement parts of the protocol such that things get lost or misinterpreted between platforms.\n\nAnd so, despite being technically \"not isolated\", people have multiple accounts all over the place to reroute around these mismatch frictions, which are significant enough to create prohibitive separations.\n\n---\n\nWhether its a misinterpretation from users or an overzealous advocacy of the power of the protocol and fediverse ... I think it's absolutely fair enough to say that we've arrived at a point where the promise of multiple platforms and instances all in a single unifying space is a bad over promise.\n\nThe friction involved in trying to reach for that is bad enough that most just bounce off of it, either ditching the fediverse, or giving up on this so called promise and staying on their platform of choice, or just creating multiple accounts and tolerating the chaos.\n\nAt the root of it is this lack of mobile identity (as well as, IMO, some other general design decisions). Not least because bridging these gulfs is exactly the sort of thing necessary to make the fediverse realise its killer potential. At the moment to many, probably most, the fediverse is in practice \"just\" a sea of disparate platforms. Which is a shame TBH, but also shouldn't be glossed over as a non-issue.",
"mediaType": "text/markdown"
},
"summary": "",
"tag": [
{
"href": "https://mastodon.social/users/Gargron",
"name": "@Gargron@mastodon.social",
"type": "Mention"
},
{
"href": "https://mastodon.social/users/rabble",
"name": "@rabble@mastodon.social",
"type": "Mention"
},
{
"href": "https://mastodon.social/users/ricmac",
"name": "@ricmac@mastodon.social",
"type": "Mention"
}
],
"to": [
"https://mastodon.social/users/Gargron",
"https://www.w3.org/ns/activitystreams#Public",
"https://mastodon.social/users/rabble",
"https://mastodon.social/users/ricmac"
],
"type": "Note",
"updated": "2024-04-14T08:59:17.320545Z"
}