Somebody brought this iPhone 3G in a few days ago. I'll give you three guesses why.
You're absolutely correct, she wanted a software update. The owner has no plans to replace the screen - after all, it works perfectly aside from the occasional ear-cutting incident.
She's been through two screen replacements so far with this handset. For her next phone I might recommend a nice sturdy case to go with it.
Tuesday, 27 September 2011
Monday, 26 September 2011
Package updates looping in Ubuntu 10.04 LTS
A quick snip of weird behaviour from . On my old fileserver (running Ubuntu 10.04 LTS), I noticed an infinite loop of packages being added and removed.
And after removal, if you try dist-upgrade you get..
And so on ad infinitum.
It looks like those packages are simultaneously required and unnecessary for my system, which I'm fairly sure isn't normal behaviour. A quick look at the package dependencies points the finger at gstreamer0.10-plugins-bad being kept back. Since it's not a vital package, one quick removal and everything is back to normal.
Okay, I may not have found the root cause of the problem, but this works just as well for me.
root@mybox:~$ apt-get autoremove Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED: libass4 libcelt0-0 libdca0 libdirac-encoder0 libfftw3-3 libflite1 libgme0 libkate1 libmimic0 libofa0 liborc-0.4-0 0 upgraded, 0 newly installed, 11 to remove and 1 not upgraded. After this operation, 16.8MB disk space will be freed. Do you want to continue [Y/n]? y
And after removal, if you try dist-upgrade you get..
root@mybox:~$ apt-get dist-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following NEW packages will be installed: libass4 libcelt0-0 libdca0 libdirac-encoder0 libfftw3-3 libflite1 libgme0 libkate1 libmimic0 libofa0 liborc-0.4-0 The following packages have been kept back: gstreamer0.10-plugins-bad 0 upgraded, 11 newly installed, 0 to remove and 1 not upgraded. Need to get 0B/9,685kB of archives. After this operation, 16.8MB of additional disk space will be used. Do you want to continue [Y/n]?
And so on ad infinitum.
It looks like those packages are simultaneously required and unnecessary for my system, which I'm fairly sure isn't normal behaviour. A quick look at the package dependencies points the finger at gstreamer0.10-plugins-bad being kept back. Since it's not a vital package, one quick removal and everything is back to normal.
Okay, I may not have found the root cause of the problem, but this works just as well for me.
Thursday, 15 September 2011
Get Inifinite Email Addresses in Google Apps
You've got your own domain. It's for personal use, so you've set up Google Apps to get free and effective email. What could possibly make this better?
The Google Apps Catch-All address, of course.
The Basics:
A Catch-All address is an email account that receives all incorrectly addressed email for your domain. If somebody typos your address but gets the domain right, the email winds up in the catch-all email account. The account owner will occasionally check through to make sure the email gets to the right recipient (If they type the domain wrong, they end up with a much bigger problem).
The catch-all address became less popular as spam got worse for fairly obvious reasons. Google, however, has remarkably good spam filtering, which gives us the option back.
What you can do with it:
You can come up with any email you like on the spur of the moment (say, SpurOfTheMomentEmail@yourdomain.com) and it'll reach your inbox. You can give a different email address to every person you meet and every site you sign up for and receive them all. It gives you an essentially unlimited supply of email addresses, because *@yourdomain.com is now yours. Hell, I sometimes use it to send subtle messages - If dave is hounding you for your email address, giving him stopannoyingmedave@yourdomain.com might get the point across.
Aside from the awesomeness and flexibility this gives you, it has some practical advantages - you can treat addresses as 'throw-away' email accounts. If a site sells your address on to spammers, you can just blacklist all mail to that address with email filters (shown below).
Setting it up:
Assuming you've already got a domain and set up google apps, it's very, very simple. If not, you may want to start at the beginning.
Log into the Google Apps control panel, and choose Settings followed by Email. Under the catch-all email section, choose to forward it to your main email account.
Save, and that's it. If you look under your account settings, you now have *@yourdomain.com listed as one of your addresses.
Blacklisting:
Blacklisting one of the addresses you gave out is easily done under your email settings. Click on Filters and then Create a new filter. Type the email you want to blacklist in the To: field, and hit Next Step.
Now simply check the Delete it box and click Create Filter, and that's it! Any future messages sent to that address will be silently moved to the deleted folder.
Now enjoy the freedom that only an infinite supply of email addresses can give you.
The Google Apps Catch-All address, of course.
The Basics:
A Catch-All address is an email account that receives all incorrectly addressed email for your domain. If somebody typos your address but gets the domain right, the email winds up in the catch-all email account. The account owner will occasionally check through to make sure the email gets to the right recipient (If they type the domain wrong, they end up with a much bigger problem).
The catch-all address became less popular as spam got worse for fairly obvious reasons. Google, however, has remarkably good spam filtering, which gives us the option back.
What you can do with it:
You can come up with any email you like on the spur of the moment (say, SpurOfTheMomentEmail@yourdomain.com) and it'll reach your inbox. You can give a different email address to every person you meet and every site you sign up for and receive them all. It gives you an essentially unlimited supply of email addresses, because *@yourdomain.com is now yours. Hell, I sometimes use it to send subtle messages - If dave is hounding you for your email address, giving him stopannoyingmedave@yourdomain.com might get the point across.
Aside from the awesomeness and flexibility this gives you, it has some practical advantages - you can treat addresses as 'throw-away' email accounts. If a site sells your address on to spammers, you can just blacklist all mail to that address with email filters (shown below).
Setting it up:
Assuming you've already got a domain and set up google apps, it's very, very simple. If not, you may want to start at the beginning.
Log into the Google Apps control panel, and choose Settings followed by Email. Under the catch-all email section, choose to forward it to your main email account.
Save, and that's it. If you look under your account settings, you now have *@yourdomain.com listed as one of your addresses.
Blacklisting:
Blacklisting one of the addresses you gave out is easily done under your email settings. Click on Filters and then Create a new filter. Type the email you want to blacklist in the To: field, and hit Next Step.
Now simply check the Delete it box and click Create Filter, and that's it! Any future messages sent to that address will be silently moved to the deleted folder.
Now enjoy the freedom that only an infinite supply of email addresses can give you.
Monday, 12 September 2011
Perth Verge Collection Map
Update:
This map is now very out of date, last updated 2014. Thankfully, a new champion has taken up the challenge and the current map can be found at vergeside.com.au
Original post:
I've been fiddling with this for a while, so it's time to share: A google maps layer that shows the Vergeside rubbish collection areas for the whole Perth metropolitan area. This is pretty useful to anyone around Perth who're looking for some free furniture or appliances, as well as to those just wondering when their next vergeside collection is.
I'll update this post with relevant data as it changes.
How it works and notes:
View Perth Verge Collections in a larger map
Local Government Areas currently mapped:
Click on a council to see their information page about bulk rubbish.
Local Government Areas currently lacking data:
If you have one of the council verge collection pamphlets for these areas, please let me know
This map is now very out of date, last updated 2014. Thankfully, a new champion has taken up the challenge and the current map can be found at vergeside.com.au
Original post:
I've been fiddling with this for a while, so it's time to share: A google maps layer that shows the Vergeside rubbish collection areas for the whole Perth metropolitan area. This is pretty useful to anyone around Perth who're looking for some free furniture or appliances, as well as to those just wondering when their next vergeside collection is.
I'll update this post with relevant data as it changes.
How it works and notes:
- Click here to get to the full version of the map. It's easier to work with than the embedded version below.
- On the left you have the various collection zones/councils with the next known collection date. Flick through the pages to see the rest of the zones, as google maps won't display them all at once by default.
- The date represents when the collection itself starts, not when to start putting things out.
- You can save this map directly in your google profile by hitting the save to my places button.
- You can export the map data as KML if you want and do anything you like with it. It should work with most mapping applications that support layers.
- This works great on your mobile phone. It works with Google Maps for Blackberry and Android, Google Earth for iOS, and it should work with any map software that supports google layers or importing kml data. Combined with your phones GPS, it's pretty handy when you're in the field.
- This is a work in progress, and there's bound to be gaps and occasional errors. Local councils often provide patchy data.
- For similar projects try Freecycle Perth , Free items on gumtree, and the Perth Kerbside Collection Facebook page.
- If you have any suggestions or updated information, email me or add a comment below.
- I can't believe I'm putting this in, but it keeps coming up: If you want to interview me about verge collecting or the map, emailing me the questions is the easiest and most reliable way to get a response.
View Perth Verge Collections in a larger map
Local Government Areas currently mapped:
Click on a council to see their information page about bulk rubbish.
- City of Canning
- City of Cockburn
- City of Fremantle
- City of Joondalup
- City of Mandurah
- City of Melville
- City of Nedlands
- City of Perth
- City of Rockingham
- City of South Perth
- City of Stirling
- City of Subiaco
- City of Swan
- City of Vincent
- City of Wanneroo
- Town of Bassendean
- Town of Cambridge
- Town of Claremont
- Town of Cottesloe
- Town of East Fremantle
- Town of Kwinana
- Town of Mosman Park
- Town of Victoria Park
- Shire of Mundaring
- Shire of Peppermint Grove
Local Government Areas currently lacking data:
If you have one of the council verge collection pamphlets for these areas, please let me know
- City of Bayswater - NO VERGE COLLECTION
- City of Belmont - NO VERGE COLLECTION
- City of Armadale - Only distributes pamphlets to houses?
- City of Gosnells - Mapping data difficult to extract
- Shire of Kalamunda - NO VERGE COLLECTION, replaced with skip bins.
Using this on the move:
- Sign into your google account and save the map above to your account. This will allow you to access it from any program that supports layers.
- If you have an android phone, use the built-in google maps. When you go to load layers, it will appear on the list of options.
- If you have a blackberry phone, install google maps for Blackberry. You can sign into your account via the menu and load layers.
- If you have an iPhone/iPad, install Google earth. Sign into your google account, and load the layers from there.
Here's a screenshot of what the ipad version looks like on the move - The blue dot is your current location. It makes it damn easy to work out the edges of verge pickup.
Labels:
bulk rubbish,
google,
local council,
map,
Perth,
vergeside collection
Location:
Perth WA, Australia
Sunday, 28 August 2011
A brief analysis of Yahoo captchas
Captchas, initially a huge annoyance, are generally recognized as a necessary evil now. They stop bots from abusing your services, and there's a lot of interesting variants to use. The biggest is google's recaptcha, which is so popular even microsoft uses it occasionally. Today my attention is on Yahoo's implementation. You'll know them, they look like this:
In a nutshell: I had to type a few of these lately, and the character distribution didn't look quite right. I grabbed a hundred captchas, laboriously typed them out, and broke it down by character.
What you can't see here: Yahoo works with the traditional 'random combinations of letters and numbers' form of captcha. They use at least three different fonts, which are then physically skewed in a variety of ways. There's no additional visible interference between you and the letters, and the average length is 7.2 characters.
What you can see: Yahoo captchas use a relatively small subset of alphanumeric characters. A, B ,F ,G ,H ,J ,L ,M, T and V appear only in uppercase while c, d, e, n, p, r, s, t, y, q, y and z appear only in lowercase. Out of the numbers we have only 2, 3, 4, 5, 6, 7, and 8. This leaves 8 alphanumeric characters completely unrepresented - i, k, o, q, x, 1, 9 and 0.
Most of these seem to be omitted due to possible confusion. O, o and 0 are easily mistaken and so all are avoided, and the same goes for l/1 and K/X. Additionally, some two-character combinations which look similar to existing characters are omitted.
In this example the letter d is very easily mistaken for either 'cl' or 'ol' due to the font. However c, l, and o never appear in the captchas, presumably for this reason.. The letter p suffers similarly, while B and 8 manage to escape despite being sometimes difficult to distinguish.
I'm not entirely sure of the strategy here. They're purposefully obfuscating the word by overlapping the characters, but at the same time dramatically reducing the number of characters that could be present. By cutting down the total alphanumeric characters from 62 to 28 they're making it easier for OCR to render their technique ineffective.
In a nutshell: I had to type a few of these lately, and the character distribution didn't look quite right. I grabbed a hundred captchas, laboriously typed them out, and broke it down by character.
What you can't see here: Yahoo works with the traditional 'random combinations of letters and numbers' form of captcha. They use at least three different fonts, which are then physically skewed in a variety of ways. There's no additional visible interference between you and the letters, and the average length is 7.2 characters.
What you can see: Yahoo captchas use a relatively small subset of alphanumeric characters. A, B ,F ,G ,H ,J ,L ,M, T and V appear only in uppercase while c, d, e, n, p, r, s, t, y, q, y and z appear only in lowercase. Out of the numbers we have only 2, 3, 4, 5, 6, 7, and 8. This leaves 8 alphanumeric characters completely unrepresented - i, k, o, q, x, 1, 9 and 0.
Most of these seem to be omitted due to possible confusion. O, o and 0 are easily mistaken and so all are avoided, and the same goes for l/1 and K/X. Additionally, some two-character combinations which look similar to existing characters are omitted.
In this example the letter d is very easily mistaken for either 'cl' or 'ol' due to the font. However c, l, and o never appear in the captchas, presumably for this reason.. The letter p suffers similarly, while B and 8 manage to escape despite being sometimes difficult to distinguish.
I'm not entirely sure of the strategy here. They're purposefully obfuscating the word by overlapping the characters, but at the same time dramatically reducing the number of characters that could be present. By cutting down the total alphanumeric characters from 62 to 28 they're making it easier for OCR to render their technique ineffective.
Wednesday, 10 August 2011
RIM: Now checking your email from the wrong country
I like the way my blackberry handles multiple email accounts. RIM servers effortlessly stream my gmail traffic directly to me wherever I am, handling two-way sync, calendars and contacts with ease.
Today google forced me to re-authenticate in gmail a couple of times. A quick look at the recent activity list revealed why:
216.9.249.99 turns out to be bda-216-9-249-99.bis3.ap.blackberry.com and is the first time a foreign IP has been handling my mail for an extended period.
They have Australian servers that work perfectly well, and I cant find any notices about local downtime. I'm not entirely happy with this, we'll have to see if it stays.
Edit: A week later, It's still all Canada. Either google has reclassified all RIM IP space as physically in canada, or RIM has made a fairly drastic change to how they access your email account.
Today google forced me to re-authenticate in gmail a couple of times. A quick look at the recent activity list revealed why:
216.9.249.99 turns out to be bda-216-9-249-99.bis3.ap.blackberry.com and is the first time a foreign IP has been handling my mail for an extended period.
They have Australian servers that work perfectly well, and I cant find any notices about local downtime. I'm not entirely happy with this, we'll have to see if it stays.
Edit: A week later, It's still all Canada. Either google has reclassified all RIM IP space as physically in canada, or RIM has made a fairly drastic change to how they access your email account.
Tuesday, 2 August 2011
Boxify.me: A brief lesson in what privacy isn't
Boxify.me is getting a bit of press lately as a new site that allows sharing multiple files with others in 'boxes'. No sign up required; you just click on the 'start sharing' button, upload files, and share the URL around with others.
Here's their current front page.
Before I go further, I should mention this kind of sharing is inherently insecure - they make no promises about keeping your data safe and there's no password protection. Anything you put up there can be accessed by whoever has the private URL, and that's how it's designed. The only thing they specify on that page there is that your box has a 'private URL'.
That should be easy, right? All they have to do is set up robots.txt so that nobody can spider their site, after all.
Unfortunately, I'm wrong.
And as a result of that:
Now, I know what you're thinking -"That's not too big a deal, google can't find anything that's not already linked to". That's where the second mistake comes in, which is only obvious because of the first.
When you click on the link to uploads.boxify.me, you get this lovely page.
Yup. That a public xml file with hard links for the thousand most recently uploaded files. I'm not sure why the file exists, but the fact it's publicly accessible is just terrible. In 15 minutes you could knock up a shell script that regularly checks for and downloads every single file uploaded to the site.
So the outcome here: Boxify.me may turn out fine one day, but so far Loren Burton's claims of a private URL aren't holding up.. If you don't want your files immediately available to the general internet, don't use boxify.
Interesting Sidenode: The example box they link to on the front page can also be edited by the masses. Consequently, it has naughty material for the discerning visitor.
Here's their current front page.
Before I go further, I should mention this kind of sharing is inherently insecure - they make no promises about keeping your data safe and there's no password protection. Anything you put up there can be accessed by whoever has the private URL, and that's how it's designed. The only thing they specify on that page there is that your box has a 'private URL'.
That should be easy, right? All they have to do is set up robots.txt so that nobody can spider their site, after all.
Unfortunately, I'm wrong.
And as a result of that:
Now, I know what you're thinking -"That's not too big a deal, google can't find anything that's not already linked to". That's where the second mistake comes in, which is only obvious because of the first.
When you click on the link to uploads.boxify.me, you get this lovely page.
Yup. That a public xml file with hard links for the thousand most recently uploaded files. I'm not sure why the file exists, but the fact it's publicly accessible is just terrible. In 15 minutes you could knock up a shell script that regularly checks for and downloads every single file uploaded to the site.
So the outcome here: Boxify.me may turn out fine one day, but so far Loren Burton's claims of a private URL aren't holding up.. If you don't want your files immediately available to the general internet, don't use boxify.
Interesting Sidenode: The example box they link to on the front page can also be edited by the masses. Consequently, it has naughty material for the discerning visitor.
Subscribe to:
Comments (Atom)











