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/111622856327656104/replies",
"type": "Collection",
"first": {
"id": "https://infosec.exchange/users/realn2s/statuses/111622856327656104/replies?page=true",
"type": "CollectionPage",
"next": "https://infosec.exchange/users/realn2s/statuses/111622856327656104/replies?only_other_accounts=true&page=true",
"partOf": "https://infosec.exchange/users/realn2s/statuses/111622856327656104/replies",
"items": [
{
"id": "https://infosec.exchange/users/realn2s/statuses/111724811831789469",
"type": "Note",
"summary": null,
"inReplyTo": "https://infosec.exchange/users/realn2s/statuses/111622856327656104",
"published": "2024-01-09T07:28:56Z",
"url": "https://infosec.exchange/@realn2s/111724811831789469",
"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/111724811831789469",
"inReplyToAtomUri": "https://infosec.exchange/users/realn2s/statuses/111622856327656104",
"conversation": "tag:infosec.exchange,2023-12-18:objectId=118774018:objectType=Conversation",
"content": "<p>To close this thread, lets collect some good (at the time of writing and IMHO) password guidelines.</p><p>And, if you are a developer, please take care that your system supports, encourages, or even enforces them.</p><p>Dos & Don'ts</p><p>Users:<br />* Do choose long passwords. 12+ characters<br />* Don't use dictionary words, or terms related to you, your family, or work. <br />* Don't trick the password rules by just adding a year<br />* Do use <a href=\"https://infosec.exchange/tags/MFA\" class=\"mention hashtag\" rel=\"tag\">#<span>MFA</span></a>/#2FA wherever possible.<br />* Don't reuse the same password<br />* Do use a password manager/password safe. <br />* Do generate your passwords (with the help of a password safe)</p><p>Admins (all the user recommendations and):<br />* Don't enforce regular password changes<br />* Do check passwords against dictionary word including context specific term (like brand names) as well as known password. And disallow them. I would love this check not only when the password is changed, but also regularly on login.<br />* Do enable <a href=\"https://infosec.exchange/tags/2FA\" class=\"mention hashtag\" rel=\"tag\">#<span>2FA</span></a>/#MFA<br />* Do keep mobile in mind, entering very long password, with a lot of mixed case, numbers and special characters can be a major pain</p><p>Developers:<br />* Don't limit the characters which can be used. Every character which is printable should be valid. Allow blanks or punctation. Allow Unicode (don't just allow letter or numbers or ...)<br />* Do allow Copy & Paste such than a password manager can be used.<br />* Don't limit the length of the password (for technical reasons you probably must, NIST recommends at least 64 characters)<br />* Do provide <a href=\"https://infosec.exchange/tags/2FA\" class=\"mention hashtag\" rel=\"tag\">#<span>2FA</span></a>/#MFA</p>",
"contentMap": {
"en": "<p>To close this thread, lets collect some good (at the time of writing and IMHO) password guidelines.</p><p>And, if you are a developer, please take care that your system supports, encourages, or even enforces them.</p><p>Dos & Don'ts</p><p>Users:<br />* Do choose long passwords. 12+ characters<br />* Don't use dictionary words, or terms related to you, your family, or work. <br />* Don't trick the password rules by just adding a year<br />* Do use <a href=\"https://infosec.exchange/tags/MFA\" class=\"mention hashtag\" rel=\"tag\">#<span>MFA</span></a>/#2FA wherever possible.<br />* Don't reuse the same password<br />* Do use a password manager/password safe. <br />* Do generate your passwords (with the help of a password safe)</p><p>Admins (all the user recommendations and):<br />* Don't enforce regular password changes<br />* Do check passwords against dictionary word including context specific term (like brand names) as well as known password. And disallow them. I would love this check not only when the password is changed, but also regularly on login.<br />* Do enable <a href=\"https://infosec.exchange/tags/2FA\" class=\"mention hashtag\" rel=\"tag\">#<span>2FA</span></a>/#MFA<br />* Do keep mobile in mind, entering very long password, with a lot of mixed case, numbers and special characters can be a major pain</p><p>Developers:<br />* Don't limit the characters which can be used. Every character which is printable should be valid. Allow blanks or punctation. Allow Unicode (don't just allow letter or numbers or ...)<br />* Do allow Copy & Paste such than a password manager can be used.<br />* Don't limit the length of the password (for technical reasons you probably must, NIST recommends at least 64 characters)<br />* Do provide <a href=\"https://infosec.exchange/tags/2FA\" class=\"mention hashtag\" rel=\"tag\">#<span>2FA</span></a>/#MFA</p>"
},
"updated": "2024-05-08T08:13:17Z",
"attachment": [],
"tag": [
{
"type": "Hashtag",
"href": "https://infosec.exchange/tags/mfa",
"name": "#mfa"
},
{
"type": "Hashtag",
"href": "https://infosec.exchange/tags/2fa",
"name": "#2fa"
}
],
"replies": {
"id": "https://infosec.exchange/users/realn2s/statuses/111724811831789469/replies",
"type": "Collection",
"first": {
"type": "CollectionPage",
"next": "https://infosec.exchange/users/realn2s/statuses/111724811831789469/replies?only_other_accounts=true&page=true",
"partOf": "https://infosec.exchange/users/realn2s/statuses/111724811831789469/replies",
"items": []
}
},
"likes": {
"id": "https://infosec.exchange/users/realn2s/statuses/111724811831789469/likes",
"type": "Collection",
"totalItems": 5
},
"shares": {
"id": "https://infosec.exchange/users/realn2s/statuses/111724811831789469/shares",
"type": "Collection",
"totalItems": 4
}
}
]
}
}