

… and replace them with a whole new class of bugs.
Source: I’ve been writing software since 1982.
Anything and everything Amateur Radio and beyond. Heavily into Open Source and SDR, working on a multi band monitor and transmitter.
#geek #nerd #hamradio VK6FLAB #podcaster #australia #ITProfessional #voiceover #opentowork


… and replace them with a whole new class of bugs.
Source: I’ve been writing software since 1982.


And if you think that migration to Rust will magically remove all bugs and vulnerabilities, you haven’t been writing software for very long.


Excellent. Thank you.
Now look at the questions again and when you read the word “you”, insert “preludeofme”.
I’m asking because you’re also wanting to offer a service to customers.


That took significantly longer than 15 minutes to complete and most of the questions were mandatory, which both were explicitly stated otherwise.


AI bots will hammer your endpoints into the ground if left unchecked. They’ll happily compromise your services while they’re at it.


Here’s some questions:
Note that I’m not picking on you, nor is this list comprehensive or in priority order. I’m trying to determine if you’ve considered these common issues and concerns associated with hosting stuff that has great sentimental value, if not actual value.


Ssh access should be passwords only
What are you basing this on?


Yeah … voting around here is interesting from time to time.
On a positive note, I hadn’t heard of the Linux Security Audit Project, looks interesting, thank you.
I only briefly skimmed through the readme so I might have missed it, but I wonder how they’re able to claim compliance with specific standards.
It was my understanding that it’s typically a drawn out expensive process with a certificate to hang on the wall after the fact.


Compliant with what?
“Security compliant” is a completely meaningless phrase, right up there with “locked door” or “secret code”.


Perhaps Windows users are finally learning about privacy and hiding their identity.


An extra observation, if you’re doing QA and you’re running out of memory, there is a good chance that the actual users will experience the same issue.
If you’re running this inside Docker, you can specify exactly how much memory it has access to, which can also act as a data point for your QA process.


Puppeteer is the tool. It takes some getting used to.
You can set a bunch of triggers that determine exactly when the screenshot fires, and you can simulate mouse movement and scrolling to deal with lazy loading.
There’s even time delays that differentiates between human time and machine time, allowing you to have the software act as if it was running for longer than it actually was, which deals with other weirdness seen in web apps.
You can run it inside Docker which might simplify things for you.
I ended up writing a node.js app to control puppeteer precisely how I needed to.
Source: I spent 48 months or so using it for a project that required all of that.


Seems like a valid use of the technology…


That appears to be an earthed plug into an unearthed adaptor. They’re not supposed to fit.
Note, I’m not familiar with Italian plugs, but they look a lot like Dutch plugs which I grew up with.


The website has a heading proclaiming that apparently it’s a bad year for the Linux kernel.
I have to ask … compared to what … the Windows kernel?


Wow … so I can finally have root on my own phone?
Writing software is about problem solving skills which improve with practice. Often the process involves breaking down a problem into smaller pieces and breaking each of those down, until you know how to “solve” each problem.
Writing down each “solution” and stringing them together is then the actual “programming” part of this activity … which brings with it a whole new layer of “problems” to “solve”.
It’s as much art as it is accounting and the more you do it, the better you get at it.
Source: I’ve been writing software since 1982.