Board for everybody who is interested in BrainKing itself, its structure, features and future.
If you experience connection or speed problems with BrainKing, please visit Host Tracker and check "BrainKing.com" accessibility from various sites around the world. It may answer whether an issue is caused by BrainKing itself or your local network (or ISP provider).
MM- It is to save emails & such.. That can slow you down a bit if it is too full with saved emails. Have the webtver go to storage & clean up the discarded emails & the sent emails also..
They may help a bit..They can also use the 'goto' to access the site..If the person has the site saved under a fav number tell them to get rid of it...then try accessing the site they also should turn unit off. unplug it from the wall for 10 seconds then replug it..then reconnect but hit 'Moved' then connect to the net. then try acessing the site.
Fencer, just a quick question. How much bandwith does this site use? I know the page views are out the roof, but the data can't be too high can it? 100GB month?
I can finally enter the site after numerous numerous times today trying. But can't play any games. I can not get to my messages. I can not even read my own fellowships discussion board or some other discussion boards also. :(
I have called webtv technical support, they also tried accessing Brainking and were unable to.More then 1 technical person tried. They also told me that something in the coding in the games is making the pieces disappear. It is not compatible to webtv. We have no proxy cache I was told by them also. I hope that helps Fencer to maybe solve the problem for webtvers! :)
PrettyBlueEyes: What coding? There were no changes in HTML code for more than half a year! The site is working properly, it is tested and proven. And it IS compatible to WebTV. I have no idea why your device suddenly stopped working with it.
Finally.....
Hi everyone. After days of trying I am finally able to get here. I don't think it's a webtv problem. Something is going on here. I've been getting the to busy to use notice. It's 5:00am now and probably the only reason it let me in, less traffic. Deleting cookies didn't help either.
Aaarggghhhh! Nothing is going on here. Get a computer with normal browser instead of that "browser" with no support for meaningful error messages or HTTP header console.
Don't say it to Liquid, he would kill you within ten seconds. Because we had spend almost the whole day investigating all possible problems OUTSIDE our server which is NOT a part of our responsibility and THE SITE IS NOT BUSY!
One more "problem" like that and I will mark WebTV as an unsupported platform.
Hi, all seems fine for me this morning. Not one problem so far, all is like it was before Saturday.
I was able to get one once Saturday during the BK2.0 use, and what I saw then looked pretty cool.
I have had the same problems as by reported by other webtv users over the last several days, but again, all seems 'normal' this morning, and I have not done anything on this end....
ood luck Fencer, and PLEASE don't get too frustrated and stop supporting WebTV :)
Is the message WebTV users are getting (about site being too busy) a page ON brainking, or a WebTV message?
One good thing Fencer - If BK2.0 went up, and webtv people were having problems - you would then be wondering if it was on your side with the new coding. But since everything is the same today as it was last week - it almost has to be something on WebTV's side.
If Fencer makes this site unsupported from a webtv then I would need my funds back. I am paid through December 2005 on the basis that this a site that is accessable with webtv. If it changes then I think it would be reasonable to expect a refund.
Yes it works good for webtv now. However my comment was such that if and when BK2.0 is here for good and if webtv will not be supported due to the coding or whatever reason, I feel webtv customers should be compensated for the unused portion of their membership as a result. Unlike other things like phone, cable, electric, etc where you pay so much a month and you are paying as you go, here you are paying in advance for a certain length of time based on the accessability. If the time comes that service is no longer available due changes beyond the consumer's control, they should be compensated accordingly. However I do feel they will take care of the webtv bug, because they do have a number of paying members on webtv. I am also curious if the NTL service had problems like the webtv service did.
Have a look at the computer board, Brian. I don't follow all of it, but it doesn't seem to be a problem at BrainKing that caused webtv users to be unable to access the site.
I'm not an expert, and I haven't read the computer board.... It seems to me that it was a problem with WebTV but the cause of the problem was BrainKing. If it wasn't for Brainking Switching over and then back, there would have been no problem at all.
BTW... Were there access problems for everyone in BK2? Or were there other problems including WebTv access?
Brian1971: There were a couple of webtv users testing BK2 before it went public as it were. They experienced no problems.
IMupChucKing: Yes, a couple of PC users did have a problem getting here after BK2 but that problem sorted itself out. Something to do with DNS and servers.
- Everyone could access the site
- BK started the switchover.
- Everyone could still access the site
- BK2.0 came up
- Everyone could still access the site
- (about 30 seconds after BK2.0 was up, it had problems)
- During one of the "down times", or "server reboots", WebTV's proxy server checks BrainKing, and does not see it - so it took it off it's list of working sites. (Proxy server keeps "copies" of some sites to increase speed - instead of the user from making it all the way to the destination and back, it stops half way at the proxy server and pulls that page - saving 1/2 the time)
- BrainKing 1.0 comes back on-line
- Most world can see BrainKing, but WebTV see's the broke proxy server copy of BrainKing
- WebTV after a day or so updated it's proxy server and now works for WebTV
OK - that is a very simple explination on what I think happened. :-)