FaceTime on the web requires Chrome or Edge, no mention of Firefox
31–40 of 199 posts
Re: FaceTime on the web requires Chrome or Edge, no mention of Firefox
#32Earlier quoted context omitted.
Firefox can require more bandwidth for WebRTC calls I think, see https://bugzilla.mozilla.org/show_bug.cgi?id=1600698 I also have some memory of asking all participants in Jitsi meetings to not use firefox, because the call would start to lag for all participants if bandwidth was an issue for the firefox users in the call. Don't know if that is still the case or not though.
This should be fixed.
Re: FaceTime on the web requires Chrome or Edge, no mention of Firefox
#33Keep giving money to a company that uses slave labour. What is the worst that can happen?
They do but who doesn't? Apple isn't different than any other tech companies. That said, yes, the global south produces for west in slave like conditions and it's sad.
And whats worse is that these companies have the audacity to get behind social movements. Its predatory and just another scheme to improve their bottom line and lull their customers into believing that they are making an ethical choice by purchasing their products.
The raw reality is that everyone is getting exploited so we (the west) can enjoy using an iDevice while sitting on the toilet.
Its sickening.
Re: FaceTime on the web requires Chrome or Edge, no mention of Firefox
#34Re: FaceTime on the web requires Chrome or Edge, no mention of Firefox
#35What are (if any) the technical blockers for Firefox to be considered on the same level of support?
You cannot achieve true E2E encryption on Firefox as it doesn't support insertable streams, so I guess this is where the limitation is. EDIT: bug on bugzilla https://bugzilla.mozilla.org/show_bug.cgi?id=1631263
Re: FaceTime on the web requires Chrome or Edge, no mention of Firefox
#36Earlier quoted context omitted.
At a guess, codecs seem the most likely explanation. Firefox has a h.264 decoder, but not an encoder I think.
Why can't firefox invoke the system dll or libraries for H.264 encode/decode? Like many video players do. Why must every browser ship its own codec or even Unicode collection is beyond me.
Re: FaceTime on the web requires Chrome or Edge, no mention of Firefox
#37Earlier quoted context omitted.
At a guess, codecs seem the most likely explanation. Firefox has a h.264 decoder, but not an encoder I think.
Why can't firefox invoke the system dll or libraries for H.264 encode/decode? Like many video players do. Why must every browser ship its own codec or even Unicode collection is beyond me.
Re: FaceTime on the web requires Chrome or Edge, no mention of Firefox
#38Earlier quoted context omitted.
Fairphone doesn't. Fairphone goes as far as giving percentage of phone sales to factory workers.
A percentage of phone sales always goes to factory workers in the form of wages...
Re: FaceTime on the web requires Chrome or Edge, no mention of Firefox
#39Earlier quoted context omitted.
Why can't firefox invoke the system dll or libraries for H.264 encode/decode? Like many video players do. Why must every browser ship its own codec or even Unicode collection is beyond me.
Because of a long tradition of the system libraries being fucked. All this stuff started in the days of Windows XP, which shipped with such a meagre selection of codecs you couldn't even play DVDs. And the codecs you could download? Either they cost money (i.e. most users wouldn't have them), or they were dodging license costs by some questionable means, or they had bigger aspirations than just providing a mere codec…
Re: FaceTime on the web requires Chrome or Edge, no mention of Firefox
#40Earlier quoted context omitted.
For H.264, it's a question of patents IIRC. Cisco granted a free of charge decoder, but not necessarily an encoder.
Hi ow can I pay to get the encoder into my FF? Like I paid to get some en/decoding in my raspberry pi’s.
Why would we encourage Firefox or others to do the same and develop a business model based on patents? Especially so when these patents are owned by huge conglomerates of corporate psychopaths (hello MPEG-LA) and the software editor we're talking about (Mozilla) had to lay-off a lot of staff during the confinement by lack of funds.
To be fair, Firefox is more than capable to encode/decode into free codecs and there's no reason why a third party plugin couldn't support H264 encoding as well. It falls on Apple to support proper standards for their communications platform and not on Firefox to support every piece of proprietary tech they can come up with.
But well, we all know what Apple thinks of standards. With their AirPlay, iMessage, iCloud and other Apple-specific solutions. If only we had free-software, standards-compliant solutions to all these computing problems. /s