Ugh, poor error reporting is such a frustrating time sink.

I was simply pleased by your comment, to see how much you care about helping folks and moving the community forward. Seems like quite a lot of effort to me, far more than I’d be able (willing?) to contribute, and I’m just forever grateful for folks you like you and wanted to say something about it :)

I appreciate the invite. I’m not at a point currently where I can put sincere effort toward much that’s non-essential, but if that changes, Rust is on my short list of targets for ways to spend some spare effort and time.

Welp, YOU’RE frickin cool, kudos!

Cool thanks! I haven’t tried it for troubleshooting, I’ll give that a go when I next need it.

Are you using one integrated into your IDE? Or just standalone in a web browser? That’s probably what I ought to try next (the IDE end of things). I saw an acquaintance using PyCharm’s integrated assistant to auto gen commit messages, that looked cool. Not exactly game changing of course.

Do you feel like elaborating any? I’d love to find more uses. So far I’ve mostly found it useful in areas where I’m very unfamiliar. Like I do very little web front end, so when I need to, the option paralysis is gnarly. I’ve found things like Perplexity helpful to allow me to select an approach and get moving quickly. I can spend hours agonizing over those kinds of decisions otherwise, and it’s really poorly spent time.

I’ve also found it useful when trying to answer questions about best practices or comparing approaches. It sorta does the reading and summarizes the points (with links to source material), pretty perfect use case.

So both of those are essentially “interactive text summarization” use cases - my third is as a syntax helper, again in things I don’t work with often. If I’m having a brain fart and just can’t quite remember the ternary operator syntax in that one language I never use…etc. That one’s a bit less impactful but can still be faster than manually inspecting docs, especially if the docs are bad or hard to use.

With that said I use these things less than once a week on average. Possible that’s just down to my own pre-existing habits more than anything else though.

Not nearly as big a story as it seems:

• all existing users (and anyone who makes an account before Aug 21) are grandfathered into the free model forever
• the app is really a secondary feature altogether and pretty unimportant; I use my Anova sous vide plenty and have not once felt I wanted to use the app

This honestly seems pretty damn reasonable. And for just about anyone with enough disposable income to be cooking sous vide, $2/month (or they offer $10/yr!) is almost certainly no more than a rounding error.

What I don’t get is why (and how) they’re talking about disabling Bluetooth, that was mentioned but not really discussed or justified. I do have a big problem in principle with any situation where I’ve bought something, and without my consent the mfg changes it to remove functionality. That should be explicitly illegal (with maybe exceptions for true safety issues).

Excellent work, and thank you for sharing. What a win! I’m always heartened to hear about straightforward open source wins against leeches 👍

KenM? You made your way to the lemmyverse?