Embed Notice

HTML Code

<blockquote style="position: relative; padding-left: 55px;"><section><a href="https://discuss.systems/users/ricci/statuses/117175284637908344">Rob Ricci (ricci@discuss.systems)'s status on Saturday, 29-Aug-2026 23:56:09 JST</a><a href="https://discuss.systems/@ricci" title="ricci@discuss.systems"><img src="https://gnusocial.jp/avatar/116194-48-20260823104837.webp" width="48" height="48" alt="Rob Ricci" style="position: absolute; left: 0; top: 0;">Rob Ricci</a><div><a href="https://neuromatch.social/@jdp23/117174716817439547" rel="in-reply-to">in reply to</a><ul><li><li><a href="https://gnusocial.jp/user/295917" title="cwebber@social.coop">Christine Lemmer-Webber</a></li><li><a href="https://gnusocial.jp/user/325615" title="jdp23@neuromatch.social">Jon</a></li></ul></div></section><article><p><a href="https://neuromatch.social/@jdp23">@jdp23</a> <a href="https://aseachange.com/@elena">@elena</a> <a href="https://lile.cl/@adriano">@adriano</a> <a href="https://social.coop/@cwebber">@cwebber</a> </p><p>Apparently this is known app behavior that enables abuse associated with post editing. Despite this, every time post editing comes up (which as you know, it does frequently) the team hems and haws about the potential for abuse. Even though a super pernicious version of abuse is enabled right now, by decisions they have already made. </p><p><a href="https://bsky.app/profile/ricci.io/post/3mu6a2g3ujs2j" rel="nofollow">https://bsky.app/profile/ricci.io/post/3mu6a2g3ujs2j</a></p></article><footer><a rel="bookmark" href="https://gnusocial.jp/conversation/6651119#notice-13101485">In conversation</a><time datetime="2026-08-29T23:56:09+09:00" title="Saturday, 29-Aug-2026 23:56:09 JST">about 10 days ago</time> <span>from <span><a href="https://discuss.systems/@ricci/117175284637908344" rel="external" title="Sent from discuss.systems via ActivityPub">discuss.systems</a></span></span><a href="https://discuss.systems/@ricci/117175284637908344">permalink</a><h4>Attachments</h4><ol><li><article><header><div>Domain not in remote thumbnail source whitelist: cdn.bsky.app</div><h5><a href="https://bsky.app/profile/ricci.io/post/3mu6a2g3ujs2j">Rob Ricci (@ricci.io)</a></h5><div> from <span>Rob Ricci (@ricci.io)</span></div></header><div>I would like to make the case that it is long past time to support edits because the current Bluesky appview behavior is *already* enabling one of the worst-case scenarios: edit a popular post to be some vile racist shit (plenty of ways to do this already), people on the Bluesky app have no way of</div><footer></footer></article></li></ol></footer></blockquote>

Corresponding Notice

Embed this notice
Rob Ricci (ricci@discuss.systems)'s status on Saturday, 29-Aug-2026 23:56:09 JSTRob Ricci
in reply to
@jdp23 @elena @adriano @cwebber
Apparently this is known app behavior that enables abuse associated with post editing. Despite this, every time post editing comes up (which as you know, it does frequently) the team hems and haws about the potential for abuse. Even though a super pernicious version of abuse is enabled right now, by decisions they have already made.
https://bsky.app/profile/ricci.io/post/3mu6a2g3ujs2j
In conversationabout 10 days ago from discuss.systemspermalink
Attachments
1. Domain not in remote thumbnail source whitelist: cdn.bsky.app
  Rob Ricci (@ricci.io)
  from Rob Ricci (@ricci.io)
  I would like to make the case that it is long past time to support edits because the current Bluesky appview behavior is *already* enabling one of the worst-case scenarios: edit a popular post to be some vile racist shit (plenty of ways to do this already), people on the Bluesky app have no way of

Public

Embed Notice

HTML Code

Corresponding Notice