erstwhile<p>Ho Ho!! what's this, <a href="https://theblower.au/tags/Gitlab" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Gitlab</span></a> VScode plugin <a href="https://theblower.au/tags/Feature" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Feature</span></a> advertising <a href="https://theblower.au/tags/Enshitification" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Enshitification</span></a> delivered to your editors next new line !? </p><p>Oh well Gitlab, your plugin is now gone, removed from my <a href="https://theblower.au/tags/VScodium" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>VScodium</span></a> instance.. </p><p>Keep your <a href="https://theblower.au/tags/Shite" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Shite</span></a> pushy feature advertising out of my text file editor.</p><p>Guess that's the queue to find a new on-prem git server .. if they'll push paid features on <a href="https://theblower.au/tags/FOSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>FOSS</span></a> users in an editor plugin with an `Opt out` styled delivery, folks with ethics and concerns will walk, from *all* their products ...</p><p> (Like they all did for <a href="https://theblower.au/tags/Microsoft" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Microsoft</span></a> when they bought GitHub, ring any bells? )</p><p>When the work instance comes up for serious upgrade/renewal, I'll be pushing for a change. Consider it instant dismissal if I see it in the Gitlab CE on-prem code. </p><p>Wonder if <a href="https://theblower.au/tags/Gitea" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Gitea</span></a> does this sort of bullshit for their on-prem git server code, chime in if you have seen such ??</p>