Embed Notice

HTML Code

<blockquote style="position: relative; padding-left: 55px;"><section><a href="https://mastodon.social/users/HistoPol/statuses/111583331607309059">HistoPol (#HP) 🥥 🌴 (histopol@mastodon.social)'s status on Friday, 15-Dec-2023 16:48:43 JST</a><a href="https://mastodon.social/@HistoPol" title="histopol@mastodon.social"><img src="https://gnusocial.jp/avatar/44595-48-20221221005726.webp" width="48" height="48" alt="HistoPol (#HP) 🥥 🌴" style="position: absolute; left: 0; top: 0;">HistoPol (#HP) 🥥 🌴</a><div><a href="https://social.alastair87.me/notes/9n9hzppmjl4nlneo" rel="in-reply-to">in reply to</a><ul><li><li><a href="https://gnusocial.jp/user/3399" title="lilithsaintcrow@raggedfeathers.com">Lili Saintcrow</a></li><li><a href="https://gnusocial.jp/user/158597" title="alastair@social.alastair87.me">alastair87</a></li></ul></div></section><article><p><a href="https://social.alastair87.me/@alastair">@alastair</a> <a href="https://raggedfeathers.com/@lilithsaintcrow">@lilithsaintcrow</a> </p><p>I agree.<br>I'd even say, it is too risky for you to endanger your established  account here.<br>It is always better to have several distribution channels.</p><p>I would not, however, block the <a href="https://mastodon.social/tags/MetaHordes" rel="tag">#MetaHordes</a> on an instance level anymore for the reasons <a href="https://indieweb.social/@tchambers">@tchambers</a> explained.* Also, because <a href="https://mastodon.social/tags/Threads" rel="tag">#Threads</a> will counterblock your instance right away, which might be hard to undo afterwards.</p><p>Use this method: </p><p><a href="https://mastodon.social/@HistoPol/110661216855577004" rel="nofollow noreferrer">https://mastodon.social/@HistoPol/110661216855577004</a></p><p>*<br><a href="https://indieweb.social/@tchambers/111575220489288762" rel="nofollow noreferrer">https://indieweb.social/@tchambers/111575220489288762</a></p></article><footer><a rel="bookmark" href="https://gnusocial.jp/conversation/2455961#notice-4858713">In conversation</a><time datetime="2023-12-15T16:48:43+09:00" title="Friday, 15-Dec-2023 16:48:43 JST">about a year ago</time> <span>from <span><a href="https://mastodon.social/@HistoPol/111583331607309059" rel="external" title="Sent from mastodon.social via ActivityPub">mastodon.social</a></span></span><a href="https://mastodon.social/@HistoPol/111583331607309059">permalink</a><h4>Attachments</h4><ol><li><article><header><div>Domain not in remote thumbnail source whitelist: files.mastodon.social</div><h5><a href="https://mastodon.social/@HistoPol/110661216855577004*">HistoPol (@HistoPol@mastodon.social)</a></h5><div> from <span>HistoPol</span></div></header><div>Attached: 2 imagesIMPORTANT #BlockMeta(1/n)Take precautions:
#Meta joins the #Fediverse Today, I have reposted toots about the many data abuses #Meta has already committed.Alas, my instance, mastodon.social, has not responded what they intend to do about #Project92 ,aka #Threads (i.e. #defederate). The #CJEU's published a damning ruling on 07/05/23 that all its practices regarding data collection contravene #GDPDR. I have therefore decided to at least block the presently over 2.500 instances that...</div><footer></footer></article></li><li><article><header><div>No result found on File_thumbnail lookup.</div><h5><a href="https://indieweb.social/@tchambers/111575220489288762">Tim Chambers (@tchambers@indieweb.social)</a></h5><div> from <span>Tim Chambers</span></div></header><div>#Admin #IndieWebSocial So #Threads is in the early stages of testing Federation. As we do with any new Fediverse server, we welcome them to the neighborhood but also will not hesitate to take moderating action if needed at any scale appropriate.Blocking them en masse as a "first strike" is, in our view, fundamentally unwise for the goals of the open social web &amp; unneeded to protect our users.Read more on this strategy here: https://www.timothychambers.net/2023/06/23/project-and-the.htmlcc: @fediversenews@venera.social</div><footer></footer></article></li></ol></footer></blockquote>

Corresponding Notice

Embed this notice
HistoPol (#HP) 🥥 🌴 (histopol@mastodon.social)'s status on Friday, 15-Dec-2023 16:48:43 JSTHistoPol (#HP) 🥥 🌴
in reply to
@alastair @lilithsaintcrow
I agree.
I'd even say, it is too risky for you to endanger your established account here.
It is always better to have several distribution channels.
I would not, however, block the #MetaHordes on an instance level anymore for the reasons @tchambers explained.* Also, because #Threads will counterblock your instance right away, which might be hard to undo afterwards.
Use this method:
https://mastodon.social/@HistoPol/110661216855577004
*
https://indieweb.social/@tchambers/111575220489288762
In conversationabout a year ago from mastodon.socialpermalink
Attachments
1. Domain not in remote thumbnail source whitelist: files.mastodon.social
  HistoPol (@HistoPol@mastodon.social)
  from HistoPol
  Attached: 2 images IMPORTANT #BlockMeta (1/n) Take precautions: #Meta joins the #Fediverse Today, I have reposted toots about the many data abuses #Meta has already committed. Alas, my instance, mastodon.social, has not responded what they intend to do about #Project92 ,aka #Threads (i.e. #defederate). The #CJEU's published a damning ruling on 07/05/23 that all its practices regarding data collection contravene #GDPDR. I have therefore decided to at least block the presently over 2.500 instances that...
2. No result found on File_thumbnail lookup.
  Tim Chambers (@tchambers@indieweb.social)
  from Tim Chambers
  #Admin #IndieWebSocial So #Threads is in the early stages of testing Federation. As we do with any new Fediverse server, we welcome them to the neighborhood but also will not hesitate to take moderating action if needed at any scale appropriate. Blocking them en masse as a "first strike" is, in our view, fundamentally unwise for the goals of the open social web & unneeded to protect our users. Read more on this strategy here: https://www.timothychambers.net/2023/06/23/project-and-the.html cc: @fediversenews@venera.social

Public

Embed Notice

HTML Code

Corresponding Notice