In the json version the as_no, as_info, and as_name fields are redundant amongst themselves.
Dropping as_info and joining as_no and as_name where needed for display could save about 132kB.
In the json version the as_no, as_info, and as_name fields are redundant amongst themselves.
Dropping as_info and joining as_no and as_name where needed for display could save about 132kB.
Interesting! The JSON version is what was introduced by the angularize stuff, I guess? How would I look into the JSON data when making a request?
I don't know JS/angularize, I presume the data fields are used by the other JS code the browser downloads in order to display them. If you mean how to see https transactions you can use 'tamper data' plugin with Firefox. Fetch urls offline with curl or equivalent. result.json with arguments provides the raw tor data for scrapers.
Trac: Sponsor: N/AtoN/A Reviewer: N/AtoN/A Severity: N/Ato Normal Summary: compass: trim out the fat to Make output smaller by removing comments and unnecessary data
I believe that gsathya has stopped working on any of these tickets quite a while ago. Reassigning to the friendly metrics-team user. (gsathya, thanks for having worked on all these tickets back when you did!)
Trac: Owner: gsathya to metrics-team Status: new to assigned
The metrics team has put a goal of shutting down Compass in its roadmap and merging functionality with Relay Search (previously known as Atlas). This ticket is specific to Compass and as development on Compass has ceased, I am marking this ticket as wontfix.
See #23517 (moved) for information on the planned work to integrate Compass functionality into Relay Search.
Trac: Resolution: N/Ato wontfix Status: assigned to closed