Well, it seems it’s not fixed. :nard:

But browsers data usage for August 2022 are already available on canistop.net :ouaisouais:.

Show thread

The past 3 months, Can I Stop was late to notify you on Mastodon and Twitter because of a misconfiguration in the system handling the notification automation.

This _should_ now be fixed for the next one.

The scheduler was using PHP 8.0 process instead of the PHP 8.1 one, making readonly class prop crash (new in PHP 8.1).

And I (@meduz) was too lazy to dig into this issue before today, so I posted May and June tweets manually. :oscar:

Browsers data usage for June 2022 are now available on canistop.net

Can I Stop boosted

Browsers data usage for May 2022 are now available on canistop.net

If English is not your only browser language, Can I Stop now translates countries name, and even lets you search using that translated name!

So it means your options to filter countries are now:
- the country code (`jp`);
- the country English name (`Japan`);
- the country name in your own non-English language.

And you still can get several countries by separating any of the previous options with a coma (`,` ).

Can I Stop boosted

Opinion needed from people familiar with RTL (right-to-left) languages.

I’m adding a “countries name auto-translation” to @canistop (feat. `Intl.displayNames`). The whole UI remains in English, however.

Which of the following layouts makes more sense?

Browsers data usage for February 2022 are now available on canistop.net

Browsers data usage for January 2022 are now available on canistop.net

Browsers data usage for December 2021 are now available on canistop.net

Browsers data usage for November 2021 are now available on canistop.net

Browsers data usage for October 2021 are now available on canistop.net

Browsers data usage for September 2021 are now available on canistop.net

Can I Stop boosted

Just to give you an idea of how hard and expensive it is to maintain compat, here's a story from the trenches:

Once when I was on the MS Edge team (pre-Chromium), I was debugging a "perf" bug in a site. It showed an infinite loading bar; the site never loaded. Turned out the loading bar was fake – it was hard-coded to expect very precise timing for some JS timer function (requestAnimationFrame or setTimeout, idr) so it worked on Chrome but not Edge. The user was convinced Edge was just "slow."

Show thread
Show older
NintendojoFR

Ceci est l'instance du site NintendojoFR. Elle est réservée aux membres de la rédaction et à nos chers lecteurs qui souhaitent avoir un compte.