@kkarhan@infosec.spaceAnyone 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.
Skrevet af @benjamin
I får lige en forsmag på det den hjemmeside vi arbejder på, samt lidt om hvordan vi arbejder.
Noget af det første vi skulle finde ud af var hvordan vi arbejder sammen på projektet. Vi er alle tilhængere af #OpenSource og #SelfHosting, men vi vil nødigt afhænge af enkeltpersoner og deres hjemmeservere. Bl.a. derfor har vi lavet et projekt i #gitlab som anvender gitlabs CI til at bygge hjemmesiden med en statisk side generator, samt deploye den til gitlab pages. (Til de interesserede så har vi taget udgangspunkt i https://www.getzola.org/documentation/deployment/gitlab-pages/#setting-up-the-gitlab-runner). Det giver gode muligheder for samarbejde samt en klar ændringshistorik at have det hele i git.
Vi har grønne pipelines 
så nu taster vi løs for at levere noget tekst + fede logoer så vi kan få defineret konceptet Folkeføderation så tydeligt som muligt. Sig til hvis i vil være med, så bliver i inviteret ind i gitlab-klubben.
#GitLab users: how to connect "issue Foo" as child of "issue Bar"?
and.. what does this message ever mean? 
If you are running away from #GitLab after last recenties, consider forking Phorge in your organization 
we have a very good bug tracker, and we support #git + #svn + #mercurial.
If you need support, you already have! contact your random local web developer.
https://we.phorge.it/book/phorge/article/installation_guide/
@ZiggyTheHamster@ruby.socialThis is super disappointing because I know a few of you who work there and don’t share this trash opinion, and also #GitLab has in the past gone out of their way to be ethical.
https://woof.group/@aphyr/114134266721872222
@arve If you're doing open source development, the European alternative Codeberg has automated import/migration from GitLab (and from GitHub, too). Not just code but also issues, wiki, etc. Just sayin'. Hint, hint. 
@markwyner@mas.toGitLab CFO, Brian Robins, says they are “aligned with the goals of DOGE, because the company’s software tools aim to help people do more with less. What the Department of Government Efficiency is trying to do is what GitLab does.”
You either support fascism or you don’t. It’s binary. There’s no gray area or “aligning.”
Considering GitLab? Don’t. Use @Codeberg.
(Hat tip @aphyr)
If you’re currently using #gitlab this is your time to leave for literally any other service as they have chosen to align with the current US regime.
Via https://www.washingtonpost.com/business/2025/03/09/doge-companies-warnings-sec-filings/
@pierrenick@hachyderm.ioWell at least #GitLab lets you delete your account with no fuss. Good CI though, shame.
Hey peeps, if you're still using #GitLab and #GitHub and you're twitching a bit because they're fellating fascists, I want to point to the sign that says you can self-host @forgejo - a project which is also working on decentralisation and federation.
Failing that, @Codeberg also exists, are a European non-profit that also supports the development of Forgejo.
Hope that helps 
For everyone belatedly realizing that GitHub and GitLab are Problematic: there are alternatives!
Update: now a blog post which I will update instead! https://nevillepark.ca/2025/03/13/branching-out-some-github-gitlab-com-alternatives/
Gitea is 1) commercial and 2) based in the US, which I know many people are looking to avoid.
@Codeberg (https://codeberg.org) is a public server running Forgejo, which began as a Gitea fork: https://forgejo.org/compare-to-gitea/ It's where I have most of my stuff.
A few more public Forgejo servers: https://codeberg.org/forgejo-contrib/delightful-forgejo#public-instances Shout-out to @besties' https://git.gay.
There's also the venerable Sourcehut, whose UI makes me break into hives: https://sourcehut.org/
Want to self-host? @yunohost is dead easy to set up and has Gogs, Gitea, Forgejo, and GitLab apps: https://apps.yunohost.org/catalog?search=git&category=dev
OK with Gitea/GitLab servers outside the US? @Framasoft has a public GitLab server: https://framagit.org So do @autonomic: https://git.autonomic.zone and https://git.coopcloud.tech, plus they'll do paid hosting (price scales with budget).
For cheap independent hosting, PikaPods has Gitea: https://www.pikapods.com/
There are SO many options if you are willing to give up the "everyone on the planet uses the same public Git server" model.
If you run a #Drone CI server, set DRONE_REGISTRATION_CLOSED=true (and manually create users only when you really really trust someone).
The CPU on my CI/CD server suddenly spiked to 100% today.
A closer look found some users who had registered on git.platypush.tech and on the CI/CD server and created a repo with a .drone.yml, a .gitlab-ci.yml and some scripts with base64-encoded commands.
The repo also contains a deepCC.ipynb Jupyter notebook that downloads some training data from S3 and uses Tensorflow to train a model, and then uses the deepCC binary to do something with that model.
The repository also has a configure script with base64-encoded commands that seem to configure a miner (the wallet ID is R9WpFbvkb6dep6bfLdbpcyz3LpMeikUL6W and the coin is VRSC, if anyone is interested in investigating further).
The deepCC binary is itself quite big (~50 MB), and a look at the setup script reveals that it’s actually a .tar.gz archive with a larger binary inside.
A quick run of strings on the binary confirms that it’s actually a miner - it connects to eu1-etc.ethermine.org and it also has a bunch of CUDA bindings to run on GPUs.
I still don’t get what’s the point of the Jupyter notebook that trains a model and passes it to this miner, but if you feared the day of the arrival of the zombie Docker containers that exhaust system resources by mining cryptocrap AND training AI models, well, I’m afraid to inform you that that day has come.
If you are a #Gitea / #Forgejo admin, take a look at the users and repos created in the past couple of weeks. Check in particular if any recently registered users have created a repo named deepcc-v.
The most likely authors are users named farzanfarid16 and zurizoey0.
A quick search confirms that both these users are registered on #Gitea too and have already created the incriminated repo:
And if you are a Drone CI or #Gitlab admin, check if any of these users have also started CI/CD pipelines connected to that repo.
For now, disabling the execution of CI/CD pipelines unless a user has been explicitly authorized is the best idea that comes to my mind.
@jak2k@mastodontech.de@GeopJr I though it's a shitpost, but no: Gnome's GitLab is protected by an anime girl! 
Achievement unlocked: loaded a GNOME #GitLab link that was pasted in a chatroom and triggered @cadey's "Anubis" anti-LLM-scraper protection catgirl with my genuine Firefox browser, and had to watch my CPU burn for a minute 
I regret to inform you that we have now entered the DEFCON 1 stage of the struggle against the LLMs "AI" #enshittification bubble 
What I don't quite understand is why the GitLab instance would put up this challenge to already logged-in users 
@jwildeboer@social.wildeboer.netAnd after going through the replies and comments, let me give you an alternative opening statement:
#codeberg or your own #forgejo instance are #GoodEnough to be used instead of #Github and #Gitlab for 95% of your new FOSS projects, IMHO.
(refocused on new projects) 6/6
@jwildeboer I am also running #forgejo since several years and it's great. Super robust and resource-efficient, packed with features incl. LDAP support, ... the list goes on.
What I particularly like (as an admin) is that the update to a new version involves replacing a single binary. That's it.
I used #gitlab before and that, in comparison, was a PITA. Bloated, memory-hungry, slow. Particularly updates were painful and broke the system multiple times because migrations failed.
@jwildeboer Yes, it takes some resources. Again, functionality is a key for me, not minimal resources being used.
And it runs pretty nicely on RPi anyway...
(Projects like Forgejo will probably get there, too, one day... maybe... I decided to stick with #GitLab until then...)
