LukeLambert

  speedtest -f json -I eth0

https://gist.github.com/LukeLambert/dd722e49bc773bcb27e859d9...

If the publishers don't want their photo, headline, and first sentence or two appearing without payment as a rich preview on Facebook, well ok. I think it's a stretch, but I can at least see their perspective. It's worth noting that publishers are already in control of that preview with Open Graph tags.

However, if they want to get paid for an unadorned <a> tag, that completely goes against the spirit of hypertext.

  <link rel="canonical" href="https://www.twintown.com/collections/acoustic-guitars"/>

  javascript:prompt('URL',window.location.origin+window.location.pathname)

I believe all resizing operations a user might realistically want can be achieved with three parameters: width, height, and crop. Additional x and y parameters (floats between 0.0 and 1.0) could be used for setting the focal point of the crop box.

Examples:

  source.jpg?width=400

  source.jpg?height=300

  source.jpg?width=400&height=300

  source.jpg?width=400&height=300&crop=true

However, it's unclear from the docs [0] if one of the most common use cases is supported: requesting an image at a specific aspect ratio while not exceeding a maximum size.

For instance, I want a 1600×900px hero image at the top of my blog posts, but my source image is only 1200px wide. I request:

  transform: {
    width: 1600,
    height: 900,
    resize: 'cover'
  }

A few more notes:

The blog post states "default mode maintains aspect ratio and the resize mode is fill", but the docs say that cover is the default mode.

The docs say, "If only one [width or height] parameter is specified, the image will be resized and cropped, maintaining the aspect ratio." I believe that with only one parameter, you could either resize or crop, but not both. I hope it's resize.

For cropping modes, is it always from the center? Are there plans to support other "gravity" modes?

[0] https://supabase.com/docs/guides/storage/image-transformatio...

  div {
    width: 640px;
    aspect-ratio: 16 / 9;
  }

[1] https://letsencrypt.org/docs/challenge-types/#tls-sni-01

fit=cover will return a square (as requested), but will enlarge it (which you never want because it wastes bandwidth).

fit=crop will cut off excess pixels if either dimension exceeds 512, but it does not always return a square. (And contrary to the docs, it does not behave like fit=scale-down.)