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/iampytest1/statuses/113353999027815942",
"type": "Note",
"summary": null,
"inReplyTo": null,
"published": "2024-10-23T00:52:40Z",
"url": "https://infosec.exchange/@iampytest1/113353999027815942",
"attributedTo": "https://infosec.exchange/users/iampytest1",
"to": [
"https://www.w3.org/ns/activitystreams#Public"
],
"cc": [
"https://infosec.exchange/users/iampytest1/followers"
],
"sensitive": false,
"atomUri": "https://infosec.exchange/users/iampytest1/statuses/113353999027815942",
"inReplyToAtomUri": null,
"conversation": "tag:infosec.exchange,2024-10-23:objectId=205671261:objectType=Conversation",
"content": "<p>uBlock Origin 1.60.1b16 fixes an issue where connections on IPv6-only networks which used NAT64 would falsely be detected as connections to LAN (Local Area Network) IP addresses. This is the only change in that release.</p><p>Issue report: <a href=\"https://github.com/uBlockOrigin/uBlock-issues/issues/3426\" target=\"_blank\" rel=\"nofollow noopener\" translate=\"no\"><span class=\"invisible\">https://</span><span class=\"ellipsis\">github.com/uBlockOrigin/uBlock</span><span class=\"invisible\">-issues/issues/3426</span></a><br>Commit: <a href=\"https://github.com/gorhill/uBlock/commit/2621c908c31b70a983dacf5482600c116ee35102\" target=\"_blank\" rel=\"nofollow noopener\" translate=\"no\"><span class=\"invisible\">https://</span><span class=\"ellipsis\">github.com/gorhill/uBlock/comm</span><span class=\"invisible\">it/2621c908c31b70a983dacf5482600c116ee35102</span></a></p><p>On NAT64:</p><blockquote><p>the primary purpose of NAT64 is to allow an IPv6-only client to initiate communications to an IPv4-only server</p></blockquote><p><a href=\"https://www.cisco.com/c/en/us/support/docs/ip/network-address-translation-nat/217208-understanding-nat64-and-its-configuratio.html\" target=\"_blank\" rel=\"nofollow noopener\" translate=\"no\"><span class=\"invisible\">https://www.</span><span class=\"ellipsis\">cisco.com/c/en/us/support/docs</span><span class=\"invisible\">/ip/network-address-translation-nat/217208-understanding-nat64-and-its-configuratio.html</span></a></p><p>The issue here was that <code>64:ff9b::/96</code> was treated as LAN addresses. However, this is reserved for NAT64 in RFC6052:</p><blockquote><p>This document reserves a \"Well-Known Prefix\" for use in an algorithmic mapping. The value of this IPv6 prefix is: 64:ff9b::/96</p></blockquote><p>Behind CloudFlare: <code>https://www.rfc-editor.org/rfc/rfc6052</code></p><p><a href=\"https://infosec.exchange/tags/uBlockOrigin\" class=\"mention hashtag\" rel=\"tag\">#<span>uBlockOrigin</span></a> <a href=\"https://infosec.exchange/tags/IPv6\" class=\"mention hashtag\" rel=\"tag\">#<span>IPv6</span></a> <a href=\"https://infosec.exchange/tags/NAT64\" class=\"mention hashtag\" rel=\"tag\">#<span>NAT64</span></a></p>",
"contentMap": {
"en": "<p>uBlock Origin 1.60.1b16 fixes an issue where connections on IPv6-only networks which used NAT64 would falsely be detected as connections to LAN (Local Area Network) IP addresses. This is the only change in that release.</p><p>Issue report: <a href=\"https://github.com/uBlockOrigin/uBlock-issues/issues/3426\" target=\"_blank\" rel=\"nofollow noopener\" translate=\"no\"><span class=\"invisible\">https://</span><span class=\"ellipsis\">github.com/uBlockOrigin/uBlock</span><span class=\"invisible\">-issues/issues/3426</span></a><br>Commit: <a href=\"https://github.com/gorhill/uBlock/commit/2621c908c31b70a983dacf5482600c116ee35102\" target=\"_blank\" rel=\"nofollow noopener\" translate=\"no\"><span class=\"invisible\">https://</span><span class=\"ellipsis\">github.com/gorhill/uBlock/comm</span><span class=\"invisible\">it/2621c908c31b70a983dacf5482600c116ee35102</span></a></p><p>On NAT64:</p><blockquote><p>the primary purpose of NAT64 is to allow an IPv6-only client to initiate communications to an IPv4-only server</p></blockquote><p><a href=\"https://www.cisco.com/c/en/us/support/docs/ip/network-address-translation-nat/217208-understanding-nat64-and-its-configuratio.html\" target=\"_blank\" rel=\"nofollow noopener\" translate=\"no\"><span class=\"invisible\">https://www.</span><span class=\"ellipsis\">cisco.com/c/en/us/support/docs</span><span class=\"invisible\">/ip/network-address-translation-nat/217208-understanding-nat64-and-its-configuratio.html</span></a></p><p>The issue here was that <code>64:ff9b::/96</code> was treated as LAN addresses. However, this is reserved for NAT64 in RFC6052:</p><blockquote><p>This document reserves a \"Well-Known Prefix\" for use in an algorithmic mapping. The value of this IPv6 prefix is: 64:ff9b::/96</p></blockquote><p>Behind CloudFlare: <code>https://www.rfc-editor.org/rfc/rfc6052</code></p><p><a href=\"https://infosec.exchange/tags/uBlockOrigin\" class=\"mention hashtag\" rel=\"tag\">#<span>uBlockOrigin</span></a> <a href=\"https://infosec.exchange/tags/IPv6\" class=\"mention hashtag\" rel=\"tag\">#<span>IPv6</span></a> <a href=\"https://infosec.exchange/tags/NAT64\" class=\"mention hashtag\" rel=\"tag\">#<span>NAT64</span></a></p>"
},
"attachment": [],
"tag": [
{
"type": "Hashtag",
"href": "https://infosec.exchange/tags/ublockorigin",
"name": "#ublockorigin"
},
{
"type": "Hashtag",
"href": "https://infosec.exchange/tags/ipv6",
"name": "#ipv6"
},
{
"type": "Hashtag",
"href": "https://infosec.exchange/tags/nat64",
"name": "#nat64"
}
],
"replies": {
"id": "https://infosec.exchange/users/iampytest1/statuses/113353999027815942/replies",
"type": "Collection",
"first": {
"type": "CollectionPage",
"next": "https://infosec.exchange/users/iampytest1/statuses/113353999027815942/replies?only_other_accounts=true&page=true",
"partOf": "https://infosec.exchange/users/iampytest1/statuses/113353999027815942/replies",
"items": []
}
},
"likes": {
"id": "https://infosec.exchange/users/iampytest1/statuses/113353999027815942/likes",
"type": "Collection",
"totalItems": 7
},
"shares": {
"id": "https://infosec.exchange/users/iampytest1/statuses/113353999027815942/shares",
"type": "Collection",
"totalItems": 2
}
}