@eyedeekay
+R4SAS
+RN_
+T3s|4
+dr|z3d
+hk
+orignal
+postman
+qend-irc2p
+snex
+wodencafe
Arch
BubbRubb
Danny
DeltaOreo
FreefallHeavens_
HowardPlayzOfAdmin
Irc2PGuest21522
Irc2PGuest21557
Irc2PGuest51104
Irc2PGuest54655
Over1
SigSegv
Sisyphus
Sleepy
T3s|4_
Teeed
aargh
acetone_
ardu
b3t4f4c3___
bak83_
death
dr4wd3_
duanin2
duck
eyedeekay_bnc
hagen_
nilbog-
not_bob_afk
ohThuku1
poriori_
pory
profetikla
r00tobo
rapidash
shiver_
solidx66
thetia
u5657
uop23ip
w8rabbit
wew
x74a6
zzz
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