aaaaand this is back

I hope it does better than it did previously.. Likely more valuable as a common point of reference for the increasingly disperate community offerings.. just need to keep the Tobin Factor to a minimum and I think it will be useful again

XULvolution in all its forms.. kinda makes you feel i dunno more optimistic

top menu will likely become something akin to Front Page | Around the XULsphere (posts about releases and happenings) | BinOC Resources | SM Resources | MCP Resources | Additional Resources

but i need to do a dropdown.. wonder if that menu is still compatible with the later BinOC modifications .. have to look into it

HEY FRG

best stop SeaMonkey, according to Waterfox Classic being based on gecko/56 means backporting security updates is difficult if not impossible.

and that is why it is now abandoned

frg_Away: with the last beta from Bill a bug was introduced. The preview in the Taskbar no longer works for the browser window, the mail window is not affected. Please see: imgur.com/a/dvprS5j

frg_Away: this is on Windows 10 prof x64. It worked with the build from 01.02.23

frg_Away: disabled hardware acceleration and cache but no change :(

Hi, does anyone know what happened to news.aioe.org/nntp.aioe.org? Seems to be down since two weeks now. I'm asking because it is recommended on the SeaMonkey website and I used it for quite a while now. Is there an alternative news server that hosts alt.comp.software.seamonkey?

mike747: RAID failure

mike747: wiki.mozilla.org/User:Njsg/News_providers

mike747: if you choose eternal-september, be sure to check the (account settings) option to always authenticate, otherwise you won't see the full list of groups

I'll try these. Thanks a lot!

hardys I will take a look. See an NS_ERROR_FAILURE in the log

hi frg_Away

CaptainTobin Hi

so i was thinking about SM specific resources to add to the menu of thereisonlyxul the status meetings is one.. how relevant is MDN vs UDN sources?

link to build instructions and the repo too would be nice i suspect

frg_Away: any other suggestions?

I am seldom looking at mdn any longer. It has become generic. I usually just search via search engine.

older resources that still apply that could be useful to one of all of us

there is that one resource wolfbeast likes to link specifically when it comes to extension scopes and mozilla.cfg

you remember what that guy's name was?

CaptainTobin no unfortunately.

nuke would know but he ain't gonna tell me.. heh

sigh.. likely have to use google site search and search the damned forum i guess.. later

planet xul and all the other older stuff is mostly dead. Has Waterfox Classic been declared dead oficially too?

effectively

they say it is impossible to backport security fixes

so they left a list of bug numbers and say patches welcome.. and no tangible activiy since end of november

frg_Away: do people still believe backporting security patches is impossible after everything?

CaptainTobin well most patches I have recently seen are regression patches. So it is impossible to backport if the original bug is not in :)

I find things like the clipboard api an unifixable security hazard is implemented . So feeling safe without such stuff :)

that is why I was all about the UXP Mozilla Security Patch summery.. since wolfbeast didn't want to just use the Mozilla commit message and kinda hide em away as common one off patches I insisted that be tracked each cycle.. Indeed my insistance on realigning the release cycle to major minor major minor was in an effort to both reduce time spent on release engineering but also to catch every security bug as soon as possible to explicitly combat that

old and insecure mantra so we listed number of bugs that fixed vulnerablitys, defense in depth where the fix is only important if other changes expose it, and those that don't apply due to not being vulnerable or plum not even having the whole component

besides, backporting mozilla security fixes was an accomplishment because very few actual NEW holes were ever opened up by our efforts.. so UXP gets more and more secure while mozilla basically remains perpetually zero sum

it was nice

oh.. frg_Away i am gonna give you the UXP version of weave not the additionally modified GRE turned ARE version

cause if your syncui worked with it pre-fxa it should JUST WORK with it now but if not i know where reference code is to resolve it

this will be faster and more consistant with your workflow if it isn't supercustomized just has the amo integration disabled/killed

SEE frg_Away I CAN ADAPT

I MAY BE BORG AFTER ALL!

CaptainTobin I suspect most bad stuff is now in the third party stuff. Trying to get gfx updates in as fast as possible usually.

indeed

we should also get you on 2022 or at least 2022 capable

should be fairly trivial just needs DONE i suspect

it would be valuable to have everyone capable of being on the same compiler VERSION for comprative reference

i think so

anyway

frg_Away: a huge swath of your platform is far closer to me and them than it is to mozilla my friend ;)

current day*

seems UXP identified some specific caveat regarding windows 32bits and 2022

CaptainTobIn it is the one bug I mentioned previously currently.

have to specify a slightly older version or it just won't run on older hardware or some shit

YES

ok

why did i think those were two seperate things

as for 32 bit it can go the way of the dodo. My oldest T61 Thinkpad from 2008 is running Windows x64 with 4GB fine.

I am just gonna drop windows 32bit and gtk2 and gcc older than 10 when EL7 dies

and vs older than 22

17 and 19 are stiff fine and being updated.

sure

but as one person it is difficult to support multiple compilers

and I don't like leaving broken support in

MS is doing a Windows 11 on 22. It is constantly changing. 19 is the best bet currently. Needed to work arend an ICE in 22 previously too and this has not happened in a long time before. So yes for support bot no for dropping 19. 17 can go.

frg_Away: yeah and I told Moonchild that but he didn't listen obviously.. It may have even been stated in some earlier issues.. but he has done that and I have to either deal with it by keeping 2015 or going 2019 and hoping i can solve differences or just deal by accepting 22.. whatever happens for this very moment i kinda have to just accept 22 until i know more..

or things get harder than I am able to cope with right now.. later perhaps but not right now

you know

it was FAR easier to avoid bs like that when you were in charge of avoiding it before it happens eh?

If 22 can compile the soruce 19 can. Don't see anything which would make updating to 22 a requirement.

22 can compile uxp.. that was based on 52.. i am sure 22 can compile your codebase especially seeing as it already went past the 2015 mark so.. you are already in better shape than most

just needs to get done is all

like most stuff like this

Hardest part was to get it into moz.configure :)

that bit of moz.configure is more comprehensable than others let alone the backend thgat drives it

Problem with 22 is/was that the locations changed to the x64 directory without the x86.

i wonder why the hell we couldn't just use the batch file with vswhere to just shit the paths into the same vars we always used

hardys next build should fix it. Thanks for reporting it.

let's just see if this code still compiles with 2015 str8 up sans jxr

and with that one xpcom patch

cause if so well i deff don't need jxr in interlink and jxr is doubious since chrome rejected it

i have a feeling it won't like JS

frg_Away: you know in another decade or two there will be an episode on history channel of ancient aliens asking if ancient aliens created the first browser

and that MCSA Mosiac is based on ancient source code from a tablet that no longer exists

already happened in dimension X123AFG

LOL

Fucking amazing

I quite enjoyed that.

hardys fixed it

frg_Away: Thanks for fixing, I will try the new build tomorrow. Do beta testing every day

needed to remove a patch. Not sure why this one caused the failure but was not essential for now. Just fluff for later stuff.

I think it is a good thing to report this "zeitnah" so you know where to look for based on your latest bug fixes

hardys yes. I would probably have spotted this one too soon but was about to move things around which would have made it harder.

Last status meeting notes are up. Sorry for the delay again: