While I'm obviously pro enterprise policy, I think we need to be convinced that this is Mostly Harmless without policy, perhaps with CORS-RFC1918 as a pre-req. But if we're going to talk CORS, why not just introduce a CORS-Anonymous spec? What's the use-case?
image display in webmailers: the whole reason you use a proxy is to hide the client IP
-
-
I think you misunderstand the use case, because neither example makes sense for this proposal. Try this: A podcast listening app. It reads RSS and caches audio files for use offline. Today all that routes through the app's server, even though it's handling public resources.
- 18 more replies
New conversation -
-
-
Can already do image display. Document (json/xml) fetches are what I think they're proposing. Currently the solutions are: - Proxies - CORS - script inclusion - iframes An anonymous fetch feels equal/better than almost all of those.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.