[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
[tor-bugs] #33500 [Community/Outreach]: Figure out what we want to learn about the Akamai interface for Tor exit discrimination
#33500: Figure out what we want to learn about the Akamai interface for Tor exit
discrimination
------------------------------------+----------------------------
Reporter: gk | Owner: ggus
Type: defect | Status: new
Priority: Medium | Milestone:
Component: Community/Outreach | Version:
Severity: Normal | Keywords: network-health
Actual Points: | Parent ID: #33499
Points: | Reviewer:
Sponsor: |
------------------------------------+----------------------------
Before we try to find the right folks at Akamai to talk to, we should
gather information and questions regarding their interface for dealing
with Tor relays.
As arma said, we should do a bit of work on our side here, so they can see
easily that we are actually interested in solving this problem.
Gaba pointed out we might be able to look at the free-trial they offer on
their website. Either way, this could be a good starting point anyway.
Questions worth considering (without digging deeper):
1) Is the option to block Tor connections of by default?
2) Where does the blacklist come from? How is it powered?
3) What does the explainer for the Tor blocking option say? (And can we
get Akamai to make it better?)
Ultimately, it might be smart to think about the above questions from the
"how to create a template for akamai users"-angle, so that we could
approach the owners of the above mentioned websites (and others) with some
template figuring out how the help them and learn at least why the have
the Tor option on.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/33500>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs