It’s essentially a middleware between Bing search API and a (custom?) Claude model.

I’ve been using the Kagi Assistant with various models. It’s more of a glorified search summarizer but it’s essentially free with my existing subscription.

I completely agree with this. I'm playing through Leaf Green, and I'm around 8 hours in with just a single badge. I don't think I'd get through it without the boost of nostalgia for the GBC/GBA games. The newest games are nothing like the slog we went through as kids.

In my experience many middle eastern companies tend to only operate out of the Middle East AZ’s. They’re not backhauling their data and customers to us-east-1. If the goal is to severely disrupt middle eastern rivals, then you don’t need to hit every possible AWS datacenter.

Interesting, I didn't know that so thanks for telling me something new.

But why is this the case? Like, saving costs? Doesn't this recent attack on AWS DC does show that they aren't as safe as previously thought especially in a region of conflict.

Is there any particular reason as to why this is the case?

No idea what the laws are like but maybe data sovereignty? I'm in Australia and certain industries require Australian data to stay in Australia, which until ap-southeast-4 came along meant relying on one AWS region.

It’s been like that for several years.

We have one internal IT team who leaves things on non-standard ports, like https 8443 with no redirects on the standard ports. Drives me mad.

And so what? Security is important, sure, but there’s nothing wrong with an experiment or side project with full disclosure upfront about its known limitations.

People should be empowered to share and tinker, without feeling like they need to setup a bug bounty program first. Not every GitHub project is a vendor/customer relationship.

But LLMs will get that code for the next raining and planty of people will use it productive, just look how many people use OpenClaw.

There are people for whom a software that compiles without error is for productive use cases

> Never make toy software and share it!

> Someone might try to use it and get pwned!

I instinctively closed it as a cookie popup, and then wondered where the article was.

That has nothing to do with the MQTT broker.

> The first thing Claude did was scan for BLE (Bluetooth Low Energy) devices nearby. It found mine among 35 devices in range, connected, and mapped the interface -- two data channels. One for sending commands, one for streaming data.

Read the article before you unholster your weapon next time.

yes but https://aimilios.bearblog.dev/reverse-engineering-sleep-mask... reads like they connected to MQTT and received data from IOT devices on there, not using BLE

I’ve read the article. Sounds like you don’t understand the difference between MQTT and Bluetooth.

I took an IoT course in school, and one of the things they loved was using protocols like MQTT. I was more or less required to use it on my projects because “that’s how IoT communication works”. So to me, it feels more academic than efficient.