<p>If security through obscurity is fine, then just keeping the nodes bearing the links private is enough, and we can go with mod_proxy. Personally I think that's fine. I can even put "salt" in the URL's so they can't be guessed without access to the node.</p>
<p>On May 20, 2010 7:56 PM, "Chris Ritzo" <<a href="mailto:chris.ritzo@gmail.com">chris.ritzo@gmail.com</a>> wrote:<br><br><p>I think Joe said that there were licensing issues with making the recordings available to the www. That's why we were discussing using drupal users or roles to limit access to wrfu members. </p>
<p><blockquote type="cite"><p><font color="#500050"><br>><br>> On May 20, 2010 7:30 PM, "Josh King" <<a href="mailto:josh@ucimc.org">josh@ucimc.org</a>> wrote:<br>><br>> No, in my scenario it would be...</font></p>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><p><font color="#500050"><p><font color="#500050"><br>>><br>>> ><br>>> > I just installed feedAPI and set up a new content type "Show Recording".</font></p>
> Currently only admins...</font></p><p><font color="#500050"><br>>><br>>> <a href="http://recordings.wrfu.net">recordings.wrfu.net</a> <<a href="http://recordings.wrfu.net">http://recordings.wrfu.net</a>> would only be visible</font></p>
<p>
<font color="#500050"><p><font color="#500050"><br>>><br>>><br>>> > on the internal IMC networks. This is a fine a path as any... Once we</font></p>> have a CSV file and the s...</font></p><p><font color="#500050"><br>
>><br>>> > <mailto:<a href="mailto:josh@ucimc.org">josh@ucimc.org</a>>> wrote:<br>>> ></font></p><p><font color="#500050"><p><font color="#500050"><br>>><br>>> > Sorry, I shouldn't have said path. Instead of a filesystem path, I</font></p>
> mean a request URI path...</font></p><p><font color="#500050"><br>>><br>>> <a href="http://grimlock.i.chambana.net">grimlock.i.chambana.net</a> <<a href="http://grimlock.i.chambana.net">http://grimlock.i.chambana.net</a>> on the</font></p>
<p><font color="#500050"><p><font color="#500050"><br>>><br>>><br>>> > internal network, but I'm not sure how that works with Feeds/FeedAPI</font></p>> (Chris, you probably...</font></p><p>
<font color="#500050"><p><font color="#500050"><br>>><br>>> > <mailto:<a href="mailto:josh@ucimc.org">josh@ucimc.org</a> <mailto:<a href="mailto:josh@ucimc.org">josh@ucimc.org</a>>>> wrote:<br>
>> ></font></p>> In that case, I thin...</font></p><p><font color="#500050"><p><font color="#500050"><br>>><br>>> > <mailto:<a href="mailto:joefutrelle@gmail.com">joefutrelle@gmail.com</a> <mailto:<a href="mailto:joefutrelle@gmail.com">joefutrelle@gmail.com</a>>>>><br>
>> ><br>>> > ...</font></p>>...</font></p><p><font color="#500050"><br>>><br>>> > <mailto:<a href="mailto:chris.ritzo@gmail.com">chris.ritzo@gmail.com</a> <mailto:<a href="mailto:chris.ritzo@gmail.com">chris.ritzo@gmail.com</a>></font></p>
<p><font color="#500050"><p><font color="#500050"><br>>><br>>> > <mailto:<a href="mailto:chris.ritzo@gmail.com">chris.ritzo@gmail.com</a> <mailto:<a href="mailto:chris.ritzo@gmail.com">chris.ritzo@gmail.com</a>>>>><br>
>> ><br>>> > ...</font></p>
>...</font></p><p><font color="#500050"><br>>><br>>> > <mailto:<a href="mailto:joefutrelle@gmail.com">joefutrelle@gmail.com</a> <mailto:<a href="mailto:joefutrelle@gmail.com">joefutrelle@gmail.com</a>><br>
>><br>>> > <mailto:...</font></p><p><font color="#500050">> <mailto:<a href="mailto:chris.ritzo@gmail.com" target="_blank">chris.ritzo@gmail.com</a> <mailto:<a href="mailto:chris.ritzo@gmail.com" target="_blank">chris.ritzo@gmail.com</a>></font></p>
<p><font color="#500050"><p><font color="#500050"><br>>><br>>> > <mailto:<a href="mailto:chris.ritzo@gmail.com">chris.ritzo@gmail.com</a> <mailto:<a href="mailto:chris.ritzo@gmail.com">chris.ritzo@gmail.com</a>>>>><br>
>> ></font></p>> ...</font></p>
</blockquote><p><font color="#500050"><br><br>-- <br><p><font color="#500050">> This message has been scanned for viruses and<br>> dangerous content by MailScanner, and is</font></p>believe...</font></p></blockquote>
</p>
</p>
<br />--
<br />This message has been scanned for viruses and
<br />dangerous content by
<a href="http://www.mailscanner.info/"><b>MailScanner</b></a>, and is
<br />believed to be clean.