Michiel Sikkes's dashboard

Michiel Sikkes replied on February 04, 2009 16:33 to the problem "Error: "Oops! Something behind the scenes went wrong"" in Firmhouse:

Boris. The problem was caused because you still had our old account encryption method for your account. I've flushed the encrypted password.

If you login now, it should work!

Michiel Sikkes reported a problem in Firmhouse on January 12, 2009 23:21:

Boxes on the dashboards are shuffled after saving them

After adding boxes to a new dashboard they get reshuffled on the page.

This is due that we do not save the order of the boxes yet and you can't re-order them yet in the interface. We're working on this :)

Michiel Sikkes set one of Michiel Sikkes' replies as an official response to "Add textbox to send Tweets" in Firmhouse

Michiel Sikkes replied on January 12, 2009 23:17 to the idea "Add textbox to send Tweets" in Firmhouse:

Should be up and running in the newest interface updates as of Jan 13th :)

Michiel Sikkes replied on January 12, 2009 18:07 to the problem "My reply input box gets hidden suddenly sometimes" in Firmhouse:

We're going to refresh the status updates inline so the box will remain the same and only the status update items get updated.

Michiel Sikkes reported a problem in Firmhouse on January 12, 2009 18:06:

My reply input box gets hidden suddenly sometimes

The box on the dashboards auto-refresh making it impossible to reply a tweet sometimes because it refreshes the form.

Michiel Sikkes reported a problem in Tweetburner on January 05, 2009 22:03:

The bookmarklet doesn't remember my account info

Do you have troubles with the bookmarklet not remembering your account info? We are receiving reports that the "remember" option in the bookmarklet does not work correctly, but we cannot reproduce the error ourselves. It would really help us if you can test it for us. There are three scenarios:

1. You are not logged in and are using the bookmarklet by manually inserting your Twitter/Friendfeed account-info


2. You are signed in with Tweetburner and added your Twitter and/or Friendfeed account info in the Settings tab.


3. You are signed in with Tweetburner but have not saved your Twitter and/or Friendfeed account info.

If you have more information or thoughts on this issue, please let us know by replying!

Michiel

A comment on the question "Is it possible to force-release a revision?" in Beanstalk:

Thanks for the response. (Re)deploying a specific revision would be good. To rollback or to force-release something if a thing went wrong during uploading.

I think keeping a deployment server per host is important or if the host changes that the deployment history will be deleted and you can re-deploy every release.

For now for advanced deploying scenarious I would still use Capistrano but for simple uploading of html mockups for my other team members to review them the ftp deployment is my primary tool :)

Michiel – Michiel Sikkes, on December 12, 2008 13:23

Michiel Sikkes replied on December 11, 2008 16:10 to the question "Is it possible to force-release a revision?" in Beanstalk:

Hi Petyo,

Thank you very much for your quick response. The point is that the deployment method was already set to manual so I couldn't manually re-deploy because the latest revision was already in place in the old server.

I fixed it now with a dummy commit but force-releasing the last release (also if already released) would be a great thing :)

Michiel

Michiel Sikkes asked a question in Beanstalk on December 11, 2008 14:32:

Is it possible to force-release a revision?

I would like to force-release a revision. For instance, I just changed the host details of my Production server and I want to deploy everything over ftp to the new server. Beanstalk already has updated the old server with the latest revision so now I'm forced to make a new revision in the repository to re-release everything to the new server.

Thanks in advance for your answer :)

Michiel Sikkes replied on October 17, 2008 13:35 to the question "GET API method" in Tweetburner:

A POST is the best standard method to create or modify data on websites. From a standards point of view, all data that is destroyed or created should be modified by a POST request.

Because we know the GET request might be more usable for more applications, we put it on the list to be able to call it without an XMLHttpRequest.

So for now, it's not possible with a simple GET request but we're looking at implementing it at a later time.

Michiel Sikkes set one of Michiel Sikkes' replies as an official response to "GET API method" in Tweetburner

Michiel Sikkes replied on October 17, 2008 13:07 to the question "GET API method" in Tweetburner:

Hi Glenn,

Yes we do have some API functions available through the GET method. Onfortunately they aren't documented yet but you can use the following:

Send an XMLHttpRequest to http://tweetburner.com/links/create?u... and you'll get the Twurl in plaintext. But, the best way to generate a twurl is to do a POST to http://tweetburner.com/links/create with postBody is "link[url]=http://johndoe.com"

If you want to grab statistics of a Twurl, do a GET to either of these URL.

• http://tweetburner.com/links/code.json
  
• http://tweetburner.com/links/code.xml
  

I hope this helps. If you need more info, please let us know!

Michiel Sikkes replied on July 13, 2008 14:39 to the problem "Does changing twitter password create a problem?" in Tweetburner:

Hi! It should not make a difference. Tweetburner only stores your username to get your account data. It is possible that we did not track all your twurls! We are looking into this. Thanks for your comment.

Michiel Sikkes replied on June 23, 2008 07:49 to the problem "Twurl doesn't track my twurls" in Tweetburner:

Hi aburiano! Thank you for your report. I looked at the links you posted and it does indeed look like we have not tracked all your Twurls. First of all: I'm sorry for that. Secondly, we're investigating better means of following all users on Twitter. Due to Twitter's instability the last few weeks it has been a somewhat painful journey.

We will keep you updated!

Michiel Sikkes replied on June 20, 2008 13:19 to the problem "Latest Twurls not showing up in stats." in Tweetburner:

Hi Roeland,

Thank you for your positive feedback! Indeed it seems like you hit a bug on our side :) Can you tell me how you posted the second tweet? The one where there are no statistics on your profile page.

Maybe we can talk on Google Talk or Jabber. You can add me with michiel@firmhouse.nl

Thanks for reporting!

Michiel Sikkes replied on June 18, 2008 22:05 to the problem "Not all Twurls picked up by Tweetburner" in Tweetburner:

We're still investigating on why Summize and our own script are still not picking up all of the Twurls posted through Twitter. As you might know, due to the issues with Twitter itself, we can't use all functionality to search for all tweets.

We'll keep you updated through the blog, the homepage and the GetSatisfaction page!

Michiel Sikkes replied on June 16, 2008 21:58 to the problem "Not all Twurls picked up by Tweetburner" in Tweetburner:

Hm that's odd indeed. It might be that our Summize script didn't pick it up correctly. We're going to look into it.

Michiel Sikkes replied on June 15, 2008 22:38 to the problem "Not all Twurls picked up by Tweetburner" in Tweetburner:

Ok. Thank you for noticing. We have made some improvements in the Summize integration and everything should be fine now.

Michiel Sikkes set one of Michiel Sikkes' replies as an official response to "Tweetburner not tracking all links from Twitterfeed" in Tweetburner