01:08:31 be careful browsing JWZ's website - he planted some anti-AI/LLM bot traps which includes a nasty coal burner / fork bomb traps 01:09:13 and once you hit the trap, even the main website will render that... and your SeaMonkey will spend a while burning massive coal even if you closed the tab! 01:09:32 ugh, maybe it's time to disown our god and creator :/ 01:11:08 apparently he is using a "zip bomb" variant of malformed images designed to trigger massive memory leaks and/or high CPU usage, as I'm seeing a ImgDecoder thread pegging a entire core 01:11:57 (if you get hit by this, clear your cookies for jwz.org) 16:21:42 It's pretty great that seamonkey still has new releases in 2025. 16:33:01 gobi we try 16:33:13 join the fight~ 16:34:18 what challenges do you face ? 16:34:39 gecko engine is too old ? 16:36:28 I also remember using k-meleon back in the day. 16:38:18 Mostly outdated SpiderMonkey (js) and no support for new style system yet. 17:02:39 tomman: that might actually make an amazing test case if one wants to design a way to detect that and avoid memory exhaustion or extensive CPU usage. 17:04:42 gobi: I suppose right now: code changes that make backporting some features harder, and right now a bunch of JS features some frameworks have started to take for granted are still behind such hurdles. And that new style system is relevant because some CSS features have been implemented in it, so can't be simply backported. For example, discourse's "overflow: revert" inside