Chronotope’s avatarChronotope’s Twitter Archive—№ 136,601

      1. …in reply to @reconbot
        reconbot I think there's a few underlying problems that make it complicated, the first is that there were metrics that said it wasn't in heavy use but the metrics seem like they were prob wrong: slightlylate/1423051145140871175
    1. …in reply to @Chronotope
      reconbot I think there was a failure of proactive messaging that would have greatly helped, but is a problem that almost every part of the web platform has. pwnallthethings/1423068975940919300
  1. …in reply to @Chronotope
    reconbot The initial plan is (as I understand) just to remove cross-origin alerts, and I think that's a legit initial step that creates good responses and addresses security concerns AND creates an opportunity for more responses and feedback on the broader project that can steer it.
    1. …in reply to @Chronotope
      reconbot And finally, I do think, just *security* and not also performance is a reasonable reason to depreciate something. I don't know how commonly alert is used (and it's clear that no one does) but I think it can very reasonably be replaced by devs...
      1. …in reply to @Chronotope
        reconbot I think web specifications are living documents & they will change. A web application requires development & updates like anything else. I think there was a trend at one point to really try and freeze particular features, but safety is the best argument to unfreeze them imo.


Search tweets' text