diggernet

Unfortunately, even at a descent rate of 30,000 feet per minute you've got a full minute to anticipate the impact before you don't feel it.

Back in the day, the industry was run by computer enthusiasts who saw computers as an amazing tool to improve lives and enable and empower people. Today the industry is run by money enthusiasts who see computers as an amazing tool to extract money and manipulate and control people.

Never byod. Besides MDM issues, it makes your personal device in scope for discovery if any lawsuit against the company.

Fences can be made out of the tree that fell. Even post holes are optional. Only thing you need to pay for is some cheap wire mesh, and that may be reusable for repairs.

2.009 appears to be some kind of class id. The actual class discussed was in 2017.

That's my main problem with Thread. With Zigbee I have confidence that the mesh is 100% local and offline. How do I get that confidence with Thread? How can I really be sure that something isn't helpfully opening it up to the world?

They are an invasive species in most of the world. Wiping them out is restoring the ecosystem.

Oh good. Then Google will be "clean", while countless homes will be getting their power from coal or whatever instead of this nuclear plant.

Why didn't you tell me about this years ago?

Nice to learn about Traffxml, but that allows taking in traffic data from where? Seems like there would need to be some service consolidating traffic reports from users of various map apps.

Not really. I imagine a sqlite db, but I haven't thought about any particular schema.

Yeah, there are all kinds of interesting things that can be done with shared data like this. But the first step is to have some standard ContentProvider to let apps share the data locally on a single device, similar to how other user data is handled. Because I'm tired of having several map apps installed for various reasons that all have separate favorites.

Once that is in place, people can create apps that build on it in lots of different ways.

Thanks for the reminder that ContentProvider is the Android term I couldn't remember when I wrote my other comment here.

And the reminder that I should have added this to my list:

3. A ContentProvider app for OSM map data, so that apps can share the same offline map data.