@eyedeekay
&zzz
+R4SAS
+RN
+RN_
+StormyCloud
+T3s|4
+dr|z3d
+eche|off
+hagen
+hk
+mareki2p
+orignal
+postman
+qend-irc2p
+snex
+wodencafe
AnOtterMoose
Arch
BubbRubb
C341
Chrono
Danny
DeltaOreo
FreeB
FreefallHeavens
HowardPlayzOfAdmin
Irc2PGuest43584
Irc2PGuest70310
Irc2PGuest82088
Irc2PGuest88009
Onn4l7h
Onn4|7h
Over
Sleepy
SlippyJoe_
T3s|4_
Teeed
aargh
acetone_
aisle
ardu
b3t4f4c3___
b4dab00m
carried6590
cumlord
death
dr4wd3
duanin2
eyedeekay_bnc
nilbog
nnm--
not_bob_afk
ohThuku1
poriori
pory
profetikla
r00tobo
rapidash
shake_
shiver_
solidx66
thetia
uop23ip
w8rabbit
weko_
wew-
x74a6
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