jroes

http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2012-5664

It references two articles that require session secrets.

Also, even open source projects typically ensure or recommend that the secret token be regenerated when using in production environments.

What is the likelihood that you own or would have compromised 10 top domains? Not sure if that matters, just curious.

At the very least I'd personally prefer to use an open, understandable methodology to generate my passwords than some of the more popular options that are secured through obscurity.

So, I wrote a gem:

http://github.com/jroes/passwordy

When is an RFS considered "closed?"

Unfortunately there are many other factors involved in building software that matter as well.

One challenge in the Node community is the ecosystem. There are not nearly as many libraries in npm as there are in RubyGems. Of that small set of libraries, a large portion of these have been abandoned. Of that smaller set that haven't been abandoned, there are large portions of missing functionality, are not very stable, or are constantly changing.

There are certain cases that Node works really well for right now, like building real-time chat apps. But having worked on some medium-scale Node projects recently, I constantly find myself re-implementing Rails functionality or rewriting common Ruby gems due to the lack of mature libraries.

I just wanted to make the typical legal fees clear to keep things realistic. I'm not sure if it's the same with this type of case, but for personal injury claims, the typical lawyer contract entitles the attorney to 1/3 of the dollars won plus fees.

Of course, 2/3 of 10k is still > 0.

I think the ubiquity and ease of use of things like WordPress causes people to overlook this solution. Also, I believe the caching plugins that people use with WordPress are doing something very similar.

There are a lot of static site/blog generators out there like Jekyll, but not many of them are targeted toward a general audience. WordPress is easy and well-known.

Does your product have any competitors? Find people who are using your competitors' products. E-mail them this afternoon and see if they're interested in what you're building.

I think connecting me through the phone would be best. I was a little confused about how the call was going to work initially until I stopped skimming and actually read what was on the page.

Another good rationale is that the user may not have a microphone on the machine they're on. Or there could be security restrictions on the machine that prevent access. It also opens up a new world -- you could let them schedule the call during business hours for the senator's office, or a time when the user is free.

My senators have a system that requires me to press 1 to leave a voicemail and 2 to speak with someone. I had to actually dial on my phone to make it happen.

Maybe a little keypad could be displayed while on the call?

Here's how I think blogging should work:

1. Visit a web app where you create your blog post, add pictures, use your rich text editor, that sort of thing.

2. Click the "Publish" button, which generates static HTML and runs any other processing like tag generation or pngcrush.

3. Your static HTML gets pushed out to some server that does the hosting for you. It could even be one of those really cheap shared hosting providers.

If you really want comments, let someone like Disqus or Intense Debate handle it. Pretty much any dynamic feature you need can be outsourced.

Seems like a safer bet to go after a demographic that you know typically pays for things.

Maybe a solid approach is:

Take the list of features your competitors have. Subtract the features people don't want Add the features that people are looking for that no one has.

If you implement more features, you don't necessarily have to implement them poorly. Maybe you need a larger team or more time.

  (cons "Is it an underhanded penny auction rip-off site?" *phrases*)

This is probably best as a web app, not a browser plugin.