amstan

I can't tell if any of this gives you more access than the normal http admin interface.

On the other hand, my local qwen model (3.8-flash-next) was trying to convince me that the eMudhra CA thing is no big deal since you need to be "positioned correctly" (eg: any wifi network) to be able to MITM, and most of the IOT devices would have patched stuff by now.

Are you sure the models did not have your exact solved proof already in their dataset?

One thing that i see often: just because both your debug cable and your target runs at the same voltage (eg: 3.3V), doesn't mean it's safe to plug them together. You could easily have a situation where your target or your debugger is off, so at that point you're powering the off thing through the uart pins (the esd diode on the pin).

The safest thing is to have a 4th vref/vccio pin, then the debugger should power its tx signal from that pin, at whatever voltage it's at. Same for the RX pin, it's not nice to have a pullup to a certain voltage when the target is off.

you should try vulkan instead of rocm. it goes like 20% faster.

Ah yes, because "How now the smart flies take the new time beyond new time where new times come." is so much easier to remember than "2001:db8::1".

I want my time back :D . Here I was picking things that i liked the most, and it gave me Ubuntu Mono, a font I already have selected in my editor.

Yeah, it's worse, half of the devices on that list are peripherals that cannot be flashed with any firmware.

4 times, you forgot the owner of the bot that did the PR.