Skip to content
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

[Demo] Use custom html (web export) #6

Open
freehuntx opened this issue Jan 2, 2024 · 5 comments
Open

[Demo] Use custom html (web export) #6

freehuntx opened this issue Jan 2, 2024 · 5 comments
Labels
enhancement New feature or request

Comments

@freehuntx
Copy link
Owner

We should use a custom html in the demo web export to explain the "COI" error and what to do about it. (Allow service worker)

@freehuntx freehuntx added the enhancement New feature or request label Jan 2, 2024
@ValorZard
Copy link

Could you go into more detail as to what this error is? I'm interested in using godot-matcha, but I want to know what I'm getting myself into

@freehuntx
Copy link
Owner Author

Its no error that comes from godot-matcha. Its a typical problem with web exports of godot. See: https://docs.godotengine.org/en/stable/tutorials/export/exporting_for_web.html#serving-the-files

This issue just exists because i host a demo of godot-matcha in github pages. This requires me to use the "coi-serviceworker" workaround mentioned in the link above.

So if people use my demo in private window, they will get an error page.
The idea: Add text to that error page which mentions something like "please open without private mode"

@freehuntx
Copy link
Owner Author

PS: Im reworking the library to use mqtt. The API will be changed alot but be more stable (hopefully).
So if you plan to use godot-matcha you should expect alot of changes. Be sure you are ready for that ride ^^
Otherwise you can see this repo as a POC in the current state which you can learn from or change the library how you need.

@coelhucas
Copy link

Hey, I still don't know much about mqtt but got curious about the rationale of why using it over WebRTC and whether this would still support direct connections — I suppose so since the implementation will likely still rely on WebTorrent for signaling?

Sorry for bothering, just interested in reading more about it

@freehuntx
Copy link
Owner Author

its webtorrent vs mqtt.
webrtc stays.
webtorrent has some limitations regarding peer count and flexibility in regards of signaling.
mqtt on the other side is a pubsub system that allows for far more Connections.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants