What a jerk.
3,624 karma · joined March 3, 2013
https://simple.industries/about.html
If you apply the dogs on acid mental model it helps establish appropriate levels of trust.
A big concern with these (and other associated laws) being pushed through is it grants the eSafety Commissioner powers to edict what’s allowed.
That position is appointed, not elected.
Fixing something that’s visibly and publicly broken (or able to be sold) gets immediate praise. Preventing that issue before it occurs is thankless and invisible.
There are people doing that invisible work in every org. They normally become visible around a week after they quit.
They should never be network connected. Ever.
It doesn't matter if they are a domestic or commercial device.
Consider their usage in emergency response centres, situation rooms, infrastructure monitoring, meeting rooms in government offices, boardrooms at publicly listed companies, trading desks, or peoples homes as their source of news.
They have access to every pixel shown. They'll also likely have a full audio feed even if audio is passing through another system. You can have all the security control that you like on upstream systems, strong integrity guarantees, and comprehensive validation of that. This is the device where you are most open to exfil or tampering before it's shown to someone.
Even if the vendor isn't the one trying to actively exploit you they're almost universally running some form of incredibly dated, unpatched, and unhardened OS that is riddled with nightmare material vulnerabilities. Don't even put them on your IoT/untrusted network. If you need to control them, use CEC/DDC or a serial connection. Preferably unidirectional.
From personal experience, and as noted here, this approach is valuable for everyone regardless of age. In the short term it's far more efficient to learn by having the right way 'pushed' to you. However, by taking the time to fail, repeatedly, and eventually 'pulling' that knowledge the tacit understanding you build has a depth that's hard to shortcut.
Ah, I remember pre-parent life too.
On that note, this is a world I've recently taken a dive in to. I was about to roll a Pi Zero / ESP data logger to track distance travelled on my commuter bike for planning service intervals. Was keen on a solution that didn't involve draining a phone battery and remembering to start trips, a full bike computer, or smartwatch. After a bit of research I picked up a Garmin Speed Sensor 2 - highly recommend as a bit of stupidly effective tech.
The device straps around your hub and is essentially a coin battery and mems rotation sensor. In addition to running as an ANT+ peripheral it will operate standalone and log the last 300 hours of ride time then sync next time you open the app. Speed and distance is then inferred based on wheel circumference.
AU$25 (~US$18), or AU$7.70 (~US$5.50) with a concession card if you qualify for subsidy.
If you're in Australia it's worth a chat with your GP rather than less regulated channels.
The canonical example is ramps on footpaths providing equivalent benefit to people in wheelchairs, parents with strollers, and commuters on bikes, scooters or skateboards. The door width example you provide is another perfect case.
There are many aspects of things we design and build where a small focus of accessibility for one group brings benefits to many.
Any usage of short links can (and sometimes should) link to a canonical source with an immutable URI. This is just a foreign key for humans.
For those bringing that into modern telemetry stack I can't recommend Grafana Alloy enough (https://grafana.com/docs/alloy/latest/). There's a loki.source.syslog component that lets you ingest RFC5424 or RFC3164 format messages over UDP, TCP, and with mTLS. These can then be parsed, filtered, transformed, and routed to anywhere else you require.
If you're stuck with a device that's UDP only it can deploy to a nearby host (e.g. container runtime on a switch, or local ingest node), perform log collection, then queue and forward via OTel to central or cloud infra with encryption, delivery and integrity guarantees from there. It's a really neat and powerful tool.
> Operating systems aren’t really equipped to work with the user to ensure that a microphone stays a microphone, and doesn’t spontaneously turn into a keyboard that hits Win+R and drops a payload to steal all your data when the room is quiet enough that it can assume you aren’t watching.
In a world of USB-C everything we no longer have power supplies that are physically bound to power delivery, HDMI or DP display connections that have constrained data channels, or analogue mics, headphones, and speakers. Any device can dynamically change what it senses, does, or emits.
The other common mark you’ll see are leads which are two lights, one behind the other. The front is lower and the rear is higher. When they’re aligned you’re on the channel. These also have day shapes attached that provide an upwards and downwards facing triangle to align.