<div dir="ltr">It actually looks like I have the introducer setup correctly, but my storage nodes still need some work. You should be able to connect, but just not access any storage.<br><div class="gmail_extra"><br><br><div class="gmail_quote">
On Mon, Feb 4, 2013 at 9:06 AM, Paul Rabahy <span dir="ltr"><<a href="mailto:prabahy@gmail.com" target="_blank">prabahy@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">I volunteer to become "<span style="font-family:arial,sans-serif;font-size:13px">Test Grid Wrangler". I setup a new introducer and hooked up a storage node to it. </span><font face="arial, sans-serif"><a href="https://tahoe-lafs.org/trac/tahoe-lafs/wiki/TestGrid" target="_blank">https://tahoe-lafs.org/trac/tahoe-lafs/wiki/TestGrid</a> has been updated with the new introducer furl and public test directory.</font><div>
<font face="arial, sans-serif"><br></font></div><div><font face="arial, sans-serif">It still appears that I need to setup some more port forwarding or something because I cannot connect to it from outside my LAN. I'll try to do that this evening (Eastern Timezone).</font></div>
<div><font face="arial, sans-serif"><br></font></div><div><font face="arial, sans-serif">@Till, I haven't seen a setting for this. My main thought is that if a person was trying to abuse the system they could just break the file into many small chunks and upload them all. Hopefully once the accounting project is finished we will be able to set per-user storage limits.</font></div>
<div><font face="arial, sans-serif"><br></font></div><div><font face="arial, sans-serif">@Eric, Agreed. The test grid was the first place I went to quickly try out Tahoe-LAFS. Without it, I believe that I would have lost interest and tried to find a different product.</font></div>
<div><font face="arial, sans-serif"><br></font></div><div><font face="arial, sans-serif">@Greg, My plan is to have a public introducer, but each user will have to setup their own node. If another person sets up a public WUI, I don't know if there is much I will be able to do about it. We can cross that bridge if/when we come to it.</font></div>
</div><div class="gmail_extra"><br><br><div class="gmail_quote"><div><div class="h5">On Mon, Feb 4, 2013 at 8:37 AM, Greg Troxel <span dir="ltr"><<a href="mailto:gdt@ir.bbn.com" target="_blank">gdt@ir.bbn.com</a>></span> wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5">
<div><br>
"<a href="mailto:erpo41@gmail.com" target="_blank">erpo41@gmail.com</a>" <<a href="mailto:erpo41@gmail.com" target="_blank">erpo41@gmail.com</a>> writes:<br>
<br>
> I liked the test grid when I was just getting started. If I had had to set<br>
> up my own introducer and server and client just to try it out, I probably<br>
> would have passed. I definitely would not have set up multiple VMs to play<br>
> with different values of n and h.<br>
><br>
> To prevent abuse, we could just set the expiration time for files to 48<br>
> hours.<br>
<br>
</div>My impression is that the cause of the abuse (not fair, I know) is the<br>
public gateway. Once you need to set up a client to use it, the effort<br>
becomes too high compared to other file distribution methods. I found<br>
the pubgrid very useful when getting started, and the public WUI not<br>
really that useful.<br>
<br></div></div><div class="im">_______________________________________________<br>
tahoe-dev mailing list<br>
<a href="mailto:tahoe-dev@tahoe-lafs.org" target="_blank">tahoe-dev@tahoe-lafs.org</a><br>
<a href="https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev" target="_blank">https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev</a><br>
<br></div></blockquote></div><br></div>
</blockquote></div><br></div></div>