Security & Compliance in GitLab 17.11:
Custom Compliance Frameworks
Protected Container Tags
Static Reachability for Python
https://about.gitlab.com/releases/2025/04/17/gitlab-17-11-released/
I have just taken the time to thoroughly read the following article
This article has led me to the conclusion that an Open{source} War will have to be waged against LLM large language model abusers of data collection.
The work of these bots is pure DDoS denial of service. An interesting set of offensive tools have been programmed and are already implemented. They have proven to be quite effective and are being refined into sophistication to literally work to knock these networks of bots offline, in a DOT MMORPG approach.
It is unthinkable that LLM bots steal our Open Source resources servers bandwidth and financial cashflow without serious repercussions!
WTF are LLM companies thinking? Even Meta has waged war against us!
LLM has waged a brutal war.
The Open Source Community is responding; even those at The Dark Side of the internet are making tools to assist everyone against Artificial Intelligence LLM DDoS attacks, which knock whole Open Source Networks offline, as we speak.
It doesn't matter if in the end it looks like a Terminator landscape globally on the IT scale. Open source will win. LLM will disappear...
#Gitlab already locked out users from mainland China, Macao and Hong Kong back in January, deleting accounts in February this year, BTW, in case you think they are an alternative.
2/3
From a usability perspective, the last thing to implement is a method for downloading a tarball of the repo (at a specific commit, tag, or branch). That would enable us to integrate support for distset downloading in the #HardenedBSD ports tree (similar to how #GitLab and #GitHub distset support is implemented).
Mikel Larreategi @erralin of https://codesyntax.com shows how to Deploy Cookieplone Based Projects With GitLab CI/CD #plone #plone6 #wpd2025 #CMS #Python #React #volto #opensource #community #DevOps #GitLab #CICD https://youtu.be/7d1KQSXpodY
Finally merged my #Tekton experiment.
Added 34000 lines of YAML to drop 62. Not the best ratio 
But let's see where things go from here. I'm quite confident that I'll be able to replace gitlab-runners in the next few weeks and find a good pattern for the pipelines.
But I think I'll take a day off working on these. It's so crazy abstract, but that's also the potential tekton holds.
I have to reference #gitlab merge request and issue numbers a lot while doing dev stuff for #postmarketOS and #alpinelinux (like for giving to our mrtest tool), so I made a simple bookmarklet that will copy this number to my clipboard:
https://gitlab.postmarketos.org/-/snippets/10
Bookmarklets are neat!
Tried to login to #Gitlab today. The OTP code they sent to my email (which landed in Spam) didn't work and further login attempts, the code never arrived and now my account is locked, even if logging in through GitHub, etc, and the login page for their Zendesk also doesn't load for me to submit a ticket, so that's fun. I'm remembering again why I opted for deploying #Forgejo over it.
Und ein weiterer Vorfall reiht sich in die lange Reihe von #Databreaches ein - dieses Mal wohl beim Mietwagenanbieter #Europcar und erneut über #Gitlab. Sollte sich der Verdacht bewahrheiten, ist nicht nur der Autovermieter von einem massiven #Cybervorfall betroffen, sondern ebenso dessen Kunden:
"Europcar hat den Angaben nach bereits bestätigt, dass tatsächlich Daten des Unternehmens abgeflossen sind."
https://www.golem.de/news/datenleck-kundendaten-und-quellcode-von-europcar-abgeflossen-2504-195077.html #cybersecurity
Over the coming months I will move all my personal and private repositories from #GitHub and #GitLab to #Codeberg. I run many static sites and intend to use https://ci.codeberg.org to trigger the builds.
Once this process is finished and everything works fine with #forgejo. I will also migrate the repos of my company #MintSystem to https://www.codey.ch/. As there are some GitHub integrations I can't get rid of, I intend to mirror back the repos.
I'll keep you updated via #CodebergMigration.
Cool. 20th anniversary of #git and #GitLab celebrated with an interview with Linus Torvalds: https://about.gitlab.com/blog/2025/04/07/celebrating-gits-20th-anniversary-with-creator-linus-torvalds/
Many universities and research institutes have their own #Gitlab or #Gitea instances, which is a good thing. But are there any plans for these instances to be federated ? It's a bit cumbersome to open a new account on a new instance every time I want to collaborate on a project. #openscience
@bd808 My personal struggle with #GitLab is that it's not even possible to *know* what the commit message would be, because that's decided by the merge/squash commit template (which you can't see unless you're a maintainer) *and* by whether the person who presses the final button decides to check the squash/edit commit checkboxes.
Anyone else having issues with #PyCharm randomly "forgetting" / bricking #logins on #UbuntuLTS Desktop?
The only workaround is to literally delete the configs and manually reenter the credentials, only for those to get fucked up with an update or at random.
Quería sugerir una nueva aplicación para que la pusieran en la tienda de software llamada @fdroidorg
Resulta que utilizan #GitLab lo que en mi opinión es mejor el usar #github lo que pertenece a #Microsoft como sabrán.
Cosa que no me gustó para nada:
Hay que no solamente dar un número telefónico y correo electrónico, sino también metódos de pago y allí ya no quería ninguna cuenta en Gitlab.
Lástima.
Do I have any #golang developers in my followers that are located in Canada and looking for contracts ?
No need to be a senior. Looking to give a chance to local talent.
Must have an #OpenSource philosophy, know #Linux well, #Git, #Gitlab
Reply or DM me.
How does everyone organise all their projects on #GitHub within their teams, like projects into groups or topics? naming schemes or have you switched to #GitLab for this feature?
#research #genomics #bioinformatics
