@joshuef I have started work on drop in replacement for
solid-auth-client and on getting their demo app working in SAFE Browser, I think I’m seeing that the browser already has
solid-auth-client as a dependency:
I’m aiming to make
solid-safe-client a drop in replacement for any Solid app, meaning that it would ‘just work’ on SAFE, but revert to
solid-auth-client if run on the web.
UPDATE: Ah, I see, it is a dependency of
rdflib and so being pulled in there.
This is tricky because
solid-auth-client messes with the window object!
I may be able to handle it, but not nicely:
- if we assume my solid-safe-client init happens after SAFE Browser solid-auth-client (reasonable I think as I’ll be in the web app), and then I can overwrite those mods with my own
- but there’s a danger the app might start using the solid-auth-client before I do that - do you think?
The best solution would I think be to prevent the solid-auth-client in SAFE Browser from adulterating
window (see here). I’m not sure how easy it would be for you to do that.
Security: also, do you think this might be a security issue - a dependency of the browser being able to modify the