Worse than just taxing them properly.

Most correct answer possible.

• Insulin
• Sourdough Starter
• An SSH private key that might come in handy later

You killed him! NOW IT’S JUST “Lake”!

Lmao this is fantastic, thank you.

• MuseScore 4 is a (the!) free music notation software. It is genuinely fantastic. It’s also a lot of fun, if you know some notation basics and want to play around.
• Darktable is a Raw photo editor in the vein of Lightroom. Except where lightroom is sleek, polished, user friendly and Adobe (🤮), Darktable is FOSS, and clearly so both in the design and functionality: it could easily make a UX designer cry, but if you’re willing to give it a try, there does not exist a more potent raw editor on this earth. Lightroom is a toy in comparison. (Now whether you need that is another question… But I’ve been using it for more than 10 years, and am still finding new, incredibly useful sub-menus, drop-down contexts on hidden sliders,…)
• rmpc is a really cool TUI music player

1. Signal
2. XMPP
3. Matrix

In that order. I self-host both XMPP and Matrix, and I wouldn’t want to stop using matrix. Spaces, arbitrary amounts of self-chats, and so on are great. I use matrix every day.

But for chatting… It sooner or later fails you. It’s slow. Notifications break. Messages are shown as sent, but somehow do not appear in the recipient’s devices until TWO WEEKS LATER (yeah IDK, happened twice already, in different chats and directions. Best part is, I’m not even federated!). Encryption is great IF YOU KNOW SOME CRYPTOGRAPHY BASICS, and utterly confusing otherwise.

XMPP just works. Especially the calls, holy shit, I had to fight Matrix for so long to make voice and video calls work, and xmpp just… Works. Notifications are way more reliable (as in, have been absolutely perfect). I really like monocles as a chat app on Android. (The downside is: can’t decrypt old messages on new devices, and desktop clients are ugly.)

So why Signal above XMPP?

Because it’s not your fault should something ever break in a vital service. Also the encryption and privacy afforded by it a great.

I’ll second Pocket-ID.

I originally had Authentik setup. It worked well enough. However, their packaging constantly broke and no-one seemed to care.

Switched to Pocket-ID and won’t be looking back. Passkey-based OAuth was all I wanted anyways. (Also, the logins themselves are noticeably faster!)

Burden of proof is on Astrology claiming to be real.

• AI bad
• Astrology 100% superstitious bullshit

Yeah, like 3-4x/week.

This includes things like train tickets, because I refuse to have to have my phone with me.

Sheet music, shopping list, letters to doctors/government offices/…

I feel like one could legitimately run on this platform at this point.

No

That’s not a physics statement btw. I just think that you, personally, are too slow to be able to do that. Offense intended.

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.