EDIT: It looks like some people may have been using ghost.blog.cloudflare.com/rss because we used to use Ghost but the actual URL was/is blog.cloudflare.com/rss. We're setting up a redirect for anyone who was using the ghost. URL.

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

Fast forward and now I have 1GB symmetrical fiber-to-the-home.

Really nice to have that, but the leap from DSL to Starlink was life changing, the leap from Starlink to fiber was merely a minor improvment.

Then my rural power company saved the day by stringing fibre to EVERY single drop in their system. 1000 symmetric but really more like 950/800 but I'm doing fine, thanks.

I really think fiber is it for rural internet. They have the will to do it and it's rolling out all over in some states.

Previously was on the only local competitor without data caps, 6 mbps via DSL. All others are either cell or satellite based and would destroy my wallet at my usually usage (<=1TB/mo).

Starlink has been a godsend.

While this is usually a bit more bandwidth than I get, that isn't consistent and the ping is much worse. I pretty consistently get 50/15 with 15ms ping at about $90/mo after tax+fees. Based on some of the hype and press Starlink gets I assumed it would have had much better bandwidth, even if the latency is about inline with my expectations. Thanks for gathering and sharing this.

https://www.speedtest.net/apps/cli

works good.

  speedtest -f json -I eth0

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.

Content from news publications can't be viewed in Canada in response to Canadian government legislation.

https://www.terracestandard.com/wp-content/uploads/2023/08/3...

I'm excited about using ChatGPT/GPT-4 because it takes the time I need to figure out how to do something "easy" down from half an hour to sub-5-minutes.

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

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

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...

The default resize mode is cover and the blog post had a typo. Fixed now, thanks!

> resize or crop

We crop by default since the default mode is cover.

> gravity

we will be adding crop with gravity soon.. currently the crop is always from the center

> requesting an image at a specific aspect ratio while not exceeding a maximum size.

I'll get back to you on this one - Inian had to get some sleep, it's very late (early) for him

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

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

So basically not supported, and you have to go back to div hell.

There should be some future.js file that you can import to make all this stuff just work in older browsers.

I've been using if for months with no issues in cross-browser testing, and I haven't enabled any experimental flags.