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 think the text is somewhat dubious in its arguments, but this (and the arguments built on this assertion) is just plain wrong:

[Signals servers have] a few important pieces of data;

Message dates and times Message senders and recipients (via phone number identifiers)

Signal clients implement the Pond protocol. As a result, Signals servers know who a message is for (obviously, how else do you get the message) but cannot know who it is FROM.

I’ve been playing around with implementing a secure/private messenger demo for myself, and have been consistently impressed with how privacy preserving Signal is when reading their papers and code. I wish it was selfhostable, but apart from that, it’s great.

The server would be NICE to be OSS, but ultimately, privacy breaches are prevented client/protocol side.

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, I assume? https://github.com/frida/frida That is indeed a bit eyebrow-raising. Though they do offer pre-built binaries.

Also for stuff like this, I can highly recommend the Nix package manager, even if you are not on NixOS. There it would, for example, just be nix run nixpkgs#frida-tools, from any distro.

But I know you’re not OP. Would actually be interesting what exactly they tried to install.

pip and cargo are not intended as (system) package managers. Your target package may of course have dependencies on them, but from the way you described it it sounds like that’s what you attempted?

This doesn’t make a call to government servers.

The app (or desktop application BTW, incl. Linux) reads your national ID’s NFC tag, once. When you need to prove your age, the app locally computes a zkp that only tells the site “at least 18yo yes/no”.

Note that every EU country has a form of national ID, and the digital capabilities of these IDs are already used for a bunch of stuff (e.g. taxes, bank account creation,…). This doesn’t worsen the privacy situation for EU citizens, but instead ensures that no privacy-unfriendly solutions emerge.

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.