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

Is it safe to get multiple chips? They’re about the size of a grain of rice, so it shouldn’t be too unwieldy to get chipped from a couple of different vendors at the same time. With a chip, GPS collar, maybe an AirTag, that’s about all you can do besides lots of training.

The chip will still be working after 24PetWatch is gone, you can enroll the same serial to more providers i.e. AKC Reunite.

Or your city when you register your pet

there's no point in getting another chip. the existing chip will still work, you can just register the data with another database.

Why do websites constantly insist on having small gray on white background text, stretching 160+ characters per line? Practically impossible to read on desktop. I wish people would think about default readability. Even Microsoft Edge’s reading mode barely made a difference.

An Easter egg, in the context of computing, is a hidden feature, joke, or message included by the developers. An example is the Konami code in video games.

Back tap is a legitimate accessibility feature, documented and searchable in the settings app. Just because you didn’t know about it (introduced in iOS 14 according the link) doesn’t make it an Easter egg.

I’m on a project at work replacing our R430s and R730s. They’ve been absolute tanks with very few hardware failures. That said, my company chooses to have OEM support for replacing failed components and keeping firmware/bios/idrac updated. You can absolutely run these if you’re OK with 3rd party replacements or parting out spare machines. Some industries are more tolerant to this than others.

I ran 3x R620s 24/7/365 in my homelab for ~6 years (well, other than when I moved, or shut one down for a clean-and-inspect, or lost power in excess of what my UPS could handle... thanks, Texas). The only things that failed during that time were a couple of sticks of RAM, and a PSU.

Being able to read some iteration of potential source code doesn’t make it open source. Licensing, copyright, build chains, rights to modify and redistribute, etc are all factors.