And why do all the update messages sound like AI slop?

Looks like this was published recently. When I did research about 6 months ago there wasn't really much information other than a vague "you need to do mdns broadcast and a bunch of firewall hackery" at which point I gave up as it was not worth the effort.

Still not sure if it's worth the effort but at least there's a guide :)

Your post reinforces that feeling.

ESPHome or Tasmota work really well for all kinds of things. The last one I replaced was an infrared blaster for controlling my AC. The previous one, even though it was in an IoT VLAN decided to spam the network with requests to its mothership (never succeeding, fortunately).

That being said, without an antenna it is highly improbable that it could still find an open WiFi AP to connect to (especially if you don't have one in your house).

I've just reverted back to using that as it's faster to load and has all the features I need.

I've often had new phones that are 'faster' but I barely notice the fastness until I go back to my old phone and realise that my finger-memory needs adapting because things take just a bit longer to load.

I'd assume it's similar for screen refresh rates.

Github is so bad I don't even know where to start. It's fine for small personal projects and the odd project with a few collaborators. But it's just not built for managing large software projects. Even the PR process is awful compared to Azure Devops (and Azure Devops was, in my opinion, ok bordering on good). Diffs are somehow worse than any tool I've ever used.

I am now questioning what Microsoft has been doing all these years they've owned it.

I use unbound and have a similar question. Shouldn't we just encourage everyone to run their own resolvers (it's turnkey for the most part!)? Will Sony/beIn start going after the root servers and enforce a global block?

Anyone who's ever directed AI at a very large legacy code base will have noticed that AI just gets dumber and slower the worse (larger + inconsistent) the code base gets (just like us humans do). The big difference is that with AI you can get to the point where the code base is an unmaintainable legacy mess in a fraction of the time that it used to take. Directing architecture is the only way to mitigate this to some extent.

Since then they cut the price but the intelligence (of 6 and 6.1) has gone down to Sonnet 4 levels. I am back in a world where the model is lazy, cuts corners, ignores existing coding standards and context, makes stupid mistakes etc.

I am not sure how those models still rank so high in benchmarks when real-life usage is so obviously bad.

The only big memory guzzlers are generally proprietary software, like the unifi network controller software which basically requires an entire room of Cray supercomputers just to view your Wifi AP status.

This is something we've been trying to do for a while now and have not found a convincing metric.

Where do you live or shop that you are happy to take what is effectively a 3% pay cut for the privilege of having a slightly easier option to get your money back if someone charges you the wrong amount?

I assume because it has Python wrapper, the HomeAsstant integration can make use of it soon?

You often get flights sharing the same flight numbers such as JFK-SLC and SLC-SFO being the same flight number, even if it's a completely different plane doing the route!

Also super confusing when trying to search for your (or a loved one's) flight online as you'll get multiple matches.

I've never seen such a large degradation in intelligence in a model until I tried out Sol 6 after having used 5.6 almost exclusively for several weeks.

With Sol 6 I am back in a world where the model writes bad code because it is lazy ("You're absolutely right, I did not [do it properly] because I did not want to edit [a normal amount of files]").