Posts Tagged ‘error’
You might remember the products. You might remember the hype. Then, you are tooling down highway 41 years later and all of a sudden you think to yourself – “Hey, whatever happened to…”
Failed ideas. Maybe it was a great idea, but wasn’t made right, or design errors brought it down. Maybe it was just a bad product. Well, let’s take a stroll down memory lane and see if we cannot repeat these errors again.
Oh yeah, why 16? Well because we could.
The Computer Watch: Whether it was the Ruputer, the MSN Direct ‘Smart’ Watches, the Timex Data Link Watch or another gadget watch – BTW – I remember having a “Transformers watch”. It was awesome!
Still, the Dick Tracey style communication watches, the “Computer on a wrist”, never really hit it off. I even remember a watch that gave you directions. You would put in the paper tape and turn a little dial to indicate where you are and where you are going.
I went to Hulu this afternoon to catch up on my HEROES. I didn’t get to see it on Monday, so I knew that I could go up there and watch the show without issue. Or COULD I?
Turns out Avast won’t have it. It is blocking the SWF from playing and saying “Malicious Code”. Tried a few times in Firefox and IE. Every show or movie I try to play comes up with the same thing.
Here’s the kicker – neither Avast nor the Event viewer is showing any more info. In fact, it’s not even logging the event!
Could this be a malicious code? Could it be that Avasts’ database is off? Maybe Hulu changed some stuff to thwart Boxee from going through the RSS backdoor?
Well, there is a way around that. I went to NBC.com and watched the episode. I hope it’s not a real issue on Hulu…
**Update – Avast has posted an update to allow the Hulu SWF through. There was still no Event log on what it blocked**
For the last 6 months, Geekazine has been using OpenID to try and give people another way to comment on the articles. Ever since, there have been problems with this plugin. Error logs going off the chart in what I can only determine as bots using the interface.
We have tried to fix the problems and keep OpenID alive on Geekazine. Alas, the end result was it didn’t make sense to keep the ideal around right now. Therefore, until further notice, we have decided to cut ties with OpenID until a viable solution can be made.
Once the system is up and proven working properly, we will reimplement. Sorry for any inconvenience.













