SpoonMeiser

Python

You don't have to worry about memory management, pointers and the like, and can just focus on the algorithms.

All that stuff it super important to also know, but probably easier to learn about them separately.

Just one question: Can it automatically hide any links to techcrunch? That's the killer feature that's missing from all of these things.

Ha ha

Surely that's the null hypothesis? It's up to proponents of organic food to prove a benefit.

Exactly what I was thinking

I have a gpg encrypted file on a server that I manage manually - made slightly easier by the gpg plugin for vim. Not found a password manager with a UI that I get on with yet.

theoldreader.com looks like a good alternative

re point 2.

I don't see a problem with using a regex to validate email, unless you get false negatives. Rejecting anything that could be a valid e-mail address is bad and will cause frustration for someone at some point.

I don't think allowing validly formed e-mail addresses that don't have corresponding accounts (or even domains - consider a web app working in offline mode) is a bad thing, especially when taken with point 1, as surely the point of client side validation is a heads up to the user that the data is wrong, rather than actual validation?

The problem I find with something like gnome, is that it pulls in a huge amount of dependencies, and it isn't always easy to cleanly remove it.

My wife has a horrible time with HSBC, and I always get a bit aggitated when I see people recommend them, so I'm glad to see other people sharing their horror stories about them.

Her situation is that she visits family in Canada once a year. They won't make a note of her being out of the country if she calls them beforehand. The fraud people then call her if she needs to use her card at unsociable (for Canada) hours and never leave answerphone messages. When they do get her, they require her to answer security questions without identifying themselves first. If she calls them, the person she speaks to has no way of knowning if anyone has been trying to call her for any reason.

They are, in my opinion, the "Worlds worst Bank"

I like the Barclaycard (I think) fraud thing.

You get called by a computer that asks you to identify yourself by picking a piece of personal information from a list. It might ask for the month and date of your birth, for example, and give you 5 options.

Because there are 365 possible month + date combinations, and yours appears in the list, you know they already have this information so you're safe to confirm it, and they also get to confirm that you are (likely) who they're intending to talk to.

I like the Barclays mobile app. You authenticate it once using a pin sentry device, and give it a pass code, and from then on you can just use that pass code to get your balance using the app. The app also acts as a pin sentry when you want to access your account using a computer.

HSBC are also (or at least were very recently) in the habit of calling customers and launching immediately into security questions without even identifying themselves first, which is wrong for all sorts of reasons.

"We're announcing Go version 1, or Go 1 for short"

I foresee the next version being considered harmful.

This really doesn't sound like a problem with the update function, this just sounds like web applications 101 - don't trust user data.

Is it just me, or doesn't this sound very similar to SQL injection, only as applied to an ORM instead?

That is, if my understanding is correct, they're taking user posted data and trivially turning it into a command to update data.

This doesn't sound like a problem with Rails, in the same way that if I turn data I receive from the user straight into an SQL statement, the fact that people can abuse it isn't a problem with SQL.

"The full set are true monospace fonts, each character being exactly 0.5em wide"

Umm... a 0.5em width m?

That's a good analogy, because until recently, I was writing all my PNG files by hand.

Also, it says that directly on the site itself.

Great. Can it be adapted to hide any stories from TechCrunch instead?

Can't wait to try this out on my touch-screen phone or tablet PC...

...oh, wait.

This is excellent advice.

s/solve/cause/

I can't log in with either my 'free' or 'open' accounts. The client outputs something like this:

  12:53:03.051 I [ap:1387] Connecting to AP B2.spotify.com:4070
  12:53:03.054 I [ap:937] Connected to AP: 78.31.8.17:4070
  12:53:03.073 E [ap:3280] Connection error:  404
  12:53:03.576 I [ap:1387] Connecting to AP B1.spotify.com:80
  12:53:03.609 I [ap:937] Connected to AP: 78.31.8.15:80
  12:53:03.629 E [ap:3280] Connection error:  404
  12:53:03.810 I [ap:1387] Connecting to AP B3.spotify.com:443
  12:53:03.840 I [ap:937] Connected to AP: 78.31.12.9:443
  12:53:03.913 E [ap:3280] Connection error:  406
  12:54:25.855 I [offline_authorizer.cpp:156] Unable to login offline: no such user

What struck me about the memo, is the constant references to 'the problem', without ever defining what the actual problem was. People not working long hours might be a symptom of a problem, but it is not a problem in and of itself.

You ask how we'd tackle the problem, but I don't know how anyone can answer that without knowing what the problem actually is.

This might have been communicated, or evident, outside of this memo, but it sounds like he's trying to fix a problem that doesn't necessarily exist, based on questionable metrics.

The correct term is "crawl", not "creep"

It is? Why?

What about a million and one?