-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Karsten Loesing:
That timestamp is updated as last step of the hourly update
process. The details documents that you're fetching may
have been updated before. That would also explain some
differences.
Wouldn't it make sense to mention/use
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello Tim,
On 21/04/15 23:01, Tim Semeijn wrote:
Improved documentation and process of setting up Onionoo would be
welcomed by more people, including myself. Busy setting up Compass
and with Atlas and Globe mirrors active the cherry on the pie
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 25/04/15 19:58, nusenu wrote:
Karsten Loesing:
That timestamp is updated as last step of the hourly update
process. The details documents that you're fetching may
have been updated before. That would also explain some
differences.
Hi,
Actually I've been meaning to ask a question related to this. I've
been wondering if, during the development of Onionoo, you considered
any other frameworks? I'm not familiar with the history of Onionoo so
I don't know if you made the choice based on some constraint. I read
the design doc
To be clear, Tim is talking about HTTPS Everywhere in general, not the
browser extension!
On 4/24/15 8:05 PM, Mike Perry wrote:
Maciej Soltysiak:
http://www.w3.org/DesignIssues/Security-NotTheS.html
The problem with his argument is that the web (and any protocol, really)
needs a way to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 25/04/15 12:44, nusenu wrote:
Karsten Loesing:
These might either be bugs, or one instance was missing a
descriptor or consensus that the other instance was processing.
I assume the instances do not process the same descriptors in
every
On Fri, Apr 24, 2015 at 08:05:43PM -0700, Mike Perry wrote:
** Sure, there could be a pile of new attribute flags that could be set
on every HTML resource tag that says the resource must use a secure
http: channel if the parent document happened to load over a secure
channel, but the net
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Karsten Loesing:
These might either be bugs, or one instance was missing a
descriptor or consensus that the other instance was processing.
I assume the instances do not process the same descriptors in every
case. That would explain most of the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 25/04/15 13:44, nusenu wrote:
If their 'relays_published' timestamp match, they processed
the
same consensus, correct?
That timestamp is updated as last step of the hourly update
process. The details documents that you're fetching may have
This may be a naïve question, but how do I parse the clients who have
used my bridge relay on my Debian box à la Vidalia? Just set the syslog
to info and run a search or script? I routinely tell my friends which
nation-states have become especially active (an interesting metric of
geopolitical
Hey,
On 04/25/15 15:29, Kenneth Freeman wrote:
I routinely tell my friends which
nation-states have become especially active (an interesting metric of
geopolitical turbulence in and of itself)
this is not directly an answer to your question but if you are very
interrested in this topic you
11 matches
Mail list logo
