Open Source - "where the source code is freely available". Different from "Free Open Source" - which includes definition of license.

One client in 4 years of greylisting has had that problem, for something like 40,000 unique senders per month. I like those numbers.

I do, regularly enough that when I'm attending one of the "tech only" training day the local apple guys know that I will be a source of useful information and will tell them what is shit and where, but that sort of thing doesn't make the news.

There's also the percentages problem - considering the size of the user base, it's not really surprising that people encounter problems with the product. The only piece of software I've seen work flawlessly in the last, what, 20 years would be Hobbit's netcat, and that doesn't handle IPv6.

Not defensive of either company here - Google wrote their own apps for iOS and Android and not for MS, ok, MS got given a list of requirements to comply with something that will be used in a not-insignificant market share, but there's this little gem which I almost missed the first read through:

Which I'm reading as "fuck it, too hard, let's just release what we've done and see what happens". Now they complain.

I don't care what they say about me, just make sure they spell my name right! - P.T. Barnum



*Disclaimer* I may not be quoting directly/ correctly from memory :)

Funny, but bug 1 wasn't fixed by Ubuntu, and doesn't match the spirit of the discussion (e.g. a bug in software, not sales). There were no tools around to detect and determine the fault. IIRC at the time most techs couldn't reproduce but almost every consumer I ran into (and read about) could. Figures.

Except that's a crap line (which I have spouted in the past). Gnash is the perfect example - you have the opportunity to fix it, but the source code is such a pain in the ass to get around that nobody does it. Pick any large project with long standing bugs - why are they long standing? Because nobody wants to fix it - whether for lack of ability, lack of replication of the bug, or fear of the rip-off's license agreement (which is why there are, what, 5 gnash developers on the planet). Pick a large project with long standing bugs (memory leaks in firefox were a good example until too many people complained about it) and ask yourself why those bugs are long standing and well documented.

Fuck that. I usually propose running Cat 5e in a single strand for 300m. If the project is approved.....

Not if you're in on any of my contracts no, you can't. And don't even think about uttering the word "cloud" while talking about your development model. Some clients, most (small time?) clients, will be ok with you putting the code in a private repository. More specifically, they won't care where you put your code, bigger clients want to know exactly where everything is.

The Bendigo at least set those fields to autocomplete off - so should the browser actually be doing that then... or even keeping it for two hours plus.

Not really a banks fault though - why is the browser hanging on to post'd data after it's been post'd??

Well, yeah, that's kind of the point - emulate what we've seen of google glass as much as possible (and also be useful when watching morons drive). I made sure to be well aware of the local surveillance rules and all of that, clients are told about the glasses and the possibilities, people are so excited about GG technology that they're not stopping to consider the ramifications. Pretty much anyone who posts on here has thought about them (as is evidenced by the attempted testosterone flowing from some of the other comments) but they're not the general public.

All I see in the news lately is how good Glass is, with lots of comments about the need to be looking directly at the person to take a picture. The public are being calmed before the storm.

I've spent the last 8 months wearing a pair of sunglasses that contain a camera in the bridge, mostly because I see lots of stupid drivers on the road, but also because google glass has been coming along. I'm careful to remove the SD card fairly regularly, but in that 8 months only 3 people have questioned my very chunky glasses with half cm buttons on the left side.

People don't care about privacy, not until it's the "creepy" guy staring at them instead of the average guy.

AC has a point. This is why you get companies (here's a local example: http://www.attache.com.au/products/attache-accounts/ ) who give you your pay slips via HTTPS (because it's secure) but have the beancounters email through the base files in plain text (because they've got no idea how any of this works).

Are you using SCTP or have you rolled your own standard?