I’ve delivered simple, clear and easy-to-use services for 20 years, for startups, scaleups and government. I write about the nerdy bits here.
— @joahua
Oh dear. I stumbled across this web address in today’s Sydney Morning Herald: http://www.nohsc.gov.au/
It’s actually the National Occupational Health and Safety Commission’s (NOHSC) website, but that in itself makes the link even clearer: The HSC poses an occupational health and safety risk, as is evident even in the URL of this organisation!
For that photo website at that elusive domain name.
And now for the important statistics! (Because I’m a pessimist ;-))
So… this means if you still haven’t uploaded photos, do so!
On another note, I’m thinking about implementing that upload thing Michael blogged about (or rather, linked to ;-) That doesn’t actually qualify as posting: you’ve still got a way to go before you redeem yourself for lack of that of late!) on the form to make life easier for people who don’t seem to be able to follow my pretty straightforward (I even made pretty screenshots!) “How to make a ZIP file” guide. Ah, technology.
So, I use a Dynamic DNS service to point the CNAME alias record home. on this domain to, surprisingly enough, my home Internet connection with Telstra BigPond (or puddle, whatever).
I’m using a Dynamic DNS service instead of just setting up an A record (much simpler, plus that would mean I could have a catchall on the domain… my current DNS host — also my registrar, Joker.com — doesn’t like wildcard CNAME records, though) because, theoretically, my plan only has a dynamic IP address prone to changing at any given moment. Dynamic DNS services really should only be used by people with dynamic IP addresses, for a number of reasons… the most obvious one being that they are designed to change, and expire if you don’t let them. (At least with DynDNS, which is pretty excellent for the price… free.)
With this in mind, I received this message today:
A hostname you have registered with Dynamic Network Services at DynDNS, sn0239410.dnsalias.net, with current IP address 60.225.85.25, will expire in the next 5 days. This expiration is due to an automatic timeout; your host has not been updated for 30 days, and hosts are removed after not being updated for 35 days. This is our policy to prevent a stagnant DNS system. Users with static IP addresses can use the Static DNS system, which does not have this timeout.
There’s more, I just can’t be bothered repeating it here.
That’s the fourth time I’ve read that paragraph in separate messages. That exact paragraph. Yeah, not even the IP changed.
To give that some time scale, see the quoted portion above: “hosts are removed after not being updated for 35 days”. I’ve manually touched my subdomain’s record once every 35 days or thereabouts for the last four months. Before that, the same situation existed, but then only for three months. Before that? Two. (And before that was iiNet, back in the day, and that doesn’t really bear commenting… every time your modem disconnected you’d get a new IP, and sometimes more often! Though it seems to have improved since…)
Seems to me as though Telstra is slowly and quietly making its dynamic IPs more and more static as broadband adoption picks up. So, Telstra, when are you giving us (mere plebs) IPv6?
A few weeks ago I posted about the image persistence problems that I was having with my Polyview V372 monitor. Well, Michael called me a few days ago and said that he had some friends who’d had similar problems with low-latency LCD panels (mine is 8ms), not of any particular brand, and that they’d successfully had them replaced.
Turns out Polyview’s Australian distributor, Protac, are replacing the panel for me. Even cooler is it’s an onsite warranty, so I don’t even need to leave the house. Good stuff! Anyway, they pick it up Tuesday (because I called yesterday and it’s a long weekend here in Australia… or at least NSW, the ACT, and SA), and it’s meant to take up to 14 days for a replacement to come… which will hopefully knock out the desire to procrastinate somewhat, as CRT displays burn ;-)
I posted several months ago on converting ACT files recorded on an MP3 player to something readable on a computer. It’s probably without competition the most-read and commented-on post on this site: there are many people out there who are looking for a tool to do this. And it seems that the ACT files generated by newer MP3 player devices aren’t compatible with the older convertors.
So, one of the readers, Phil “Mumbles”, discovered a tool that works for this stuff. He’s sent me the file after having cut it down from 8MB for a few apps to under 300KB for the just new sound convertor tool.
You can download it here — please post if it works or doesn’t work with your MP3 player/recorder so that other people looking for information on their device can find it.
One closing note from Phil:
and BTW,
It appears to hang if you don’t let it run its course (gives a not responding msg). the “hang” grows accordingly with the .act file size.
Cheers
Phil