Slashdot Mirror


User: privtz

privtz's activity in the archive.

Stories
0
Comments
5
First seen
Last seen
Profile
(view on slashdot.org)

Comments · 5

  1. Re:horrible summary, poor research paper on High-Frequency Trading For Your Private Data · · Score: 1

    Fyi, Please comment here on this as well: http://www.arpitaghosh.com/papers/paper.pdf So at the same time you have and don't have this data which makes it a quantum superposition.

  2. Re:horrible summary, poor research paper on High-Frequency Trading For Your Private Data · · Score: 1

    OpenRTB is actually in the references of this paper. As well as other docs. Which RTB are you developing? Because there are important differences between them.

  3. Re:horrible summary, poor research paper on High-Frequency Trading For Your Private Data · · Score: 1

    Hello, I am glad a developer behind RTB is here. RTB faciliates tracking and profiling. It makes it easier. Also, sites are being sent in the bid requests... Price for an ad on site X.com is different than on Y.com. How else do you explain the price difference? Do you seriously want us to believe that you don't know the site you're displaying ads on? Also, where is the list of bidders which receive bids with my data, when I visit a site? Why is the technology so untransparent? Prices for users in USA are higher than in some other places, retargeted ads receive higher prices... Please be more elaborate than just spotting wordings in abstracts and text.

  4. Re:Only $0.0005? Great! on High-Frequency Trading For Your Private Data · · Score: 1

    As the other author suggests, please use solutions on https://team.inria.fr/privatics/yourvalue/ This can show it in real-time and allow comparisons.

  5. Re:leak on High-Frequency Trading For Your Private Data · · Score: 1

    Please see: https://team.inria.fr/privatics/yourvalue/ And the linked description. Long story short: RTBs encrypt the value of prices... But in some cases this does not happen and even those careful enough find themselves be leaking this infos while using OTHER non-encrypting systems. So the leak is due to the fact that some of them encrypt, others do not, but the detection phase requires looking up the encrypted ones.