ActivityPub Viewer

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.

Open in browser →
{ "@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", "Hashtag": "as:Hashtag" } ], "id": "https://post.lurk.org/users/rra/statuses/106402786721783292", "type": "Note", "summary": null, "inReplyTo": null, "published": "2021-06-13T09:47:58Z", "url": "https://post.lurk.org/@rra/106402786721783292", "attributedTo": "https://post.lurk.org/users/rra", "to": [ "https://www.w3.org/ns/activitystreams#Public" ], "cc": [ "https://post.lurk.org/users/rra/followers" ], "sensitive": false, "atomUri": "https://post.lurk.org/users/rra/statuses/106402786721783292", "inReplyToAtomUri": null, "conversation": "tag:post.lurk.org,2021-06-13:objectId=7908605:objectType=Conversation", "localOnly": false, "content": "<p>On monday I&#39;m presenting a paper on solar.lowtechmagazine.com during the &#39;Computing within <a href=\"https://post.lurk.org/tags/Limits\" class=\"mention hashtag\" rel=\"tag\">#<span>Limits</span></a>&#39; conference.</p><p>In the paper I&#39;m describing the design choices we made, such as designing for unavailability and how they were based on reducing a few key metrics such as data transferred, calculations per request and use of third party services. This opens up a way of thinking about <a href=\"https://post.lurk.org/tags/degrowth\" class=\"mention hashtag\" rel=\"tag\">#<span>degrowth</span></a> and ICT. We should be looking in to that waaaay more. </p><p>The paper also tries to implicitly answer the &#39;how do we do sustainable web design?&#39; question and argues aiming for reduction (of bytes transferred, computation and infra required) as useful rule of thumbs guiding a design. That is to say, solar protocols, &#39;low tech look&#39;, 3.5MB dithered images, green CDNs etc ain&#39;t it.</p><p>However, it also self-criticizes solar.lowtechmagazine.com for the fact that it is so unreproducible and a very limited and &#39;easy&#39; use case. So yeah no answer but thinking through degrowth should definitely be considered as the direction of the answer.. </p><p><a href=\"https://computingwithinlimits.org/2021/papers/limits21-abbing.pdf\" target=\"_blank\" rel=\"nofollow noopener noreferrer\" translate=\"no\"><span class=\"invisible\">https://</span><span class=\"ellipsis\">computingwithinlimits.org/2021</span><span class=\"invisible\">/papers/limits21-abbing.pdf</span></a></p>", "contentMap": { "en": "<p>On monday I&#39;m presenting a paper on solar.lowtechmagazine.com during the &#39;Computing within <a href=\"https://post.lurk.org/tags/Limits\" class=\"mention hashtag\" rel=\"tag\">#<span>Limits</span></a>&#39; conference.</p><p>In the paper I&#39;m describing the design choices we made, such as designing for unavailability and how they were based on reducing a few key metrics such as data transferred, calculations per request and use of third party services. This opens up a way of thinking about <a href=\"https://post.lurk.org/tags/degrowth\" class=\"mention hashtag\" rel=\"tag\">#<span>degrowth</span></a> and ICT. We should be looking in to that waaaay more. </p><p>The paper also tries to implicitly answer the &#39;how do we do sustainable web design?&#39; question and argues aiming for reduction (of bytes transferred, computation and infra required) as useful rule of thumbs guiding a design. That is to say, solar protocols, &#39;low tech look&#39;, 3.5MB dithered images, green CDNs etc ain&#39;t it.</p><p>However, it also self-criticizes solar.lowtechmagazine.com for the fact that it is so unreproducible and a very limited and &#39;easy&#39; use case. So yeah no answer but thinking through degrowth should definitely be considered as the direction of the answer.. </p><p><a href=\"https://computingwithinlimits.org/2021/papers/limits21-abbing.pdf\" target=\"_blank\" rel=\"nofollow noopener noreferrer\" translate=\"no\"><span class=\"invisible\">https://</span><span class=\"ellipsis\">computingwithinlimits.org/2021</span><span class=\"invisible\">/papers/limits21-abbing.pdf</span></a></p>" }, "attachment": [], "tag": [ { "type": "Hashtag", "href": "https://post.lurk.org/tags/limits", "name": "#limits" }, { "type": "Hashtag", "href": "https://post.lurk.org/tags/degrowth", "name": "#degrowth" } ], "replies": { "id": "https://post.lurk.org/users/rra/statuses/106402786721783292/replies", "type": "Collection", "first": { "type": "CollectionPage", "next": "https://post.lurk.org/users/rra/statuses/106402786721783292/replies?only_other_accounts=true&page=true", "partOf": "https://post.lurk.org/users/rra/statuses/106402786721783292/replies", "items": [] } } }