Day 7 of the Latest Clownflare Siege: little progress, mainly from site operators

Wine dropped their CF brickwall from the AppDB in late Thursday

science.org now loads most of the times, someone just told me that they had to make exceptions for feed readers

(you may get lucky if you email Derek Lowe)

our HN plea for help thread had zero effect

an actual CF user (paid customer) complained at the forums because of this, got promptly told to pound sand

and now the Internet is split in two for us: the regular Internet, and the Clownflare Securenet®

Turnsickle continues being as unpredictable as ever, and it insists that all Mozilla-based browsers have BigInt for their fingerprinting crap

This is all for now - this report ends here, Friday, February 7th 2025, 10:#2 VET

--10:32 VET

tomman: all as I have foreseen..

because it's bleeding obvious and has been for years if not from the start...

my issue now is .. i expected to avert it or not survive to deal with it.. I am obviously here still.. so yeah my status as some sort of mozoracle has come to an end some months ago .. can still follow certain threads but I have no idea what will happen anymore the trends are far outside predictability except extremely broadly should nothing be done

I do think there is a way to captialize on this split to perhaps isolate and push them into their bubble and then the free and open world wide web can expand regardless.. why? because WE ALL have been doing this long enough to deem ourselves at LEAST as much of an expert as anyone else.. There is still endless potental and possibilities in an Internet of Protocols and a World Wide Web of people not policies.. I say push them to the point where they

try and take it all and crush any opposition.. eventually others will grow tired of it and push back...

SeaMonkey is literally as old as the roots of Modern Mozilla.. and still holds a spark of the Mozilla Organization that same netscape spark that made them release the source code rather than let AOL eat it.

AOL I remind everyone never had any intention of using the netscape engine but Oracleizing it by parting it out for its relevant tech as AOL had deals with Microsoft .. so a Netscape based AOL was never going to happen and the AOL Browser another IE shell confirmed it.. AOL was part of Microsoft's Stratagy all along.. I wonder if anyone remembers that

in fact everything feels very 2002 right now

well 2002 by way of 1939

anyway

In any event, yeah they have split the web into people who love the web and people who sell and buy the web

digital manifest destiny and imperialism

well,MercadoLibre broke my search provider :/

wonder what these Argentinian clowns did this time

now searching with its provider from the search box on SeaMonkey just redirects to the homepage

gitlab wip updated

frg_Away: what's new in wip?

bigint by default and other stuffs looks like

yes. With activated BigInt it seems the startup scriptcache has a problem but despite the startup errors seems to not cause failures. Need to check but hopefully just ignoreable for the near future.

Still without optinal chaining and new regexp so not very usable despite some sites like ebay working better

^optional

UXP has long stopped bothering with the precompiled cache disabling it is now part of Pale Moon's standard build instructions.. I do belive this became the case because of bigint so if there is a solution for precompiled startup cache it will have to come from Mozilla

it is more trouble than it is worth that plus not actually clearing dist/bin as a delete job but by know file manifests are some of the worst hinderences to extension and some frontend ui development

There are two caches. I disabled the startup cache long ago. buc enabled it but not worth the few seconds startup time if even that much. Now need to look into the scriptcache too.

whenever I play with extension provided xpcom components such as working on DOMi I have to fight the cache and it only provides a small startup boost on new profile creation

oh there are

thought they were the same

Nope. There is also a child script and url cache left it seems.

First time after install everything is fine. The after later startp throws memory errors. Suspect might have something to do with the whole utf8 stuff changed.

hmm

artifical speedups like caches and async dispatched ui events really bug me leaves me feeling disconnected from the actual processing the program does

frg_Away: I have a question .. if mozilla xhtml can just use whatever html5 tags are implimented and we had a parser that worked fine .. why did there need to be a java codegen'd parser glued on?

ask mozilla :) I am a dummy here

since the html5 parser is just a glued in component .. not even a real component in the mozilla sense.. it isn't actually difficult to control

not that the xml content sink or when the htmlcontentsink wasn't gutted was difficult either

because it had xpcom interfaces

frg_Away: so it may or may not please Clownflare :D

now I wonder about the other weird problem I have with Turnstile: the one where the captcha box only renders when poked with the inspector

...and its elements don't even appear on the Inspect tab document tree

HeRe mE Am to savE tEh dAy!