[12:12] <tomreyn> On https://ubuntustudio.org/ "Release Notes" points to https://wiki.ubuntu.com/FocalFossa/ReleaseNotes/UbuntuStudio , which are for Focal Fossa, so 20.04
[12:15] <tomreyn> It should probably point to https://ubuntustudio.org/ubuntu-studio-22-04-lts-release-notes/ (also because there is not https://wiki.ubuntu.com/JammyJellyfish/ReleaseNotes/UbuntuStudio )
[15:28] <Eickmeyer> tomreyn: Yeah, I updated that after it was poitned out on Twitter.
[15:30] <Eickmeyer> BrianHechinger[m: Did you test the studio-controls in -proposed?
[16:07] <BrianHechinger[m> Not yet, i just got it rebooted and set back to ALSA then i had to run out for a bit. Will check soon.
[16:10] <Eickmeyer> BrianHechinger[m: Cool. Just remember to enable proposed, install studio-controls from the command line, and disable proposed. You don't want that to remain enabled, stuff has a bad habit of breaking when that happens. :)
[16:10] <BrianHechinger[m> I don't need that, no, so thanks for the tip. :)
[16:11] <Eickmeyer> Yeah, wholesale upgrades with -propsed enabled = bad.
[21:10] <tomreyn> And you might want to set some additional HTTP headers (if that's something you can do - sorry if i asked before): https://securityheaders.com/?q=https%3A%2F%2Fubuntustudio.org%2F&hide=on&followRedirects=on
[21:10] <tomreyn> Content-Security-Policy can require some testing, the others should be painless.
[23:15] <Eickmeyer> tomreyn: We have no such access, that's 100% on Canonical IS.
[23:17] <Eickmeyer> tomreyn: It's also Wordpress, so I'm pretty sure they don't even have that kind of level.