Muscle Memory!! Muscle Memory!! I'm sure, previously, when disconnecting from these Chat Groups, the 'Disconnect' instruction WAS in the 'Edit' drop-down list (second drop-down, in any case) but now it's in the 'Chatzilla' drop-down list.

Makes sense, I suppose, but now I need to retrain my Muscles!! ;-P

lifting some weights is helpful~

Maniel: probably bug 1943783? (so have a look in case there's something else you need to retrain for

)

I personally would probably try /DISCONNECT before even thinking of the menus. And I say this without knowing for sure whether chatzilla has such a command

oh joy, Clownflare changed their challenge pages once again

now they render absolutely NOTHING

not even the "Complete the following action blah blah" text

it now dies in an absolutely blank page

(which wants BigInt, and also barfs at another, new, unrelated internal function)

the only static HTML tags surviving are a couple meta tags, a noscript telling people that you can go away if you do not enable JS, and a couple nested DIVs

That's It.

The inspector shows the page manages to do absolutely nothing before dying. On the flip side this means there is no risk (this time) to get stuck into a hardware-specific CPU loop

but this now means SeaMonkey is totally and completely BLOCKED by CF, with not even a proper error message this time

hmmm, if you leave said failure blank tabs alone, they will eventually reload themselves at random times

is this why some news sites now show a small message about enabling JS, or are NYT et al. using something other than CF?

njsg: the browser war was still lost in 2021

the moment zoom happened

really it was lost when firefox shipped drm

but we could have pulled it back

as far as refactorings from 52 to 56 .. i couldn't care less.. anything important and a few things I wish wasn't backported specifically by janek and rubberstampped by Moonchild was in UXP in 2018

and mozilla refactoring? what do you guys think has all but killed the mozilla project

doesn't matter

I'd think it was about applying the refactoring paradigm to things like UI and APIs

the point of the experiment is to gadge what would be the best course of action not the one someone may just be in the habit of.. i been basically out the game save false starts for years now.. and i still can't find any better solution than what I already spent a decade doing

it's strange that someone would remove exactly the things that make the program stand apart, in an apparent effort to be like other products (quick: what do you think that happens if your product doesn't have much difference from the competition?)

Just by not changing the UI look and feel a project probably avoids part of the mozilla doom

but seamonkey's UI has not been spared

by not destroying the extensibility a project probably gets to run doom

and that has always been my friction with the status of SeaMonkey

nsITobin: you mean how it departed from XPFE?

the core mission statement is not being followed because no solutions exist to maintain it

as i learn more about xpfe it was a superior system but had early days syndrome where tooling was conserned

it was more advanced than toolkit but harder to wrangle up front

njsg: splash screen and lack of install-time componitization

things I already figured out how to fix a decade ago

that is the foundation of my agitation

OH WOW, AP News now uses Clownflare challenges too!

how ironic, I was expecting my very own government from censoring me that

...instead Clownflare gets that honor :/

apnews.com/article/iran-whatsapp-me…el-d9e6fe43280123c9963802e6f10ac8d1 test link

hmmm, now the "Just a moment" page briefly rendered, then... WSoD'd

guess that's what we get now that Clownflare is a fully AI-driven corporation, down to the last line of code

... I just read "whatsapp" as "warship". I may need to sleep.

well, the world is at war, grab your nuke and go to the barracks~

*sigh* this is nuts.

need to buy some Nutella, thanks for the reminder

no, not Satya Nutella

njsg: fork mozilla and diverge.. make a tech allience.. diversfy and support and help birth new projects and varients.. document and be as self sustainable as possible and build alliences.. which is what everyone else does and that last part is the only reason seamonkey is not on UXP right now

now i can continue blaming my self and i surely will but again this is not all my fault nor should I have had to be put into a position where I needed to fork anything

because while yes I am a mal-adjusted and poorly socialized autist the burdon shouldn't have been on my shoulders alone and others should have helped me not merely helped them selves to what I envisioned then made manifest

tl;dr if i have to do a thing.. someone else fucked up and continues to fuck up and shows no signs of doing anything else.. in MOST cases.. certainly was true in 2014

So basically to go forward.. I am no longer going to be conserned with fucking up.. cause frankly that's the world wide general status quo.. and if it gets me killed so be it.. I was willing to die on a MAGA hill .. and unlike that THIS actually means something because it is universal.. fucktard nazi trump people and communistic alphabet gender liberals alike.. and they both too dumb to see what a fuckin fat autistic mess could see 25 fucking years ago

and could articulate well.. enough.. 15 years ago

Since SeaMonkey is obviously not interested in competeing with other browsers.. how about we let SeaMonkey compete with its self.. not just as an experiment but outright.. SeaMonkey Mainline (2.53 as normal) SeaMonkey Suiterunner (UXP) and SeaMonkey.html (modern mozilla) manifest them and give them to the users .. UXP version is under my general direction.. html is whatever managed to be accomplished and mainline as business as useal .. and the

minimal web infra to support all three.

web infra to support browsers, now where is that qdb entry about how firefox should be a webapp :-P

njsg: you know what I mean blocklist, add-ons, documentation, update servers.

everything anything remotely mozilla like needs

perhaps a good way to summarize this is "mozdev"

it's gone and took a bit too much with it, code repositories, bug trackers, documentation

yep

and forge hosting is a massive undertaking that would require custom code cause everything off the shelf is too fuckin badly coded to be scailable without .. money

i tried..

but it hardly matters everyone wants github or gitlab

or rather all the techies are forced into agreeing to be and only use what morons can manage to sign on to and submit a pr for

that is the real reason Mozilla went github

HERE IS MY SIMPLE LOGIC.. To get seamonkey developers you need seamonkey users specifically ones that would oherwise help contribute and would be excited about the UI and the technology and the capabilities it gives them.. others would want something very much like today's 2.53.. and others still just want a decent simulation of seamonkey with every other modern mozilla facility save telemetry

so.. the more traditional xul platform, the patchqueue progression, and some sort of modern equivant even if it doesn't CLEANLY come from patched ports forward.

once you have all three going then you see which gets the most attention and users and dare I say contribution and eventually shift focus to that one path and faciliate handing off the others to someone else if desired.

then seamonkey has a new future or a completely affirmed current one

all for the price of largely and almost exclusively MY time and brain.

and dealing with me of course :P

it has some risk .. but it also has great potentional

the final decision need not be made today.. but it will need to be made by the time I am ready to begrudgingly consider the rust toolchain for my operating system

packages for it*

because that is when I will be ready to commit to mozilla code again.. when i have an OS to run it on.

and no i am not gonna go to war if i don't get my way.. I will just write and host webcode until i can't anymore..

The decision is up to all of you not just the counsel