Archive by Author

Heads Up

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

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

Development Update

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!

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!

Quick Update Re: Player

We have begun work fixing the player, but it will probably be next week sometime before you can see any difference.  Basically Blip uses neolithic-era versions of third party APIs, and those third parties have stopped supporting the most ancient versions, so we have to update.  Some users have had no issues, while others have been encountering a major problems.  We will update you when the work is completed.