shakedown.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A community for live music fans with roots in the jam scene. Shakedown Social is run by a team of volunteers (led by @clifff and @sethadam1) and funded by donations.

Administered by:

Server stats:

255
active users

#contentnation

0 posts0 participants0 posts today
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://beige.party/@theropologist" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>theropologist</span></a></span> <span class="h-card" translate="no"><a href="https://beige.party/@ItsThatDeafGuy" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>ItsThatDeafGuy</span></a></span> <span class="h-card" translate="no"><a href="https://beige.party/@rothko" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>rothko</span></a></span> do you have any IPs and/or FQDNs or domains <a href="https://infosec.space/tags/Maven" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Maven</span></a> uses for <a href="https://infosec.space/tags/Scraping" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Scraping</span></a> so I can add them to my <a href="https://github.com/greyhat-academy/lists.d/blob/main/activitypub.domains.block.list.tsv" rel="nofollow noopener noreferrer" target="_blank">public blocklist</a> that already has <a href="https://infosec.space/tags/Bridgy" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Bridgy</span></a>, <a href="https://infosec.space/tags/awakari" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>awakari</span></a><br>and <a href="https://infosec.space/tags/ContentNation" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ContentNation</span></a> on? </p><p>If so, please feel free to message me and/or <a href="https://github.com/greyhat-academy/lists.d/issues/new/choose" rel="nofollow noopener noreferrer" target="_blank">open up an issue</a>...</p>
:mima_rule: Mima-sama<p></p><blockquote>Even more shocking is the revelation that somehow, even private DMs from Mastodon were mirrored on their public site and searchable. How this is even possible is beyond me, as DM’s are ostensibly only between two parties, and the message itself was sent from two hackers.town</blockquote>WHAT THE FUCK? There should have been no way that <a href="https://makai.chaotic.ninja/tags/Maven" rel="nofollow noopener noreferrer" target="_blank">#Maven</a><span> was able to read DMs, even if they're poorly coded (should be importing Public posts only) and the DMs are not E2EE.<br><br>I guess the common wisdom of not trusting the privacy of </span><a href="https://makai.chaotic.ninja/tags/Mastodon" rel="nofollow noopener noreferrer" target="_blank">#Mastodon</a> DMs is very correct all along. ​:koishtare:​<span><br><br>Oh, and I was skeptical of whether this is block worthy (don't want another </span><a href="https://makai.chaotic.ninja/tags/ContentNation" rel="nofollow noopener noreferrer" target="_blank">#ContentNation</a> or <a href="https://makai.chaotic.ninja/tags/Awakari" rel="nofollow noopener noreferrer" target="_blank">#Awakari</a> incident again), but this definitely is <a href="https://makai.chaotic.ninja/tags/fediblock" rel="nofollow noopener noreferrer" target="_blank">#fediblock</a> worthy considering their casual response. Reading someone else's DMs is never acceptable. This flaw should've been acknowledged and reported to Mastodon (and perhaps other <a href="https://makai.chaotic.ninja/tags/fediverse" rel="nofollow noopener noreferrer" target="_blank">#fediverse</a><span> developers too just in case).<br><br></span><a href="https://makai.chaotic.ninja/tags/fediversemeta" rel="nofollow noopener noreferrer" target="_blank">#fediversemeta</a><span><br><br>RE: </span><a href="https://wedistribute.org/2024/06/maven-mastodon-posts/" rel="nofollow noopener noreferrer" target="_blank">https://wedistribute.org/2024/06/maven-mastodon-posts/</a><p></p>
Evan Prodromou<p>We're discussion <a href="https://cosocial.ca/tags/ContentNation" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ContentNation</span></a> at <a href="https://cosocial.ca/tags/Fediforum" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Fediforum</span></a>. I really appreciate this comprehensive article at WeDistribute about the topic:</p><p><a href="https://wedistribute.org/2024/03/contentnation-mastodons-toxicity/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">wedistribute.org/2024/03/conte</span><span class="invisible">ntnation-mastodons-toxicity/</span></a></p>
We DistributeThe <a class="hashtag" href="https://social.wedistribute.org/tag/contentnation" rel="nofollow noopener noreferrer" target="_blank">#ContentNation</a> situation is a dumpster fire for the <a class="hashtag" href="https://social.wedistribute.org/tag/fediverse" rel="nofollow noopener noreferrer" target="_blank">#Fediverse</a>. What would you do if you were building something, people misunderstood what it was, and things escalated to a point that someone loaded CSAM onto your server for the sake of reporting it?<br><br><a href="https://wedistribute.org/2024/03/contentnation-mastodons-toxicity/" rel="nofollow noopener noreferrer" target="_blank">https://wedistribute.org/2024/03/contentnation-mastodons-toxicity/</a>
Sean TilleyThere seems to be some discourse about <a class="hashtag" href="https://social.wedistribute.org/tag/contentnation" rel="nofollow noopener noreferrer" target="_blank">#ContentNation</a> being some kind of Fedi scraper, and I think people are overreacting.<br><br>I'm not going to link to the thread, but some people were freaking out because they put in their handles into a search field and saw their profiles and posts there. It's like they didn't realize they were literally performing a Webfinger request, and were just looking at some cached data of public statuses.