On 2013-03-29 12:28, Nick Jennings wrote:
> Hi Michiel, interesting article.
>
> A question, isn't using the 5apps CORS Proxy, using a hosted service?
>
> It prompts the discussion: what are the idealogical & technical
> differences between sockethub, the 5apps cors proxy, and a
> traditional
> hosted service?
>
> I'm interested to hear your thoughts, it seems kind of glazed over
> (not addressed directly) in the article.
you're right, i should have discussed that in there. i'll add a
paragraph.
basically, i hadn't really thought about it much. i guess the right
thing to do would be allow the user to specify a custom proxy to use,
and leave the 5apps one only as a default.
this could be either at runtime or at install time (we could add a
readme file to the app that explains how to choose your cors proxy by
editing the code).
technically, i would say the cors proxy functions as a simplified
alternative for a subset of sockethub's functionality. i'm in two minds
about whether for instance a freedombox should contain remoteStorage +
sockethub + a cors proxy, or just remoteStorage + sockethub. maybe if an
app already uses sockethub, then it should also use sockethub for
cors-proxying, but if it doesn't, then it makes sense maybe to use only
a cors-proxy that just requires prefixing the URL with an extra string.
but that means that a user who want to control their data would have to
run 3 services instead of 2, so it's not ideal.
in practice, you are already trusting 5apps to not insert eavesdropping
code into the app, so it makes sense that they also host the proxy. but
then as we open-source the app, we should do it in such a way that a
user can host it themselves and use sockethub for the cors-proxy part.
does that make sense?