Is there actual REQUIRED upkeep though or could you say fuck it, and go ashore with a tent, row boat and the freshwater and food required for a week?

Quick! Get this person a series A, B and C funding!

Outside of a massive sorting facility in every supermarket generating no value for the store owner

We already do exactly that for plastic bottles in Germany. You pay 5-30ct premium on each bottle and get that back when disposing of the bottles in the sorting machine. Participation is close to 100%.

For glass, it at least gets sorted into white/green/brown glass to make recycling easier (not in the supermarket though, just containers positioned in residential streets / recycling centers).

Yeah Librewolf is amazing. I dialed some if the ootb settings back for usability, but all the “new” stuff Mozilla adds is filtered right back out upstream, so I never even see it.

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!)

How about take turns.

Yeah. Out of curiosity though, how far did you get into it?

(Not that it gets better in this regard or anything)

Well, no. Hopefully NOT the same shit.

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.

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.

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”