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/ChallengeApathy/statuses/112007245318182457",
"type": "Note",
"summary": null,
"inReplyTo": null,
"published": "2024-02-28T04:35:29Z",
"url": "https://infosec.exchange/@ChallengeApathy/112007245318182457",
"attributedTo": "https://infosec.exchange/users/ChallengeApathy",
"to": [
"https://www.w3.org/ns/activitystreams#Public"
],
"cc": [
"https://infosec.exchange/users/ChallengeApathy/followers"
],
"sensitive": false,
"atomUri": "https://infosec.exchange/users/ChallengeApathy/statuses/112007245318182457",
"inReplyToAtomUri": null,
"conversation": "tag:infosec.exchange,2024-02-28:objectId=137563163:objectType=Conversation",
"content": "<p>It really blows me away how hard <a href=\"https://infosec.exchange/tags/Microsoft\" class=\"mention hashtag\" rel=\"tag\">#<span>Microsoft</span></a> is pushing people to use Microsoft accounts in <a href=\"https://infosec.exchange/tags/Windows\" class=\"mention hashtag\" rel=\"tag\">#<span>Windows</span></a>. </p><p>Before, one might be able to think that a Microsoft account was a convenience feature, but with as hard as they push it, there's obviously a reason.</p><p>The number 1 reason is that they want to be able to better tie your telemetry data with a central ID. This makes it easier for them to build data profiles to sell to data brokers.</p><p>However, I suspect it's more than that.</p><p>Have you ever wondered why almost all <a href=\"https://infosec.exchange/tags/AI\" class=\"mention hashtag\" rel=\"tag\">#<span>AI</span></a> requires you to have an account? </p><p>It's not security, it's not legality, it's control. No, again: they want to build a data profile based upon your queries. In time, mixing existing AI LLMs with a central data profile might be enough to start developing precrime-styled predictions.</p><p>Sure, if you don't ever plan to commit a crime, that might not scare you but precrime predictions would, at best, place you into a bubble with others like you and they'll leverage other AI to scour the web (and the internet as a whole) for anything to add to your data profile.</p><p>This is a terrifying future for human rights, but again, even if you don't feel scared by this, imagine this scenario:</p><p>In the future, your prices everywhere will be custom-tailored based upon your data and these AI predictions. Now, imagine that CBDCs end up being rolled out by this point and everyone is required to use them.</p><p>If the banks and governments determine you've driven your car too much, if they've determined you're eating too much meat, if you've been anywhere NEAR a major protest (even the peaceful, legal kind), all of these will impact your data profile and the AI predictions that are tied to your data profile. </p><p>All of this is building a foundation for a social credit score like China has. Sure, you might think I'm being dramatic by connecting Microsoft's push for people to use a Microsoft account on Windows, but don't underestimate the value of these small steps. Windows is the most popular operating system for home users and businesses. Even if you block telemetry via a firewall, there's still a chance that your data is making it back to Microsoft somehow. If your telemetry data is tied to your Microsoft account, and your Microsoft account is tied to a single email, and if that email is used in multiple places, this alone would be enough for them to gather the data needed to make bank off of your average usage of your computer. This goes for other big tech conglomerates like <a href=\"https://infosec.exchange/tags/Google\" class=\"mention hashtag\" rel=\"tag\">#<span>Google</span></a>, as well.</p><p>Data harvesting is an outward web. While it's true that not every connection is going to be followed (bad data is useless data), why take a chance?</p><p>Do what you can to protect your <a href=\"https://infosec.exchange/tags/privacy\" class=\"mention hashtag\" rel=\"tag\">#<span>privacy</span></a> today or you may no longer have privacy tomorrow.</p>",
"contentMap": {
"en": "<p>It really blows me away how hard <a href=\"https://infosec.exchange/tags/Microsoft\" class=\"mention hashtag\" rel=\"tag\">#<span>Microsoft</span></a> is pushing people to use Microsoft accounts in <a href=\"https://infosec.exchange/tags/Windows\" class=\"mention hashtag\" rel=\"tag\">#<span>Windows</span></a>. </p><p>Before, one might be able to think that a Microsoft account was a convenience feature, but with as hard as they push it, there's obviously a reason.</p><p>The number 1 reason is that they want to be able to better tie your telemetry data with a central ID. This makes it easier for them to build data profiles to sell to data brokers.</p><p>However, I suspect it's more than that.</p><p>Have you ever wondered why almost all <a href=\"https://infosec.exchange/tags/AI\" class=\"mention hashtag\" rel=\"tag\">#<span>AI</span></a> requires you to have an account? </p><p>It's not security, it's not legality, it's control. No, again: they want to build a data profile based upon your queries. In time, mixing existing AI LLMs with a central data profile might be enough to start developing precrime-styled predictions.</p><p>Sure, if you don't ever plan to commit a crime, that might not scare you but precrime predictions would, at best, place you into a bubble with others like you and they'll leverage other AI to scour the web (and the internet as a whole) for anything to add to your data profile.</p><p>This is a terrifying future for human rights, but again, even if you don't feel scared by this, imagine this scenario:</p><p>In the future, your prices everywhere will be custom-tailored based upon your data and these AI predictions. Now, imagine that CBDCs end up being rolled out by this point and everyone is required to use them.</p><p>If the banks and governments determine you've driven your car too much, if they've determined you're eating too much meat, if you've been anywhere NEAR a major protest (even the peaceful, legal kind), all of these will impact your data profile and the AI predictions that are tied to your data profile. </p><p>All of this is building a foundation for a social credit score like China has. Sure, you might think I'm being dramatic by connecting Microsoft's push for people to use a Microsoft account on Windows, but don't underestimate the value of these small steps. Windows is the most popular operating system for home users and businesses. Even if you block telemetry via a firewall, there's still a chance that your data is making it back to Microsoft somehow. If your telemetry data is tied to your Microsoft account, and your Microsoft account is tied to a single email, and if that email is used in multiple places, this alone would be enough for them to gather the data needed to make bank off of your average usage of your computer. This goes for other big tech conglomerates like <a href=\"https://infosec.exchange/tags/Google\" class=\"mention hashtag\" rel=\"tag\">#<span>Google</span></a>, as well.</p><p>Data harvesting is an outward web. While it's true that not every connection is going to be followed (bad data is useless data), why take a chance?</p><p>Do what you can to protect your <a href=\"https://infosec.exchange/tags/privacy\" class=\"mention hashtag\" rel=\"tag\">#<span>privacy</span></a> today or you may no longer have privacy tomorrow.</p>"
},
"attachment": [],
"tag": [
{
"type": "Hashtag",
"href": "https://infosec.exchange/tags/microsoft",
"name": "#microsoft"
},
{
"type": "Hashtag",
"href": "https://infosec.exchange/tags/windows",
"name": "#windows"
},
{
"type": "Hashtag",
"href": "https://infosec.exchange/tags/ai",
"name": "#ai"
},
{
"type": "Hashtag",
"href": "https://infosec.exchange/tags/google",
"name": "#google"
},
{
"type": "Hashtag",
"href": "https://infosec.exchange/tags/privacy",
"name": "#privacy"
}
],
"replies": {
"id": "https://infosec.exchange/users/ChallengeApathy/statuses/112007245318182457/replies",
"type": "Collection",
"first": {
"type": "CollectionPage",
"next": "https://infosec.exchange/users/ChallengeApathy/statuses/112007245318182457/replies?only_other_accounts=true&page=true",
"partOf": "https://infosec.exchange/users/ChallengeApathy/statuses/112007245318182457/replies",
"items": []
}
},
"likes": {
"id": "https://infosec.exchange/users/ChallengeApathy/statuses/112007245318182457/likes",
"type": "Collection",
"totalItems": 7
},
"shares": {
"id": "https://infosec.exchange/users/ChallengeApathy/statuses/112007245318182457/shares",
"type": "Collection",
"totalItems": 2
}
}