netol

This may be Safari-specific? Google recommends setting both: https://developer.chrome.com/docs/lighthouse/best-practices/...

About Twitter Embeds:

> These meta tags (and some other, less frequently used ones) were used on Twitter when generating link embeds. However, the documentation and card validator are no longer accessible (previously at https://dev.twitter.com/cards/getting-started and https://cards-dev.twitter.com/validator respectively). X falls back to the widely respected Open Graph meta tags, making the Twitter-specific declarations largely useless. They should be removed in favour of Open Graph tags. Further, they should be removed because X is an awful site with poor moderation that is owned by a man who publicly performed a Nazi Sieg Heil salute and has directly contributed to the rise of fascism in the United States of America and globally, among other horrors.

Ok but I believe `twitter:card` has no OG equivalent and still works?

Hola!

While I think this is mostly correct, I don't think it's OK to downplay climate change as just a "blame target". These current and extreme wildfires result from hotter and drier conditions, too. That is a major reason. And yes, we can do something about it.

Also, I know that controlled burns, grazing and firebreaks are widely used today in Spain, they are not universally forbidden.

The fact that Valencia and Barcelona are still not connected, for example

I agree, this was not a hack. It is combined behavior from documented features (preload with media and lazy loading).

Are you sure? I can see the image loading much later on mobile: https://pagegym.com/compare/uu5641qndi/4d3ifzdbxk

To not preload, yes

I could not find this hack documented or discussed anywhere, that's what I meant.

The XML/config side of things just isn't for everyone. Sometimes Go's simplicity wins out.

My dad does. He prefers older versions though (and he switched from FrontPage)

source code: https://github.com/JSLegendDev/sonic-runner

exa is abandoned. There is now a maintained fork called eza: https://github.com/eza-community/eza

There is also https://github.com/ChrisTitusTech/winutil, which works for Windows 10 too

In comparison, Meld is not stable, nor fast, especially for big diffs. The UI is also more limited. Araxis Merge and WinMerge are good alternatives

I also did something similar 14 years ago. It was a php website that allowed you to subscribe to online newspapers and get the news sent to your Kindle, in MOBI format. It worked but it was basically calling calibre under the hood. I never made it public (and I remember a similar website existed already at that time that did not work well)

> With mod_php, every Apache process has the PHP engine embedded in it, even if PHP isn't needed, e.g., to serve a request for a .css file. When Apache gets a bunch of requests for flat files, it forks all those processes and fills up RAM with copies of the PHP engine that aren't used. That's not only wasteful, but it dramatically increases the chances that you'll run out of memory. You can limit the number of Apache children of course, but you'll see timeouts sooner when you get a traffic spike.

Yes, that is true. But most high-traffic websites will cache static files such as CSS files and images, using a reverse proxy (e.g. Varnish, a CDN, or usually both). So I don't think this is a real problem, most of the time (99.9%?), a request for a static file will not hit Apache.

I'm not saying mod_php is better for all scenarios, of course, but I think it can be ok.

It's simple and there is less overhead. Since PHP runs directly within the Apache process, there is no need for inter-process communication (no TCP, no sockets), reducing the overhead. This can lead to lower latency for individual requests.

Nobody chooses the Beta for production. The Beta is used for testing. And it is not outdated.

I wonder how many xz-like backdoors could be in there.

I have a lot of respect for xz's original author, I just didn't think about the legal stuff, and that sounds quite reasonable to me now.

Personally, I find it hard to subscribe to certain theories, such as the possibility of Lasse being impersonated or involved in the incident. But that doesn't mean we should dismiss them outright at this stage. (And I'm sorry if you don't like to hear that, saying this is not comfortable for me either).

I fail to understand why this, now. For these minimal gains (compared to Brotli), servers and CDNs will need to increase memory and disk space to store the cached responses in zstd.

This makes sense

It is unfortunate that Lasse Collin has been silent about what he knows about him

It's faster to load images

No that many. It supports the most important ones though, and it is the fastest

Because it may be good enough. In my case, because I already maintain an instance of MariaDB in production, and I may prefer to share this that maintain another thing

Cool, thanks!

The part I'm missing is how these dictionaries are created. Can I use the homepage to create my dictionary, so all other pages that share html are better efficiently compressed? How?

This is useful, but note that with `table {break-inside: avoid;}`, if there are tables longer than the page, the browser will add a break before it, and that could be not desirable.

I have used, too:

    footer {
        page-break-inside: avoid;
    }

    summary {
        page-break-after: avoid;
    }

    body {
        min-width: 992px;
    }

Explanation:

- I usually don't want to break the page footer.

- Similar to headings, usually it is not desirable to produce a break after the summary element (for details element). If the details elements are never longer than the page, `details {break-inside: avoid;}`can be useful.

- Avoids rendering the mobile version of a page