03:11:50 which missing lib causes XPCOMGlueLoad error? 03:14:50 nvm, found it 03:15:09 libgtk-3-0 on buntu wasn't installed 03:16:59 only libgtk-3-common was 09:11:23 tomman: I think it's like third or something. Second at least for sure. 14:27:19 Status meeting in 37 minutes - https://wiki.mozilla.org/SeaMonkey/StatusMeetings/2024-01-07 14:27:40 ah you had a visit from the ted cruz spammer 14:28:15 I set this in mah channel * CaptainTobin has changed the topic to: Welcome to BinOC/Chat :: No response? Highlight-a-Tobin! :: We like Bob Dole, Bob Dole likes Bob Dole, but Bob Dole doesn't like spam.. BOB DOLE! :: XLINE: CaptainTobin added a permanent Z-line on [ipv6 addy] : Ted Cruz to the topic. 14:36:55 seamonkey-2.53: Cross-Reference does not need regenerated at this time. 14:36:56 seamonkey-2.53: Finished checking tree. 14:37:32 also you know it actually helps to reload nginx after grabbing a new cert? 14:37:58 CaptainTobin Hi. Hopefully at 2.53.18 already. I sometimes are late to update the file in the master branch. 14:38:17 i seems somethimes late to renewing my domains certs etc 14:38:35 late new year's resolution 14:38:40 renew things BEFORE they expire 14:38:43 hi frg_Away 14:39:21 IanN_Away: don't go away yet there is a status meeting i heard lol 14:40:28 frg_Away: so i learned how to create basic drop-files rpm and recompile source rpms that are already made 14:40:58 who manages the fedora package for seamonkey btw 14:46:31 CaptainTobin buc is the Fedora maintainer. 15:00:30 on time today~ 15:00:38 hi .* 15:00:50 tomman hi 15:00:52 never buy QLC SSDs with Maxiotek controllers~ 15:01:28 is that a sub-brand of Broadcom? 15:02:57 broadcom owns vmware 15:03:02 conserning 15:03:02 (Broadcom, a brand widely known for the stability and resilience of their firmware for wireless NICs) 15:03:22 broadcom a brand wide knownly for substandard products and crappy drivers 15:03:33 sorry njsg 15:03:47 i have a different longer term experience with broadcom tech 15:03:54 and it tends to rather annoy me 15:04:00 so where is this status meeting 15:04:02 lol 15:04:53 CaptainTobin: that was sarcasm :-P 15:05:02 checking in for the meeting 15:05:11 oh good then we don't ACTUALLY HAVE to disagree 15:05:20 i like when that happens 15:05:28 rsx11m Rainer_Bielefeld hi 15:05:32 Hi, 15:05:47 I will be lurking and see whether there are tasks where I will be able to assist a little. 15:06:07 hi all 15:06:20 Status meeting time - https://wiki.mozilla.org/SeaMonkey/StatusMeetings/2024-01-07 15:06:23 I didn't know there was gonna be one and I been very hit and miss.. i just .. sensed a need to show up. 15:06:28 Rainer_Bielefeld: hi 15:06:29 rsx11m: hi 15:06:47 * CaptainTobin quiets down 15:06:50 hi rsx11m 15:06:58 Hi rsx11m, all 15:07:06 Happy New Year to all! 15:07:16 Who's taking minutes? 15:07:20 CaptainTobin: Normally every 3 weeks but hollidays required adjustments 15:07:21 hi Rainer_Bielefeld 15:07:26 happy new year. 15:07:35 I do and late again probably 15:08:05 hi .* (to expand the scope of the first regex), and yes, happy new year .* 15:08:48 hello new year~ 15:08:56 njsg: yes difference between regexps and file name refernces 15:09:03 frg: thanks 15:09:13 the shell does not use regexps 15:09:26 frg: no, Maxiotek is a JMicron spinoff of their former SSD controller division 15:09:34 Nominees for Friends of the Fish Tank? 15:09:57 rsx11m for setting up the meetings and CaptainTobin for maintaining the xref. 15:10:00 second 15:10:19 second both to be clear 15:10:26 tomman: (JMicron, I think I had bad experience with one controller being less than optimal...) 15:10:41 thirded both 15:10:51 offtopic: Never buy QLC and you are good. 15:11:38 agreed 15:12:05 Action Items 15:12:46 I think the move to our won archive is more or less done thanks to ewong. 15:14:01 ^own 15:15:00 yes 15:17:35 Status of the SeaMonkey Infrastructure 15:18:09 No change I think. website is now maintained in heptapod. 15:18:31 IanN I saw some build jobs using heptapod. Is gitlab still needed for it? 15:18:41 Die ewong say something about it? 15:19:03 frg: he's being doing some testing but we're still using gitlab for the moment 15:19:29 ok Not much of a problem pusning to both. 15:19:42 ^pushing 15:20:08 I think pushes to comm-central no longer update our bugs but might be one time. 15:20:09 Status of the SeaMonkey Source Tree 15:20:44 All building. central updated too with latest stuff from central queue and revied patches. 15:21:21 thanks for those checkins 15:21:41 all my builds seem to be working 15:21:53 Thanks to Bill to keep it building too. 15:22:03 newly working are 2.53 linux 32 bit builds 15:22:59 Release Train 15:23:27 We will do a 2.53.18.1 Wanted to set it up last week but real life came in between... 15:23:27 I am working with ewong to figure out hwo to integrate my 2.53 builds to the new archive site 15:23:45 why a .1 this time? 15:24:01 to fix a crash in MessageChannel 15:24:32 and some security fixes 15:25:00 http://forums.mozillazine.org/viewtopic.php?f=40&t=3116906 15:25:09 I pan to still keep my archive site but will advetise the official one wonce it wotks untill we have miror sites for the offisal archive. a dont want a single point of failure 15:25:53 so iof an issue on the officails site I can just update the #SeaMonkey topic temporarily to my site till t is fixed 15:27:52 and once 2.53.18.1 is out will start thinking about 2.53.19b1 15:28:00 In case new people wonder about the new background on my site that is the it is the snowstorm background as it is snowing here. 15:31:39 Extensions Tracking 15:31:51 nothing new here I think 15:33:03 i'm not aware of anything that's changed 15:33:57 no new breakages to report from here so far 15:35:09 2.Next, Feature List, Planning and Roundtable 15:35:38 BAU for me 15:35:49 Still trying to get SpiderMonkey updated with Myckel. Now at mid 62a1 but the new regexp breaks. 15:36:08 buc took a look too and found one problem but still no go. 15:37:04 Looks like I need to put in the patches from the wip branch in piecemeal: https://gitlab.com/frg/seamonkey-wip 15:39:00 most wanted JS features these days for frameworks: dynamic imports is becoming a widespread one, also BigInt 15:39:18 I've noticed some frameworks are getting better at concealing errors about unsupported features 15:39:35 yes, always helpful! 15:39:45 sorry, some spillover sarcasm. 15:39:47 so that makes it somewhat difficult to figure out why websites break as you can't see the why from the get go 15:40:42 tomman yeah the wip branch has the "beginnings" in. Would be a snap to add it fully from it wouldnÄt it be for the regexp breakage. Taking this out would mean the other half of the web breaks again. bahhh... 15:41:04 the usual recommendation to find out what breaks would be to check the JS console for errors, but some pages will indeed either hide it, or show an error in unrelated code that can't handle an error condition 15:41:48 off topic: If it were not for SeaMonkey I woudl leave IT probably now. No more fun with mondern OS versions and the web itself. Only good for shopping around now mostly. 15:42:32 for me still woring with ewong to be able to post builds form my automation to the new archive server seems i can not post directly from my build server unless i update to later linux version whch would mean my builds would have less backwards comptibility. thying to see if the jumphost could be used as an intermeidataly that I could put builds on in a zi[p file with a sccript to run to... 15:42:33 ...install them so scp the zip file and then ssh a command to process the zip fileused t do this back in the day when we for security reasons has zer acces to ur external web server for the conapny form our internal net and had do post a file with info and files it should install 15:43:33 this was set up by my much smarter friend Howard. I just inherited it when he left the company. 15:43:34 it seems there might be a stronger push towards Wayland in the linux world, which probably won't help adding to actual fun, unless you don't need the X Window System 15:43:48 njsg yes this too 15:44:51 frg: I haven't researched yet, my first question is, I think "how are BSDs handling this?". One thing is some linux distros wanting to ditch X11, another thing is the whole *nix universe. 15:45:06 ah, Wayland 15:45:25 well just next iteration of what was originall called W for windows and then updated so called it X as next letter in the alphbet but then for next udate instead of calling it Y decided to name it after a twn in the ares 15:45:27 X11 is the hill I chose to die on, but distros may not have any option after Red Hat effectively signed X.org's death warrant 15:45:41 so it's get on board or die (XWayland is a bandaid at best) 15:46:14 Also, what's the future of 32-bit SeaMonkey versions? 15:46:20 it makes it sound way different because of a differnt way of naming but really now differnt than when W became X 15:46:30 that's another thing on the chopping block not only on Windows, but also across the Linux ecosystem 15:46:36 for backwards compatibility, the question is how not to require newer versions of standard libraries (especially GNU libc++, but probably also GNU libc), right? 15:46:40 next Debian stable will not ship i386 installers anymore 15:46:44 Firefox only recently more or fully supported it. If someone wants this in SeaMonkey we need help. It is about 6000 patches to widget. Not all needed but a bunch will be. 15:47:54 is just the latest way to do windows in *IX form MIT 15:47:59 just a new name 15:48:02 Personally I will ditch any wayland only and not shipping kde too distro. 15:49:02 Wayland inlcudes a thing called Weson (a neighboring town) to permit running X11 apps under wayland 15:49:19 Weston 15:49:23 a problem is that wayland is different and may not have all X11 features 15:49:26 IanN As for i386 I assume no decision yet. When we switch to Rocky 8 for building it should go away for the official builds imho. 15:49:27 WG9s_: no, Weston is the "reference" compositor 15:49:40 it does not provide X11 compatibility - XWayland is a separate thing 15:50:03 last I checked PRIMARY was TODO or in progress in Wayland; Also, it seems the different approach breaks xscreensaver 15:50:12 and not all DEs use Weston - GNOME and KDE Plasma bring their own compositors, and the GNOME one is infamous for only supporting what GNOME requires and nothing else 15:50:13 at least according to some blog at jwz.org 15:50:27 frg: yeah, need to switch to Rocky 8 soon though 15:50:28 tomman: well, it *is* GNOME 15:50:29 njsg: yeah, Wayland also breaks screensavers, and this is by design :/ 15:50:42 njsg: sadly the most used Wayland compositor is GNOME's one 15:50:48 hey folks 15:51:07 tomman: yeah, precisely what I was aiming at, it's not that the design is good or bad, but that it is different, so it's bound to not work for some things, it's bound to introduce undesirable differences for some users 15:51:17 I hope it's okay if I speak a bit here, since I'm a Wayland aficionado? 15:51:18 that's the single biggest problem with Wayland: you can't assume your compositor will implement the features your app needs 15:51:23 macOS native building is sitll also broken because of some missing stuff which could only go in for the Rocky builder. 15:51:25 so gotta be careful there 15:51:30 ah, Mac 15:51:34 which these days means ARMac too 15:51:36 I summoned some BinOC Re-enforcements to assist. 15:51:39 Son_Goku sure. 15:52:01 problem with the gnome is that is is severly bloated and is why we are thinking of dropping linus 32-bit suppot becuase gnome on a 32-bit system really sucks 15:52:11 IanN: and would the switch to Rocky 8 affect backwards compatibility in linked binaries? 15:52:24 so from the perspective of features that a web browser needs, the baseline is generally implemented in Mutter (GNOME), KWin (KDE), and any compositor using wlroots as their building block 15:52:28 njsg probably. Later libstdc++ 15:52:49 at least at this point now, maybe not a few years ago, but definitely now 15:53:19 my guess will require glibc version 2.28 15:53:28 Son_Goku personally I just want it to work. Don't care but either X11 or Wayland. But Wayland seems to be an ongoing big construction site. 15:53:54 Yes any bump in el build host and deps will affect backwards compatibility to be .. non-existant lower than the glibc version 15:53:56 frg: WG9s_: so the problem is in requiring newer libstdc++ and possibly newer libc? As in, is this the *only* thing that'd need a solution? 15:54:01 frg: I think the main thing SeaMonkey would be concerned of is integration of the xdg-desktop-portal API for screensharing, camera, and microphone access 15:54:38 otherwise, the rest of it is windowing "stuff" that IIRC you guys get mostly from GTK already? 15:54:48 oh and portal for file picker 15:54:59 frg: WG9s_: I remember seeing some options about that, but IIRC a problem was also in other packages and libraries built and linked with seamonkey? 15:55:11 They do not use client drawn window controls except in full screen Son_Goku 15:55:25 they rely on window manager client decorations 15:55:28 right, so that means libdecor integration 15:55:50 libdecor handles SSD setup in all environments, especially ones that don't have it directly supported 15:55:51 Son_Goku There are just not enough devs around. I am keeping Windows and macOS floating and IanN and WG9s mostly Linux. No problem doing backports but not much time left to actually do our own stuff. 15:55:51 firefox has both modes on linux now so patchqueue i guess? 15:55:58 ... client drawn window controls, is this a world where everything looks like a TWAIN scanning appled designed by the vendor to look unique? :-) 15:56:10 njsg: i build with --enable-stdcxx-compat to get wanings about issues and then have a script the post processes the log file output to find those and find the latest version required and all it reports is needs glibc 2.28 15:56:13 yeah, I think there's some judicious cherry-picking from Firefox 15:56:17 that could work here 15:56:32 but it may require bringing in all the compositor work in general 15:56:36 which could be massive 15:56:52 stranksy and jgrulich did most of the work for this upstream firefox, I could connect you with them if it'd help? 15:56:56 and not wholey compatible with this design 15:57:58 this is using an old version of fedora to try to maintin compatibility for my builds I amd using f29 15:58:06 Son_Goku I/we know what to do in general but just no time. Easier to just put the wigtet fixes in chronologically and rebase. 15:58:11 ah okay 15:58:13 sorry 15:59:03 I didn't mean to make it sound like you don't know stuff 15:59:11 Son_Goku nothing to be sorry about. It is just that we are so few devs. Mozilla toiplet paper budget and resources are probably higher :) 15:59:17 lol 15:59:52 how close is your webrtc integration code to upstream firefox? 16:00:00 Son_Goku No offence taken. I is just still a wonder hat we are managing with so few people. 16:00:21 "Mozilla toilet paper budget", gonna steal that one 16:00:25 60 61 but not supported anyway witout an add-on 16:00:32 okay 16:00:50 that's really where the meat and potatoes are for the "Wayland experience" for browsers anyway 16:01:56 issue here is we have people wanting to run on latest Linux that kind of wants Wayland and those who have 32 bit systems they bought 20 years ago hat they still want to work. and we have limited resources. 16:02:02 May sound really backwards but mozilla slowed down much after about 65. We just need to mover over this hill while keeping compatibility with classic add-ons. 16:02:13 ^to move 16:02:25 Wayland windowing has worked for a while in Firefox, I think since at least 65 16:02:36 in Fedora we've had it on by default since Firefox 65 16:03:08 WG9s_: realistically 32-bit architectures are screwed by the end of the decade anyway... Y2K38 is coming 16:03:22 and all the potential "fixes" are ABI breaks, which means nobody can realistically do them 16:03:31 I plan to update widget but js first. 16:03:51 spidermonkey et all IS a higher target 16:03:58 others have prioritized the same 16:04:48 frg: honestly, I'm not surprised that they slowed down after 65 16:04:49 yeah, the biggest priority now is JS compatiblity 16:05:06 wasn't that the Quantum release? 16:05:16 57 was quantum. 16:05:24 well I was close :P 16:05:26 Son_Goku: re 32-bit and y2k38, at least for IA32, how much of a problem would an ABI break be, couldn't it all be compiled as a 'different' architecture, say "IA32-y2k38"? 16:05:48 njsg: everyone who cares about 32-bit x86 seems to want binary compatibility 16:05:52 that's where the problems are 16:06:11 It seems the momentum lasted some time but I see not much change lately. But keep in might that I might be wrong :) 16:06:19 * njsg 's bland reaction to "ABI break" might be related to certain Gentoo events of the early 21st century :-P 16:06:29 there's a discussion going on in lkml, libc-alpha@, and distributions@ and nobody has come up with a good solution here that doesn't create even more problems 16:06:49 any more AOB? 16:06:50 Biggest breakages was after 60 when the classic add-on stuff was removed. 16:06:59 nothing from me. 16:07:01 as an example, one suggestion was to make 32-bit time_t unsigned, but... that breaks "negative time" (that is, counting dates before UNIX Epoch) 16:07:19 Son_Goku: prblem is borwsers have become bloated adn pwople who ony want to use it to buy things and do banking have to carry all of the bloat to do streaming audio.video which soes not fit in a 32 bit application 16:07:29 I don't entirely disagree 16:07:50 but I also am in the weird position of being slightly thankful because otherwise I'd have a much harder time using Linux as a daily driver for work 16:08:09 the writing is on the wall for 32-bit anyway - in 10 years from now on those of us that will still be running it are retroenthusiasts, virtual machines, and people living on extremely poor countries where the Pentium 4 is still a hot commodity 16:08:16 but no modern software would run on it anyway 16:08:21 Son_Goku: oh, I can appreciate lack of compatibility being an issue, was just wondering because I suppose it'd at least be possible to keep some IA32 system still running with newer software and no y2k38 issue 16:08:36 njsg: there are a few ways if you're fine with no binary compat 16:08:47 the easiest is forcing 64-bit time_t everywhere 16:09:15 * njsg wonders what would changing the epoch entail, and opens IEEE 1003.1 16:09:21 oh dear 16:09:22 :) 16:09:28 also, convincing web devs to stop jumping on the latest JS shinies shipped by Chrome is another pain point 16:09:33 and I still don';t now waht is going to happen in 2033 worse than Y2k is when the number of seconds since jan 1 1970 gets too big 16:10:11 tomman: I don't know how broad it is, but at least in my circles, there seems to be increasing pushback on that nowadays 16:10:12 Hmmm... I should be try setting the date on my 386SX-40 to 2038 and see how Windows 95 halts and catches fire 16:10:19 that would be funny :P 16:11:05 IanN: I don't think I have more to add to AOB either. 16:11:24 too big for 32 bit integer 16:11:28 Anyway, none of my 32-bit boxes run web browsers anyway these days (except for that ol' XP laptop which I use only for email) 16:11:31 sorry that I wasn't any help here, but if y'all do have questions about Wayland stuff, feel free to ask 16:11:53 Son_Goku: my view is that such code, especially frameworks, should do at least a minimum job on handling error conditions and not failing unless they have to 16:12:11 njsg: there's increasing pushback on those frameworks in general 16:12:12 Son_Goku: Ideally telling what's the missing feature instead of "upgrade to Other-Browser XYZ" 16:12:22 yeah 16:12:35 Son_Goku I really like to discuss things and keep and open mind so all good. I know that we need to play catch up. 16:12:44 okay, thanks for your time today, next meeting is in 3 weeks time, same bat channel, same bat time 16:12:53 I remember when Google Translate's "Translate this page" broke because they had fallback code for lack of window.performance, but were not checking for a much newer feature 16:13:17 I'm sure that any report to google would be received the same way my request to unblock mozilla.support.seamonkey was. that is, ignored 16:13:18 frg: well I'm here, and you can also catch me on the Matrix side if you're over there (that's where I usually hang out) 16:14:00 (there was a suggestion out there that Google unplugging Groups from USENET was because somebody inside Google managed to escalate a ticket about the spam coming from Groups) 16:14:04 Son_Goku thanks. 16:14:14 the whole y2k issue had to do with 2 things first keeping 2 digit years in the code so sudenl they go back to 1 and second incorrect leap year crap which dud laep year is every 4 years except those divided by 100 but 2000 was a leap year 16:14:27 becaseu was divisible by 1000 16:14:39 Son_Goku: if you visit places like Hacker News, you'll find nothing but praise for frameworks "pushing things forward" (and people spreading FUD about "old Firefox forks") 16:14:50 oh yeah I know 16:14:59 hilariously on the Fediverse it's the opposite 16:15:06 ha, Mastodon 16:15:06 and there's a lot of disdain for HN these days 16:15:15 real rule is skip leap year if year is divisible by 100 unless it is also divisible by 1000 16:15:16 the social network that absolutely requires JS to work :/ 16:15:23 tomman: re HN: and also cloudflare staff which actually handles support requests when cloudflare DDoSes itself! 16:15:24 (wish there was a Nitter for Mastodon) 16:15:52 mastodon's official web interface is a nightmare. it's heavy, and possibly geared toward doing everything in a single tab 16:15:55 doesn't RSS work for this? 16:15:58 takes time to load, loves to be async 16:16:00 I've found some Mastodon instances that do not render at all on SeaMonkey due to some latest JS shiny not supported 16:16:04 oh it does, yes 16:16:17 njsg: I don't use masto's official UI myself 16:16:27 there is Brutaldon, a JS-less web client, but it requires an account 16:16:28 tomman: usually you can get RSS of accounts and tags at a mastodon server, might not always work if it's not the official software I guess? 16:16:39 (I only read threads, I don't actively use social media) 16:16:42 I use Elk or Tokodon 16:16:57 while Elk is more JS-heavy, Tokodon is a native client 16:17:04 my ideal way to handle something like mastodon would be something like a USENET client 16:17:08 WG9s_: 100 unless it is also divisble by 400 16:17:09 I'm not interested in native clients for that, sorry :/ 16:17:13 so the so called y2k issue was 2 problems one was only keeping the lat 2 digits of the year and 2 not undersatnidning the leap year rules 16:17:19 tomman: no worries 16:17:22 as I've said, I don't actively use social media, I only need to read linked stuff 16:17:38 maybe someday Brutaldon will drop the requirement of having an account for read-only purposes... 16:17:48 WG9s_: 100 unless it is also divisble by 400 unless it is also divisible by 1000 16:17:54 or maybe someone will make a Nitter fork 16:18:03 yes 16:18:08 ah 16:18:15 reminder: 2024 is leap year! 16:18:28 would be fun a release on February 29th :D 16:18:45 IanN I think we are done with the meeting. Next one in 2 weeks but that doesn't mean everyone needs to stop talking now :) 16:18:55 and the newer issue is that i think it is in 2033 that the *nix universally used number of seconds passed the epoch overflows a 32 bit integer 16:19:10 tomman: there doesn't seem to be a request for brutaldon to have a nitter-like mode 16:19:17 maybe ask and they may do it 16:19:25 do they use Github? 16:19:29 gitlab: https://gitlab.com/brutaldon/brutaldon 16:19:33 ah, Gitlab 16:19:38 frg: 3 weeks isn't it? 16:19:45 at least that one is not THAT broken here yet 16:20:01 IanN Ah sorry 3 I mean. 16:20:21 frg: though the notes say 21st currently 16:20:22 wonders how many things that will break 16:20:34 oh god, Clownflare is checking my web browser to figure out if it is Secure™ 16:20:48 tomman: also: older versions of mastodon's web ui didn't require JS and could be read without JS 16:21:41 ha, I had never bothered creating a Gitlab account :D 16:21:52 isn't SeaMonkey on GitLab? 16:22:23 or is it just a mirror there? 16:22:48 tomman: if you have a nicer way to follow RSS, given a mastodon URL, try adding .rss to see if it works 16:23:29 Son_Goku yeah for the 2.53 line. central is broken but building in commn-central. But usually use the command interface only. Wasn't that bad when we started. 16:23:39 ah 16:24:25 Son_Goku use Vivaldi as a second browser now fro broken sites. The closest Chromium thing to the suite. 16:24:45 Edge was ok first but junk now. 16:25:21 Now deinstalling Edgeand the webview2 junk right and left on my systems. 16:25:33 I've been increasingly able to get away with using Firefox for things 16:26:06 there's only one thing I use regularly that requires Chrome for me, and that's for communicating with a specific group on their preferred video call platform 16:26:20 and Fedora's Chromium works well enough for me for that 16:26:37 ugh, Gitlab is SLOW 16:29:20 tomman anything using webcomponents is a bloated pig usually. Even in a Chrome browser no speed daemon. 16:37:07 add to that a 12 year old Sandy Bridge i5, and you get a GAAAAAAH from me :/ 16:38:27 tomman: I know the feels 16:38:39 most of my computers are ~7-10 years old 16:39:49 yeah, even typing text on forms here is SLOW 16:57:13 damn, letting GitLab open for too long really made my SM very sluggish... 16:57:50 that's where about:memory sometimes brings relief~ 16:59:17 tomman: final or b1pre? 16:59:36 build 20240104220119 16:59:43 that is... yesterday 16:59:43 I think the debug menu has an option for that 17:00:12 hmm, have never noticed that "Flush memory" menu! 17:00:36 I usually enter about:memory, and try GC, then Minimize Memory 17:00:59 Will be handy, unless that entry is for something else? Is this doing GC, CC and minimize memory? 17:01:28 generally I do GC first, if it doesn't help, I go with Minimize Memory 17:01:31 * njsg should probably just go read the code or inspect with the DOM inspector... once he frees some memory used by another seamonkey process 17:01:56 after a few days I have to restart the browser anyway, because there comes some point where even Minimize Memory won't help anymore 17:42:17 Will I ever be able to login with SM on Discourse forums? 17:48:10 > Discourse 17:48:12 abandon all hope 17:48:20 you don't fit into Jeff's vision 17:49:46 TED CRUZS GRANDFATHER AND HITLER WERE LOVERS 17:50:15 TED CRUZS GRANDFATHER AND HITLER WERE LOVERS THEY FAGFUCKED EACH OTHER CROSSEYED EVERY DAY 17:50:36 TED CRUZ RAPED NUKES ASS 17:50:49 TED CRUZS GRANDFATHER AND HITLER WERE LOVERS THEY FAGFUCKED EACH OTHER CROSSEYED EVERY DAY 17:51:14 CaptainTobin I AM INEVITABLE 17:51:38 CaptainTobin TED CRUZS GRANDFATHER AND HITLER WERE LOVERS THEY FAGFUCKED EACH OTHER CROSSEYED EVERY DAY 17:51:43 TED CRUZS GRANDFATHER AND HITLER WERE LOVERS THEY FAGFUCKED EACH OTHER CROSSEYED EVERY DAY 17:52:10 TED CRUZ RAPED TOBINS ASS 17:54:14 TED CRUZS GRANDFATHER AND HITLER WERE LOVERS THEY FAGFUCKED EACH OTHER CROSSEYED EVERY DAY 17:54:15 TED CRUZS GRANDFATHER AND HITLER WERE LOVERS THEY FAGFUCKED EACH OTHER CROSSEYED EVERY DAY 17:54:16 TED CRUZS GRANDFATHER AND HITLER WERE LOVERS THEY FAGFUCKED EACH OTHER CROSSEYED EVERY DAY 17:54:17 TED CRUZS GRANDFATHER AND HITLER WERE LOVERS THEY FAGFUCKED EACH OTHER CROSSEYED EVERY DAY 17:54:43 TED CRUZ KEEPS A JAR OF HITLERS CUM IN HIS FRIDGE 17:55:22 OH GOD 17:55:29 TED CRUZS GRANDFATHER AND HITLER WERE LOVERS THEY FAGFUCKED EACH OTHER CROSSEYED EVERY DAY 17:55:37 WG9s_: this one is for you 17:55:48 TED CRUZS GRANDFATHER AND HITLER WERE LOVERS THEY FAGFUCKED EACH OTHER CROSSEYED EVERY DAY 17:56:23 TED CRUZ PUTS HIS CUM IN MILK CARTONS TO SEND TO SCHOOLS FOR STUDENTS TO DRINK 17:57:26 TED CRUZ KEEPS A JAR OF HITLERS CUM IN HIS FRIDGE 17:57:49 TED CRUZ RAPED NUKES ASS 17:58:10 TED CRUZ KEEPS A JAR OF HITLERS CUM IN HIS FRIDGE 17:58:27 HE TAKES A SIP EVERY YEAR 17:59:04 TED CRUZ RAPED ATHENIANS ASS 17:59:44 TED CRUZ SHARES A CUP OF HITLERS CUM WITH JWZ 18:00:20 TED CRUZS GRANDFATHER AND HITLER WERE LOVERS THEY FAGFUCKED EACH OTHER CROSSEYED EVERY DAY 18:01:57 tomman did a kcik ban 18:02:07 kicks are cool~ 18:04:25 so did a ban then a kick so the ban should prevent re-joining at least for now 19:05:33 Honestly the weirdest thing is the mention of Zawinski. I wouldn't have expected him to be on the radar for that kind of spam. 19:07:46 I didn't even notice, that's... too context-aware. 19:18:57 someone should send the log to JWZ :D 20:13:14 IanN_Away: this guy is using ip addresses all over telus's alloc 20:13:26 on my irc server I just banned telus for a while 20:13:38 I wonder who the HELL I pissed off in canada 20:14:23 well he sure is an idiot. 20:14:32 jonadab: I am convinced this spam is happening to target me specifically 20:14:38 because I am here 20:14:41 you get spanned 20:14:43 spammed 20:14:48 CaptainTobin: doubt it, I've seen that idiot spamming on other channels 20:14:59 where else 20:15:05 but the "on-topic" F-bombs are certainly new 20:15:16 I think I saw him once at #debian or something like that 20:15:26 this has also happened on my irc server every time its happened here 20:15:32 so its the same guy 20:15:32 or was it #networking? Can't recall 20:15:50 he is STILL targeting me and my server where no one has said more than a few messages in months 20:15:52 but the Ted Cruz crapola was the same 20:15:59 and when it was offline people sent even less 20:16:18 well who hates me and debian and maybe you guys 20:16:28 i say whomever it is is a bsd user 20:18:28 thing is ted cruz is a corrupt republican and jzw is irrepuably liberal.. why are they sharing hitler's bodily fluids? 20:18:46 so confused 20:18:58 I've always thought trolls have VERY weird fetishes :D 20:19:17 the specific wordchoice is interesting 20:19:24 fetishes straight out from a Japanese visual novel :D 20:19:45 send em to the bme pain olympics 20:20:16 welp 20:20:20 back to linuxing 20:20:27 BOB DOLE! 20:38:30 CaptainTobin: I've seen that spam elsewhere, I think. I can't recall where, might have been #gentoo-*, or perhaps it was on another network... 20:39:12 CaptainTobin: sorry I can't recall the details, but I'd be inclined to say it's not targetting you or at least not just you. I wish I had more data to offer. 20:43:12 now if the spammer gets in here again and starts OFFERING DATA, either they've got another connection here or they're reading from some log?