Thanks, I’m very happy to hear that!

!pferdesindkacke@feddit.org

I actually have things like “play x by y” functioning really well without a LLM.

Have a custom service that exports all song/album/artist names from MusicAssistant, does some simple cleanup, and places the list where HomeAssistant expects it for custom voice intents. Then this: https://github.com/charludo/hass-closest-intent is enough that imperfect STT can still easily be matched to those song/artist/… names.

I’m just gonna shamelessly plug my project here: https://github.com/charludo/hass-closest-intent

You do need local STT, but it’s fine if it’s somewhat bad; the conversation agent linked is sufficient to “get” what you meant, without LLM.

Stop moving the goal post. To process satellite images, you need way, waaaaay, waaaaaaaaaaaaaaaaay less compute than for AI datacenters. We are not arguing about image processing for a single satellite. (Which is still jot a great idea, ideally you’d want to improve throughput instead since you still want the raw images for people to work with, just faster, no?)

No, what you were talking about were data enters for AI (no, you didn’t say AI, but that’s what everyone on Lemmy says is a bad idea in space, and you were referring to everyone on Lemmy, so, we are talking about AI data enters in space).

• putting them in space doesn’t make them faster.
• putting them in space is incredibly expensive
• cooling them in space is way harder than on earth; radiating heat away is a function of the surface area of the cooling modules, and you cannot escape that
• maintenance (remember - things fail) is way harder and astronomically expensive and slow
• and, thanks for reminding me, sending AI output to and from is subject to the same slowness as for images from telescopes

Sorry, “data-center in space” is a stupid idea. Musk yaps about it because a) he’s an idiot and b) enough investors fell for it

Datacenters in space are a supremely stupid idea.

I know that this makes me fit exactly with what you were describing; indeed I’m not rejecting your premise, I just think you’ve chosen a hilariously bad example to demonstrate it.

But… That would force them to provide a great user experience in order to retain users!! That’s an unacceptable burden on the largest companies in the world!!

Yeah. Honestly. For platforms like Instagram, Facebook, TikTok, mandate chronological feeds of only people you have followed, paginated at like 30.

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

They saved lifes.

Glad to have cleared that up for you 👍

It’s just a helper. It’s a way for your calendar to ask “uhhh… Should I already know of any calendars…?” and the service going “oh actually yeah, the user configured their email account, hold on, here’s the corresponding calendar”.

That’s just basic functionality. Maybe what’s tripping you up is that it’s a separate service? Because I assume you have nothing against inputting your email into a mail client and a calendar separately.

If so, then for one, it’s not really a difference if the mail app stores this into or the service does; and second, it’s a good thing to have this standardized into a single purpose built service, rather than having each app reimplement this stuff.

CPU and RAM usage is so negligible it’s laughable.

IDK.

It seems like you read something about personal data in the service description and just jumped to the conclusion that this is something nefarious.

How exactly is it bloatware though? Not a KDE user myself, just had a look at the wiki. Seems it’s just a convenience utility to allow you to not have to enter the same things into multiple applications?

This is VERY different from pre-installed apps in your start menu that collect and sell info about you…

Yeah, thinking more about it, I don’t think the term “bloatware” (as it is commonly used) applies here at all.

How do I completely disable it forever?

To answer your question: sudo systemctl mask <servicename>.service

The much more common disable just disables autostart; masking will point the service file at /dev/null, which makes it impossible to load or start the service, even when other services or apps (like the clock widget someone mentioned in the comments) request it.

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.

“Gabe the Diver”

Also, hard disagree.

“average 50-59 year old weighs 5000 pounds” factoid actually just statistical error. Average person weighs 150 pounds. Pounds Georg, who lives in a cave and weighs over 50000000000000000000000000 pounds, is an outlier adn should not have been counted.

Add “linux” and enjoy the empty feed

Awesome!! And thanks for actually letting me know! :D

Edit: anything for the wishlist?

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.

Yes, you can! See the “threshold” value/slider. It’s at 0.7 by default, which seems to be a good tradeoff. 1 means exact match or failure, 0 will afaik match anything to everything.

Ah, I didn’t see the Edit, so we’re both in the same boat 😂