Will empeg put this stuff configured-to-run in the dev image sometime?

I gotta tell ya, Nils... I'm nervous about there even being a published "idiot's guide to FTP" for the Empeg, let alone a pre-built FTP server made easily available at their web site.

I mean, Hugo and Mac have been very nice to give the BBS'ers hints where necessary. But to me, even that is dangerous. What if the RIAA decided to sue them? Even without them supplying the software, the RIAA could say that they were helping the end-users to develop a music player capable of piracy. Even if Hugo didn't give us any hints... even if we came up with an "idiot's guide" on our own, there is the possibility that the Empeg could be legally considered a device capable of copying.

You see, the problem isn't really the idea of piracy so much, it's whether or not the Empeg can be classified as a digital music copier or a digital music player under the AHRA. Right now, the Empeg doesn't yet fall under the category of copier. Therefore, according to the text of the AHRA, Empeg doesn't have to pay a tax to the RIAA for every player sold. So if the Empeg were proved to be a copying device, the RIAA would see the Empeg as skirting around their little AHRA tax and could sue them for lost revenues plus damages.

Think about this for a minute... Don't you think that, at Empeg, they've already got a pre-built, easy-to-install image that includes PPP and FTP? Of course they do, they need it to do their development work and testing. They just can't give it to us because that would cross the line between music player and music copier. And if it's a music copier, that's when they have to get in bed with the RIAA and start paying the AHRA tax, and then it just gets too complicated.

___________
Tony Fabris