-
-
Notifications
You must be signed in to change notification settings - Fork 52
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
In-browser work? #182
Comments
There's potential. Sciencefair relies on Dat which I don't think can run directly in the browser currently however there are developments with proxies/gateways to do so. |
Dat works in the browser with webrtc and Gateways, see dat-js |
@blokhin indeed, part of the strategy for sciencefair has always been to ensure that the experience users have in the app can (eventually) easily be integrated into any platform on any device that supports the web. Another part of the strategy is to ensure that the technologies we depend on are as stable and straightforward as possible. These are not just goals but are actively featured into every major decision about the project. For example:
Currently sciencefair is not in active development, but when development does re-start (and it will), we will need to work on separating out non-browser APIs from the client-side code before any significant part of it can really be re-used in the browser. There are a bunch of things that depend on Electron's renderer-process node integration, but shouldn't, that we need to refactor. |
Hi, I see it's based on Electron, which means at least theoretically it can have an in-browser GUI. Is that true?
The text was updated successfully, but these errors were encountered: