<Additional information about your API call. Try to use verbs that match both request type (fetching vs modifying) and plurality (one vs multiple).>
-
URL
<The URL Structure (path only, no root url)>
-
Method:
| // Unfollow everyone on twitter.com, by Jamie Mason (https://twitter.com/fold_left) | |
| // https://gist.github.com/JamieMason/7580315 | |
| // | |
| // 1. Go to https://twitter.com/YOUR_USER_NAME/following | |
| // 2. Open the Developer Console. (COMMAND+ALT+I on Mac) | |
| // 3. Paste this into the Developer Console and run it | |
| (() => { | |
| const followButtonQuery = '[data-testid$="-unfollow"]'; | |
| const confirmButtonQuery = '[data-testid="confirmationSheetConfirm"]'; | |
| const sleep = ({ seconds }) => |
| # The Witness Algorithm: Privacy Protection in a Fully Transparent System | |
| By **Vlad Gluhovsky** and **Gavin Wood** | |
| # Introduction | |
| Being based upon a quasi-Turing-complete (quasi because it's actually bounded) virtual machine, Ethereum is an extremely versatile system. However one of its greatest strengths---universal auditability---seems to lead to a fatal flaw, namely an inescapable lack of privacy. Here we demonstrate an algorithm in order to prove that this is not the case. | |
| The algorithm could be used to make an Ethereum contract which, given two sets of addresses sources, `src`, and destinations, `dest`, will guarantee exactly one of two possible eventualities: | |
| - For each address in `src`, the controller of that address controls a corresponding address in `dest` (though the two cannot be related *a priori*). |
Edward Snowden answered questioned after a showing of CITIZENFOUR at the IETF93 meeting; this is a transcript of the video recording.
For more information, see the Internet Society article.
| application: you-app-name-here | |
| version: 1 | |
| runtime: python | |
| api_version: 1 | |
| default_expiration: "30d" | |
| handlers: | |
| - url: /(.*\.(appcache|manifest)) | |
| mime_type: text/cache-manifest |