Archive for January, 2017

Development Update

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 support@blip.fm. 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!

Pain and progress

Happy 2017!  Thanks for all the helpful feedback on the on the move from FLASH to an HTML player.  A few people are still reporting errors and issues with the new player, but we will continue to track those and hopefully iron them out soon.  Moving forward, the good news is we are going to upgrade the code to current standards and fix outstanding FB and Twitter connectivity bugs. Although this will not result in a fancy new UI or new bells and whistles, we are excited just to make some long overdue code fixes. These fixes are necessary in order for Blip to continue to function, so yes they are the priority. Regarding content, we will do everything we can on our end to maximize availability, but ultimately content owners (artists, labels) determine what they make available to Blip.  Please continue to email support@blip.fm with detailed bug reports - these are extremely helpful.

Thanks again!