During maintenance the counters of props, listeners and blips have been reworked and will show zero values the next couple of days. This issue will be fixed soon. We apologies for the possible inconveniences.
Blip will be offline for 2-4 hours beginning 3 am Pacific Standard Time on April 11 , while we make updates to our servers. After coming back online, please report any bugs to firstname.lastname@example.org.
We are getting close to deploying updates to the site, so we wanted to give a heads up, properly set expectations, etc. To that end we have tried to anticipate some of your questions:
-”When is this thing going live?” We plan to put the updated site up by April 21, but be advised these sorts of dates tend to move.
-”What is going to be different?” Visually not much. Things should break less. Twitter and Facebook integrations should work again (though you may have to reset these connections). Most importantly the updated backend code will allow us to efficiently make later changes and improvements (such as to the UI).
-”Hey this thing is broken! I thought you were going to fix it not break it more.” It is likely that the updated site will have bugs we were unable to detect during our Q&A process. Please report any bugs by email to email@example.com.
-”What, this looks the same to me. Has anything even changed?” Sadly this is true. This update does not add any new features or update the user interface. That being said, these upgrades are a prerequisite to those kinds of future changes.
Please send any additional questions to firstname.lastname@example.org!
Just a quick update on development work and timing. Work is underway, but it will be quite a while before anything is visible (May). Keep in mind that the work being done is focused on updating the core code and fixing bugs (including FB and Twitter integrations). Something more fun like a design refresh is not in this round.
Thanks to some modest success in fundraising, we are about to commence a significant amount of development work to improve Blip.fm. If you have particular bugs that you want to see fixed during this work, make sure you email details to email@example.com. Please note that posting @replies to the blipfm account is not a good way to get bugs on the fix list. That account is not monitored for bug reports, so please use the support email.
Since the work being done constitutes a major rewrite of much of Blip’s code, in many cases it would be inefficient to go in and individually fix those bugs, only to have to rewrite that same code a couple weeks later. Sorry for any frustration this causes, but we have to be judicious with our limited resources.
Thanks for being a part of Blip!