Embed Notice

HTML Code

<blockquote style="position: relative; padding-left: 55px;"><section><a href="https://mas.to/users/tokyo_0/statuses/111649737564297951">Tokyo Outsider (337ppm) (tokyo_0@mas.to)'s status on Wednesday, 27-Dec-2023 10:16:35 JST</a><a href="https://mas.to/@tokyo_0" title="tokyo_0@mas.to"><img src="https://gnusocial.jp/avatar/89924-48-20240308124607.webp" width="48" height="48" alt="Tokyo Outsider (337ppm)" style="position: absolute; left: 0; top: 0;">Tokyo Outsider (337ppm)</a><div><ul><li></ul></div></section><article><p><a href="https://433.world/@Yuvalne">@Yuvalne</a> It's inaccurate and disingenuous to call this "authorized fetch circumvented" — it suggests there's something flawed with <a href="https://mas.to/tags/authorized_fetch" rel="tag">#authorized_fetch</a>, when there's no way any system would miraculously know to block a different domain because it happens to be used by the same person as a domain that is already blocked.</p><p>This is just the same whackamole problem that presents itself with all blacklist rather than whitelist systems, not a problem with <a href="https://mas.to/tags/authorizedFetch" rel="tag">#authorizedFetch</a>.</p><p><a href="https://mas.to/tags/ActivityPub" rel="tag">#ActivityPub</a> <a href="https://mas.to/tags/fediBlockMeta" rel="tag">#fediBlockMeta</a></p></article><footer><a rel="bookmark" href="https://gnusocial.jp/conversation/2503891#notice-4954723">In conversation</a><time datetime="2023-12-27T10:16:35+09:00" title="Wednesday, 27-Dec-2023 10:16:35 JST">Wednesday, 27-Dec-2023 10:16:35 JST</time> <span>from <span><a href="https://mas.to/@tokyo_0/111649737564297951" rel="external" title="Sent from mas.to via ActivityPub">mas.to</a></span></span><a href="https://mas.to/@tokyo_0/111649737564297951">permalink</a></footer></blockquote>

Corresponding Notice

Embed this notice
Tokyo Outsider (337ppm) (tokyo_0@mas.to)'s status on Wednesday, 27-Dec-2023 10:16:35 JSTTokyo Outsider (337ppm)
- Talya (she/her)
@Yuvalne It's inaccurate and disingenuous to call this "authorized fetch circumvented" — it suggests there's something flawed with #authorized_fetch, when there's no way any system would miraculously know to block a different domain because it happens to be used by the same person as a domain that is already blocked.
This is just the same whackamole problem that presents itself with all blacklist rather than whitelist systems, not a problem with #authorizedFetch.
#ActivityPub #fediBlockMeta
In conversationWednesday, 27-Dec-2023 10:16:35 JST from mas.topermalink

Public

Embed Notice

HTML Code

Corresponding Notice