-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Travis Northrup:
Yes, it can. The program can spend the processor time to run that
extra instruction set. Do we actually need or want that? Would it
be worth spending the cpu time in exchange for just a miniscule
effort to do it ourselves?
Are
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Yes, it can. The program can spend the processor time to run that extra
instruction set. Do we actually need or want that? Would it be worth
spending the cpu time in exchange for just a miniscule effort to do it
ourselves?
On Tuesday, November 26,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Roger Dingledine:
On Sat, Nov 23, 2013 at 02:29:04PM -0800, Gordon Morehouse wrote:
Lunar:
Gordon Morehouse:
Why not just accept KB/sec, KiB/sec, GB/mo, GiB/mo in the
config file?
That would be #9214 [1], implemented by CharlieB, shipped
On Mon, Nov 25, 2013 at 1:29 PM, Gordon Morehouse gor...@morehouse.me wrote:
Why not just accept KB/sec, KiB/sec, GB/mo, GiB/mo in the
[1] https://bugs.torproject.org/9214
We now support gbits (127) and gbytes (130) in the torrc file,
but we do not support gib. Or I think more correctly, we
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
This argument (Mbit/s versus GiB/month) reminds me of the old saw
about the most useless unit of velocity (furlongs/fortnight instead
of m/sec).
Mick
I know exactly what you mean. Personally, I consider any change to be
a convenience
Why not just accept KB/sec, KiB/sec, GB/mo, GiB/mo in the config file?
Because KB/sec would be rejected as not conforming to
either SI or IEC prefix specs. Therefore the above proposed
'AND' would fail ;)
___
tor-relays mailing list
On Sat, 23 Nov 2013 02:50:03 +, grarpamp wrote:
Why not just accept KB/sec, KiB/sec, GB/mo, GiB/mo in the config file?
Because KB/sec would be rejected as not conforming to
either SI or IEC prefix specs.
Why so? The SI prefix spec only specifies that K means 1000,
it does not limit the
Gordon Morehouse:
Why not just accept KB/sec, KiB/sec, GB/mo, GiB/mo in the config file?
That would be #9214 [1], implemented by CharlieB, shipped since tor
0.2.5.1-alpha.
[1] https://bugs.torproject.org/9214
--
Lunar lu...@torproject.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Lunar:
Gordon Morehouse:
Why not just accept KB/sec, KiB/sec, GB/mo, GiB/mo in the config
file?
That would be #9214 [1], implemented by CharlieB, shipped since
tor 0.2.5.1-alpha.
[1] https://bugs.torproject.org/9214
Good, this is the most
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
krishna e bera:
On 13-11-18 07:28 PM, grarpamp wrote:
A proper IEC gibibyte = GiB = 2^30 = 1024^3 = 1073741824 for data
storage, ram (binary bit handling) A proper SI gigabyte = GB =
1E9 = 1000^3 = 10 for data transmission (packet
On 13-11-18 07:28 PM, grarpamp wrote:
A proper IEC gibibyte = GiB = 2^30 = 1024^3 = 1073741824
for data storage, ram (binary bit handling)
A proper SI gigabyte = GB = 1E9 = 1000^3 = 10
for data transmission (packet counting, rocketships)
https://en.wikipedia.org/wiki/Binary_prefix
On Mon, 18 Nov 2013 00:26:32 +, Roger Dingledine wrote:
...
I understand your perspective, but Tor is an overlay application just
like bittorrent. Tor moves bytes around. It happens that it moves the
bytes over the network,
Is there anything nowadays that does move data on networks
in
On Mon, 18 Nov 2013 00:14:15 +, grarpamp wrote:
...
People, can we please mind using the proper units.
How is 'bytes' improper when that is the basic transfer unit of TCP/IP,
and half of the underlying protocols? The only ones who really don't
care about bytes are the layer 1 guys.
I know
On Fri, Nov 15, 2013 at 3:47 PM, Eric van der Vlist v...@dyomedea.com wrote:
Without bandwidth limitation that's true. OTH, I currently consume only
~ 50 Gbits/month and the limit is 500 Gbits. Would a relay limited to
let's say 200 or 300 Gbits/month still be useful for the community?
People,
On Mon, Nov 18, 2013 at 12:14:15AM -0500, grarpamp wrote:
People, can we please mind using the proper units.
I know Tor doesn't make it easy because Tor itself incorrectly
uses Bytes. But Tor is a network application, and real network
apps are measured in 'bits per second'
I understand your
15 matches
Mail list logo
