Live data from Hacker News

Dumb website only lets one user in at a time

imherefor.me

51–60 of 104 posts

Re: Dumb website only lets one user in at a time

#52
post #40

Not at all the same thing I admit, but the company I work for has a product that limits the number of transactions (per user) to 1. Where "transaction" is roughly equivalent to an HTTP request. So if you run a query that takes 30 seconds, get bored, open up a new tab to do something else in the product, your new tab will hang until the transaction in the previous tab has completed. I hate it. There is a special URL t…

Ha. When I moved into my town, the public library's online book search was only turned on from 9-5, monday through saturday. Apparently it was so unstable they didn't want anyone trying to use it unless they had an IT guy on hand? I'm guessing? Anyway, they eventually outsourced to bibliocommons, but oy, what a ridiculous limitation to have as late as 2007.

Re: Dumb website only lets one user in at a time

#53
post #32

Earlier quoted context omitted.

The idea was that you would visit participating merchants, spend money there and they would give you codes on stickers that they generated from our site and then the customers would use those codes on the site with purchase amount to get sayacash. One problem we had was that the codes we generated turned out to be invalid because... we didnt know why. We generated the codes, but they werent in the database. Where did…

Wow in the first video the man behind the camera refers to customers as clowns. Acts as if the guy he grabbed is stupid and not capable to enter a code on the web page. So weird.

I just noticed that the video about donating to charities ends with the narrator trailing off with "I don't know what I should say".

I am surprised we decided to upload those videos. It might have been during the time when people weren't being paid regularly

Re: Dumb website only lets one user in at a time

#54
post #31

Earlier quoted context omitted.

It's not that uncommon in some languages where you have a long running monolith (.NET, Java, etc) instead of an instance of something that spins up per request (Node, PHP, etc). If someone does something silly like setting the session handler to be scoped to the monolith app rather than having a scope of a single request you end up with users seeing one another's data. It's dangerously easy to do in some frameworks.

No, more likely someone's used global or static variables. It's got nothing to do with monoliths vs micro services. You can do the same global/static variable crap in a micro-service. Plus you didn't even need to multi thread in old school asp.net, IIS would create a new process for every request back in the day. .Net did have a notorious 'session' object, which was the cause of a lot of problems due to novice/offsho…

I don't think node really existed when this was made in late 2009. It was built with jsf: Java server faces. Its a bit like a more enterprisey version of GWT. Everything on the page was a huge class with lots of horrors that eventually became html css and js that you never wrote.

I checked, node existed but it was a toy compared to jsf.

Re: Dumb website only lets one user in at a time

#55

You can see the page from the source code: Congratulations Only you can see this website. Don't leave or you'll lose your spot.

Looks like it's no longer in the html source, but it can still be viewed in the javascript source code:

if (status === "inside") {

   text.push("i am the only person who can see this website.");

   text.push(link);

   if (waiting > 1) {

     text.push(`${queueLength - 1} people are waiting to get in.`);

   }

   text.push("want to see it? get in line, sucker.");

 } else {

   text.push("only one person at a time gets to see this website.");

   text.push(link);

   text.push("get in line behind me.");

   if (waiting > 1) {

     text.push(`currently, ${waiting} people are waiting.`);

   }

 }



 text.push("i'm here for me.");

Re: Dumb website only lets one user in at a time

#56
post #40

Not at all the same thing I admit, but the company I work for has a product that limits the number of transactions (per user) to 1. Where "transaction" is roughly equivalent to an HTTP request. So if you run a query that takes 30 seconds, get bored, open up a new tab to do something else in the product, your new tab will hang until the transaction in the previous tab has completed. I hate it. There is a special URL t…

This sounds like ServiceNow… if it is I’d love to know that special URL.

Re: Dumb website only lets one user in at a time

#57
post #53

Earlier quoted context omitted.

Wow in the first video the man behind the camera refers to customers as clowns. Acts as if the guy he grabbed is stupid and not capable to enter a code on the web page. So weird.

I just noticed that the video about donating to charities ends with the narrator trailing off with "I don't know what I should say". I am surprised we decided to upload those videos. It might have been during the time when people weren't being paid regularly

It sounds like this was a terrible, terrible, terrible, terrible, terrible company. I suppose it's telling that a Google search mostly turns up your story about the company, and an assortment of random mentions from a decade and a half ago. How did Sayagle die in the end?

Re: Dumb website only lets one user in at a time

#58
post #31

Earlier quoted context omitted.

It's not that uncommon in some languages where you have a long running monolith (.NET, Java, etc) instead of an instance of something that spins up per request (Node, PHP, etc). If someone does something silly like setting the session handler to be scoped to the monolith app rather than having a scope of a single request you end up with users seeing one another's data. It's dangerously easy to do in some frameworks.

Stateful singletons (and/or shared classes) are _probably_ a more common blunder than session scoping.

There are many ways to shoot yourself in the foot.

Re: Dumb website only lets one user in at a time

#60
post #40

Not at all the same thing I admit, but the company I work for has a product that limits the number of transactions (per user) to 1. Where "transaction" is roughly equivalent to an HTTP request. So if you run a query that takes 30 seconds, get bored, open up a new tab to do something else in the product, your new tab will hang until the transaction in the previous tab has completed. I hate it. There is a special URL t…

Ha. When I moved into my town, the public library's online book search was only turned on from 9-5, monday through saturday. Apparently it was so unstable they didn't want anyone trying to use it unless they had an IT guy on hand? I'm guessing? Anyway, they eventually outsourced to bibliocommons, but oy, what a ridiculous limitation to have as late as 2007.

A local pizza place has a website that closes outside of business hours. Which is infuriating if you're trying to figure out business hours in the first place.
Post reply on HN