• Quick note - the problem with Youtube videos not embedding on the forum appears to have been fixed, thanks to ZiprHead. If you do still see problems let me know.

Heeeeeeere's Obamacare!

Is it really here yet if it's still impossible to sign up?
 
Is it really here yet if it's still impossible to sign up?
Well aren't you being a drama queen. Impossible? Really? It's difficult because people are signing up. I got my log in and now I have until March 31 IIRC to purchase health insurance for the first time in a decade thanks to a back injury.

Take your pre ACA America and cram it in your cram hole.
 
Well aren't you being a drama queen. Impossible? Really? It's difficult because people are signing up. I got my log in and now I have until March 31 IIRC to purchase health insurance for the first time in a decade thanks to a back injury.

Take your pre ACA America and cram it in your cram hole.
I haven't been able to sign up, and neither has anyone I know. I can get as far as the "create account" screen, but after that is filled out the message "your account cannot be created at this time" appears. Every single time.

I guess that's a slight improvement over the first few days, when none of the security questions would display.
 
I haven't been able to sign up, and neither has anyone I know. I can get as far as the "create account" screen, but after that is filled out the message "your account cannot be created at this time" appears. Every single time.

I guess that's a slight improvement over the first few days, when none of the security questions would display.

And that's because people are using the website! Have you never seen the error page on jref on a lazy afternoon or during a terrorist attack or school shooting? Multiply that by the populations of America!

I have created my account and will chill for a few days until the stampede calms down. You will create yours and eventually get in. Coverage doesn't start till the new year. Chill Winston.
 
And that's because people are using the website! Have you never seen the error page on jref on a lazy afternoon or during a terrorist attack or school shooting? Multiply that by the populations of America!

I have created my account and will chill for a few days until the stampede calms down. You will create yours and eventually get in. Coverage doesn't start till the new year. Chill Winston.
I'm not sure too many people on the site is the problem. If the system is overloaded you get a screen telling you to wait, as there are a lot of people using the system. Once you get past that page it should not be an issue.
 
Spot on . I don't see the password restrictions as a big deal either.
As a professional web developer with over a decade of experience, the password restrictions point to a few disturbing things in the back end code.
  • An explanation for the disallowed characters is they can be used for a SQL injection attack, and the forbidden characters can be difficult to trim out of passwords. But if you're trimming characters out of CGI data to prevent a SQL injection attack, you're doing it wrong! There are much better ways of doing that, such as using a proper SQL prepare/execute process.
  • An explanation for the password length restriction is they're storing the passwords in plain text in the database. That is a plateful of wrong served up with a side order of wrong. The proper way to do it is to hash the passwords with a strong hashing algorithm (e.g. SHA-128) and a long salt, and store the hash and the salt in the database.
  • It could be the result of a poorly chosen framework in which the application was built. Or worse, a home-grown framework.
  • The most charitable explanation is the restrictions are imposed by management and the back end code is perfectly safe
 
Last edited:
I'm not sure too many people on the site is the problem. If the system is overloaded you get a screen telling you to wait, as there are a lot of people using the system. Once you get past that page it should not be an issue.

I am not sure what your claim is but go ahead and provide the proof.
 
I'm not sure too many people on the site is the problem. If the system is overloaded you get a screen telling you to wait, as there are a lot of people using the system. Once you get past that page it should not be an issue.

The screen telling you to wait pops up based on the developers estimate as to how many users the system can handle. Until the system goes live, that limit is only a guess. Unexpected performance issues could make the actual limit far lower than expected.
 
Last edited:
Oddly enough, sites like Facebook, Amazon, and Google regularly handle crushing loads. I have yet to hear one of those sites going down and then blaming user traffic.
 
Oddly enough, sites like Facebook, Amazon, and Google regularly handle crushing loads. I have yet to hear one of those sites going down and then blaming user traffic.

I take it you're not a gamer, are you? It's not a particularly surprising situation if they experienced a heavier load than expecting. For example, not long ago EA released SimCity. They had a pre-sales figure to help gauge initial demand but still failed to actually support the users. For days people could barely log in, let alone play the game.
 
Last edited:
I take it you're not a gamer, are you? It's not a particularly surprising situation if they experienced a heavier load than expecting. For example, not long ago EA released SimCity. They had a pre-sales figure to help gauge initial demand but still failed to actually support the users. For days people could barely log in, let alone play the game.

Pretty much this. It'll clear up eventually, but in the mean time, this heavy traffic is a good sign people like the ACA and that Republican talkingpoints are BS.
 
Oddly enough, sites like Facebook, Amazon, and Google regularly handle crushing loads. I have yet to hear one of those sites going down and then blaming user traffic.

A single computer can only handle so much load. The bigger sites handle this by adding more servers. The more servers, the more traffic you can handle. Whether user traffic can overload your site or not depends on how much traffic vs how many servers you have to handle the traffic.

Someone on a shared web hosting service can be taken down by a single person with some scripts. A site like Google which has buildings full of server farms is not likely to ever go down due to traffic volume.
 
Oddly enough, sites like Facebook, Amazon, and Google regularly handle crushing loads. I have yet to hear one of those sites going down and then blaming user traffic.

Were you not alive during the AOL debacle in 96?

Any large endeavor, be it private or public, rarely goes as planned. Sometimes people hate the new car you've made, or you lose a space shuttle, or a mirror in the Hubble has a flaw, or your invasion of Italy doesn't go anywhere, or they don't like the new soft drink you've created,...

Relax, the ACA isn't going anywhere.
 
Oddly enough, sites like Facebook, Amazon, and Google regularly handle crushing loads. I have yet to hear one of those sites going down and then blaming user traffic.

Clearly never tried to buy tickets to the 2012 Olympics then...
 
So what is your claim?
That the web site is currently a disaster and it's nearly impossible to create an account.

Have you tried it?

eta: and after I get the "Your account cannot be created at this time" message it says "Please note that two or more answers to the security questions cannot be the same. You must provide distinct answers to the chosen security questions."

I think this message is because some software error causes the system to think my answers are the same, and they certainly are not. It's 3 different answers to 3 different questions. I really doubt this has anything to do with volume of users.
 
Last edited:

Back
Top Bottom