Chronotope’s avatarChronotope’s Twitter Archive—№ 141,686

      1. …in reply to @swodinsky
        swodinsky I mean... this is in part the argument around APIs from en.wikipedia.org/wiki/Google_LLC_v._Oracle_America,_Inc.#Decision To what extent does the form and format of developer interactions with code become an essential part of that code? ...
        OpenGraph image for en.wikipedia.org/wiki/Google_LLC_v._Oracle_America,_Inc.#Decision
    1. …in reply to @Chronotope
      swodinsky Beyond that there may be risks to the *platform* in the code that you might not want to expose. For example testing processes intended for devs might open up problems for infrastructure or be used for a DDoS attack on infrastructure since dev endpoints are rarely rate limited...
  1. …in reply to @Chronotope
    swodinsky When dev docs are about specific internal functionality they might be revealing in terms of what the source has access to about the system. Not everyone has access to every doc & for high level engineers, revealing specific function names might be enough to expose them.
    1. …in reply to @Chronotope
      swodinsky Final thing is, maybe this impacts your journalistic judgement or not (& I'm not sure it should), but docs could contain information essential to a company's ability to compete. In which case a journalist might want to extract what's newsworthy w/o actively harming the co.


Search tweets' text