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/muntashir/statuses/111272349702106377",
"type": "Note",
"summary": null,
"inReplyTo": null,
"published": "2023-10-21T09:41:52Z",
"url": "https://infosec.exchange/@muntashir/111272349702106377",
"attributedTo": "https://infosec.exchange/users/muntashir",
"to": [
"https://www.w3.org/ns/activitystreams#Public"
],
"cc": [
"https://infosec.exchange/users/muntashir/followers"
],
"sensitive": false,
"atomUri": "https://infosec.exchange/users/muntashir/statuses/111272349702106377",
"inReplyToAtomUri": null,
"conversation": "tag:infosec.exchange,2023-10-21:objectId=104282038:objectType=Conversation",
"content": "<p><a href=\"https://infosec.exchange/tags/Google\" class=\"mention hashtag\" rel=\"tag\">#<span>Google</span></a> is tightly integrating itself to the <a href=\"https://infosec.exchange/tags/AOSP\" class=\"mention hashtag\" rel=\"tag\">#<span>AOSP</span></a> by decoupling features from the stock <a href=\"https://infosec.exchange/tags/Android\" class=\"mention hashtag\" rel=\"tag\">#<span>Android</span></a> to Google Play Services (<a href=\"https://infosec.exchange/tags/GMS\" class=\"mention hashtag\" rel=\"tag\">#<span>GMS</span></a>). Examples include the removal of essential apps such as phone, contacts and SMS apps in favour of their proprietary alternatives. The rest of the AOSP apps aren't maintained properly either. The UI of these apps look as if they belong to the Lollipop-era. All the new and exciting features likely become a part of their proprietary apps rather than the AOSP apps. In <a href=\"https://infosec.exchange/tags/Pixel\" class=\"mention hashtag\" rel=\"tag\">#<span>Pixel</span></a> phones and phones from some other vendors such as Samsung, they replaced the package name of the android system apps with Google's even though both behave exactly the same way. But if the trend continues, it will not take long before they will be completely different. I don't like this because it feels as if the future of Android as an open source project is at stake.</p>",
"contentMap": {
"en": "<p><a href=\"https://infosec.exchange/tags/Google\" class=\"mention hashtag\" rel=\"tag\">#<span>Google</span></a> is tightly integrating itself to the <a href=\"https://infosec.exchange/tags/AOSP\" class=\"mention hashtag\" rel=\"tag\">#<span>AOSP</span></a> by decoupling features from the stock <a href=\"https://infosec.exchange/tags/Android\" class=\"mention hashtag\" rel=\"tag\">#<span>Android</span></a> to Google Play Services (<a href=\"https://infosec.exchange/tags/GMS\" class=\"mention hashtag\" rel=\"tag\">#<span>GMS</span></a>). Examples include the removal of essential apps such as phone, contacts and SMS apps in favour of their proprietary alternatives. The rest of the AOSP apps aren't maintained properly either. The UI of these apps look as if they belong to the Lollipop-era. All the new and exciting features likely become a part of their proprietary apps rather than the AOSP apps. In <a href=\"https://infosec.exchange/tags/Pixel\" class=\"mention hashtag\" rel=\"tag\">#<span>Pixel</span></a> phones and phones from some other vendors such as Samsung, they replaced the package name of the android system apps with Google's even though both behave exactly the same way. But if the trend continues, it will not take long before they will be completely different. I don't like this because it feels as if the future of Android as an open source project is at stake.</p>"
},
"updated": "2023-10-21T09:55:54Z",
"attachment": [],
"tag": [
{
"type": "Hashtag",
"href": "https://infosec.exchange/tags/google",
"name": "#google"
},
{
"type": "Hashtag",
"href": "https://infosec.exchange/tags/aosp",
"name": "#aosp"
},
{
"type": "Hashtag",
"href": "https://infosec.exchange/tags/android",
"name": "#android"
},
{
"type": "Hashtag",
"href": "https://infosec.exchange/tags/gms",
"name": "#gms"
},
{
"type": "Hashtag",
"href": "https://infosec.exchange/tags/pixel",
"name": "#pixel"
}
],
"replies": {
"id": "https://infosec.exchange/users/muntashir/statuses/111272349702106377/replies",
"type": "Collection",
"first": {
"type": "CollectionPage",
"next": "https://infosec.exchange/users/muntashir/statuses/111272349702106377/replies?min_id=111272367698653044&page=true",
"partOf": "https://infosec.exchange/users/muntashir/statuses/111272349702106377/replies",
"items": [
"https://infosec.exchange/users/muntashir/statuses/111272367698653044"
]
}
},
"likes": {
"id": "https://infosec.exchange/users/muntashir/statuses/111272349702106377/likes",
"type": "Collection",
"totalItems": 59
},
"shares": {
"id": "https://infosec.exchange/users/muntashir/statuses/111272349702106377/shares",
"type": "Collection",
"totalItems": 41
}
}