@eyedeekay
&zzz
+R4SAS
+RN_
+StormyCloud
+T3s|4
+cumlord
+dr|z3d
+hagen
+orignal
+postman
+qend-irc2p
+snex
Arch
BubbRubb
Daddy
Danny
DeltaOreo
FreefallHeavens
Guest99
Irc2PGuest1910
Irc2PGuest20240
Irc2PGuest21940
Irc2PGuest41816
Irc2PGuest59088
Irc2PGuest74254
Irc2PGuest78101
Onn4l7h
Onn4|7h
Over
Sisyphus_
Sleepy
SlippyJoe_
Stormycloud_
Teeed
aargh2
ac9f_
acetone_
anontor
b3t4f4c3___
dr4wd3
duanin2
duck
eyedeekay_bnc
leopold
makoto
mareki2p_
n1_
nilbog
noidea
not_bob_afk2
onon_
poriori_
profetikla
r00tobo
rapidash
solidx66_
thetia
u5657
uop23ip
vivid_reader56
w8rabbit
wodencafe2
x74a6
zelgomer
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