Embed Notice

HTML Code

<blockquote style="position: relative; padding-left: 55px;"><section><a href="https://hachyderm.io/users/dalias/statuses/113746770270935627">Rich Felker (dalias@hachyderm.io)'s status on Tuesday, 31-Dec-2024 18:39:35 JST</a><a href="https://hachyderm.io/@dalias" title="dalias@hachyderm.io"><img src="https://gnusocial.jp/avatar/40873-48-20221207231635.webp" width="48" height="48" alt="Rich Felker" style="position: absolute; left: 0; top: 0;">Rich Felker</a><div><a href="https://gnusocial.jp/notice/8379466" rel="in-reply-to">in reply to</a><ul><li><li><a href="https://gnusocial.jp/user/19724" title="glyph@mastodon.social">Glyph</a></li><li><a href="https://gnusocial.jp/user/105710" title="whitequark@mastodon.social">✧✦Catherine✦✧</a></li><li><a href="https://gnusocial.jp/user/150413" title="emma@orbital.horse">Emma Builds 🚀</a></li></ul></div></section><article><p><a href="https://mastodon.social/@glyph">@glyph</a> <a href="https://mastodon.social/@whitequark">@whitequark</a> <a href="https://orbital.horse/@emma">@emma</a> <a href="https://mastodon.social/@mcc">@mcc</a> The problem with (4) is that the parties imposing these requirements don't actually know the scenarios, and can't.</p><p>GitHub isn't distinguishing "my personal hobby game" from "critical component everyone is curlbashing".</p><p>So they end up imposing the discriminatory requirements on everyone.</p></article><footer><a rel="bookmark" href="https://gnusocial.jp/conversation/4286579#notice-8379467">In conversation</a><time datetime="2024-12-31T18:39:35+09:00" title="Tuesday, 31-Dec-2024 18:39:35 JST">about 8 months ago</time> <span>from <span><a href="https://hachyderm.io/@dalias/113746770270935627" rel="external" title="Sent from hachyderm.io via ActivityPub">hachyderm.io</a></span></span><a href="https://hachyderm.io/@dalias/113746770270935627">permalink</a></footer></blockquote>

Corresponding Notice

Embed this notice
Rich Felker (dalias@hachyderm.io)'s status on Tuesday, 31-Dec-2024 18:39:35 JSTRich Felker
in reply to
@glyph @whitequark @emma @mcc The problem with (4) is that the parties imposing these requirements don't actually know the scenarios, and can't.
GitHub isn't distinguishing "my personal hobby game" from "critical component everyone is curlbashing".
So they end up imposing the discriminatory requirements on everyone.
In conversationabout 8 months ago from hachyderm.iopermalink

Public

Embed Notice

HTML Code

Corresponding Notice