Untitled attachment

Notices where this attachment appears

1. Embed this notice
   Børge (forteller@tutoteket.no)'s status on Friday, 02-Jan-2026 06:40:23 JST Børge

   in reply to

   I also had 2 – count 'em: two(!) – contributing days to FOSS projects that use GitLab.com. 4 contributions in all, and one of which was just a new comment on a really old issue that I created for GitLab itself. Two more comments on issues for Newsflash, and one single actual new issue, also for Newsflash. But at least that issue was completed! :)

   Will 2026 be the year where more FOSS devs moves away from Microsoft and closed, AI-loving GH and moves to FOSS platforms? We'll see.

   #FOSS #FLOSS

2. Embed this notice
   Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Monday, 29-Sep-2025 01:39:07 JST Haelwenn /элвэн/ :triskell:
   @mlyoung Teachers I don't think would be much of an issue, but infra or deals with hosters would be.
   
   (Of course they could just use gitlab.com instead of hosting a forge but that has the exact same problems as github.com)
3. Embed this notice
   sodiboo (sodiboo@gaysex.cloud)'s status on Tuesday, 12-Aug-2025 04:12:25 JST sodiboo

   in reply to

   @nora@blob.love
   
   https://codeberg.org/ -> https://codeberg.page/
   https://kitsunes.dev/ -> https://kitsu.page/
   https://git.gay/ -> https://pages.gay/
   https://gitlab.com/ -> https://gitlab.io/

4. Embed this notice
   heise Developer (heisedeveloper@social.heise.de)'s status on Tuesday, 24-Jun-2025 15:56:35 JST heise Developer

   GitLab 18.1 erklärt Duo Code Review für produktionsreif

   Der KI-gestützte Dienst Duo Code Review ist allgemein verfügbar und GitLab.com gibt nun Warnungen aus, wenn User kompromittierte Passwörter nutzen.

   https://www.heise.de/news/GitLab-18-1-erklaert-Duo-Code-Review-fuer-produktionsreif-10455486.html?wt_mc=sm.red.ho.mastodon.mastodon.md_beitraege.md_beitraege&utm_source=mastodon

   #ContinuousIntegration #Git #IT #KünstlicheIntelligenz #Security #Versionskontrolle #news

5. Embed this notice
   翠星石 (suiseiseki@freesoftwareextremist.com)'s status on Saturday, 21-Jun-2025 01:36:32 JST 翠星石

   in reply to
   @SuperDicq @gianmarcogg03 @Zergling_man @Yoruka >you should probably do something about.
   It's like asking evil developers to stop using github or gitlab - good luck with that one.
   
   >I thought the "Community Edition" as packaged by Trisquel was free.
   Any git host that requires arbitrary JavaScript via the web of arbitrary malware execution for basic functionality like file listing is proprietary software, as the user doesn't have the 4 freedoms over that software, no matter what license it is under.
   
   Gitlab is an unacceptable git host for GNU packages; https://www.gnu.org/software/repo-criteria-evaluation.html#gitlab-com (gitlab.com, but also applies to any gitlab version).
   
   Ironically, the github SaaSS + (optional) proprietary software site is less bad when it comes to viewing an overview without having to clone the whole repo than even a community gitlab instance, as the README top file listing is at least shown without JavaScript and files can be viewed by appending ?raw=true to the full link, while gitlab shows nothing.
   
   The JavaScript license for gitlab is written to only license the JavaScript under MIT expat when compiled/assembled etc into obfscript, or served directly (only a few files) - therefore the source form is under no license (other than the handful with a license marked).
   
   I would like to copy-paste the exact wording, but gitlab doesn't show the license file and it's too big to clone the whole repo in a reasonable amount of time and the main Laboratory frontend instance has been sabotaged to not work unless malware is executed (before it worked fine).
6. Embed this notice
   vic (vic@shitpost.cloud)'s status on Thursday, 03-Apr-2025 06:57:54 JST vic

   in reply to

   > hosting it on US-based and US-developed Gitlab software, on US-based gitlab.com instance