@BrodieOnLinux @yisraeldov yeah.
The fact that @tails does "appointment-only" access to their #SepfHosted #Gitlab prevents me from actually helping and improving #Tails.
Tho Gitlab is propably designed on purpose for that and was never meant to be used as #public solution...
#public #tails #GitLab #sepfhosted
🌴 At #GitLab we love swag, but to improve sustainability, we are also now offering to plant trees in the names of our wider community contributors.
We have started by planting a tree for each of our Core team members. Fancy helping us grow our forest? https://tree-nation.com/profile/gitlab
Everyone Can Contribute 🌱 https://about.gitlab.com/community/contribute/
Aprende el uso de #Laravel #Taiga #GitLab #Writer con los cursos gratuitos del mes de septiembre que trae para ti el Centro Nacional de Tecnologías de Información.
Ingresa al formulario y realiza tu inscripción antes del jueves 31 de agosto.
https://sigmaformulario.cnti.gob.ve
¡Participa!
#writer #GitLab #Taiga #laravel
It's super cool to hear that #gitlab is joining the #fediverse soon. It's making me really think about stuff.
Like, I understood that #activitypub was a connectivity substrate for apps. But, I was still thinking of it as a social layer - really, though, as Gitlab is demonstrating, it's an Interop layer.
It's not really "like email", it _is_ email, but in a JSON transport, and for distributing app functionality.
Microposts / social networking are just the easiest demo use case.
#GitLab #fediverse #activitypub
Made my first very small contribution to #GitLab today.
It was great.
#EveryoneCanContribute really.
#GitLab #EveryoneCanContribute
Thank you Dannyel Fonseca for sharing your #gitlab contribution experience 🦊
Everyone can contribute 🙌
Contribution is everywhere ✨
Hackathon 👾
Boost your CV 🚀
Final thoughts 💭
LABRAT exploiting a #GitLab flaw for #cryptojacking & proxyjacking, using cross-platform #malware, kernel-based rootkits, and legit service abuse.
https://thehackernews.com/2023/08/new-labrat-campaign-exploits-gitlab.html
#informationsecurity #CyberSecurity #Malware #cryptojacking #GitLab
@epsi +9001%
#Discord also has unacceptable #ToS and is purposefully designed with neither #searchability, #indexability or #accessibility in mind.
Replacing #IssueTracker, #Support and/or (effectively non-existing) #Documentation with a shitty Discord instance is just blatant assholeism and everyone who does even consider doing so in lieu of #GitHub, #GitLab or god forbid even #Savannah and #SpurceForce should be banned from #FLOSS #Project and #CommunityManagment!
#CommunityManagment #Project #FLOSS #spurceforce #savannah #GitLab #GitHub #Documentation #support #IssueTracker #Accessibility #indexability #searchability #tos #Discord
Mind you whilst I know how to manually install the #TorExpertBundle into @ubuntu 22.04 LTS doesn't mean that's a practical option and not something one could discreetly teach someone over a wiretapped phone behind the #IronFirewall of #Putin.
I really would love to improve #Tails even if it's just writing documentation and testing stuff, but sadly they've not replied to my request for an account for their #Gitlab:
#GitLab #tails #Putin #ironfirewall #torexpertbundle
A few major gripes I have with @tails is how not only that their #GitLab is approval-only, preventing me from submitting issues, but that their [documentation is incomplete at best](https://tails.net/doc/persistent_storage/configure/index.en.html#bridge) [some functionality is crippled intentionally](https://tails.net/doc/anonymous_internet/tor/index.en.html#hiding) and some weird decisions [result in Catch 22 scenarios](https://tails.net/contribute/design/Time_syncing/)...
Which is sad because I do want #Tails to be good if not better than what I've to currently deploy instead of it.
How to sign images and artifacts on GitLab CI
https://docs.gitlab.com/ee/ci/yaml/signing_examples.html
#sigstore #gitlabci #gitlab #cosign #securesoftwaresupplychain
#sigstore #gitlabci #GitLab #Cosign #securesoftwaresupplychain
Was muss ich denn in die .ssh/config schreiben, damit #gitlab damit klarkommt? Laut deren Anleitung:
# User1 Account Identity
Host <user_1.gitlab.com>
Hostname gitlab.com
PreferredAuthentications publickey
IdentityFile ~/.ssh/<example_ssh_key1>
Das hab ich erfolglos versucht, sogar mit und ohne <>.
Und natürlich klappt die #ssh-Verbindung von meinem Rechner zu #gitlab nicht.
Ich vermute, es liegt an der config-Datei. Für Github hab ich inzwischen rausgefunden, wie ich meine SSH-Keys da eintragen muss, aber für Gitlab klappt das weder mit dem Beispiel auf deren Anleitung noch mit davon abweichenden Anleitungen, die ich übers Netz verteilt gefunden hab.
Worse are only those folks that literally abuse #Discord as #IssueTracker and #Support system for #FLOSS in lieu of #Issues of #Github / #GitLab and an actual #documentation!
#Documentation #GitLab #GitHub #issues #FLOSS #support #IssueTracker #Discord