Nicholas Riley

@nriley

MD/PhD, UVM resident. Web/Mac developer.

Burlington, VT
Joined July 2007

@nriley is blocked

Are you sure you want to view these Tweets? Viewing Tweets won't unblock @nriley.

  1. Bedside table update: Hue bridge, HiRise 2 instead of flaky inductive charger, and a remote.

  2. . brilliantly lays out case for clinician data scientists: data=unsolvable puzzle w/o them

    , , and 2 others
  3. Tonight’s annoying discovery: JavaScript weak collection data types are not iterable. So not-helpful.

  4. Huh, first time I saw this was in a VM. Dropbox still supports back to 10.6.8.

  5. Still liking Bedtime but it definitely doesn’t seem to understand my sleep schedule this month.

  6. Flame 2.0 is released to the App Store, for all your service browsing needs! It now supports the iPhone 5! <cough>

  7. Probably will migrate to an SIP client with CallKit support if it doesn't get added soon, anyway.

  8. Was about to replace my charger, but this makes a lot more sense as it also affected my father’s iPhone.

  9. For people wants to try HomeKit IP Camera, here is a general purpose ffmpeg powered plugin for homebridge ☺️

  10. Even the secret about box on the Canon Cat is triggered (in part) by a quasimode. Amused.

  11. Wondering how much time I should spend on trying to suppress CoreMedia logging on 10.10 which is silent on 10.11.

  12. Guess it was time to reinstall Xcode anyway.

  13. Ooh, this is nice. (iOS 10 Mail.)

  14. Safari extension development.

  15. Excited about the work that's going into rebuilding Gmane.

  16. Hermes 1.3.0 works on Sierra, refreshes UI and adds more song display options: (Changes: )

  17. Nicholas Riley followed and
  18. Liking Bedtime in iOS 10 (“what time did I go to sleep again?”) but it could be more aggressive about coalescing.

  19. I don’t even *have* a TV so it’s just an AirPlay audio receiver and HomeKit bridge.

  20. FWIW remote access to my HomeKit devices continues to work in iOS 10 with my 3G Apple TV.

Loading seems to be taking a while.

Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.

    You may also like

    ·