On January 27, 2019 8:19:43 PM UTC, Keifer Bly wrote:
>So, advertised bandwidth is based on how much bandwidth the clients are
>currently using and not how fast it actually is?
Yes. Here is the description of advertised bandwidth from the glossary:
"Bandwidth
The volume of traffic, both
So, advertised bandwidth is based on how much bandwidth the clients are
currently using and not how fast it actually is?
I had another question as well, I guess I should update the ContactInfo line to
a not obfuscated email address so the bridge authority can reach me easier, how
can I do this
On January 27, 2019 1:07:12 PM UTC, notatorserver
wrote:
>I am running tor 4.0.1-alpha inside a docker container with a memory
>limit (6GB). Tor runs out of memory and aborts or crashes periodically.
Tor assumes that 64-bit machines have 8 GB of RAM, unless the relevant APIs
return a lower
I am running tor 4.0.1-alpha inside a docker container with a memory limit
(6GB). Tor runs out of memory and aborts or crashes periodically.
Usually I see an error message like this:
Could not mmap file "/var/lib/tor/data/diff-cache/1149": Out of memory
...(repeated some number of times)
Hi,
Tor isn't like bittorrent or other bull download protocols. It's mainly used
for quick web page accesses. So it only uses the data it needs.
Users get their web pages faster if Tor bridges and relays have spare capacity.
So spare capacity is really good for users.
Bridge and relay
Hi Keifer!
On Sunday, January 27, 2019 at 8:23 AM, Keifer Bly
wrote:
Hi, based on the heartbeat log, about 2 clients seem to use the
bridge every six hours. The log says.
"In the last 6 hours I have seen 2 unique clients. Tor's uptime is 12
hours, with 0 circuits open."
How are you
