?

I kinda wish we could federate jellyfin instances. Just manually, with friends I trust. Would instantly expand everyone’s catalogue.

How about only apply to non-FOSS software? Most hobby projects used not just by the author altend to be FOSS, and businesses can decide to go FOSS, making their software independently auditable by anyone, or go through certification.

I guess there’s a danger of a campaign to re-brand FOSS as “uncertified” then…

No :(

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?

OK I’m curious. Would I be allowed:

• my blood glucose monitor? (It’s dead weight without a device reading it, but it does have a battery and it’s glued to/pricked into my arm)
• a stand-alone device reading values from it? (Think esp32 with a shitty 1.4" display)
• since I don’t actually own that, my phone for the sole purpose of reading my blood glucose?

Ohhh that makes sense… Somehow… about Jeff Geerling. He always felt off to me in a way I couldn’t put my finger on. Guess now I have a proper reason not to watch him.

Also yes Alec is fantastic.

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

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.

!pferdesindkacke@feddit.org

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.

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

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?