[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #5004 [Tor Cloud]: Remove support for configuring Tor cloud images as public relays
#5004: Remove support for configuring Tor cloud images as public relays
-----------------------+----------------------------------------------------
Reporter: rransom | Owner: runa
Type: defect | Status: new
Priority: normal | Milestone:
Component: Tor Cloud | Version:
Keywords: | Parent:
Points: | Actualpoints:
-----------------------+----------------------------------------------------
Comment(by phobos):
Replying to [comment:4 arma]:
> Replying to [comment:3 phobos]:
> > Has anyone actually tried this and seen the costs? Or is this just
pontification?
>
> See #4387.
Right. This ticket doesn't say anyone has actually tried to run a relay on
AWS, just that if they did, the median relay is 269 GB of traffic per
week, which could be around 1 TB per month.
> But back to pontification: I think if you have extra money and want to
help with relays, you should donate it to torservers, noisebridge, etc. A
bunch of tiny relays all in the same place is not very helpful to the Tor
network (and in fact, once I'm done with more performance analysis, I
expect to be able to say more confidently that it is harmful to the Tor
network).
I'd prefer to let the potential relay op decide, rather than us remove the
choice altogether. Many people have budgets they have to spend on certain
things, which cannot be reallocated. We can clearly state that it's
cheaper/better/more-huggy to donate to torservers, noisetor, etc, but if
someone has to spend $10,000/mo on AWS, and is under budget, then why not
make it easy for them to do so?
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/5004#comment:5>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs