This started off as a single file in my private nix config, to see if I could get it working at all. In that initial part, some parts were indeed LLM generated (esp. testcases based on my existing intents and failures).

When I noticed that this might actually work and be useful not just for myself though, I moved everything out manually, refactored and cleaned it up, and everything since has just been myself. I guess you’re still right though. I’ll see about adding a disclaimer to the README until I’ve gotten the chance to properly rewrite everything.

Huh, interesting. Does that work with wildcards like “put x on my shopping list”? Also, what are you using for that, if I may ask?

Sorry, I don’t quite follow 😅

What’s the problematic response?

Yay, that’s fantastic to hear!

Also, how’s your experience been with the PE? Getting a readymade device in a nice shell is appealing for sure 😅

Oh, in the demo gif, that’s via a shortcut (holding power for half a second). Sorry, can’t help with wakeword there 😅

Very cool. I’ll definitely look into that, and let you know back here :D

Glad to be of service… 😄

did you consider metaphone matching?

I did not even know about this. Sounds super interesting. Though it seems to be very language specific?

My original intent was to not rely on language specifics. But maybe we could just define additional steps in the pipeline for specific languages. Hm. I’ll have to think about this some more, but it might definitely be a great idea for a future version, so thanks for telling me about it!!

Have fun, hope this works out for you! FYI: you can also use an LLM as an additional fallback (first closest-intent, then on failure, LLM). README mentions it further down on Github.

Yeah. I think this is one of the best examples of letting nix do the hard stuff for you.

Neovim, configured entirely through nixvim. I always liked neovim, but it’s never been as incredibly stable as now with nixvim.

Main/only IDE both in private and at work. Can’t ever go back, muscle memory has ensured that.

I don’t really know, sorry :(

If you want to migrate, is going conduit - conduwuit - continuwuity (first version) - continuwuity (current version) maybe an option?

I went with continuwuity and am happy with it. Development happens at a steady pace, with sane priorities. The server is stable and I haven’t had any issues to speak of, despite one minor bug that got resolved very quickly after creating an issue.

This is the one true answer.

Just an IP, nothing else. And easily curlable.

If you use nixos, you basically have to know/learn/use day-to-day the nix language.

nixpkgs are written using nix the language, using concepts mostly familiar from just using nixos.

Basically everyone using nixos is capable of contributing packages.

Ah, sorry. https://repology.org/repositories/graphs

Just gonna leave this here

Not arguing that. Of course there’s worse things.

But you must also acknowledge that it’s trivial to make this a non-issue. For example, I’ve seen lots of places where the door opens outwards with a kick. Or, even better (if slightly less space efficient) just have no door at all, and instead a short entrance with two 90 degree turns.

I think this is something that more and more places do anyways, basically any modern-ish place I’ve been to in recent years do the no-door-thing.

So? Like a their to half of people (sorry don’t remember the stat, just remember being shocked how high it was) do not wash their hands after using public toilets.

Why would I want to touch that doorhandle.

Definitely, yeah

• German (native)
• English (pretty well I hope; half my working life and almost all my free time spent on the internet, shows, books,… has been happening in English since, like, 8th grade)
• Japanese (learning; enough for talking about food, the weather, hobbies,… in somewhat acceptable grammar 😄)