Tomorrow – (in Australian time at least) – is the 40th anniversary of the first flight of NASA’s Space Transportation System (STS) – better known to most people as the Space Shuttle.
That first flight was taken by OV-102 – (named “Columbia” at the time of commissioning) – on April 12th 1981, and marked America’s return to space for the first time since the Skylab space station was abandoned in 1974.
So it was a big deal. I clearly remember watching the launch on television at our home in Townsville, and the subsequent regular updates. For someone who was interested in the space program, but not having been alive or old enough to remember Apollo and Skylab, people in space again was amazing to me.
Astronauts John Young – (the ninth man to walk on the moon) – and Robert Crippen took Columbia into orbit that day for what amounted to a test flight – launch it, get it to orbit, and land it a couple of days later.
Columbia was of course lost in 2003 on return from space while completing STS-107, only the second shuttle lost after Challenger just after launch on STS-51L in 1986.
$access_token – this is the same as your existing OAuth application access token – this has not changed, at least in my case.
$group_guid – this is the only new piece of information you might need. While you can query for this value via the API, for most people the simplest way to get it is to open into your Bitly account in a web browser, where you will find the GUID in the URL, as per this image:
$shorten_domain – if you have a custom domain – (for example, I have the domain “mwyr.es” for shortening purposes) – this is the value you need here. If you don’t have a custom domain, just use “bit.ly”.
$shorten_url – this is the URL you wish to shorten – simple!
So now you can call the function, with the required information.
Firstly, the input data required by the API is converted to JSON via the json_encode() function.
Secondly, we set up the cURL handle, and then supply it with the required data. Note the JSON data is passed within the “CURLOPT_POSTFIELDS” variable, and that the access token is passed as the “Authorization: Bearer” header in the “CURLOPT_HTTPHEADER” variable.
Then we execute with curl_exec() – and store and return the results for further processing.
To understand the returned JSON – (including the generated short link) – and the HTTP response codes, refer to the excellent Bitly API v4 documentation.
Many people working in the Information Technology industry today, probably started their journey when they learnt the computer language BASIC – (Beginners All-purpose Symbolic Instruction Code) – on computers such as the Apple II or the Commodore 64.
What many people won’t know is the fascinating story of how BASIC started, at Dartmouth College in 1964. In today’s “Sunday Nerding”, learn about the origins of this once ubiquitous programming language.
Back when the NBN was first mooted in 2008 – (though one could argue its origins go back the OPEL Networks plan from 2006) – everyone was supposed to be on one of three different technologies – 93% of the population with Fibre-to-the-Premise (FTTP, with up to 100Mbps), 4% with Fixed Wireless (FW, with up to 25Mbps), and 3% Satellite Broadband (SB, with up to 12Mbps).
Enough capacity was to be put into the ground in the FTTP footprint to support 6 separate services – (4 data, and 2 voice) – in every single premise in those areas. The fibre going into the ground was to support services of up to 40Gbps.
To achieve those speeds – (over and above the standard 100Mbps offered initially) – all that would be required is an update to the electronics at each of the fibre connection.
Yes – the original 2008 NBN plan would have allowed for 40Gbps, dependent on CVC and backhaul capacity to be provided by individual ISPs.
Leading up to the 2013 election – and the change of government – then opposition communications spokesweasel, Malcolm Turnbull, and opposition leader Tony Abbott had other ideas.
Simply to oppose on politically ideological grounds, they decided that Conroy’s plan was “too expensive”, and would take “too long”.
Their alternative was to be “cheaper” and “faster to deliver” – neither which has been proven, and has in fact been widely debunked. Their plan called for all areas in which FTTP had not already been deployed, to change to Fibre-to-the-Node (FTTN, with up to 100Mbps), using existing copper.
The rollout has proven to be no faster to deliver – (and in fact has taken longer) – and sustainable speeds of 100Mbps have been so difficult to reach that most ISPs no longer even offer 100Mbps plans – including on the parts of the network that are deployed with FTTP.
What we in fact end up with is what Turnbull called the “Multi Technology Mix” (MTM) – which would leave Australia covered with FTTP in areas where it had already been rolled out, Hybrid Fibre Coaxial (HFC) cable in areas where HFC was already rolled out, FTTN in the remaining areas where FTTP had not already been committed and there wasn’t already HFC, and finally FW and SB in much the same areas as originally planned.
The FTTN areas were later broken up further to include some Fibre-to-the-Curb (FTTC) deployments when they realised FTTN, in particular, wasn’t cutting it. Many areas which they earmarked for existing HFC later switched back to FTTN or FTTC, because many of the existing HFC networks they purchased couldn’t be made suitable.
And 100Mbps? Not even remotely likely unless you’re in an FTTP area, and with an ISP that has purchased enough CVC and backhaul capacity.
So what does the MTM end up looking like? Take a look at this small area in the western part of Geelong, Victoria, with mapping provided by NBN MTM Alpha:
The purple dots represent locations that are serviced by FTTP; the yellow dots locations that are serviced by FTTN; the green dots locations that are serviced by FTTC; the pink dots locations that are serviced by FW; the orange dots locations serviced by SB; and finally the blue dots locations that are serviced by fibre from a non-NBN provider.
This is pretty stunning – and stunningly stupid.
You’ll see in the bottom right a patch of FTTC – (green) – where some premises right next door to green dots are getting FTTN – (yellow).
In the same street.
In the middle of the map, you’ll see the hamlet of Fyansford – where at the southern end of town you have a non-NBN fibre provider – (blue) – and at the northern end of town you have FTTP – (purple) – with a blob of FIXED WIRELESS in between. This band of fixed wireless is about 10 house blocks wide – or around 120 metres.
Apparently nobody thought that this area – (which is the newest part of that residential estate) – right next door to two fibre areas should get any kind of fixed-line service – not even FTTN or FTTC.
Finally, zooming into the area just to the right of Fyansford – (which is on the side of a hill) – we see this:
Locations on the eastern side of Hunt Road get FTTN – (yellow) – locations on the western side get SATELLITE – (orange) – and just a little way down the hill, locations get Fixed Wireless – (pink).
And just to the north? A purple dot of FTTP.
I mean, what the hell?
Australia will one day rue this shemozzle of a “multi-technology mess”.
Trouble is, that day has already come, and Turnbull should hang his head in shame.
A while back I wrote about the amazing – (and ongoing) – restoration of an Apollo Guidance Computer – one of the very first digital computers, developed at MIT for NASA, which was crucial to achieving the goal.
While everyone remembers Apollo 11 – (and to a lesser extent Apollo 13, due to the problems it struck) – very little is thought about with respect to Apollo 8 – the mission where NASA figured out how to do two of the four main important tasks of a successful moon landing – getting there and getting back.
The following video discusses the pivotal role Apollo 8 played in making Apollo 11, and all of the subsequent moon landings possible.