new permissions in chrome cause us huge, huge headaches from a support standpoint (it disables the extension) and so they are pretty much a non-starter...  options:  1) if that URI endpoint supports CORS, you don't need the permission anyway.  2) use optional permissions like we do for twitter.  it's more work, but unfortunately necessary. 