They hit all the right Node(j)s!
- 2 Posts
- 34 Comments
Joined 2 years ago
Cake day: June 11th, 2023
You are not logged in. If you use a Fediverse account that is able to follow users, you can follow this user.
10·9 days agoFor anyone wondering what “TDS” means:
Trump derangement syndrome (TDS) is a pejorative term, used to describe criticism of or negative reactions to President Donald Trump that are perceived to be irrational and to have little regard for Trump’s actual policy positions.[1] The term has mainly been used by Trump supporters to discredit criticism of him, as a way of reframing the discussion by suggesting that his opponents are incapable of accurately perceiving the world.[2][3] Some journalists have used the term to call for restraint when judging Trump’s statements and actions.[4][5][6]
Despite the usage of the term syndrome suggesting a medical condition, TDS is not an official medical diagnosis.[7] A 2021 research study found no evidence to support the existence of TDS among Trump detractors on the left, but instead found bias among his supporters.[8
GitOps + Renovate.
Tools that allow you to work GitOps (everything is defined in text files in Git) are:
- Kubernetes
- NixOS
- to a lesser degree, Ansible
Here’s a nice starter template for running your own Kubernetes cluster via GitOps with Renovate pre-configured: https://github.com/onedr0p/cluster-template
Mostly yes, but there are some closed source services which are still good options for this specific threat model.
And I just thought the clear explanation of the why combined with the list, makes this an excellent blog to send to people who don’t get it yet.
The list itself is something most of the people in this community know already, but you might want to send this when someone asks “why?”
31·14 days agoUndervalued comment right there. This is better than the OP
Took a look at the specification, this is what I found:
For federated servers performing delivery to a third party server, delivery SHOULD be performed asynchronously, and SHOULD additionally retry delivery to recipients if it fails due to network error.
So they should retry. Note that should is not the same as must. So there is no obligation. There is no timeline in the spec about for how long or how often retries should be done. The wording says network error.
My interpretation: the spec leaves a lot of room for implementations to differ. Network problems don’t normally last for days though. I’d guess that if your server is down for 5 minutes, you’ll still receive most or everything you’d normally receive. I wouldn’t trust on that if your server is offline for more than a day.
Yes, I test in production and so should you
- Charity Majors
Animals are individuals, servers are cattle!
The Vegan GitOps lifestyle
Check the sidebar.
It’s about self-hostable alternatives to closed online software. It doesn’t say anywhere that the hardware has to be in your own home, just that it is about self-hostable software.
Similarly, !selfhosting@slrpnk.net is about self-hosting services, the hardware part is (even with the slrpnk folk) only a prefetence.
So feel free to discuss hosting your own services on a VPS here
Of course we all have our preferences and personal history with these things, but I think we can all agree that most preconfigured Debian, Ubuntu, Fedora and openSUSE ISOs with popular desktops are already more sensible and simple than the mess that is “searching for a setting in Windows”.
Whether it’s GNOME, KDE, Cinnamon, Budgie, Mate, XFCE, LXQt.
Compared to Windows, every Linux desktop is a blessing. Even that one that you personally don’t like or had a bad experience with.
Windows XP… such expressive, truly material-like, design, only Vista comes close. But XP ran so much better.
Good point. I guess you’re right, there are no flattering roles. But each of those options you list would have been less on top of existing prejudices.
Making her the (non-technical) project manager whose only contribution is “how many story points is that?”, who’s then silenced because “this is important!”, confirms the typical prejudices about women in tech:
- no technical expertise
- is not in charge
- does not have anything to say that is worth listening to in times of crisis
Especially being talked over. This matches many women’s experiences in men-dominated environments to a T.
I’d much rather the technically competent, important but socially weird engineer (Jared) be the woman, or the incompetent boss, who’s in charge and calls the shots. Even having no women in the skit would be better than this Cindy role.
Or, weird idea I know, multiple people with different roles being women. 🙄
We all get frustrated with scrum at times, but not all of us use TTS to make a casually sexist skit about it.
Unlike most houses, in mine the Fox won’t change the default browser.
And since we’re on the topic, if we’re borrowing things from Android I would love to have the application sandboxing and permissions. I think they’d be a much bigger benefit – to all distros, immutable or not.
Flatpaks and Wayland should fill out this part nicely.
I’m guessing this refers to the not entirely separate groups of Nix(OS), Haskell, XMonad fans
NixOS - Queer kid who gets 10/10 at every written test, but stutters so badly that they can’t do anything when asked to improvise in front of class or at speaking tests.