Enable Firefox Hello with boot argument

[dittaeva]

Firefox Hello seems to be a very promising technology for video telephony/conferencing, but to use it in Firefox the button for it needs to be enabled, and there might be extra settings that need enabling on debian.

I think video conferencing terminal could be a use case for Webconverger, and thus an API argument for it could be warranted with the next release using Firefox 35.

[kaihendry]

Yes, the hello button is hidden in my tests. IIUC there is no keyboard shortcut.

I can however join a Hello conversation IIUC by following a URL? e.g. https://hello.firefox.com/Ucov22K4-K0

So it doesn't have to be explicitly enabled in the UI, does it now?

Any thoughts @mkaply ?

Btw I've never got it to work yet. Always says "already two people in the conversation" room when I try to join. :(

[dittaeva]

What I'm asking for is for the button to be enabled so that Webconverger could be used to make a "Firefox Hello terminal" also for calling people up with Firefox Hello.

Did you read the tweet I linked to? Apparently "you need to enable it explicitly by setting "loop.throttled" to "false" in about:config".

The service/feature does seem to be unstable though, and is in beta, so I suppose supporting/implementing this isn't at all urgent.

[kaihendry]

OK, IIUC you want the button to initiate calls. Hmmm, I don't see why this can't be done via a Web app instead of a dedicated chrome UI addition.

Not sure about this loop throttled stuff, though you could experiment yourself via the prefs= API.

e.g. prefs=http://prefs.webconverger.com/2015/disable-pdfjs.js

No hurry. :-)

[dittaeva]

Looks like the throttle setting is only used for a gradual introduction of Firefox Hello, and will be removed entirely in FF36.

WebRTC can be used via a web app, but can you easily interact with Firefox Hello using a web app? I'll try setting the loop.throttle setting (to false), but from what I understand, any new button will have to be "a dedicated chrome UI addition" so it will most likely have no effect.

[kaihendry]

Why not just use http://getaroom.io/?

I don't see the point of having dedicated Chrome UI to favour one of many WebRTC services.

[dittaeva]

Indeed, thanks for the link.