1 day) and stem's website update.
Please, let us know whether that works for you,
Cheers,
juga.
[1] https://github.com/torproject/stem/releases/tag/1.8.1
[2] https://github.com/torproject/stem/commits/maint
___
tor-dev mailing list
tor-dev@lists
teor:
> Hi juga,
>
> I read your meeting notes from this week's network team meeting:
>
> juga(offline):
>Week of 05/20 (planned)
> - Add Tor version to the bandwidth file (#30196)
>Week of 05/20 (actual)
>Week of 06/03 (plan)
> - Co
Matt Traudt:
> Teor, Juga
>
> There's a lot of things fighting for my attention right now, so you
> might have noticed I've slowed way down on attending to sbws
> tickets/PRs/etc. I think time will free up in the next few days.
>
> I think sbws is in a very go
Hi,
as commented by nickm [0], the specification has been merged into
torspec git repository.
If you find any issues with it, as usual, we can open a ticket and patch
the specification.
Thanks,
juga.
[0] https://trac.torproject.org/projects/tor/ticket/25869#comment:10
ode in
> our parser (and also for tor to reuse existing code too) rather than
> being something entirely new.
That was the idea :)
Thanks!
juga.
___
tor-dev mailing list
tor-dev@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev
about their opinion about this.
Thanks,
juga
[1] https://lists.torproject.org/pipermail/tor-dev/2018-May/013141.html
[2] https://lists.torproject.org/pipermail/tor-dev/2018-May/013154.html
---
Tor B
teor:
> Hi Nick,
>
>> Suggestion: Add a field to hold the Ed25519 Identity of the relay being
>> measured. Say that implementations SHOULD include both RSA fingerprint
>> and Ed25519 identity, and that implementations SHOULD accept lines that
>> contain at least one of them.
>
> Suggestion: the
juga:
>>> Each relay_line MUST include the following key_value in arbitrary order:
>>
>> Do existing implementations accept arbitrary order here?
>
> Good question, it seems like bw must be behind node_id, but they can
> have things in front and behind. I probably s
uities pop up, but I'll let others finish having their
> comments integrated first.
It's fine to continue to make comments on the thread where others
commented, no need to wait until those comments are integrated. But
either way works.
Thanks for your comments!,
juga.
___
tor-dev mailing list
tor-dev@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev
Hi,
Thanks Nick for the comments, i'm replaying only to the parts where i
give an answer or i've more questions. I'd accept the rest of your
suggestions unless there will be further comments.
Nick Mathewson:
> Hi, Juga!
>
> This is a review of t
Karsten Loesing:
> Hi Juga,
>
> On 2018-05-01 14:36, Nick Mathewson wrote:
>> This is a review of the document from
>> https://raw.githubusercontent.com/juga0/torspec/c7f06023dd1d5d47adad128de541f8eba2a13bfb/bandwidth-file-spec.txt
>> , which I *think* is the same as
Hi,
after teor's revision, second version pasted below.
Changes can be seen: in
https://github.com/juga0/torspec/commits/bandwidth-file-spec
Best,
juga
=
Tor Bandwidth Measurements Document F
gs on bwscanner code [1].
I'm MS in computer engineering, senior developer and have worked as
sysadmin and researcher.
Best regards,
juga.
GnuPG key fp: 2DA81D01455C3A0032198850F305447AF806D46B
[0] https://lists.torproject.org/pipermail/tor-dev/2018-April/013071.html
[1] https://github.com/The
Hi,
as commented with teor and pastly, i send in-line a draft specification
for the document format that the bandwidth scanner implementations
should produce.
I've left my own questions/notes in square brackets.
Thanks,
juga.
===
Tor Band
14 matches
Mail list logo
