, pub-6750398400224078, DIRECT, f08c47fec0942fa0

10 Years on Twitter

10 Years on Twitter

So I received a notification from Twitter this morning, that’s nothing unusual, except that this one said “It’s your Twitter anniversary…

What?!  Apparently it’s ten years since I signed up to Twitter.  If you’d asked me yesterday, I would have said that the social media giant wasn’t even around ten years ago.  Some research this morning has enlightened me, Twitter was launched in July 2006.  I signed up two and a half years later.

As a relatively early adopter, I was able to secure my real name as my Twitter handle @SimonYeo.  Good luck to anyone trying to get their real name as a username today!

I’m only an occasional user of Twitter these days.  Below are some of my earliest tweets from 2009.

If the embedded tweets aren’t loading in your browser, click HERE for a screenshot (opens a new tab).

Train hassles

12 Year old Brad and I decided to take the train into Melbourne today to see the Grand Final parade, and other festivities at the MCG and Yarra Park.  Brad is excited about football, and it’s a great way to soak up some finals atmosphere without actually going to the big game tomorrow.  We took the train, rather than drive, to avoid having to find a car-park and because Public Transport Victoria (PTV) had promoted a hassle free way to “Get from A to the G” (‘G’ is an abbreviation of MCG – Melbourne Cricket Ground).

We live walking distance to Pakenham train station, so the car stayed at home and Brad and I set off on foot.  I wasn’t too concerned about waiting 20 minutes for a train to the city, as today is a public holiday, so I assume there were less services than normal.  Our train departed Pakenham station on time, crossed Main Street, but the acceleration turned to sudden braking and the train stopped before we made it to the next level crossing at McGregor Road.  A couple of minutes later the train driver walked passed our window, passengers were wondering if there had been an accident.  After a few more minutes the driver walked passed again, in the same direction, I assume he was walking around the train looking for something.  We finally started moving again after around 15 minutes, there was no explanation.  (I’ve been on trains before when the driver would announce over the speakers that there had been a delay due to a signal fault.)

The rest of our journey was unevenetful, until we passed Richmond Station.  We were planning on going through the City Loop (subway) to Parliament Station, which is close to where the parade was starting from.  The sign inside the train said “Next station is Parliament” and I was expecting the train to start descending onto the underground tracks, but it instead stayed above ground and headed towards Flinders Street Station.  That sign in the train changed to “Arriving at Flinders Street”, which was followed by cursing by other passengers and some people saying “we’ll just have to walk from here”.  I was hopeful the train would go around the loop after Flinders Street, but when we pulled up at the platform the screens said that train was heading to Cranbourne without going via the underground stations.  (I wonder if skipping the City Loop was to make up time for the delay at Pakenham and arrive at Flinders Street “on-time”?)  Thankfully the screens also gave information on which lines were the next to travel through the City Loop, so we went a couple of platforms over to the Glen Waverley line and hopped on a train to Parliament Station.

A few hours later, after watching the Grand Final Parade and walking down to Yarra Park for the MCG festivities, we made our way to Richmond Station to catch a train back home to Pakenham.  Everything was normal on the way home until we were approaching Dandenong station.  The in-carriage announcement said “Arriving Dandenong, this train will be terminating at Dandenong”.  Terminating means the train wont be going any further, so most passengers got off the train to then watch it depart towards Pakenham.  I’m not sure whether it actually kept going to Pakenham, or just went up the line a little way to change tracks, but regardless there was no explanation why we were told the service was terminating when it was scheduled to go all the way to Paky.

Once on the platform at Dandenong there was no information to say when the next Pakenham train would arrive, another passenger went to find out and came back to say there wasn’t another metro train to Pakenham for at least 20 minutes.  However there was a Vline (regional service) arriving in one minute, the platform sign said it would run express to Nar Nar Goon, which is the next station after Pakenham, but classed as a regional station because the electrification ends at Pakenham.  I called my wife and asked her to pick us up from Nar Nar Goon, but when we boarded the Vline train the in carriage sign said “Next station is Pakenham”.  I texted my wife back about the conflicting information and said I will let her know whether we were able to get off at Pakenham or whether we’d need a ride from Nar Nar Goon.  The Vline train did stop at Pakenham and we walked home from there.

Yes the public transport system got us around today, but thanks to conflicting or insufficient information we had a frustrating and disappointing experience.  As you can see, I tried to interact with PTV through social media, but there was no response to my tweets.  Knowing my way around Melbourne and surrounds helped us get to where we wanted to go when the train schedules unexpectedly changed.  Who knows how a tourist, or young teenagers travelling alone, would be affected by similar disruptions.

PTV promo A to G

Screenshot of my tweets to PTV

My tweets to PTV


Thanks to the power of Twitter, it turns out possibly an unauthorized person in the rear driver’s cab caused the delay just after leaving Pakenham this morning.

Twitter screenshot re unauthorised person in rear drivers cab at Pakenham

Twitter screenshot


I’ve received the following correspondence from Metro regarding my travelling experience.

Dear Simon

Thanks for your email received on 2 October 2015.

I’m sorry you were affected by delays and alterations to your Pakenham line trains on both the morning and afternoon of the same day.

I have checked our train performance records and the 9:53am Pakenham to Flinders Street train was delayed by approximately 15 minutes between Pakenham and Cardinia Road stations after an unauthorised person accessed the rear driver’s cabin.

The 2:35pm Flinders Street to Pakenham train (scheduled to depart Richmond at 2:48pm) was delayed by approximately ten minutes before being altered to terminate at Dandenong station due to a trespasser near the tracks at Dandenong.

When trespassers are reported on or near trains or tracks, we have to either suspend or run trains at a reduced speed while Victoria Police attend and investigate the scene. This can result in trains and drivers being out of position to operate services, causing further delays.

Following service delays, our train controllers must sometimes alter the scheduled stops or terminating points of trains to prevent ‘knock on’ effects on other services. We regularly review these decisions, with reports brought to the attention of Executive Management.

During disruptions of this nature, announcements are made by our staff based on the information made available to them, as guided by Victoria Police.

All our staff have been asked to keep you informed of service delays and alterations as soon as possible, and I’m sorry this was not your experience. We are continuing to monitor this aspect of their performance.

As regional services are outside of our responsibility, your feedback regarding the V/Line train you boarded at Dandenong station has been referred to V/Line under case reference 2015/xxxxxx.

Thank you again for your feedback. If you wish to discuss further, or would like more information, please call Public Transport Victoria: 1800 800 007, quoting reference number LC/xxxxxx, or send an email to

Yours sincerely

Laura Crofts
Customer Relations Coordinator


Flickr V 500px

If you’ve read my early posts on this blog (from January this year), you may know that I used to love Flickr, and had uploaded 1000s of photos and enjoyed the online community of photographers from all walks of life.  However, in October last year, the site’s owners – Yahoo! – started making changes with their “New Photo Experience“, which in reality actually made it worse.  They were slow to act on user feedback, and slow to keep users up to date with the ongoing changes.  Even today it has been over a month since an update to users on the site’s (hard to find) forum.  They’ve made some recent upgrades to their mobile apps and blog, but users still get different Flickr experiences depending on their device, browser and language.

The mess Yahoo! made of Flickr drove me away in frustration, I tried the other major photo sharing site, 500px, but ended up going to SmugMug to make my own photo site.

Now I read on the 500px blog that they are making some major changes to their site too.  It’s going to be interesting to see how the 500px site evolves, it certainly wont be too hard for them to do a better job than Yahoo! is doing with Flickr.

The war of the photo sharing web sites is heating up.  I will be keeping an eye on both services, but will be concentrating on my own photo site, hosted by SmugMug, and blogging about my photography here on my photo blog.


This blog post was originally published on

at this URL


Today has been my biggest day on Twitter since I joined several years ago.  Including re-tweets, I tweeted 43 times today.  My topics varied from the passing of cricket legend Tony Greig, interacting with a guest on ABC News24, a very healthy “discussion” on the safety of B-Triple trucks, photography re-tweets and linking to a YouTube video of my kids.

All these tweets today took my total number over 1000, but I still call myself only a casual user of Social Media.

Twitter are slowly rolling out the ability to view all of your twitter history.  When it’s available to me, I’ll be really interested to look back at what I posted in my early days.


This post was originally published on