12:59:31 frg_Away: I'm having problem registering my Bugzilla account (problem is on my side and will be fixed soon), so just let me ask a question from yesterday again: 12:59:51 Is it intended that 2.53.11 Beta 1 is still listed with an own section on https://www.seamonkey-project.org/releases/? 13:00:13 I guess not because it's already listed in "Old and Unofficial Releases". 13:05:11 It would be a nice idea for SeaMonkey to join one of those "bug bounty" places to attract more developers 13:05:22 if anything because kids these days won't code if they're not paid handsomely 13:05:41 …which is somewhat reasonable, to be quite honest. 13:05:52 Is there are good bug bounty place? 13:06:06 msiism Was so since the ice age. Makes it a bit easier to maintain the site/release notes. For the next beta just need to update version numbers. Otherwise would need more adjustments. Personally I would drop the betas and just delay turning on automatic updates for a week or so. Rather do a point release to address issues. 13:06:35 I see. 13:06:49 oh, forgot that bug bounties require donations :/ 13:07:02 :) 13:07:08 and webkids these days only care about shiny webtech aka Chromeisms 13:07:35 Wonder why places like Hackernews and Slashdot NEVER talk about SeaMonkey 13:07:40 It's not only the kids, unfortunately. 13:07:51 even Pale Moon and Wateforx get mentions every few years 13:08:06 Bad marketing. :-P 13:08:14 but The Latest Chrome Fork Of The Week gets 200+ comments 13:08:31 I did link SeaMonkey on my website, yesterady, to help fix this. ;) 13:09:02 It would also need at least some sort of coordination. Not enough people around to do this. 13:09:27 it would need kinda of a Hail Mary play 13:10:11 I guess a thorough review on some site that interested folks read would do a lot. 13:10:29 It doesn't need to be an uncritical review. It shouldn't, actually. 13:11:49 I used to read Slashdot - SeaMonkey would have been a nice fit for the old userbase there 13:12:11 notice the emphasis on "old", as this place has become largely a cesspool of trolls (this is why I left two years ago) 13:12:38 HackerNews won't even take a look because "it's ooooold, unsafe, and without a path to monetization, plus it's not Chrome" 13:12:42 https://www.kuketz-blog.de/ would be a good place for such a review. But someone would have to try to persuade the author to do it. 13:12:54 It would also only cover a German audience. 13:13:00 But that's better than nothing. 13:14:27 Well we are probably still the most up to date and maintained fork. I can live with being under the radar. With all the breakage becuase of msssing support of later features it is pretty hard to attract new users. And if we are late again like with 2.53.11 might get blasted left and right because of open sec issues. SeaMonkey is a niche product and will likely stay this way. My personal view... 13:14:28 ...is that opensource is dead. 1000 people complaining and wanting something and 1 doing the work. You see this with almost any project these days. 13:14:50 sadly that's true 13:15:07 once again, Hacker News using "what's your plan for monetization" on pretty much every new FOSS thread 13:15:14 as the very first comment 13:15:33 that's the mindset nowadays, turn your Hello World into the next unicorn 13:15:55 frg_Away: Yeah, that is a real problem. I guess that also has to do with massively increased diversity and complexity in building software, though. 13:16:43 I mean, I guess, 20 years ago, you usually didn't check out 25 programming languages and then decided for a 26th… :) 13:16:51 https://digdeeper.neocities.org/ghost/browsers.html I'm surprised this paranoid nutter names pretty much every Firefox fork under the sun EXCEPT for SeaMonkey 13:17:25 (plus a bunch of Chrome forks too) 13:17:32 that's sad 13:17:59 https://unixsheikh.com/ might also have half an interest in looking at SeaMonkey. 13:18:09 That said, I could also write a review myself. 13:18:21 But not this month. 13:19:46 SeaMonkey is sometimes mentioned in comment threads of El Reg articles 13:20:15 Good stuff. :) 13:21:56 * msiism needs to go to work. 13:22:36 ah, El Reg, the last serious meeting room for graybeard sysadmins 13:23:58 the day they implement Chromeisms too, the world is over 13:24:47 wouldn't that be alt.sysadmin.recovery? :-P 13:25:27 newsgroups?! 13:25:32 But that's, like, for dinosaurs! 13:26:20 wonder how sysadmins will be in 10 years from now on 13:27:18 fit, diverse, and without beards (unless they're from a minority, of course), and well versed in Kubernetes, Node.js, several Big Cloud APIs.. and no basic knowledge about how to plug an HDD or how to make a directory from CLI 13:29:16 Well the good thing about SeaMonkey development is that the people still on board care about it much and we are not a 1 man army trying to conquer the world. So the end is NOT near :) 13:33:46 if we aren't vaporized first by you-know-who, yeah :) 13:38:28 tomman it would be sad day but fortunately I have enough other things on the platter which I even neglect a bit too much now because of SeaMonkey. 13:41:04 Given the state of the web I wouldn't miss much and just do some online shopping. I still remember browsing for hours when there was still content on major websites. Now Intel and the olter ilk just talk about how good they are for the planet and humanity and new product news or information is a few advertising words between huge white blocks and / or pictures. 13:41:24 in 48pt font size of course. 13:42:37 don't forget Apple! 13:42:49 we're in Apple Hype Cycle this very week 13:44:13 (if you believe that a souped-up cellphone GPU can wipe the floor with a RTX3090, I have a couple bridges for sale) 13:46:01 tomman if you find a buyer I might be able to arrange a follow-up deal for some swap land which will soon be worth millions too. 13:46:22 That said the M1 mini is not a bad system. 13:50:02 and make it swamp land 17:29:19 https://www.newegg.com/, my most used shopping site, is no longer usable in SM. At some point it will peg CPU and cause all response to stop. :( 17:32:09 GitHub no longer supports this web browser. Learn more about the browsers we support. 17:40:01 please don't say github is pointing to browsehappy too... 17:40:21 a-865: can you close newegg? does the CPU usage go away after that? 17:46:55 https://webcompat.com/issues/100804 17:47:44 trying to close the tab may or may not work, if focus can first be moved to another tab 17:57:13 "GitHub no longer supports this web browser. Learn more about the browsers we support." came from https://webcompat.com/, but it let me login and report anyway. 18:13:32 I do not support or care about github so we are even :) 18:18:04 oh GiggityHub~ 18:19:14 well, initially I see some CPU spikes on Newegg here 18:19:30 ...and after 30 seconds or so, a script hung warning 18:20:01 > [AMBER]: Error: PromoteIQ desktop SyntaxError: invalid regexp group 18:20:14 > ⚡ Hiring now @ https://www.newegg.com/d/Careers/TabIndex 18:20:39 I will NOT take any JS developer job EVER, not even for all the money (be it flat or crypto) in the planet 18:20:56 that's just an addendum to the log message, or the error actually happened for that message? :-D 18:21:08 https://cdn.quadpay.com/v1/quadpay.js:2:17480 this is the script that goes hung 18:21:20 njsg: the [AMBER] and PromoteIQ tags? 18:21:37 yes, those are logged by whatever toxic JS library they're using 18:22:21 ok here with NoScript and uBlock Very memory and script hungry. Lots of bad third party scripts lately. Have seen a few ones which them block everything. 18:23:03 > Script: https://cdn.quadpay.com/v1/quadpay.js:2 18:23:18 that's a domain that I would add to my blocklists 18:23:25 that one reliably softlocks here 18:23:40 > Report security vulnerability to us through wecaresecurity⊙nc 18:23:43 lolno 18:23:58 I love when I get job offers and crap on browser consoles... 18:24:12 I wish the Crapium borwsers would count external script sites and block anything over three. Won't happen because bad for adware. 18:25:49 quadpay.com redirects to https://zip.co/us BUT DON'T GO THERE! 18:25:53 it will eat your CPU too! 18:26:19 (I don't get script hung warnings this time, but I had a hard time killing that tab) 18:26:31 sounds like a payment provider or some crapola 18:26:47 couldn't even read their homepage: it was hung from the initial load 18:26:53 tomman: 0.0.0.0 cdn.quadpay.com in hosts works, so big big thank you!!! 18:27:25 a-865: hope it doesn't break anything serious for Newegg, but I guess they're now a rotten egg :/ 18:31:41 I get most of my computer stuff from newegg. 18:32:02 zip.co seems to loop on lin 86 of a script . Need to check if I find some more svg fixes. With such clean code in one line I wonder why... 18:32:03 https://controlc.com/edce478d 18:33:54 40K of css crap to display a simple site. Well done. Pay rise imminent. 18:34:29 ironic, considering that these guys are in the "we take your money" biz 18:37:10 Well Credge does not have a problem. Seems a simple css grid with a few buttons. Support for css grids was buggy and incomplete around 56. Working on it and a 100 other things :) 19:21:04 https://www.yankeevictor400.com/post/recordando-al-primer-a380-que-visit%C3%B3-venezuela moar React breakage crapola 19:21:32 the post contents are visible for a split second, then a couple huge backtraces are dumped on the console, and the page contents dissapear 19:21:54 maybe if you stop the page load fast enough, you'll be able to read the contents (and blurry images) 19:22:12 ...nope, that doesn't work 19:22:26 the page contents go away as soon as those two exceptions get logged 19:24:45 "Error: Controller loading error. Please check https://bo.wix.com/pages/yoshi/docs/editor-flow/issues/controller-error for more info" 19:24:56 so helpful... NOT 19:25:21 "hydrate" is a bad word to me 20:14:33 frg_Away: try again now ;) 21:01:49 https://www.redvoicemedia.com/video/2022/03/duck-duck-go-is-now-duck-duck-gone-now-manipulating-russian-disinformation-search-results/ 21:01:55 Someone shoot the Duck 21:09:55 as much as I hate Google, I've never bothered with anything else, much less with DDG 21:10:26 I can blame Yahoo! circa 2001, when it sourced results from this newfangled "Google" thing 21:13:46 https://developer.mozilla.org/en-US/docs/Web/API/Barcode_Detection_API YOU'RE DRUNK MOZILLA GO HOME 21:13:48 oh wait 21:13:52 > Chrome: partial support 21:14:09 > Chrome Android: full support 21:14:11 of course 21:14:13 GOOGLE!!! 21:14:28 who asked for a native barcode API on a frickin' web browser?! 21:17:21 https://chromestatus.com/feature/4757990523535360 even Google themselves can't get it right 21:20:59 I guess it helps when people insist on providing information in the form of QR codes, but the better solution is to get people to stop doing that. 21:23:16 QR codes belong to cellphones 21:23:26 just install a barcode reader app, people 21:23:33 oh, iPhones already come with one 21:24:10 then that's Google task to make QR barcodes a first class citizen in vanilla Android, instead of relying on 9000+ fake malware QR scanner crapps 21:24:36 * msiism doesn't even have a mobile phone. 21:25:22 nearly every Japanese dumbphone circa 2005 could already scan QR codes (which makes sense: Denso invented the tech and Japan quickly embraced it - it took ages for QR to become popular overseas) 21:26:12 the biggest obstacle here were the horrible cameras on your average cellphone (I tried back in 2009 with my RAZRs - it was an exercise in frustration most of the times) 21:44:25 tomman: yankee victor does keep the content without js, albeit with blurry images 21:46:12 tomman: to me it looked like getting a simple reader/decoder without tons and tons of permissions required might be another obstacle 21:47:07 I have the idea it wasn't uncommon for "scanners" to act automatically on the content of the qr code either. but I'd have to check again 21:48:19 and about YV400, a shame that lazyloading can't be opt-in, if that's lazyloading even 21:50:18 ... it's not lazyloading, it's plain css /me headdesks 21:50:33 wat 21:50:39 so it's... fake?! 21:51:25 "._3ii3f { position: relative; filter: blur(8px);}" 21:51:30 1) I've never figured out the point of lazyloading, and I'm the one still stuck on garbage-tier DSL 21:51:36 2) why even bother faking it?! 21:51:39 3) I've never figured out the point of lazyloading, and I'm the one still stuck on garbage-tier DSL 21:52:40 back in my ancient dinosaur times, I just was very patient while I waited for my 56K-working-at-29K winmodem to download po-- er, images! 21:53:02 1) possibly google web search ranking ("loads faster on android"?)? 21:53:34 2) I don't know, if it's that important, I'd make the image interlaced. I mean, I'm guessing the idea is to make some transition as this would probably be later undone with javascript? 21:54:58 also, if you really want that "slow loading blurry effect", you've got interleaved PNGs for that... 21:55:06 The first time I learned about lazy loading I was just like, oh wow this would have been so useful IN 1998 21:55:46 I suppose the user-agent could always postpone loading some images 21:56:23 Or simply optimize your crap, and if you need to post large, inline pictures, just use a clickable low-res thumbnail! 21:56:51 (maybe with some flags for hi-rez display users to tell the UA to simply load the full res version if you're on 4K, for example) 21:57:19 speaking of hi-rez displays 21:57:35 today I had to help $UNCLE with his online banking (reset a password) 21:57:40 I think there's also support for multiple versions in the same , but some javascript sites do instead something that requires javascript 21:57:47 this specific bank assumes I'm using a 1080p display at the very least 21:58:02 was it "srcset"? 21:58:29 and of course, scrollbars are now verboten, you NEED to buy a new display! 21:58:37 good luck doing that in this country 21:59:07 with some pages it might be easier than figuring which DOM element to focus on in order to be able to use the arrow keys 21:59:23 oh, probably unless "overflow: hidden"? 22:02:02 if you're a bank and have my money with you, but have to bring on the Developer Tools every time I need to move my money from your homebanking portal, consider that the prelude for closing my account with you and taking my money elsewhere 22:02:53 (oh, "hidden" still allows arrow keys to scroll) 22:03:17 while most banks here are (thankfully) stuck in the pre-Chrome ages (due to hardware costs here - the Pentium 4 is still popular!), a few ones are getting dangerously close to the Chromeisms zone :/ 22:04:01 and this include a couple of the government-owned ones 22:06:25 they should be investing in new ATMs and not letting more branches close due to poor wages, not in moar Javascripts! 22:55:02 o 22:55:57 Hi 23:18:23 links to actual downloads never show up on https://www.seagate.com/support/downloads/seatools/#downloads 23:21:07 links show up on an older install I've got here, did you get anything interesting in the inspector console? 23:25:14 > Seagate 23:25:16 don't 23:25:49 hmmm, I get redirected to https://www.seagate.com/la/es/support/downloads/seatools/#downloads 23:25:58 and I can see working links there 23:26:31 I get redirected as well to pt/pt 23:26:41 if I change the locale to English, it still shows working links here 23:26:45 which is awesome, assuming a language from something possibly related to the ip address 23:26:49 no errors on console 23:27:11 other than a couple warnings about deprecated JS stuff and blocked scripts 23:27:51 could be worse 23:28:25 wonder if WD's warranty checker still relies on IE bugs largely fixed decades ago (but recently emulated by Mozilla because I DON'T KNOW?) 23:30:37 "You are running a development build of Vue.Make sure to use the production build (*.prod.js) when deploying for production." 23:30:50 WD please... 23:31:37 maybe that means their site isn't production 23:31:52 my experience with their online "catalog"/"store" wasn't that positive 23:32:17 oh, they fixed it! 23:32:51 well, they redesigned the entire website and hide the warranty checker form behind a few layers of links, but it now works again on SM! 23:32:51 if I didn't want to see information or actually choose based on specific features, I'd just randomly order something with WD in the name. 23:33:24 Support->input serial->figure out your product line->Warranty Checker->input serial again->done 23:34:01 eh. that looks like it was well designed and implemented 23:34:12 maybe they should ask for a final confirmation 23:34:29 one could always make the same typing error twice in a row 23:34:29 however, there is no obvious way to go back and check another drive, other than clicking the browser's Back button a couple times 23:35:31 oh, my laptop SMR warranty expired! 23:35:38 guess it's time to make another backup~~~ 23:35:42 --SMR HDD