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",
"type": "OrderedCollectionPage",
"orderedItems": [
{
"type": "Create",
"actor": "https://www.minds.com/api/activitypub/users/509073988811501572",
"object": {
"type": "Note",
"id": "https://www.minds.com/api/activitypub/users/509073988811501572/entities/urn:activity:509084308443508736",
"attributedTo": "https://www.minds.com/api/activitypub/users/509073988811501572",
"content": "REUSING EXISTING AND EXPANDING NEW WORKS\r<br />A feature that enable to \"embed/nest\" posts along a manner that also allow to \"expand/collapse\" the \"embedded/nested\" posts akin \"sections/paragraphs\" where each \"embedded/nested\" posts title can be clicked as the element by what to \"expand/collapse\" - could offer content management akin \"master/slave documents\", as well offer a base-solution to many other features. \r<br />\r<br />To bear in mind could be whether to enable/allow also \"embedding/nesting\" posts by others than oneself as well what sort of handling there could be found interesting regarding management across the account/user population. In extent, there ought also entail plenty space for additional features along such as \"credits\" of sorts. \r<br />\r<br />Though all such ideas would in this context want to be explored and assessed around this idea whether or not consider pursuing to enable \"embedding/nesting posts\". As the client-side markup codes basically seem built for this sort of functionality, one recons that it would pretty much boil down to the data-architecture, DB and some other server side stuff including making calls between client and server, and also the perceptive realities represented in the UX.\r<br />\r<br />Any takers, any reasons for why not or anything else seemingly relevant to the idea ?\r<br />\r<br />/endless thanx for minds - it inspires hope, happiness and even new and old ideas coming to life =)<br /><a href=\"https://www.minds.com/\" target=\"_blank\">https://www.minds.com/</a>",
"to": [
"https://www.w3.org/ns/activitystreams#Public"
],
"cc": [
"https://www.minds.com/api/activitypub/users/509073988811501572/followers"
],
"tag": [],
"url": "https://www.minds.com/newsfeed/509084308443508736",
"published": "2015-11-05T19:19:17+00:00",
"source": {
"content": "REUSING EXISTING AND EXPANDING NEW WORKS\r\nA feature that enable to \"embed/nest\" posts along a manner that also allow to \"expand/collapse\" the \"embedded/nested\" posts akin \"sections/paragraphs\" where each \"embedded/nested\" posts title can be clicked as the element by what to \"expand/collapse\" - could offer content management akin \"master/slave documents\", as well offer a base-solution to many other features. \r\n\r\nTo bear in mind could be whether to enable/allow also \"embedding/nesting\" posts by others than oneself as well what sort of handling there could be found interesting regarding management across the account/user population. In extent, there ought also entail plenty space for additional features along such as \"credits\" of sorts. \r\n\r\nThough all such ideas would in this context want to be explored and assessed around this idea whether or not consider pursuing to enable \"embedding/nesting posts\". As the client-side markup codes basically seem built for this sort of functionality, one recons that it would pretty much boil down to the data-architecture, DB and some other server side stuff including making calls between client and server, and also the perceptive realities represented in the UX.\r\n\r\nAny takers, any reasons for why not or anything else seemingly relevant to the idea ?\r\n\r\n/endless thanx for minds - it inspires hope, happiness and even new and old ideas coming to life =)\nhttps://www.minds.com/",
"mediaType": "text/plain"
}
},
"id": "https://www.minds.com/api/activitypub/users/509073988811501572/entities/urn:activity:509084308443508736/activity"
}
],
"id": "https://www.minds.com/api/activitypub/users/509073988811501572/outbox",
"partOf": "https://www.minds.com/api/activitypub/users/509073988811501572/outboxoutbox"
}