OK, so further development of the Squeezebox product line and ecosystem as we know it by Logitech is now officially dead or being extincted. However, legacy SB devices such as the SBx players, Duet, Touch, TP etc. can continue to function perfectly well to service a local music library without further LMS development, even if mysqueezebox.com should be decommissioned. The way I see it those looking for online media consumption/ streaming devices will and should begin looking to alternatives (please lets not debate that in this thread - anyone wishing to explore this topic please do so in a separate thread) - for those of us using the SB range principally to serve as an interface to our local music collections and as DACs and/or transports to feed an external DAC, the question is what steps need to be taken to completely remove any dependency on Logitech and any of its online services to enable the devices to continue to operate independently for as long as the hardware continues to function.
The purpose of this thread then is to tease out what needs to happen and how best to make that happen. Hopefully those with the technical knowledge of some of the innards will respond where the answer isn't obvious. Please feel free to add additional questions that you may feel need to be answered in a quest to ensure continued viability of the ecosystem sans Logitech. Here's my take: - determine and archive online downloadable copies of the last known good versions of LMS to preserve a means of having a fully funtional Squeezebox as we know it - first point above should cover all platforms for which there is a build available, including the source code version. This could serve as the basis for an open source fork, in effect a community maintained and enhanced LMS - obtain copies of say last 3 firmware releases for each of the devices - ascertain how to remove all dependencies on mysqueezebox.com - to my knowledge it is only the Touch that requires this on initial registration - can it be worked around/ removed? This is key as we want to ensure that the devices have no external dependencies - 3rd party applets and plugins - a whole host of these come to mind and methods need to be devices to store and access these in future (Erland's plugin suite, Spicefly , Triode's EDO etc. come to mind) - preserve the knowledge encapsulated in this forum and in the Wiki's - can they be replicated, how would they be hosted, could they be cut down to a focused Wiki dealing with the specific nuances of each devices e.g. how to hardware reset a TP, SB3, Touch etc. - maintaining a community of interest: viable? Only viable if there is ongoing development or forking of LMS Thoughts? ------------------------------------------------------------------------ audiomuze's Profile: http://forums.slimdevices.com/member.php?userid=33613 View this thread: http://forums.slimdevices.com/showthread.php?t=96208 _______________________________________________ discuss mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/discuss
