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://join-lemmy.org/context.json",
"https://www.w3.org/ns/activitystreams"
],
"type": "OrderedCollection",
"id": "https://infosec.pub/c/crypto/featured",
"totalItems": 2,
"orderedItems": [
{
"type": "Page",
"id": "https://infosec.pub/post/23948572",
"attributedTo": "https://infosec.pub/u/TrustedThirdParty",
"to": [
"https://infosec.pub/c/crypto",
"https://www.w3.org/ns/activitystreams#Public"
],
"name": "Forum rules for !crypto@infosec.pub",
"cc": [],
"content": "<p>Hello all!</p>\n<p>Since the forum hasn’t had any listed rules until now, I’m going to import the rules which have worked over at the cryptography forum which I’ve been moderating in on reddit. I’ll list the rules here with explanations.</p>\n<h1>Forum rules</h1>\n<p>1: Stick to the topic of cryptography</p>\n<p>The focus is on modern cryptography (computer security algorithms and protocols and their implementations). We also allow related infosec topics (including phishing, security UX, etc) as well as discussion of notable historical ciphers, but keep in mind that just because cryptography is mentioned in an article it doesn’t necessarily mean it’s relevant. Analogy: a forum about motors wouldn’t let you post about road trips. In this forum, a submitted article should have a substantial security aspect. If you’re unsure, ask the mods or ask in a meta thread.</p>\n<p>2: Engage in good faith, maintain high quality & accuracy, don’t mislead</p>\n<p>To keep quality high, first of all, be kind. Behavior which discourage other good faith participants from contributing is not allowed.<br />\nSecond, modern cryptography implies threat models, public specifications, source code, security proofs, etc.\nDon’t leave out important information. Please cite your sources.\nRemember that bad advice can be dangerous!</p>\n<p>3: Crypto review requests must explain the algorithms</p>\n<p>We follow Kerckhoffs’ principle and Schneier’s Law - posts that asks for security review of custom algorithms or implementations MUST also publish the full algorithm and a description of its use. Otherwise there can be no meaningful security analysis. <a href=\"https://old.reddit.com/r/crypto/comments/1boxkg/breaking_ciphers_and_certainty/c98x4ej/\" rel=\"nofollow\">Sharing just the output is like…</a></p>\n<p>4: Challenges and puzzles must use modern crypto</p>\n<p>Simple codes, ciphers, ARGs, and other such “weak crypto” don’t belong here. Rule of thumb: If a desktop computer can break a code in less than an hour, or if it can be broken by hand, it’s not strong crypto.</p>\n<p>5: Don’t cheat on challenges or tests!</p>\n<p>Don’t use this forum to cheat on competitions, challenges or tests!\nYou may ask for help to understand a test question, but you are not allowed to ask others to solve it for you. You must also disclose the source of a problem you’re asking for help with.</p>\n<p>6: Link directly to original sources (with exceptions)</p>\n<p>We prefer original sources of news, source code, academic papers or similar, rather than clickbaity buzzword blogspam. Avoid snake oil and low quality sources.<br />\nDo not post link shortener or to link farms or similar low quality sites, avoid mirror sites (unless necessary due to eg. paywall, like archive.org), and link directly to the original (unless you’re posting a more readable expert written summary).</p>\n<p>7: Avoid making duplicate posts</p>\n<p>In low volume forums like this, multiple posts on breaking news will easily flood the forum. Please check if news is already posted. Different sources on the same news should be posted as comments in the existing thread (exceptions may only be made for substantial new information or if the prior thread is old - ask the mods if you’re unsure)</p>\n<p>8: All use of AI / LLM and their prompts <em>MUST</em> be disclosed in your submissions and comments</p>\n<p>Instead of entirely banning LLMs, we require transparency. Due to LLMs so often being confidently wrong, we PROHIBIT all undisclosed use of LLM when posting regardless of the nature of your post. If used, you MUST share the prompt!<br />\nNo LLM / AI is exempt!<br />\nIf you’re here to ask a question, a major problem is that the LLM output will carry implied INCORRECT context which you will not recognize, but which we will see, increasing the risk of misunderstanding. We will not be able to give you correct advice if we don’t know your thought process!</p>\n",
"mediaType": "text/html",
"source": {
"content": "Hello all!\n\nSince the forum hasn't had any listed rules until now, I'm going to import the rules which have worked over at the cryptography forum which I've been moderating in on reddit. I'll list the rules here with explanations.\n\n# Forum rules\n\n1: Stick to the topic of cryptography\n\nThe focus is on modern cryptography (computer security algorithms and protocols and their implementations). We also allow related infosec topics (including phishing, security UX, etc) as well as discussion of notable historical ciphers, but keep in mind that just because cryptography is mentioned in an article it doesn't necessarily mean it's relevant. Analogy: a forum about motors wouldn't let you post about road trips. In this forum, a submitted article should have a substantial security aspect. If you're unsure, ask the mods or ask in a meta thread. \n\n2: Engage in good faith, maintain high quality & accuracy, don't mislead\n\nTo keep quality high, first of all, be kind. Behavior which discourage other good faith participants from contributing is not allowed. \nSecond, modern cryptography implies threat models, public specifications, source code, security proofs, etc.\nDon't leave out important information. Please cite your sources.\nRemember that bad advice can be dangerous!\n\n3: Crypto review requests must explain the algorithms\n\nWe follow Kerckhoffs' principle and Schneier's Law - posts that asks for security review of custom algorithms or implementations MUST also publish the full algorithm and a description of its use. Otherwise there can be no meaningful security analysis. [Sharing just the output is like...](https://old.reddit.com/r/crypto/comments/1boxkg/breaking_ciphers_and_certainty/c98x4ej/) \n\n4: Challenges and puzzles must use modern crypto\n\nSimple codes, ciphers, ARGs, and other such \"weak crypto\" don't belong here. Rule of thumb: If a desktop computer can break a code in less than an hour, or if it can be broken by hand, it's not strong crypto. \n\n5: Don't cheat on challenges or tests!\n\nDon't use this forum to cheat on competitions, challenges or tests!\nYou may ask for help to understand a test question, but you are not allowed to ask others to solve it for you. You must also disclose the source of a problem you're asking for help with.\n\n6: Link directly to original sources (with exceptions)\n\nWe prefer original sources of news, source code, academic papers or similar, rather than clickbaity buzzword blogspam. Avoid snake oil and low quality sources. \nDo not post link shortener or to link farms or similar low quality sites, avoid mirror sites (unless necessary due to eg. paywall, like archive.org), and link directly to the original (unless you're posting a more readable expert written summary).\n\n7: Avoid making duplicate posts\n\nIn low volume forums like this, multiple posts on breaking news will easily flood the forum. Please check if news is already posted. Different sources on the same news should be posted as comments in the existing thread (exceptions may only be made for substantial new information or if the prior thread is old - ask the mods if you're unsure)\n\n8: All use of AI / LLM and their prompts *MUST* be disclosed in your submissions and comments\n\nInstead of entirely banning LLMs, we require transparency. Due to LLMs so often being confidently wrong, we PROHIBIT all undisclosed use of LLM when posting regardless of the nature of your post. If used, you MUST share the prompt! \nNo LLM / AI is exempt! \nIf you're here to ask a question, a major problem is that the LLM output will carry implied INCORRECT context which you will not recognize, but which we will see, increasing the risk of misunderstanding. We will not be able to give you correct advice if we don't know your thought process!",
"mediaType": "text/markdown"
},
"attachment": [],
"sensitive": false,
"published": "2025-02-19T21:06:28.935002Z",
"updated": "2025-02-20T02:30:43.234215Z",
"language": {
"identifier": "en",
"name": "English"
},
"audience": "https://infosec.pub/c/crypto",
"tag": [
{
"href": "https://infosec.pub/post/23948572",
"name": "#crypto",
"type": "Hashtag"
}
]
},
{
"type": "Page",
"id": "https://infosec.pub/post/23659217",
"attributedTo": "https://infosec.pub/u/TrustedThirdParty",
"to": [
"https://infosec.pub/c/crypto",
"https://www.w3.org/ns/activitystreams#Public"
],
"name": "Additional moderator in !crypto@infosec.pub",
"cc": [],
"content": "<p>Hi!</p>\n<p>I’m @Natanael@infosec.pub and this account that I’m making this post from is my moderation account, which is now part of the moderators of this cryptography forum. This is the account which I’ll be handling removals/bans from, etc.</p>\n<p>I’ve been added as a moderator by @jerry@infosec.pub (server admin)</p>\n<p>I also moderate <a href=\"https://reddit.com/r/crypto\">reddit.com/r/crypto</a>, and I’ve been looking for options since the reddit admins decided to make a mess of things with the API and various policies, etc. The community will NOT be forced to migrate so these communities are separate for now, but everybody’s encouraged to join here.</p>\n<p>If you’re a member in both places, feel free to tell us both your handles so we know who you are!</p>\n",
"mediaType": "text/html",
"source": {
"content": "Hi!\n\nI'm @Natanael@infosec.pub and this account that I'm making this post from is my moderation account, which is now part of the moderators of this cryptography forum. This is the account which I'll be handling removals/bans from, etc.\n\nI've been added as a moderator by @jerry@infosec.pub (server admin)\n\nI also moderate https://reddit.com/r/crypto, and I've been looking for options since the reddit admins decided to make a mess of things with the API and various policies, etc. The community will NOT be forced to migrate so these communities are separate for now, but everybody's encouraged to join here.\n\nIf you're a member in both places, feel free to tell us both your handles so we know who you are!",
"mediaType": "text/markdown"
},
"attachment": [],
"sensitive": false,
"published": "2025-02-13T14:10:02.479923Z",
"language": {
"identifier": "en",
"name": "English"
},
"audience": "https://infosec.pub/c/crypto",
"tag": [
{
"href": "https://infosec.pub/post/23659217",
"name": "#crypto",
"type": "Hashtag"
}
]
}
]
}