

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?


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.


That ks for sharing this, this is fascinating.
Maybe the underlying rule is: the more you know about something, the more you are aware of its flaws, making the alternatives you know less about more attractive?


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, 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?


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):
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.


I’d also like to think so. In this case though, this was clearly not what was intended, and also involved a lot of porn.


So let me get this straight:
When I was 13, I managed to figure out the router password, disabled child protection for myself, then watched porn on my Android 2.3 phone that I had managed to put a custom ROM on because I liked the way it looked and had no idea what a “launcher” was yet.
This is not a hypothetical btw.
My parents were smart enough to enable appropriate blocking and secured access to those settings. I’m not sure something on-device was available at the time, but I included the bit about the custom rom to demonstrate that, even though I didn’t know WTF I was doing, I was more than capable of fucking around with the tech to get it to do what I wanted.
So were my parents in breach of their duties on child protection?
I don’t think they were. They actually did educate themselves (visiting a course / parent meetup to discuss and learn how to protect me from the Internet), and implemented everything they learned.
I was just a little shit and found a way around this.
And this is NOT an edgecase. Because guess what. It takes one kid in the friend group to figure out a way to circumvent parental controls, and then EVERYONE knows how to do it.
It simply does not fucking matter how well intentioned, knowledgeable, and present the parents are (mine were all of that).
Going “this would not be a problem if parents parented” is the LAZIEST fucking excuse, and I’m sick and tired of reading about it on here.
(Because I probably have to make it clear: I’m not advocating for photo/passport scanning, third party age verification,… and all that bullshit. What I think would be a FANTASTIC idea would be privacy-preserving age verification. There are two good ways to do this: 1) on a login attempt, prove that you are of age by presenting a fresh, signed token from a government service proving that you are over 18, and nothing else; site does not get any info, government does not know what you were trying to access; 2) a device-level age field. Proof here comes from the device itself, and can be 100% privacy preserving; just a “yep, is of age”. In this scenario… GUESS WHAT, PARENTS GET ENABLED TO PARENT “PROPERLY” BY PROVIDING THEM WITH A GOOD, SIMPLE, PRIVACY-PRESERVING TECHNICAL SOLUTION.)
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.