@eyedeekay
&eche|on
&kytv
&zzz
+R4SAS
+RN
+StormyCloud
+T3s|4
+acetone
+dr|z3d
+hagen
+hk
+lbt
+postman
+weko
+wodencafe
An0nm0n
Arch
Danny
DeltaOreo
Extractor
FreefallHeavens
Irc2PGuest17611
Irc2PGuest1833
Irc2PGuest30976
Irc2PGuest31002
Irc2PGuest42299
Irc2PGuest59134
Irc2PGuest64356
Nausicaa
Onn4l7h
Onn4|7h
Sisyphus
Sleepy
Soni
T3s|4_
Teeed
aeiou
ardu
b3t4f4c3
boonst
cumlord
dickless
dr4wd3_
eyedeekay_bnc
not_bob_afk
onon_1
orignal_
poriori
profetikla
qend-irc2p
r3med1tz-
radakayot_
rapidash
shiver_sc
solidx66_
thetia
u5657
uop23ip
w8rabbit
x74a6
yoppie
eyedeekay
R4SAS that page isn't exposing the details to me, what am I missing?
R4SAS
eyedeekay: about.gitlab.com/releases/2023/05/23/critical-security-release-gitlab-16-0-1-released
eyedeekay
Ah right
R4SAS
afaik you using gitlab
eyedeekay
Yeah we're patched already here but TBH I've about had it with gitlab
eyedeekay
It's all well and good for a github competitor and I don't have time to migrate off of it right now
eyedeekay
But it's exhausting to administer
eyedeekay
And I'm looking to move to something without JS on it's web interface
R4SAS
i know. that's why I just switched to gitea
eyedeekay
Yeah gitea is the obvious post-gitlab choice
eyedeekay
Much easier
R4SAS
gitlab chew too much resources
dr|z3d
gitlab is a beast. and not in a good way.
dr|z3d
just running idle it'll happily chew through a lot of cpu.
R4SAS
+
eyedeekay
Yeah that's bad too, but my main reason for wanting to get away from it is administrative headaches