Bart Hoekstra's dashboard

Bart Hoekstra started following the idea "Consider adding bit.ly integration as tumblr short url is too long." in Tumblr.

Bart Hoekstra replied on September 23, 2009 17:07 to the problem "LinkedIn doesn't work with Google Chrome!!!" in LinkedIn:

Well, at least it did work yesterday. Now it seems like I'm having the same problem again. Anything changed in the ads? Is LinkedIn actually going to try to solve this problem?

Bart Hoekstra replied on September 22, 2009 18:40 to the problem "LinkedIn doesn't work with Google Chrome!!!" in LinkedIn:

It seems like the problems have resolved itself. I can now use LinkedIn with Google Chrome without any problems.

Bart Hoekstra replied on September 01, 2009 18:40 to the problem "LinkedIn doesn't work with Google Chrome!!!" in LinkedIn:

I am having the exact same problem as above mentioned. I haven't found a workaround for it actually, but as said before: it probably has anything to do with the ads. When I use the Google Chrome developer tools, I can see that when the Javascript-file GetRcmd.js (http://rc.wl.webads.nl/Get/WebAds/JS/GetRcmd.js?d=82128036394715) is being loaded, the fun starts. After it's loaded there is a 'gap' between the execution time of the scripts used by LinkedIn. Although GetRcmd.js is a very small file, it seems to have quite a big influence on the system.

Here's a screenshot of Google Chrome's Developer Tools -> Resources which should make more clear what I am seeing:


And my browser configuration:
Google Chrome: 4.0.203.2 (Official Build 24690)
WebKit: 532.0
V8: 1.3.8
User Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US) AppleWebKit/532.0 (KHTML, like Gecko) Chrome/4.0.203.2 Safari/532.0

BTW: I've found out that this problem not only appears when using Google Chrome. SRWare Iron, which is also build around the Webkit-engine seems to create the same problem. Same happened in Chromium. Only webkit-browser that didn't reproduce this problem is Safari (4.0.2 running on Webkit 530.19.1).

I hope this will help solving this problem. Perhaps it'll disappear after Webkit gets updated, but still only LinkedIn's javascript seem to trigger this bug.

Bart Hoekstra started following the problem "LinkedIn doesn't work with Google Chrome!!!" in LinkedIn.

Bart Hoekstra replied on June 14, 2009 07:29 to the problem "My #hashes and my tweets don't show up!" in Twitter:

I'm having the same problem, now for 12 days.

@barthoekstra

Bart Hoekstra started following the problem "My #hashes and my tweets don't show up!" in Twitter.

Bart Hoekstra started following the idea "Energy Consumption" in Spymaster.

Bart Hoekstra shared an idea in Twones on May 05, 2009 17:18:

Stand-alone Tracker

I would love to see Twones have a stand-alone tracker, because it happens alot that I just have iTunes or Windows Mediaplayer running while I don't have Firefox running. In fact I use Google Chrome a lot more, but I know it doesn't have plugin-support yet.

Bart Hoekstra shared an idea in quub on April 30, 2009 09:08:

Make more clear what Quub actually is

When I initially applied for the Quub-beta I thought: 'Hey this looks cool! It looks like Twitter and that's cool too!' It's a bit exaggerated but I think that's the way that a lot of people will be thinking of Quub. Now I know that it's different, it's more quick status updating than it is a micro-blogging service.

I think that this (in future) might cause a problem to Quub: People thinking that it's micro-blogging, while it actually is status-updating in the purest form.

So my advice is: Make more clear what Quub is, what it stands for and how it works 'before' people join.

Bart Hoekstra replied on April 30, 2009 07:58 to the idea "Secure Authentication" in quub:

As stated above. oAuth would do the job. It would make me feel more comfortable. Although I do trust you guys won't ruin my other social networks.

A comment on the question "Twitter has locked me out for no reason!" in Twitter:

Well silverton. This was exactly my problem. I was locked out because TweetDeck probably tried to login way too many times with my wrong credentials. That made me be locked out. And I only tell this because there are a lot of people that have the problem and use TweetDeck. So it does make sense, perhaps not to you, but it might to others. – Bart Hoekstra, on April 24, 2009 04:17

Bart Hoekstra replied on April 23, 2009 19:51 to the question "Twitter has locked me out for no reason!" in Twitter:

I had the same problem and solved it. If you have TweetDeck installed, it can be the bottleneck.

1. Uninstall TweetDeck
2. Change your Twitter password
3. Install TweetDeck
4. And it should then work.

The reason for me being locked out was that TweetDeck was apparently still trying to log in with my old password.

Bart Hoekstra replied on March 26, 2009 19:29 to the problem "I am "Locked out!"" in Twitter:

I had the same problems. I solved it by uninstalling TweetDeck and then change my password. When that is finished you should be able to login on both TweetDeck and Twitter again.

Bart Hoekstra started following the question "Tweetdeck/Twitter Lockout Issues" in Twitter.

Bart Hoekstra replied on March 26, 2009 18:39 to the question "Twitter has locked me out for no reason!" in Twitter:

I am having exactly the same. Twitter skrews up. When I use 'Forgotten password?' Twitter allows me to change it (again) and login, but it doesn't solve my problems. When I logout and try to login again it says my account is locked because I tried to login multiple times and failed.

Bart Hoekstra started following the question "Twitter has locked me out for no reason!" in Twitter.

Bart Hoekstra started following the question "Twitter has locked me out for no reason!" in Twitter.