Web Science and Digital Libraries Research Group

Illustration by  Pat Hochstenbach The DOI URI Scheme: Utility or Branding? Herbert Van de Sompel 2024-11-13 A few days ago, Joe Wass published a blog post entitled " Falsehoods Programmers believe about DOIs ." It’s an excellent resource for developers that work with DOIs and a sobering read for those that attribute magical powers to DOIs. For about 10 years, Joe was a developer at Crossref , the major DOI registration agency for scholarly communication, so chances are high that he knows what he’s writing about. One of the highlighted falsehoods pertains to the challenges involved when bots attempt to resolve DOIs, following their nose from https://doi.org/ the-doi-name to eventually arrive at a landing page describing the scholarly artifact that has the-doi-name as its persistent identifier. Joe had previously described this bot Odyssey in detail in a Crossref blog post " URLs and DOIs: a complicated relationship " and now adds that “ the landscape has only got ...

  @Whitekitty2012  DMing  @BKitty2020  an image -- Twitter works very hard to protect this image from access by third parties.  @Whitekitty2012 DMing @BKitty2020 a video -- unlike the image above, this video has no HTTP protection. We have created a simple example that demonstrates that while Twitter goes to great lengths to protect images shared in direct messages (DMs), the videos shared in DMs enjoy no such protections (see also: 2022-12-22 update ).  Both image and video URLs are named based on hashes and would be difficult if not functionally impossible to guess:   Image URL:  https://ton.twitter.com/i/ton/data/dm/1600870219324465156/1600870190459256832/KM0EBzij.jpg:small Video URL:  https://video.twimg.com/dm_video/1600877027330064385/pl/320x180/Vn4h39llbQ0jfr1D.m3u8?container=fmp4   However, if the URLs are somehow leaked (e.g., guessing, reverse engineering, brute force, exported through  HAR files , intercepted by  p...