Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://udongein.xyz/users/lispi314" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>lispi314</span></a></span> <span class="h-card" translate="no"><a href="https://mk.absturztau.be/@enigmatico" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>enigmatico</span></a></span> <span class="h-card" translate="no"><a href="https://transfem.social/@bunnybeam" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>bunnybeam</span></a></span> <span class="h-card" translate="no"><a href="https://ublog.kimapr.net/users/kimapr" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>kimapr</span></a></span> <br><em>nodds in agreement</em></p><ul><li>I think having a proper <a href="https://infosec.space/tags/API" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>API</span></a> is a way to facilitate that, cuz worst-case one just slaps together some <a href="https://infosec.space/tags/aliases" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>aliases</span></a> in <a href="https://infosec.space/tags/bash" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>bash</span></a>, <a href="https://infosec.space/tags/fish" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>fish</span></a>, <a href="https://infosec.space/tags/zsh" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>zsh</span></a> or whatever <a href="https://infosec.space/tags/shell" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>shell</span></a> and just uses <a href="https://infosec.space/tags/curl" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>curl</span></a> to query stuff manually as this solves the whole <a href="https://infosec.space/tags/WebApp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>WebApp</span></a> - issue.</li></ul><p>And I do prefer <a href="https://infosec.space/tags/FLOSS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>FLOSS</span></a> as it works fine for an ever increasing audience!</p><ul><li>Even if we choose to point at bad <a href="https://infosec.space/tags/UX" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>UX</span></a> / <a href="https://infosec.space/tags/UI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>UI</span></a> combos like <a href="https://infosec.space/tags/GnuPG" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>GnuPG</span></a>, we've to also acknowledge <em>better existing alternatives</em> like <a href="https://infosec.space/tags/enc" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>enc</span></a> that <a href="https://github.com/life4/enc" rel="nofollow noopener noreferrer" target="_blank"><em>just work</em></a>!</li></ul><p>Personally, I think that everything people are <em>expected to use</em> if not <em>forced to use</em> should be <a href="https://infosec.space/tags/OpenSource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>OpenSource</span></a> as licensed in a <a href="https://infosec.space/tags/OSI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>OSI</span></a> accredited license and be released with <a href="https://infosec.space/tags/SourceCode" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SourceCode</span></a> and <a href="https://infosec.space/tags/documentation" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>documentation</span></a> to make <a href="https://infosec.space/tags/reproduceableBuilds" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>reproduceableBuilds</span></a> and thus facilitate <a href="https://infosec.space/tags/audits" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>audits</span></a> by <em>truly</em> independent parties...</p><ul><li>And if that's not possible any requirement to using said things should be outlawed no matter the context! </li></ul><p>A unsarcastically good example is <a href="https://infosec.space/tags/S3" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>S3</span></a>, even tho I hate <a href="https://infosec.space/tags/amazon" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>amazon</span></a>, they wanted <a href="https://infosec.space/tags/developers" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>developers</span></a> to integrate their <a href="https://infosec.space/tags/ObjectStorage" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ObjectStorage</span></a> which necessitated an <a href="https://infosec.space/tags/open" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>open</span></a> source'd API to the point that it's <a href="https://infosec.space/tags/backend" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>backend</span></a> is inherently reproduceable, and now every halfassing <a href="https://infosec.space/tags/Webhoster" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Webhoster</span></a> offers S3 <a href="https://infosec.space/tags/storage" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>storage</span></a>, sometimes with bit & second-precise billing.</p>