Quote:
Originally Posted by XaQ Morphy
Pretty sure you need to work on your reading comprehension, because you're coming off like a complete moron here.
OK well this comment you made was based off of a quote which I am pretty sure i deleted about 5 minutes after posting because I felt it was in bad taste. I wrote that stuff (which i subsequently deleted) mostly cuz you spoke condescendingly towards me, which did not make me feel good.
So here, I am sincerely apologizing for that foulness, even in the message which i did not delete I had some spunk, but yeah im oi (over it) and i hope you will be too.
Now somewhere between the quote below and the quote above you stated that you dont know what my issue was, here goes nothin.
Quote:
Originally Posted by XaQ Morphy
The DNS thing would be Comcast's issue. I wouldn't doubt that Google's DNS servers (8.8.8.8) would be faster. Who knows what the hell Comcast is doing. If they are filtering via DNS then they have some sort of filtering server behind their DNS servers that have to filter every single connection coming through and either allow through or block. That's going to take a lot out of a connection.
Please forgive any oi grammatical issues and just get what im saying. I am hoping that coupled with your obvious book smarts, you have street smarts to go with it.
I dont have any years of IT experience, so I say this with all due respect. I think that maybe since non-comcast customers are having the same issue, and some comcast users are NOT having any issues, the issue is not specifically with Comcast. We have word from Comcast that they are not blocking bovada.lv, and word from Bovada that they "...understand that some people are having issues with their ISPs." (this is much less direct than comcasts response, I always feel that directness deserves more benefit of the doubt then, indirectness.)
Given the data in the thread, it is unfair to place the blame of the issue on Comcast. The main point of everything Ive ever posted in this thread, is that it doesn't matter whose fault it is. BOVADA has the PROBLEM.
You see, Comcast stands to lose virtually nothing from this issue, and Bovada stands to lose alot from this issue.
I'm not claiming that I know more than you about IT stuff, and Im absolutely not looking for a fight. All i am saying is that those who blame everyone but themselves tend to go nowhere, those who are willing to admit that there is room to improve, go far.
So to be more direct, if Bovada is at least willing to look inside and find a way to adjust their client to be immune to this issue, then this problem has a chance of going away and all the happy random fishes can come to play... If bovada chooses to play the blame game and wait for comcast, or any other IP to do something about it, then we just might lose one of the only remaining good sites we have left as Americans.
You wanted to know what my issue was, well there you have it. Hopefully I have barked down your tree enough to the point to where you will be nice to me.
All this being said, I am generally pleased with how Bovada is doing things, I just hope that they maintain their general influx of randoms (whatever that volume may be) to a point where the GTDs stay where they are at or even better go up.
In this case it is my honest opinion that they need to pinpoint the issue and find a way for their client to automatically workaround the issue with zero brainpower required from the user... lets not forget who we want to be playing with us now...