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/realn2s/statuses/111603611961864032",
"type": "Note",
"summary": null,
"inReplyTo": "https://infosec.exchange/users/realn2s/statuses/111603524880422572",
"published": "2023-12-18T21:46:13Z",
"url": "https://infosec.exchange/@realn2s/111603611961864032",
"attributedTo": "https://infosec.exchange/users/realn2s",
"to": [
"https://www.w3.org/ns/activitystreams#Public"
],
"cc": [
"https://infosec.exchange/users/realn2s/followers"
],
"sensitive": false,
"atomUri": "https://infosec.exchange/users/realn2s/statuses/111603611961864032",
"inReplyToAtomUri": "https://infosec.exchange/users/realn2s/statuses/111603524880422572",
"conversation": "tag:infosec.exchange,2023-12-18:objectId=118774018:objectType=Conversation",
"content": "<p>And the Custom banned password list of <a href=\"https://infosec.exchange/tags/Microsoft\" class=\"mention hashtag\" rel=\"tag\">#<span>Microsoft</span></a> <a href=\"https://infosec.exchange/tags/EntraID\" class=\"mention hashtag\" rel=\"tag\">#<span>EntraID</span></a> <a href=\"https://infosec.exchange/tags/Password\" class=\"mention hashtag\" rel=\"tag\">#<span>Password</span></a> Protection just continues the joke.</p><p>First, it can only contain 1000 entries. And yes, I really don't want to manage a big custom list.</p><p>And it gets even worse. The list is intended to contain company specific banned words like brand or product names, company-specific internal terms as well as abbreviations. Entries must be at least 4 characters. </p><p>WTF, half the companies I worked for had 3 letter names. And there are many other BWM, KIA, SAP, IBM, GM, BBC, NBA, NFL, UPS, DHL, ...</p><p>And don't get me started on acronyms. <a href=\"https://infosec.exchange/tags/TLA\" class=\"mention hashtag\" rel=\"tag\">#<span>TLA</span></a> (Three-Letter-Acronym) is a term for a reason.</p><p>This means, taking my current company as an example, that SMA12 would be an accepted password (if it would be for the length) because 'SMA' 3 points + '12' 2 points is 5 points).</p><p>To reach the necessary length you could simply combine it. E.g. 'SMASolar1' would be an accepted password even if 'Solar' was a banned word.</p><p>And I CAN'T do ANYTHING!!!</p><p>Or at least not anything sensible. If I start to put combinations of 'SMA*' in the custom banned pw list, I'm back at an inadequate big list I have to manage myself 🤮.</p><p>And even then SMASolar1234 stays valid 🤬<br /><a href=\"https://infosec.exchange/tags/Cybersecurity\" class=\"mention hashtag\" rel=\"tag\">#<span>Cybersecurity</span></a> <a href=\"https://infosec.exchange/tags/Fail\" class=\"mention hashtag\" rel=\"tag\">#<span>Fail</span></a> <a href=\"https://infosec.exchange/tags/SecurityFail\" class=\"mention hashtag\" rel=\"tag\">#<span>SecurityFail</span></a> </p><p>Call for <a href=\"https://infosec.exchange/tags/Help\" class=\"mention hashtag\" rel=\"tag\">#<span>Help</span></a>: I would be very happy if someone can show me that I'm wrong. The state of Microsoft Entra ID Password Protection is a MUCH bigger pain than that I would have been wrong 😜.</p>",
"contentMap": {
"en": "<p>And the Custom banned password list of <a href=\"https://infosec.exchange/tags/Microsoft\" class=\"mention hashtag\" rel=\"tag\">#<span>Microsoft</span></a> <a href=\"https://infosec.exchange/tags/EntraID\" class=\"mention hashtag\" rel=\"tag\">#<span>EntraID</span></a> <a href=\"https://infosec.exchange/tags/Password\" class=\"mention hashtag\" rel=\"tag\">#<span>Password</span></a> Protection just continues the joke.</p><p>First, it can only contain 1000 entries. And yes, I really don't want to manage a big custom list.</p><p>And it gets even worse. The list is intended to contain company specific banned words like brand or product names, company-specific internal terms as well as abbreviations. Entries must be at least 4 characters. </p><p>WTF, half the companies I worked for had 3 letter names. And there are many other BWM, KIA, SAP, IBM, GM, BBC, NBA, NFL, UPS, DHL, ...</p><p>And don't get me started on acronyms. <a href=\"https://infosec.exchange/tags/TLA\" class=\"mention hashtag\" rel=\"tag\">#<span>TLA</span></a> (Three-Letter-Acronym) is a term for a reason.</p><p>This means, taking my current company as an example, that SMA12 would be an accepted password (if it would be for the length) because 'SMA' 3 points + '12' 2 points is 5 points).</p><p>To reach the necessary length you could simply combine it. E.g. 'SMASolar1' would be an accepted password even if 'Solar' was a banned word.</p><p>And I CAN'T do ANYTHING!!!</p><p>Or at least not anything sensible. If I start to put combinations of 'SMA*' in the custom banned pw list, I'm back at an inadequate big list I have to manage myself 🤮.</p><p>And even then SMASolar1234 stays valid 🤬<br /><a href=\"https://infosec.exchange/tags/Cybersecurity\" class=\"mention hashtag\" rel=\"tag\">#<span>Cybersecurity</span></a> <a href=\"https://infosec.exchange/tags/Fail\" class=\"mention hashtag\" rel=\"tag\">#<span>Fail</span></a> <a href=\"https://infosec.exchange/tags/SecurityFail\" class=\"mention hashtag\" rel=\"tag\">#<span>SecurityFail</span></a> </p><p>Call for <a href=\"https://infosec.exchange/tags/Help\" class=\"mention hashtag\" rel=\"tag\">#<span>Help</span></a>: I would be very happy if someone can show me that I'm wrong. The state of Microsoft Entra ID Password Protection is a MUCH bigger pain than that I would have been wrong 😜.</p>"
},
"updated": "2024-05-08T08:02:48Z",
"attachment": [],
"tag": [
{
"type": "Hashtag",
"href": "https://infosec.exchange/tags/entraid",
"name": "#entraid"
},
{
"type": "Hashtag",
"href": "https://infosec.exchange/tags/microsoft",
"name": "#microsoft"
},
{
"type": "Hashtag",
"href": "https://infosec.exchange/tags/password",
"name": "#password"
},
{
"type": "Hashtag",
"href": "https://infosec.exchange/tags/tla",
"name": "#tla"
},
{
"type": "Hashtag",
"href": "https://infosec.exchange/tags/cybersecurity",
"name": "#cybersecurity"
},
{
"type": "Hashtag",
"href": "https://infosec.exchange/tags/fail",
"name": "#fail"
},
{
"type": "Hashtag",
"href": "https://infosec.exchange/tags/securityfail",
"name": "#securityfail"
},
{
"type": "Hashtag",
"href": "https://infosec.exchange/tags/help",
"name": "#help"
}
],
"replies": {
"id": "https://infosec.exchange/users/realn2s/statuses/111603611961864032/replies",
"type": "Collection",
"first": {
"type": "CollectionPage",
"next": "https://infosec.exchange/users/realn2s/statuses/111603611961864032/replies?min_id=111605920209725128&page=true",
"partOf": "https://infosec.exchange/users/realn2s/statuses/111603611961864032/replies",
"items": [
"https://infosec.exchange/users/realn2s/statuses/111605920209725128"
]
}
},
"likes": {
"id": "https://infosec.exchange/users/realn2s/statuses/111603611961864032/likes",
"type": "Collection",
"totalItems": 1
},
"shares": {
"id": "https://infosec.exchange/users/realn2s/statuses/111603611961864032/shares",
"type": "Collection",
"totalItems": 2
}
}