You can already do that via the iframe embed. It still uses BYOND's login system, but I do have plans to customize this setup so you can simply bypass login and always login as guest.

Lummox JR wrote:

You can already do that via the iframe embed. It still uses BYOND's login system, but I do have plans to customize this setup so you can simply bypass login and always login as guest.

Since this is somewhat on Topic. Are there plans for including access to Facebook's Canvas's?

A.T.H.K wrote:

Ssj4justdale wrote:

Since this is somewhat on Topic. Are there plans for including access to Facebook's Canvas's?

http://www.hyperarts.com/blog/ tutorial-add-an-iframe-application-to-your-facebook-fan-page -fall-2012/

You would do it yourself and include canvas + the iframe to your BYOND game/app.

Facebook won't allow a non SSL canvas page anyway, BYOND doesn't have any SSL capabilities IIRC.

Your best bet is to host your own page with an SSL cert free startssl.com or paid from there as I said above include the game in your page.

Thanks, my issue was the whole SSL thing which is why I was curious if BYOND will provide support for it, but thats all the information I needed. Thanks A.T.H.K!

Lummox JR wrote:

Oh, BYOND internally (as in the server) has no SSL support but you could certainly change the "middle" embed. Instead of http://www.byond.com/play/embed/yourip it'd be https://secure.byond.com/play/embed/yourip for the iframe. That ought to work as far as Facebook having rules about SSL, I believe.

The only tricky part is, I'm not sure if a secure page can call an insecure frame--which would be the game itself.

I tried that but it returns on error on facebook's end for calling something.

I don't recall what it was though.


EDIT: Actually, I forgot to include the secure.*.com part.

Lummox JR wrote:

The only tricky part is, I'm not sure if a secure page can call an insecure frame--which would be the game itself.

Technically yes it could, but both Chrome and Firefox have really locked down insecure content on secure pages nowadays..

The secure.byond.com URL is the only one you have with SSL enabled right? due to the login form / payments etc.

https://secure.byond.com/play/embed/162.251.70.58:592

Chrome -

Mixed Content: The page at 'https://secure.byond.com/play/embed/162.251.70.58:592' was loaded over HTTPS, but requested an insecure XMLHttpRequest endpoint 'http://162.251.70.58:592/query'. This request has been blocked; the content must be served over HTTPS.

Firefox -

Blocked loading mixed active content "http://162.251.70.58:592/query"

..., downloading client"):A();else if(l.match(/^command:/i)){if(l=l.substr(8),n="",...


Obvious due to loading insecure content on the page from a completely different URL/IP.

Honestly I don't think it's going to be possible in either case, my post above RE Facebook SSL won't work either.

https://byondpanel.com/test.html

Mixed content issue on Chrome and Firefox.

The only way this is ever going to work is if you implement SSL connections in DD.

Lummox JR wrote:

Hrm, what I'm reading suggests an "insecure" iframe inside a secure one isn't going to work. So that might speak to a need to implement SSL in BYOND, although then you'd need a certificate if you did an embed that way. I'll try to figure out some options. If anyone else has any ideas in the meantime, please do share them.

I can get past the error, just IN BYOND the game loads but in Facebook it says the game is not available to play.

Edit: From what I noticed, its because Facebook requires the forward slash at the end of the URL.

When going to the embed URL on BYOND's website without the forward slash, it loads.

If you add the forward slash, it fails to load.

Lummox JR wrote:

Might work if you had a reverse proxy with SSL, I'll get back to you on that in a sec.

We'll be sure to get this working before the webclient is finalized, since outside publication is one of the main driving forces behind the HTML5 port. At the moment, there are more pressing stability and speed issue though.

It's hard to believe that there isn't a workaround for this right now, since there's really no reason that the end "app" content need to be encrypting in a general sense. How about the solution recommended here? http://www.xethron.co.za/ building-a-facebook-app-on-a-host-without-https-ssl-support/

I also see a number of pages that host "static iframes" (eg https://woobox.com/customtab ) that may offer the same sort of redirect (although I suspect that this is effectively what was tried above and may throw errors).