hacks.mozilla.org
ungoogled-chromium did not hang ...
hacks.mozilla.org
ungoogled-chromium did not hang ...
I never experienced this personally
>caused by Rust
So this is the power of ”memory safety”?
must have been like at 4AM in european countries, because I didn't see shit
This is what happens when you use GCP
>Makes major protocol change unannounced
Not even once. Use AWS
>ungoogled-chromium
dogshit.
probably when the stock markets were down at saturday
it's a flex from nobodys that don't want no real beef with people in power (the stock market)
idk i am still at version 72
>we quickly discovered that the client was hanging inside a network request to one of the Firefox internal services.
Good thing I use Librewolf.
what's state partitioning ?
Yes by default maybe install extensions and it will be just as good as any other browser
Thanks, testing Librewolf.
Is there something to do to keep full resolution display of the pages without disabling resist.fingerprinting ?
imagine not running debian stable
i have telemetry off so i was never affected
>browser hanged wordwide because it couldn't send telemetry and spy on people
You can't make this shit up.
>extensions can now fix network state partitioning
Go back
Telemetry and tracking is not the same, schizos
>State Partitioning is a broad effort to rework how manages client-side state (i.e., data stored in the browser) to mitigate the ability of websites to abuse state for cross-site tracking
See developer.mozilla.org
why does a browser on a private client depend on firefox servers operate?
Thanks is this the same as First Party Isolation?