Opened 9 years ago

Closed 8 years ago

#2064 closed task (implemented)

need a spec for the exit-list format

Reported by: arma Owned by: karsten
Priority: Medium Milestone:
Component: Metrics/CollecTor Version:
Severity: Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

The visitor blog post suggests that we want a python version of visitor. But the exit-list format isn't documented. It looks mostly straightforward, but things like "what time zone is that" and "what do you mean by laststatus" are unclear to me.

We also want people to be able to import these files into their own databases, e.g. if we give the files to gmail so they can annotate your logins with "(Tor)".

Giving them a walk-through of what they're seeing, and how they should interpret it, will increase the odds that they get around to using the information.

Once we have this spec, where should we put it? On the visitor howto? On the data.html page?

Child Tickets

Attachments (2)

exitlist-spec.txt (1.5 KB) - added by karsten 8 years ago.
Exit list specification draft
exitlist-spec-2.txt (1.8 KB) - added by karsten 8 years ago.

Download all attachments as: .zip

Change History (9)

comment:1 in reply to:  description Changed 9 years ago by karsten

Replying to arma:

The visitor blog post suggests that we want a python version of visitor. But the exit-list format isn't documented. It looks mostly straightforward, but things like "what time zone is that" and "what do you mean by laststatus" are unclear to me.

We also want people to be able to import these files into their own databases, e.g. if we give the files to gmail so they can annotate your logins with "(Tor)".

Giving them a walk-through of what they're seeing, and how they should interpret it, will increase the odds that they get around to using the information.

I tried to read the source and came up with this specification:

http://freehaven.net/~karsten/volatile/exitlist-spec.txt

Once we have this spec, where should we put it? On the visitor howto? On the data.html page?

I think the specification shouldn't be tied to VisiTor, but live in the same place as the TorDNSEL sources (or the design doc). How about we make it available at

https://www.torproject.org/tordnsel/

and add a link to the VisiTor section on the Tools page at

https://metrics.torproject.org/tools.html#visitor ?

Changed 8 years ago by karsten

Attachment: exitlist-spec.txt added

Exit list specification draft

comment:2 Changed 8 years ago by karsten

Exit list specification draft is attached to this task, because I'm deleting it from freehaven.net.

comment:3 Changed 8 years ago by nickm

It's a good start, but you should give a high-level view of how the entries relate to each other. Reading that spec, I would guess that the format is something like (ExitAddress | Published | LastStatus | ExitAddress*)*, but I can't say for sure.

Also, maybe you should stick the literals in quotes: "ExitAddress" rather than ExitAddress, assuming that the string "ExitAddress" appears verbatim in the file. You might want to note spaces too?

Also, is ExitAddress really used for two different kinds of entry?

comment:4 in reply to:  3 Changed 8 years ago by karsten

Replying to nickm:

It's a good start, but you should give a high-level view of how the entries relate to each other. Reading that spec, I would guess that the format is something like (ExitAddress | Published | LastStatus | ExitAddress*)*, but I can't say for sure.

Right. The fact that the first line starts with ExitNode (not ExitAddress) probably complicated things, too. I added a sentence and corrected the typo.

Also, maybe you should stick the literals in quotes: "ExitAddress" rather than ExitAddress, assuming that the string "ExitAddress" appears verbatim in the file. You might want to note spaces too?

Done.

Also, is ExitAddress really used for two different kinds of entry?

No. :)

See exitlist-spec-2.txt in the attachment. Thanks for your comments!

Changed 8 years ago by karsten

Attachment: exitlist-spec-2.txt added

comment:5 Changed 8 years ago by nickm

Looks good to me now. Feel free to check it in wherever it goes, or tell me if there's somewhere I should check it in.

comment:6 in reply to:  5 Changed 8 years ago by karsten

Great! My idea was to make the spec available at https://www.torproject.org/tordnsel/, but I don't really know who's responsible for TorDNSEL these days. Jake? Sebastian?

comment:7 Changed 8 years ago by karsten

Resolution: implemented
Status: newclosed

Thanks to Sebastian, the spec is now available here. Closing this task.

Note: See TracTickets for help on using tickets.