ItsHarper

I'm much less concerned about automated vote counters, as long as they are not connected to the Internet, enough ballots are hand-reviewed to make sure that the values from the machine don't seem way off, and the specific type of counting machine isn't uniform across the whole election.

Particularly where the machines are all of the same type or connected to the Internet. If

Cryptocurrencies don't need to do things like make sure that no human gets more than one vote, only humans (no bots) from a specific part of the world get a vote, and keep votes secret. Blockchain is not the solution.

I've started writing all of my scripts in nushell (unless It's critical that they keep working long-term without maintenance). It's incredible, and improving fast.

The underlying library (libpebble3) is open source, and Rebble has plans to fund their own app based on it. I plan to switch to that once it's ready.

In the meantime, I believe GadgetBridge is more limited, so I'm planning to stick with the official app for now.

Rust might be possible, but Kotlin Native has a GC, and definitely will not run on a microcontroller. Developing the tooling to allow writing a Pebble app in rust does not sound like something someone who has never even written rust would likely to be well-equipped to take on either, but I'm all for ambitious projects!

I wonder how much of it is inheritance, and how much of it is the parent giving their child lots of opportunity to explore their interest with them

It mostly hasn't worked in the US because cities mostly haven't been doing it. It seems to work great in other places.

There is an Internet permission, and GrapheneOS allows denying it to apps that declare use of it.

Without using Wireshark seems to be what they meant

That's how I started, but there's big advantages to workflows that are easy to mess up using got, but more natural with jj.

Doesn't mean that it won't exist in the future (I'm not sure if this was meant to be negative towards Signals efforts here)

The 60GHz heart rate sensor you're talking about (this one maybe https://wiki.seeedstudio.com/ha_with_mr60bha2) can be used with any microcontroller. It's got nothing to do specifically with ESP32, which is just one kind of microcontroller you can use it with.

I mean you can self host your own knot if you want, so it's at bare minimum possible to back it up if you're doing that

They do sell Spot, actually

Ironically, Evan You created Vite, though it looks like he hasn't been actively committing to it since 2022.

Languages with strong static type systems

PowerShell is so much clunkier than nutshell, which is truly a delight. Haven't tried murex.

I think the point is that fiber can have wayyyyyy more total bandwidth than any wireless technology, so you can afford to make your channels much larger (with more bandwidth). The only reason to make a channel smaller is to make room for a different channel.

I think it can be solved with timesheets and trusting that your employees are filing them out reasonably accurately.

I'd definitely include nushell in this

51820 is the one they use in the docs, that's probably the most common one.

Increasing the voltage doesn't require a thicker cable, and 5A power starts with 100W USB-C PD. USB-C cables that support 5A aren't that thick, but they do need a special chip so that the devices know it's safe to send 5A.

They have an open source userspace component.

I think they're hosting their own relay, so not really (besides did:plc identity resolution. Hopefully that can be made decentralized at some point)

did:plc is currently centralized, it's 100% reliant on Bluesky. Lookups have to be done at https://plc.directory/

The vast majority of Bluesky users use a Bluesky-hosted PDS.

dinit is another one with service dependency support

It's reasonable for a contributor to reject making their code available more permissively

It may not technically reassign copyright, but it grants them permission to do whatever they want with your contributions, which seems pretty equivalent in terms of outcome.