A solid idea. There should be a package for this.

Instead of reverting the updates to appease those who've been ignoring the warnings, a way forward could be to gate the old API behind an environment variable, with a name like "TEMPORARILY_REENABLE_DEPRECATED_APIS". And maybe put an expiry on the variable so it resets occasionally. Otherwise the project just becomes mired and stagnant.

Because everyone is afraid of a v4, after the 2-3 debacle. And there are things which need to be culled every once in a while to keep the stdlib fresh.

Python is culling stuff all the time, but that doesn't warrant a major version jump.

You are probably right about Pythons careful approach of when to ship v4, but for the wrong reasons. Python 3 was necessary not for the removal of functions, but because of the syntax changes e.g., moving print from a statement to a method.

Actually dived into this a bit just a couple days ago. It's very near impossibly for there to be a conflict since the timestamp resolves at the microsecond level, and if it's among threads, then there's a global state that, if somehow it should be hit 2+ times in the same microsecond, ensures detection and the random portion is incremented.

How will a single press provide that much energy?

Piezo

It's a single press, which has to power the microphone for several seconds, and wireless connection to communicate with the sync device, even later if it isn't immediately available. In what way would piezo generate that much energy?

> BLE transmitter to trigger voice input on a watch

I suggesting triggering input on a watch, not voice recording on the ring. In my suggestion the ring would be a ‘dumb’ input device.

I see. However that misses the point of always having the function at hand, 24/7/365. There will be the off time when you remove the watch to charge it for instance, or times when it may be inconvenient to wear a watch.

Your use case would be another product, likely with a different audience.

Then you'd run into waterproofing issues, and there's greater inherent complexity in providing replacement ability.

Do you never take your watch off to charge it? Or to sleep? When showering?

Already a part of it. Recordings are saved (on the sync device) in case a transcript is a bust.

Yes, but they mention there will be a subscription plan for their cloud-based transcription. If you want an open platform of devices - ensure users can use a range of transcription providers for quality and security.

You have the options of using the transcription in the app, subscribing to their cloud service, or building out your own service that access the data via webhooks:

> I love customizing and hacking on my devices. What could I do with Index 01?

> Lots of stuff! Control things with the buttons. Route raw audio or transcribed text directly to your own app via webhook. Use MCPs (also run locally on-device! No cloud server required) to add more actions.

That’s awesome! I’m sold. Now can it fit a size 3 finger?

Even given that convention, with your example, a car is a far steeper investment than this ring. The more you invest in something, the more you expect to get out of it, and this ring is designed for a very low investment point, while still being highly durable (there are other similar rings out there at even lower investment points, but they probably won't survive anything beyond a sprinkle).

Point is to not having to take it off at all, as next thing is going out without it and losing that convenience. Though I guess they can also invent a finger-mounted powerbank for it; I remember buying a case with an embedded powerbank for one of my earlier Android phones...