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",
"litepub": "http://litepub.social/ns#",
"directMessage": "litepub:directMessage",
"Hashtag": "as:Hashtag"
}
],
"id": "https://infosec.exchange/users/irrwitzer/statuses/114065633220984656",
"type": "Note",
"summary": null,
"inReplyTo": "https://social.tchncs.de/users/purelinux/statuses/114063351803395580",
"published": "2025-02-25T17:10:36Z",
"url": "https://infosec.exchange/@irrwitzer/114065633220984656",
"attributedTo": "https://infosec.exchange/users/irrwitzer",
"to": [
"https://www.w3.org/ns/activitystreams#Public"
],
"cc": [
"https://infosec.exchange/users/irrwitzer/followers",
"https://social.tchncs.de/users/purelinux"
],
"sensitive": false,
"atomUri": "https://infosec.exchange/users/irrwitzer/statuses/114065633220984656",
"inReplyToAtomUri": "https://social.tchncs.de/users/purelinux/statuses/114063351803395580",
"conversation": "tag:social.tchncs.de,2025-02-25:objectId=212971685:objectType=Conversation",
"content": "<p><span class=\"h-card\" translate=\"no\"><a href=\"https://social.tchncs.de/@purelinux\" class=\"u-url mention\">@<span>purelinux</span></a></span> YES, this really is a great addition to the routeros featureset and I too love, that ipv6 is getting some love here.<br />In regards to the fasttrack feature: ss far as I understand, fasttrack is not HW offloading - those are different things. “FastTrack is a special handler that bypasses Linux facilities allowing for faster packet forwarding.” [<a href=\"https://help.mikrotik.com/docs/spaces/ROS/pages/130220087/Connection+tracking#Connectiontracking-FastTrack\" target=\"_blank\" rel=\"nofollow noopener\" translate=\"no\"><span class=\"invisible\">https://</span><span class=\"ellipsis\">help.mikrotik.com/docs/spaces/</span><span class=\"invisible\">ROS/pages/130220087/Connection+tracking#Connectiontracking-FastTrack</span></a>] and see <a href=\"https://help.mikrotik.com/docs/download/attachments/328227/fasttrack.png?version=1&modificationDate=1570628705594&api=v2\" target=\"_blank\" rel=\"nofollow noopener\" translate=\"no\"><span class=\"invisible\">https://</span><span class=\"ellipsis\">help.mikrotik.com/docs/downloa</span><span class=\"invisible\">d/attachments/328227/fasttrack.png?version=1&modificationDate=1570628705594&api=v2</span></a> for a flow diagram telling you, what exactly will be bypassed. That's why you need the ipsec policies before the fasttrack-rule. But it will use a lot less CPU as it won't process every packet, even if it's part of a known and accepted flow. <a href=\"https://infosec.exchange/tags/mikrotik\" class=\"mention hashtag\" rel=\"tag\">#<span>mikrotik</span></a> <a href=\"https://infosec.exchange/tags/ipv6\" class=\"mention hashtag\" rel=\"tag\">#<span>ipv6</span></a></p>",
"contentMap": {
"en": "<p><span class=\"h-card\" translate=\"no\"><a href=\"https://social.tchncs.de/@purelinux\" class=\"u-url mention\">@<span>purelinux</span></a></span> YES, this really is a great addition to the routeros featureset and I too love, that ipv6 is getting some love here.<br />In regards to the fasttrack feature: ss far as I understand, fasttrack is not HW offloading - those are different things. “FastTrack is a special handler that bypasses Linux facilities allowing for faster packet forwarding.” [<a href=\"https://help.mikrotik.com/docs/spaces/ROS/pages/130220087/Connection+tracking#Connectiontracking-FastTrack\" target=\"_blank\" rel=\"nofollow noopener\" translate=\"no\"><span class=\"invisible\">https://</span><span class=\"ellipsis\">help.mikrotik.com/docs/spaces/</span><span class=\"invisible\">ROS/pages/130220087/Connection+tracking#Connectiontracking-FastTrack</span></a>] and see <a href=\"https://help.mikrotik.com/docs/download/attachments/328227/fasttrack.png?version=1&modificationDate=1570628705594&api=v2\" target=\"_blank\" rel=\"nofollow noopener\" translate=\"no\"><span class=\"invisible\">https://</span><span class=\"ellipsis\">help.mikrotik.com/docs/downloa</span><span class=\"invisible\">d/attachments/328227/fasttrack.png?version=1&modificationDate=1570628705594&api=v2</span></a> for a flow diagram telling you, what exactly will be bypassed. That's why you need the ipsec policies before the fasttrack-rule. But it will use a lot less CPU as it won't process every packet, even if it's part of a known and accepted flow. <a href=\"https://infosec.exchange/tags/mikrotik\" class=\"mention hashtag\" rel=\"tag\">#<span>mikrotik</span></a> <a href=\"https://infosec.exchange/tags/ipv6\" class=\"mention hashtag\" rel=\"tag\">#<span>ipv6</span></a></p>"
},
"attachment": [],
"tag": [
{
"type": "Mention",
"href": "https://social.tchncs.de/users/purelinux",
"name": "@purelinux@social.tchncs.de"
},
{
"type": "Hashtag",
"href": "https://infosec.exchange/tags/mikrotik",
"name": "#mikrotik"
},
{
"type": "Hashtag",
"href": "https://infosec.exchange/tags/ipv6",
"name": "#ipv6"
}
],
"replies": {
"id": "https://infosec.exchange/users/irrwitzer/statuses/114065633220984656/replies",
"type": "Collection",
"first": {
"type": "CollectionPage",
"next": "https://infosec.exchange/users/irrwitzer/statuses/114065633220984656/replies?only_other_accounts=true&page=true",
"partOf": "https://infosec.exchange/users/irrwitzer/statuses/114065633220984656/replies",
"items": []
}
},
"likes": {
"id": "https://infosec.exchange/users/irrwitzer/statuses/114065633220984656/likes",
"type": "Collection",
"totalItems": 1
},
"shares": {
"id": "https://infosec.exchange/users/irrwitzer/statuses/114065633220984656/shares",
"type": "Collection",
"totalItems": 0
}
}