

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


Quick! Get this person a series A, B and C funding!
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.


Neovim, configured entirely through nixvim. I always liked neovim, but it’s never been as incredibly stable as now with nixvim.
Main/only IDE both in private and at work. Can’t ever go back, muscle memory has ensured that.


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?
If you use nixos, you basically have to know/learn/use day-to-day the nix language.
nixpkgs are written using nix the language, using concepts mostly familiar from just using nixos.
Basically everyone using nixos is capable of contributing packages.
Just gonna leave this here


rmpc is great. But TUI, so not for everyone, I know.


Real travel videos for niche places are so annoying to find now.
I’ve really been enjoying https://youtube.com/@ririregine
I mean, how can we feel superior if we are not wasting huge amounts of time setting things up!?
Why, by boasting that it’s so easy, just look at that, it is only two options you need to set thanks to the 80 custom modules I’ve written to abstract the abstractions from nixpkgs!
I WISH I could put an /s here, but I cannot.
Ehm… I’m also on Nixos and I’d say it’s super trivial.
services.openssh = {
enable = true;
settings = {
PasswordAuthentication = false;
PermitRootLogin = "no";
};
};
users.users.<name>.openssh.authorizedKeys.keys = [ list of pubkeys ideally read from file in repo ];
Eh, the machine is actually in one of my wireguard nets anyways, but for different purposes.
The nice thing about SSH key-based access is, I either have the key and login succeeds, or I have no business trying to log in.
That’s why my remote root server bans via fail2ban after a single failed login.
Yes I’ve had to write support to get a KVM. Yes it’s still configured like this.


LLMs will never be conscious.
Past me had a dick
Sorry, couldn’t resist.
Or TUI.


Nice, I was able to send an email to that.


No-one is forcing you to install Adobe software. Stop crying about other people liking choices.
Are you sure you aren’t either applying nixpkgs overlays, or following master instead of nixos-unstable? I’ve not really experienced anything like you’ve described.
Anyways - I’ve additionally built my own cache server, which builds every output of my flake every time I push to main. System updates are ONLY downloads now. Also allowed all of my low-powered VMs to auto-update, since they’ll never need to build anything at all.