4 ms·
This behavior is unconscionable when there is such an obviously trivial technical solution to this problem. Here is my quick and dirty technical solution. (1)
by jayp 15y ago
This behavior is unconscionable when there is such an obviously trivial technical solution to this problem.
Here is my quick and dirty technical solution.
(1) Place a restriction: only allow users who have uploaded a given file to download that file. In essence, keep an "uploaded" flag for each file/user.
(2) Challenge-response to validate local copy of a globally-known file: To continue receiving the benefits of de-dup, don't actually upload an already globally-known file, but perform a challenge-response with the client on the contents of the actual file. This will still leverage most of the benefits of de-dup w.r.t bandwidth savings.
- marshray 15y agoI gues they're already at a point in their business where they feel like it's easier for them to try to silence their fanbase-hackers-modders-addon developers instead of just quietly fixing the issue. At least Twitter had the sense to phase-in client auth for apps before shutting down 3rd party developers.