[00:54] you dawg i heard you like browsers, so i put a browser in your browser... actually firefox has a 'remote' mode that kind of works like that right? [00:55] i miss the old vimprobable. if only someone had the time and the inclination to rewrite it against newer webkit or another kit [00:56] hundreds of tabs. that seems like the wrong behavior to reinforce but what do i know, i'm not one of the cool kids. [00:56] there's qutebrowser, kinda similar, and it even seems to be developed https://launchpad.net/ubuntu/+source/qutebrowser [00:57] but of course there's basically no security support for the boutique browsers [01:03] * hallyn wonders if he coudl pay someone... [01:04] qutebrowser soudns familiar, i must have tried it, i wonder why i didn't pick it up as my main replacement [01:12] hm, looks nice. (just trial-installed it) but like you say, can i trust it... [01:12] i've actually gotten very used to using w3m for a lot of my browsing [02:04] well, most of the need for security is in the SSL library & the browser engine, I guess, which are maintained well enough probably? [02:05] as essentially all these alternative browsers use Qt Webkit or Gtk Webkit or Blink? [02:06] https://launchpad.net/ubuntu/+source/qtwebengine-opensource-src focal, no updates since 2020-07-16 [02:06] bionic never got any updates [02:08] the Qt people don't do security updates or nobody works on keeping Qt up-to-date in Ubuntu? [02:11] it seems like Qt webkit is getting updates? [02:14] so we just need to bribe a new debian maintainer? [02:14] (I seem to remember webengine is being removed from some distros also?) [02:15] there is a qutebrowser-version that uses webkit [02:15] instead of webengine [02:16] I think webengine is blink? [02:18] sounds right - https://www.reddit.com/r/Nyxt/comments/rl6kiw/whats_the_deal_with_blink_qt_webengine/ [02:23] if you want a barebones browser there is also luakit & such [02:24] which is based on webkit gtk [02:26] and that is getting security fixes, it seems [02:26] heh, lua . maybe i should try it. [02:26] promising [02:28] I wonder why the link hints use numbers rather than letters, that's an odd choice :( [02:28] i've seen that... [02:29] (there might be unfixed bugs in luakit itself, of course, but e.g. webkit-gtk & libsoup should get security updates) [02:29] actually the vimium ff plugin right now does letters, but unrelated to the letters in the link. [02:30] though i'm finding the link hint numbers hard to read... [02:31] webkit2gtk is certainly a happier story https://launchpad.net/ubuntu/+source/webkit2gtk [02:31] whether or not the webkit folks can put in the effort in finding and fixing bugs that eg firefox or google can is another question.. and how much of that work makes it to the webkit2gtk upstream is another question [02:32] webkit is still apple? [02:33] you have the advantage that it's more obscure so less likely to be a target too though :) [02:33] apple is basically a blackbox. I'd be shocked if any of their work makes it out [02:33] webkit is Apple & Gnome & Qt & others maybe? [02:34] alright, time to take off, have a good night :) [02:34] \o [02:36] upstream WebKit is active enough... https://github.com/WebKit/WebKit [02:40] and the Gtk version is part of upstream, so essentially the browser engine gets all the same fixes as on Mac [02:42] and PlayStation... https://github.com/WebKit/WebKit/blob/main/Source/WebCore/PlatformPlayStation.cmake :) === TheMaster is now known as Unit193 [02:46] sarnold: so in this case Apple work in the open, it seems :) [02:47] I see apple.com, igalia.com & webkit.org email addresses mostly in the recent changelogs [02:48] oh, and some sony.com guy === tomreyn_ is now known as tomreyn [12:17] the problem with webkit is that dependencies, including compilers, get bumped once in a while preventing updates from working on older releases. We can't currently build webkit on bionic because of that. [12:18] so we get a couple of years, then it breaks === hank_ is now known as hank [18:26] mdeslaur: don't the LTS releases get newer compilers versions? (I know it happens with rust compilers at least...) [18:26] yes, but that doesn't mean it's trivial to get a new libstd to go with them [18:27] firefox has a whole shim thing to be able to build with a newer compiler but use the old libstd [18:27] AFAIK webkit doesn't [18:37] plus, there are other dependencies that get bumped too, like ICU for example...and it's difficult to bump library versions on a distro level since everything breaks ABI all the time [18:38] well, you can install versions in parallel, but that might require changes to build systems too, etc. [18:39] might as well use nixos at that point [18:39] or snaps :) [18:40] then since webkit is a library that gets used by other things, those other things need to be linked with the new versions too... [18:40] basically, this turns into a can of worms pretty fast [18:40] nah, snaps would result in 10 different versions being reused in 10 packages each, resulting in 100 copies :P [18:41] hahaha [18:41] yeah but then it's Someone Else's Problem(tm) [18:41] ;) [18:44] 18:39 < sarnold> or snaps :) [18:44] lol [18:44] :D [19:08] hey, thanks to rust, you can have all those multiple copies/versions of libraries embedded in one binary application! [19:08] (I examined all the vendered/cargoed deps in a recent rustc build in jammy and of the ~450 built in dependencies, about 25 of them had two different versions included.) [19:12] ugh [19:13] good luck doing a security audit on that... [19:15] but you don't need to because rust is immune to bugs /s [19:16] \o/ === vlm_ is now known as vlm