Opened 5 years ago

Closed 2 years ago

#11497 closed enhancement (wontfix)

Add fractions of bridge clients by country, transport, and IP version

Reported by: karsten Owned by: phw
Priority: Medium Milestone:
Component: Metrics/Relay Search Version:
Severity: Normal Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

Now that Globe displays graph averages next to the graphs, would it be possible to add fractions of bridge clients by country, transport, and IP version next to the clients graph?

Example details page on Globe:

https://globe.torproject.org/#/bridge/DE6397A047ABE5F78B4C87AF725047831B221AAB

Example clients document part from Onionoo:

"1_week": {
    "first": "2014-04-0312: 00: 00",
    "last": "2014-04-0712: 00: 00",
    "interval": 86400,
    "factor": 0.076015949,
    "count": 5,
    "values": [
        956,
        970,
        951,
        907,
        999
    ],
    "countries": {
        "ca": 0.0211,
        "de": 0.0149,
        "gb": 0.0307,
        "in": 0.0219,
        "ir": 0.4584,
        "ru": 0.0257,
        "sy": 0.0527,
        "tr": 0.0492,
        "us": 0.0926
    },
    "transports": {
        "obfs2": 0.7973,
        "obfs3": 0.1988
    },
    "versions": {
        "v4": 1
    }
}

New text could be:

  • clients by country: Iran (46%), U.S.A. (9%), Syria (5%)
  • clients by transport: obfs2 (80%), obfs3 (20%)
  • clients by IP version: IPv4 (100%)

The "clients by country" part could even show flags in addition to country names like the "Country" field on relay details pages does.

Child Tickets

Change History (5)

comment:1 Changed 5 years ago by isis

Owner: changed from rndm to isis
Status: newassigned

Changing Globe tickets to be owned by isis.

comment:2 Changed 4 years ago by isis

Status: assignednew

comment:3 Changed 3 years ago by karsten

Component: Metrics/GlobeMetrics/Atlas
Owner: changed from isis to phw
Severity: Normal

As we're retiring Globe, I'm moving this ticket to Atlas. Let's consider whether we want to implement this feature in Atlas, because if not, I'll remove that feature from Onionoo. It's only useful to provide this data if somebody uses it. (These fields still have the following warning in the spec: "BETA: This field breaks compatibility with the history objects contained in other documents pretty badly. It might be removed in the future without notice.")

comment:4 Changed 3 years ago by karsten

Oh, I guess this is blocking on #11348 which would have to be implemented first.

comment:5 in reply to:  3 Changed 2 years ago by irl

Resolution: wontfix
Status: newclosed

Replying to karsten:

As we're retiring Globe, I'm moving this ticket to Atlas. Let's consider whether we want to implement this feature in Atlas, because if not, I'll remove that feature from Onionoo. It's only useful to provide this data if somebody uses it. (These fields still have the following warning in the spec: "BETA: This field breaks compatibility with the history objects contained in other documents pretty badly. It might be removed in the future without notice.")

This is a level of detail higher than we have elsewhere in Atlas, as we're currently not doing anything with this, it may be better to drop those fields from Onionoo and then later if they are needed we can work out the best way to add them back.

"This field breaks compatibility with the history objects contained in other documents pretty badly." - Doesn't sound like something we want to keep around without good reason.

Note: See TracTickets for help on using tickets.