Is it just me, or has Microsoft gone completely crazy? They are implementing spyware that takes screenshots every second and forcing AI integration. Why would anyone willingly purchase this? Anyone with experience in computer or information security knows that it is a bad idea, even if it is locally done. Just don't do it. Yet, here we are, and they are doubling down on this idea. https://arstechnica.com/gadgets/2024/05/microsofts-new-recall-feature-will-record-everything-you-do-on-your-pc/#privacy#security
There MUST be an easy way to automatically #label merge requests in #Gitlab without having to make a webhook server or something surely in the current year.
#Gitlab still doesn't support issue templates in #yaml, the way #Github and #Forgejo can. Only #Markdown, which is a lot less attractive. But #Github and #Gitlab can do label changes in the Kanban (project) view, which #Forgejo can't.
Kennt ihr #Git? Auch wenn ihr kein(e) Programmierer:in seid, dann seid ihr bestimmt schonmal auf #GitHub, #GitLab o.Ä. gestoßen. Auch als Designer:in, Maker:in, Texter:in oder einfach nur zum Projektmanagement spielen Git und die dazugehörigen Plattformen heute eine große Rolle. Wir erklären Git/GitHub/GitLab für Nicht-Programmierer in einem dreistündigen Workshop am Sonntag, den 19. Mai. https://www.welcome-werkstatt.de/veranstaltungen/git-fuer-nicht-programmierer
With #GitLab 17.0 (stated to be released on May 16th), the operating system theme preference is now respected, as there is now an opt-in setting to enable "Auto (Experiment)" support in your user preferences panel.
It can finally switch between light & #darkmode when your OS or desktop environment requests it at various times of the day! I tried it; it works.
You can find it under "User Settings > Preferences > Appearance" when running that GitLab version (it is already the case on gitlab.com)
Join Sharkey dot Org has been OFFLINE for over 2 months. The reason given was hosting issues, and this was before the whole Hetzner drama. Join Sharkey dot Org is supposed to be the gateway for people to learn about Sharkey and how they can join.
The Documentation Page (Wiki) is still up, using the subdomain, Doc dot Join Sharkey dot Org, but the URLs are broken. I have repeatedly reported the broken URLs for over 2 months (both in the Git and on their Discord Server). No one seems to want to address that.
They have a private copy of GitLab located at ActivityPub dot Software, that you cannot find via a search looking for Sharkey (DuckDuckGo, Bing, Google). That is where you can report code changes and fixes, but you would likely not know that unless you stumbled upon the URL somewhere (or someone gave you that URL).
Sharkey raised a lot of money so they can host their own content, safely, and securely. They now own their own physical server and lease the space to have that server housed (hosted) remotely. And while the lead developer promotes that server partially as a minecraft server, Join Sharkey dot Org still remains, OFFLINE.
I have pulled funding from Sharkey and will not be supporting it further until they get their act together. It is a good software, and it is my preferred method to use the Fediverse, but you would assume they would want their website working.
@Framasoft "Your account [Framagit] has been deactivated" "Les comptes sont désactivés après un an sans activité" C'est du grand n'importe quoi, j'utilise régulièrement #Framagit.
As GitLab 17.0 is coming next week, it looks like my very polite reminder nudge might have encouraged the #GitLab maintainers to request reviews from specific people for the automatic ("system") light/dark theme mode implementation, hopefully this lands in time for 17.0 🤞 so that we don't have to wait another full year to enjoy this #accessibility and #UX improvement, even if somehow considered experimental: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/150254#note_1895251010
Die machen Werbung über sich, dass ihre KI toll einsetzbar sei und dann das, eine übliche Schwäche von Profi-Dienste. Nicht im Detail, sondern was es betrifft.
»Account-Übernahme möglich – Kritische Gitlab-Schwachstelle wird aktiv ausgenutzt:
Die Schwachstelle ermöglicht es Angreifern, beliebige Nutzerpasswörter über eine eigene E-Mail-Adresse zurückzusetzen. Tausende von Gitlab-Instanzen sind gefährdet.«
No matter if you host your own copy of GitLab Software or use GitLab's servers directly, you should enable 2-step Verification - NOW (right now, do not wait). There is a current exploit that allows someone to hijack GitLab Accounts, who are not using 2-step verification.
debugging tests that fail only in #gitlab#ci is the worst... #sourcehut absolutely has it right by allowing you to SSH into a runner that failed a job.
Hey #journalists if you're going to use an open source project as an example of a hack, can you at least let them know in advance you're about to do something reckless so they can prepare?