Imagine if it was the cause!?
- 0 posts
- 17 comments
- martinb@lemmy.sdf.orgto
Selfhosted@lemmy.world•How to Setup a Secure Ubuntu Home Server: A Complete GuideEnglish
11 monthsFelt a bit like a faff to me, so I never bothered. Does depend upon your threat model though
- martinb@lemmy.sdf.orgto
Selfhosted@lemmy.world•How to Setup a Secure Ubuntu Home Server: A Complete GuideEnglish
11 monthsPasswordless login only. No root login. Fail2ban. Add ufw to stop accidental open port shenanigans, and you are locked down enough
- martinb@lemmy.sdf.orgto
Programming@programming.dev•Live coding interviews measure stress, not coding skils
11 monthsI did stress test interviews for DevOps positions. I explicitly told them that and gave them a task and a time limit. I would watch what they did and there was nothing out of bounds as long as they were solving problems. For example, I would give them an account in cloud provider and then task them with spinning up a k8s cluster with a few basic services and make it scalable, then watch and heckle as they googled around and brought up services. The objective wasn’t to complete the task though, it was too see how they approached problem solving. Good times.
I have never heard of lazy vim. Will investigate! Thanks
LunarVim is the lazy way forwards
- 1 year
Fair enough, it lowers the risk. Are you doing key stretching? Ie. X rounds of pbkdf or whatever it’s called?
- 1 year
I feel like saving the password in the export is a bad idea if security is your thing
Do not give them ideas
- martinb@lemmy.sdf.orgto
Programming@programming.dev•How do you directly interface with GPIO in Python?
2 yearsI recall that there is a USB GPIO dongle which gives you a bunch of pins to play with. You would have to hunt around to find it though.
Try Lunarvim, it’s neovim with a bunch of great Plugins and configuration settings out of the box.
No they were not setting standards. They were in fact breaking them. Their own standards were not disclosed, forcing competitors to actually have to reverse engineer them in order to try to have a chance at compatibility. The whole reason for the lack of uniformity was Microsoft fucking with the standards!
Secondly, the competitors did not have a significant market share. Thirdly, it’s funny that you mention in the context of a developer, given that they all complain mightily, even to this day, about having to support the festering pile of IE versions still around. Still, this won’t stop you telling, so you go do your thing elsewhere please.
No. I was just looking for an example of when Microsoft created standards for IE that other browsers could adopt, given that they were tied into IIS and undocumented in order to give them an uncompetitive advantage. Let’s also think about how they deliberately downgraded performance, or broke functionality on non Microsoft browsers, again for anti competitive behaviour.
They were called browser wars for a reason, and Microsoft is very well documented indeed regarding their fuckerry. But you go ahead trolling.
Microsoft standards?




You should be forcibly kept away from production systems…