Embed Notice

HTML Code

<blockquote style="position: relative; padding-left: 55px;"><section><a href="https://mastodon.zunda.ninja/users/zundan/statuses/109515041021092760">zunda (zundan@mastodon.zunda.ninja)'s status on Thursday, 15-Dec-2022 10:15:40 JST</a><a href="https://mastodon.zunda.ninja/@zundan" title="zundan@mastodon.zunda.ninja"><img src="https://gnusocial.jp/avatar/285-48-20230130022456.gif" width="48" height="48" alt="zunda" style="position: absolute; left: 0; top: 0;">zunda</a><div><a href="https://ruby.social/@Schneems/109515021383412092" rel="in-reply-to">in reply to</a><ul><li><li><a href="https://gnusocial.jp/user/41417" title="schneems@ruby.social">Richard Schneeman</a></li><li><a href="https://gnusocial.jp/user/73849" title="avdi@hachyderm.io">Avdi Grimm</a></li></ul></div></section><article><p><a href="https://ruby.social/@Schneems">@Schneems</a> <a href="https://hachyderm.io/@avdi">@avdi</a> I'd just leave pull requests at <a href="https://github.com/mastodon/mastodon/pulls" rel="nofollow noreferrer">https://github.com/mastodon/mastodon/pulls</a> and wait :) As far as I see, the core developers give reasonable decisions as to which of PRs they'd merge.</p><p>For design principles, it'd be worthwhile reading through <a href="https://blog.joinmastodon.org/2018/07/cage-the-mastodon/" rel="nofollow noreferrer">https://blog.joinmastodon.org/2018/07/cage-the-mastodon/</a> (once the origin sever comes back :mastodon_oops:</p></article><footer><a rel="bookmark" href="https://gnusocial.jp/conversation/852455#notice-1723909">In conversation</a><time datetime="2022-12-15T10:15:40+09:00" title="Thursday, 15-Dec-2022 10:15:40 JST">Thursday, 15-Dec-2022 10:15:40 JST</time> <span>from <span><a href="https://mastodon.zunda.ninja/@zundan/109515041021092760" rel="external" title="Sent from mastodon.zunda.ninja via ActivityPub">mastodon.zunda.ninja</a></span></span><a href="https://mastodon.zunda.ninja/@zundan/109515041021092760">permalink</a><h4>Attachments</h4><ol><li><article><header><div>Domain not in remote thumbnail source whitelist: blog.joinmastodon.org</div><h5><a href="https://blog.joinmastodon.org/2018/07/cage-the-mastodon/">Cage the Mastodon</a></h5><div></div></header><div>A year ago I wrote about Mastodon’s improvements over Twitter’s lacking protections against abuse and harassment. Development in that area has not been standing still, and it’s about time we do another comparison.</div><footer></footer></article></li><li><article><header><div>Domain not in remote thumbnail source whitelist: opengraph.githubassets.com</div><h5><a href="https://github.com/mastodon/mastodon/pulls">Pull requests · mastodon/mastodon</a></h5><div></div></header><div>Your self-hosted, globally interconnected microblogging community - Pull requests · mastodon/mastodon</div><footer></footer></article></li></ol></footer></blockquote>

Corresponding Notice

Embed this notice
zunda (zundan@mastodon.zunda.ninja)'s status on Thursday, 15-Dec-2022 10:15:40 JSTzunda
in reply to
@Schneems @avdi I'd just leave pull requests at https://github.com/mastodon/mastodon/pulls and wait :) As far as I see, the core developers give reasonable decisions as to which of PRs they'd merge.
For design principles, it'd be worthwhile reading through https://blog.joinmastodon.org/2018/07/cage-the-mastodon/ (once the origin sever comes back :mastodon_oops:
In conversationThursday, 15-Dec-2022 10:15:40 JST from mastodon.zunda.ninjapermalink
Attachments
1. Domain not in remote thumbnail source whitelist: blog.joinmastodon.org
  Cage the Mastodon
  A year ago I wrote about Mastodon’s improvements over Twitter’s lacking protections against abuse and harassment. Development in that area has not been standing still, and it’s about time we do another comparison.
2. Domain not in remote thumbnail source whitelist: opengraph.githubassets.com
  Pull requests · mastodon/mastodon
  Your self-hosted, globally interconnected microblogging community - Pull requests · mastodon/mastodon

Public

Embed Notice

HTML Code

Corresponding Notice