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.

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

Did they still not release the actual torrents though?

And why would they implement it in a somewhat private manner if it could be implemented in a privacy-infringing manner?

I honestly don’t think most democratic governments have an interest in making this privacy-infringing. Lobbyists/companies on the other hand… But all the more reason to write legislation that ensures age verification must be handled like this.

That already tells the government that I’m accessing porn because why else would I need to confirm I’m an adult online?

Cinema rickets for FSK18 movie? Ordering alcohol? Gambling? Renting a car?

Basically anything you’re only allowed to do as an adult.

But that’s kind of why I mentioned, it’s just one rough draft for such a protocol.

It should be Dot Dot! But it’s Dot Dot Dot! - sanest Bitchard moment

It’s mostly just that I don’t want the government to know precisely which websites I visit. Nor do I want the the porn sites to know exactly who I am.

I understand, I want that too. It’s easily possible though (just one example for a scheme):

• you visit porn site
• porn site sends your browser a random nonce
• you/browser tell government service: sign this if I’m >18
• government signs the nonce + a timstamp to prove freshness
• your browser forwards the result to the porn site
• porn site can verify signature per standard public certificate chains
• now porn site has proof that you are >18, but knows nothing else about you; and government only knows that you wanted proof that you are an adult, but not for what site or purpose you wanted to prove that

Alternatively, if we go the “device has an age bracket field browsers access” route, it’s even simpler, and just as if not more privacy preserving.

In that case: sorry to blow up on you. I have seen to many comments on here claiming these things while being 100% serious. I just saw your comment and incidentally had time to write the above for once, so, here we are.

I agree that there’s no way to completely cut teens off from porn. Your torrent example is perfectly demonstrating this.

But I also do not understand the current outrage at anything trying to improve the situation, even when it’s not some stupid “scan your face” scheme.