Jasber

It feels a lot like the way notch developed with hot swapping during Lundum Dare.

I have an app that could fit into both, but went with Music. I'm curious if Education would be a better fit.

A singleton SettingsManager was suggested, but singletons always get a bad wrap.

So is this a good use of a singleton? What would be the correct way to handle this?

With circles, it automatically filters my stream without anyone having to post to my list or group. They just share it with me.

This is a subtle but important difference for me.

You certainly have a point, most apps are downloaded then never used. But I think everyone's "few apps" are different with lots of overlap in the apps you mention.

LastPass would sometimes post to the wrong login form.

1Password got confused a couple of times between 'Logins' and 'Accounts'.

With 1Password, when I'm away from my computer, I have to use my phone to read my passwords. If my phone dies (fairly common) I have to install the password manager (not always possible).

With LastPass I can access their web interface--but experienced too many of the issues above. Plus I am a little nervous about a 3rd party having that much power.

I'm sure all of this was my fault, but the end result was I discovered many hidden costs and it felt like I was fighting against them.

I recently looked into password managers myself after the MtGox leak. I tried 1Password and LastPass. While both do what they say--I found them cumbersome to use.

I settled on a scheme like this:

E-mail: Very strong, completely unique. 2-factor auth. If you have my e-mail, it's game over.

Bank: Very strong, completely unique.

The rest of the passwords I've broken down into tiers. I've memorized a password for each tier combined with a hashing algorithm stored in my head.

The theory here being if an entire tier gets compromised (someone figures out my hashing scheme), at the very worst I lose the entire tier.

This does keep me safe from automated attacks, but not if someone singled me out individually. Which in that case, I've got other problems.

This isn't perfect, but it gives me a couple of things I really value:

- Keep all passwords in my head

- Unique passwords on each site

- Tiered passwords so if someone figures out my hashing scheme, they only get that tier

I like the idea of password managers, but in practice they were too much hassle for me.

You need massive volume (like advertising) to make this model work--it's just not there.

Making the app paid lets me keep the service running for the few people who think it's valuable enough to pay for.

This is a better solution I think than shutting down the service all together.

I'm definitely considering an ad-supported or free version, but wanted to start with a paid version first.

I may need to adjust this in the future, so that's something good to keep in mind, thanks.

> If there's one thing you should have learned by now, it's that small, unintentional visual differences are like sand in the engine of your visual brain.

Are you going to continue adding to this?

Thanks for the video, that makes debugging much easier.

I've tweaked some settings to try and handle the load better (250K domains checked in 2 hours was a little more than I expected).

I'll work on adding more registrars, this is planned.

The site is slower than normal right now due to increased load, but should return to normal after the HN spike. If not I'll more workers.

My goal is that you should never have to wait for results. By the time you click "Load more results", they should already be available.

I had thought of clicks, but not hover ratio--that's pretty interesting.

I may have to experiment with that, thanks for the idea.

The site may be a little slower than normal right now because of HN traffic, but I'm working on keeping it going.

Thanks for your feedback.

I thought it turned out decent enough, so I'm releasing it, hoping others will find it useful.

There are tons of these domain keyword tools around, here's why I built this one:

- Wanted to check the best keywords first, then fallback to less popular keywords

- Handle plural/singular keywords gracefully (like greatguitar.com, guitargreat.com, greatguitars.com, but not guitarsgreat.com)

- Use WHOIS rather than DNS to determine availability (more accurate, but slower)

- Simple to use

- Fast

There's still a lot to do, but in the spirit of release early and often, I'd love some feedback on this.

Do you find this useful?

Currently it only does fixed-width sprites, but handles the generation of CSS for you.