4 ms·
According to the article, you need the resource ID of the link to query it in the API. The resource ID seems difficult to get; you basically need to be viewing
by morley 10y ago
According to the article, you need the resource ID of the link to query it in the API. The resource ID seems difficult to get; you basically need to be viewing the conversation (and thus the link) to get the ID. While I agree it's _possible_ to stumble onto sensitive information by downloading resource IDs, that seems too unwieldy to present a serious risk to any particular user. (It's the same amount of risk as, for example, trying to guess the URL of someone's hypothetical photo on the CDN.) Unless there's a way to get a list of resource IDs given someone's username, I'm inclined to think that this is a pretty minor security risk in the larger scheme of things, though it is scary to type a resource ID into their API tester and see a sensitive link come out.
- kevinchen 10y agoSo near the end of the article, author actually shows that it's easy to write a scraper that finds other URLs by enumerating their IDs.