I only use ip3k players, so I rely totally on a local server. I think that in a "community fork" scenario, a drastic change in users demographics must be taken into account. Casual internet radio users will go elsewhere, no new users, die-hard SB users leaving little by little. This would be the trend I think, if the fork was a great success but no new SB audio player would appear on the market.
With this in mind, I think it could be acceptable to "qualify" one small server platform (a plug of some sort), and have it managed like a router with dual firmware: reboot to update to the new firmware (which can be silently downloaded), if this doesn't work, power cycle to roll back to the working firmware. If you don't have to do this every day, I believe it could be acceptable considering the kind of users the service would have. The presence of a well-known server on the internet acting as a front end is indispensable I believe, but the layer could be thin. With a flock of tiny 24/7 servers maybe stream handling could be distributed, as in the torrents + tracker model ? Well I am sure you devs have a much clearer view of what can be done. I just want to stress the idea that if a fork happens, the user base will be different from today's. ------------------------------------------------------------------------ epoch1970's Profile: http://forums.slimdevices.com/member.php?userid=16711 View this thread: http://forums.slimdevices.com/showthread.php?t=96208 _______________________________________________ discuss mailing list discuss@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/discuss
