He made a video not too long ago about old-school windows and some of the ways that they can be still efficient and beautiful. But the kinds of projects that he works on are not really "passive house" type buildings.

https://youtu.be/hLbTpa9uEoY

I mean, he puts vacuum-sealed glass on the performance version of the windows he makes.

That's even better as a product than triple-glazed windows.

I absolutely love watching Brent Hull videos and I am kind of shocked to see his page on HackerNews. For those of us who are into aesthetic design and back-to-roots craftsmanship, this is the guy to watch.

He had a video a couple of years back on this exact subject. https://youtu.be/cWX4PgCFk7c

Came here to see if someone realized it was the same guy who did the videos. Love his stuff.

Classical musicians fight a similar battle every day with Sony, UMG, and Warner filing copyright on every single piece of classical music posted online.

Could the artists band together, collect evidence, and create a class action lawsuit? Or is the juice not worth the squeeze?

Classical musicians are too poor in general to fight this.

That's presumably true for most class action suit plaintiffs, no?

I was just on a train from Paris to Genève and was looking for a map just like this!

Please do Les Halles next. I need that!

I still remember the modem string that I always used.

AT &F &C1 &D2 &Q5 &K0 S46=0

S11=50

IOS 17 also added HEIF/HEIC support to their browers, which IMO, is HUGE.

We also support HEIF conversion with `format=heif` parameter. It's not automatic though.

And HEIF are automatically converted to JXL for iOS 17?

Yes!

I’m not clear on the benefit of doing that. Won’t you end up with worse quality from the transcode and have equivalent file size?

Do give it a try! In our tests we found that sizes are smaller and encoding of HEIF takes very very long time. Remember, we provide bunch of other things like image resize and crop etc so we always end up encoding image again. Encoding in HEIF is very slow.

From what I remember, Firefox was basically neutral on it, and didn't want to extend resources to it if it wasn't adopted at wide scale. Chrome basically said that there wasn't much interest so they weren't going to put resources towards it.

The thing is, I wouldn't be asking for support if I was able to find a fix for my issue in the first place. ChatBots are unable to fix the initial problem because the system used to fix said issue doesn't already exist in the account tools. Human intervention is required to fix the problem, so therefore chatbots are completely useless in this context.

> The thing is, I wouldn't be asking for support if I was able to find a fix for my issue in the first place.

You are the exception though, the vast majority of people don't do that. Those are the users the chatbot is designed to help (because they represent a large portion of a typical support team's interactions).

In a way though, Apple tried to solve the problem with haptic feedback. What is completely lacking in all touchscreen controls these days is any kind of feedback. So Apple actually recognized the need for a feedback with touchscreens and invented a solution. Industrial designers didn't even try to "solve" this problem.