ActivityPub Viewer

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.

Open in browser →
{ "@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", "Emoji": "toot:Emoji", "focalPoint": { "@container": "@list", "@id": "toot:focalPoint" } } ], "id": "https://mastodon.de/users/ErikUden/statuses/111940301222380638", "type": "Note", "summary": null, "inReplyTo": null, "published": "2024-02-16T08:50:43Z", "url": "https://mastodon.de/@ErikUden/111940301222380638", "attributedTo": "https://mastodon.de/users/ErikUden", "to": [ "https://www.w3.org/ns/activitystreams#Public" ], "cc": [ "https://mastodon.de/users/ErikUden/followers", "https://fedi.fyralabs.com/users/9gt5ol52km" ], "sensitive": false, "atomUri": "https://mastodon.de/users/ErikUden/statuses/111940301222380638", "inReplyToAtomUri": null, "conversation": "tag:mastodon.de,2024-02-16:objectId=17391717:objectType=Conversation", "content": "<h1>To all Fedi Admins Currently Being hit with a Spam Wave:</h1><p><strong>This kind of spam is now over! Unmute all the instances no longer on my list!</strong></p><p>I've just released <strong>v4.0.0 of The UNmute List!</strong> I'd be very happy about <a href=\"https://mastodon.de/@MastodonDE/110808633497349326\" target=\"_blank\">a small donation</a> because I have very little time and I cannot really justify working on this list with my current schedule :mycomputer:​</p><p>There is a new type of spam, the same instances are affected as before. Those responsible in Japan are said to <a href=\"https://blog.fyralabs.com/cyberbullying-gone-global-regarding-the-fediverse-spam-and-operation-beleaguer/\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">have been arrested</a>. </p><p>Without further ado...</p><p><strong><em>Limit these instances:</em></strong></p><p>[<a href=\"https://github.com/Mastodon-DE/blocklists/blob/main/spam/2024-02-15/2024-02-15-spam-mute-list.md\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">Full List of Affected Instances Here</a>] </p><p>Just get the list to download and import <a href=\"https://github.com/Mastodon-DE/blocklists/blob/main/spam/2024-02-15/2024-02-15-spam-domain_mutes-erik-uden.csv\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">here</a>.</p><p>Simply import this list and you'll mute the 47 worst spam instances currently known to me! I've worked on it for multiple weeks, sometimes ~9 hours at a time verifying all lists sent to me manually. </p><p>Limit first, defederate only in worst situations! </p><p><strong>Consider re-federating with and un-silencing any of the mentioned instances once the spam is mitigated.</strong> The admins of some of these may have just been asleep when this all started. </p><p><br><br><br></p><h2>Ban Spam Accounts via their E-Mail Domain</h2><p><strong>Block the following E-Mail Domain</strong> and whatever temp Mail provider it resolves to: <code>chitthi.in</code></p><p>Just to be safe, block these ones too (<em>same provider</em>) </p><ul><li><code>mailto.plus</code></li><li><code>fexpost.com</code></li><li><code>fexbox.org</code></li><li><code>mailbox.in.ua</code></li><li><code>any.pink</code></li></ul><p>All our spam accounts came from these E-mails. </p><p>Since you probably have some of these accounts sleeping:</p><p><code>https://[your-instance.tld]/admin/accounts?email=%25%40chitthi.in</code> there just select all and press “Ban”. </p><h2>Find Remaining Spammers</h2><p>I've seen instances that fixed the spam issue but began being hit later again. The spammers might use new E-Mails, so here is a way to find and block them anyway:</p><p><a href=\"https://mamot.fr/@vincib/111946701929274350\" target=\"_blank\" rel=\"nofollow noopener noreferrer\" translate=\"no\"><span class=\"invisible\">https://</span><span class=\"ellipsis\">mamot.fr/@vincib/1119467019292</span><span class=\"invisible\">74350</span></a></p><p><br><br><br></p><h2>IP Bans and TOR</h2><p>These spammers seem to be using the <strong>TOR Network</strong> as all of their IPs are TOR Exit Node IPs, hence an idea (<em>with some collateral damage if executed</em>) would be to ban all TOR exit node IPs for sign ups. I am personally against this idea as you'd also prevent users who simply wish to stay anonymous online (<em>political refugees, leakers of important documents, etc.</em>) from using your platform. For now, simply banning every user using a particular Spammer IP will not help and will merely ban users that try to stay anonymous! Not necessarily the spammers. </p><p><br><br><br></p><h2>How To Block All Temp E-Mails in the Future</h2><p><em>If you want to prevent this from ever happening again, you should block E-Mails from Temporary Mail providers all together:</em></p><ul><li><p><strong><a href=\"https://github.com/disposable-email-domains/disposable-email-domains/\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">Here is the list of all Temp email providers</a></strong> (<em>there are both blocklist and allowlist</em>)</p></li><li><p><strong><a href=\"https://codeberg.org/stvo/mastodon-ansible-nodocker#disposable-mail-blocking\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">Here how to install it in Mastodon</a></strong> </p></li><li><p><strong><a href=\"https://codeberg.org/stvo/mastodon-ansible-nodocker/src/branch/main/playbooks/no_disposable_mail.yml\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">The script that automatically pulls the list via Cronjob and imports it into Mastodon</a></strong></p></li><li><p><strong><a href=\"https://codeberg.org/stvo/mastodon-ansible-nodocker/src/branch/main/playbooks/templates/home/mastodon/addmaildomains.sh.j2\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">Script template</a></strong> </p></li></ul><p>Because of this, <a href=\"https://darmstadt.social/@stvo/111940755074991980\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">hessen.social, for example, was not affected by the spam attack</a>! They had already banned the email domain the spammers used ages ago. </p><p>In future updates on Mastodon, maybe Admins can simply click a button that says “Ban Temp E-Mail Providers” Automagically from the E-Mail Menu? There could be E-Mail categories that can be banned, such as temporary mails. </p><p><br><br><br></p><h2>Why did this happen?</h2><p>The real reason hundreds of us spent hours of our days during the spam on mitigating it is the following:</p><p><a href=\"https://fedi.fyralabs.com/notes/9q0ouuuw3p\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">Cyberbullying Gone Global: Fediverse Spam and Operation Beleaguer</a></p><p>This is the full exposé <span class=\"h-card\" translate=\"no\"><a href=\"https://fedi.fyralabs.com/@cappy\" class=\"u-url mention\" rel=\"nofollow noopener noreferrer\" target=\"_blank\">@<span>cappy</span></a></span> has been working on regarding the February 15th Spam Attacks!</p><p>Thank you @BrodieOnLinux@linuxrocks.online for <a href=\"https://mastodon.de/@ErikUden/111979657514522171\" target=\"_blank\">mentioning this post in a video</a>! </p><p><strong>Good luck, everyone!</strong> <br>Thanks for participating in the Fediverse Experiment! </p><p><a href=\"https://mastodon.de/tags/FediBlock\" class=\"mention hashtag\" rel=\"tag\">#<span>FediBlock</span></a> <a href=\"https://mastodon.de/tags/FediAdmin\" class=\"mention hashtag\" rel=\"tag\">#<span>FediAdmin</span></a></p>", "contentMap": { "en": "<h1>To all Fedi Admins Currently Being hit with a Spam Wave:</h1><p><strong>This kind of spam is now over! Unmute all the instances no longer on my list!</strong></p><p>I've just released <strong>v4.0.0 of The UNmute List!</strong> I'd be very happy about <a href=\"https://mastodon.de/@MastodonDE/110808633497349326\" target=\"_blank\">a small donation</a> because I have very little time and I cannot really justify working on this list with my current schedule :mycomputer:​</p><p>There is a new type of spam, the same instances are affected as before. Those responsible in Japan are said to <a href=\"https://blog.fyralabs.com/cyberbullying-gone-global-regarding-the-fediverse-spam-and-operation-beleaguer/\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">have been arrested</a>. </p><p>Without further ado...</p><p><strong><em>Limit these instances:</em></strong></p><p>[<a href=\"https://github.com/Mastodon-DE/blocklists/blob/main/spam/2024-02-15/2024-02-15-spam-mute-list.md\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">Full List of Affected Instances Here</a>] </p><p>Just get the list to download and import <a href=\"https://github.com/Mastodon-DE/blocklists/blob/main/spam/2024-02-15/2024-02-15-spam-domain_mutes-erik-uden.csv\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">here</a>.</p><p>Simply import this list and you'll mute the 47 worst spam instances currently known to me! I've worked on it for multiple weeks, sometimes ~9 hours at a time verifying all lists sent to me manually. </p><p>Limit first, defederate only in worst situations! </p><p><strong>Consider re-federating with and un-silencing any of the mentioned instances once the spam is mitigated.</strong> The admins of some of these may have just been asleep when this all started. </p><p><br><br><br></p><h2>Ban Spam Accounts via their E-Mail Domain</h2><p><strong>Block the following E-Mail Domain</strong> and whatever temp Mail provider it resolves to: <code>chitthi.in</code></p><p>Just to be safe, block these ones too (<em>same provider</em>) </p><ul><li><code>mailto.plus</code></li><li><code>fexpost.com</code></li><li><code>fexbox.org</code></li><li><code>mailbox.in.ua</code></li><li><code>any.pink</code></li></ul><p>All our spam accounts came from these E-mails. </p><p>Since you probably have some of these accounts sleeping:</p><p><code>https://[your-instance.tld]/admin/accounts?email=%25%40chitthi.in</code> there just select all and press “Ban”. </p><h2>Find Remaining Spammers</h2><p>I've seen instances that fixed the spam issue but began being hit later again. The spammers might use new E-Mails, so here is a way to find and block them anyway:</p><p><a href=\"https://mamot.fr/@vincib/111946701929274350\" target=\"_blank\" rel=\"nofollow noopener noreferrer\" translate=\"no\"><span class=\"invisible\">https://</span><span class=\"ellipsis\">mamot.fr/@vincib/1119467019292</span><span class=\"invisible\">74350</span></a></p><p><br><br><br></p><h2>IP Bans and TOR</h2><p>These spammers seem to be using the <strong>TOR Network</strong> as all of their IPs are TOR Exit Node IPs, hence an idea (<em>with some collateral damage if executed</em>) would be to ban all TOR exit node IPs for sign ups. I am personally against this idea as you'd also prevent users who simply wish to stay anonymous online (<em>political refugees, leakers of important documents, etc.</em>) from using your platform. For now, simply banning every user using a particular Spammer IP will not help and will merely ban users that try to stay anonymous! Not necessarily the spammers. </p><p><br><br><br></p><h2>How To Block All Temp E-Mails in the Future</h2><p><em>If you want to prevent this from ever happening again, you should block E-Mails from Temporary Mail providers all together:</em></p><ul><li><p><strong><a href=\"https://github.com/disposable-email-domains/disposable-email-domains/\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">Here is the list of all Temp email providers</a></strong> (<em>there are both blocklist and allowlist</em>)</p></li><li><p><strong><a href=\"https://codeberg.org/stvo/mastodon-ansible-nodocker#disposable-mail-blocking\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">Here how to install it in Mastodon</a></strong> </p></li><li><p><strong><a href=\"https://codeberg.org/stvo/mastodon-ansible-nodocker/src/branch/main/playbooks/no_disposable_mail.yml\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">The script that automatically pulls the list via Cronjob and imports it into Mastodon</a></strong></p></li><li><p><strong><a href=\"https://codeberg.org/stvo/mastodon-ansible-nodocker/src/branch/main/playbooks/templates/home/mastodon/addmaildomains.sh.j2\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">Script template</a></strong> </p></li></ul><p>Because of this, <a href=\"https://darmstadt.social/@stvo/111940755074991980\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">hessen.social, for example, was not affected by the spam attack</a>! They had already banned the email domain the spammers used ages ago. </p><p>In future updates on Mastodon, maybe Admins can simply click a button that says “Ban Temp E-Mail Providers” Automagically from the E-Mail Menu? There could be E-Mail categories that can be banned, such as temporary mails. </p><p><br><br><br></p><h2>Why did this happen?</h2><p>The real reason hundreds of us spent hours of our days during the spam on mitigating it is the following:</p><p><a href=\"https://fedi.fyralabs.com/notes/9q0ouuuw3p\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">Cyberbullying Gone Global: Fediverse Spam and Operation Beleaguer</a></p><p>This is the full exposé <span class=\"h-card\" translate=\"no\"><a href=\"https://fedi.fyralabs.com/@cappy\" class=\"u-url mention\" rel=\"nofollow noopener noreferrer\" target=\"_blank\">@<span>cappy</span></a></span> has been working on regarding the February 15th Spam Attacks!</p><p>Thank you @BrodieOnLinux@linuxrocks.online for <a href=\"https://mastodon.de/@ErikUden/111979657514522171\" target=\"_blank\">mentioning this post in a video</a>! </p><p><strong>Good luck, everyone!</strong> <br>Thanks for participating in the Fediverse Experiment! </p><p><a href=\"https://mastodon.de/tags/FediBlock\" class=\"mention hashtag\" rel=\"tag\">#<span>FediBlock</span></a> <a href=\"https://mastodon.de/tags/FediAdmin\" class=\"mention hashtag\" rel=\"tag\">#<span>FediAdmin</span></a></p>" }, "updated": "2024-04-22T19:02:50Z", "attachment": [], "tag": [ { "type": "Mention", "href": "https://fedi.fyralabs.com/users/9gt5ol52km", "name": "@cappy@fedi.fyralabs.com" }, { "type": "Hashtag", "href": "https://mastodon.de/tags/fediblock", "name": "#fediblock" }, { "type": "Hashtag", "href": "https://mastodon.de/tags/fediadmin", "name": "#fediadmin" }, { "id": "https://mastodon.de/emojis/34453", "type": "Emoji", "name": ":mycomputer:", "updated": "2023-08-11T06:52:56Z", "icon": { "type": "Image", "mediaType": "image/png", "url": "https://media.mastodon.de/custom_emojis/images/000/034/453/original/06332bb062651d4e.png" } } ], "replies": { "id": "https://mastodon.de/users/ErikUden/statuses/111940301222380638/replies", "type": "Collection", "first": { "type": "CollectionPage", "next": "https://mastodon.de/users/ErikUden/statuses/111940301222380638/replies?min_id=112316500842530363&page=true", "partOf": "https://mastodon.de/users/ErikUden/statuses/111940301222380638/replies", "items": [ "https://mastodon.de/users/ErikUden/statuses/111940485298475768", "https://mastodon.de/users/ErikUden/statuses/111946002637664413", "https://mastodon.de/users/ErikUden/statuses/112316500842530363" ] } } }