628
Fuck-up Assessment Form
(sh.itjust.works)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 12 Aug 2024
628 points (98.6% liked)
linuxmemes
21197 readers
59 users here now
Hint: :q!
Sister communities:
- LemmyMemes: Memes
- LemmyShitpost: Anything and everything goes.
- RISA: Star Trek memes and shitposts
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
2. Be civil
- Understand the difference between a joke and an insult.
- Do not harrass or attack members of the community for any reason.
- Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
- Bigotry will not be tolerated.
- These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
3. Post Linux-related content
- Including Unix and BSD.
- Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of
sudoin Windows. - No porn. Even if you watch it on a Linux machine.
4. No recent reposts
- Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.
Please report posts and comments that break these rules!
founded 1 year ago
MODERATORS
It happens to everybody, including Microsoft, Google, Amazon etc.
Actually, most of them have automatic cert renewal... in fact, most web services have that nowadays.
DNS at any company tends to be a mess. Multiply that by a thousand for a large multinational corporation. Case in point, here's Microsoft (and these are never going to stop, due to the sheer complexity):
Even when you use an automated service things can go wrong. For example I use Let's Encrypt but it needs to verify my DNS ownership so I use an API token to let the certbot make the modifications to prove that. At some point I wanted to restrict the token rights so it only has access to certain TXT records (to increase security in case the token every gets compromised). Long story short I forgot to include one wildcard and that particular certificate couldn't get renewed so it was out for the day until I fixed it.
Manjaro's website is made for presentation purposes and whether it's up or not has no impact on how the distro runs or whether you can download packages. Furthermore it's a completely different team from the distro developers so this has no bearing on the package quality. I've been a Manjaro user when some of the manjaro.org certificates expired but I never knew about it because it didn't affect me in any way.
manjaro.org uses Let's Encrypt now and it's been recently redesigned.