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.

We just rewatched The Dish and drank a glass to both Sam Neill and Tom Long.

The last time we watched, it was projected onto a bedsheet hanging off the back of my delivery van at Aileron Roadhouse in the middle of Australia surrounded by optical telescopes, a 2m “portable” broadband vSat dish, with the Sungroper solar car team during the 2003 World Solar Challenge … vying for the Yahoo! most remote internet cafe … we lost out to Mount Everest 😁

deleted by creator

My 10 mW signal was heard 13,945 km away on 28 MHz.

We’re going to need a lot of popcorn.

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.

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:

• What happens when you die?
• What happens if your house is burgled or catches fire?
• How do you protect against pe(s)ts making themselves at home in your server?
• What happens with a power or internet outage?
• What happens with hardware failure?
• What happens if you suffer dementia?
• How are you dealing with AI bots?
• How are you mitigating hacking attempts, security, authentication and exploits?
• How are you dealing with data corruption?
• How do you mitigate against ransomware having entered your systems?

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.

Did you try it?

Factory reset?

If you’re not getting spots, one common issue is time. Make sure that your clock is properly synchronised.

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.

I can’t wait to read the explosion of breathless media reports and “expert” commentary discussing the sudden spate of compromised ID systems and the subsequent finger pointing between politicians blaming each other for this entirely foreseeable outcome while the professionals who kept raising concerns have their uncredited “I told you so” moment.

Compliant with what?

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

Removed by mod

Removed by mod

Well, that was fluffy science reporting if ever I’ve seen in a long while, right up there with spaghetti grows on trees.

No mention of eaves, of double glazing, insulation in the walls, shade cloth, natural foliage, colours, types of paint, roofing materials, or anything else worth investigating.

Instead we’re reporting on a University that installed an awning, a black one at that, on a house and put heat boxes, fancy word for egg incubator I’m guessing, to simulate human heat, rather than actual humans who might live there.

Is this the Assumed Intelligence future we have to look forward to?

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.