16 ms·
FaceTime on the web requires Chrome or Edge, no mention of Firefox
- latexr 5y agoIt’s the third footnote. Direct link may obscure it slightly due to top bar.
- pacifika 5y agoWhat are (if any) the technical blockers for Firefox to be considered on the same level of support?
- ilikepi 5y agoIf there are any (as opposed to "just" the added customer support burden), I wonder if they're the same issues that prevent Slack from allowing calls in Firefox...
- nexuist 5y agoAs a corollary, I wonder if Slack will now implement calling functionality once Mozilla adds the necessary APIs for Apple to do its job here, which is probably very likely since I don't think Apple chose to ignore a non-Google browser on purpose.
- dathinab 5y agoAll necessary parts are there, which is why e.g. jitsi meet or Google meet work without problem. It's more like they don't care than anything else.
- DeliriumTrigger 5y agoSlack uses Amazon Chime as backend Chime is using h264 firefox still can not encode h264 videos in real time.
- southerntofu 5y agoYes, so it's precisely another case of "we tested on chrome and it works", which falls under "don't care" software development best practices.
- NavinF 5y agoNo, it's very practical. A lot of devices are just too weak to encode anything other than H.264 so that's the one codec you must support. Other codecs are better, but you have to do more testing and enable those codecs only on calls where all members are using a device that supports it.
- southerntofu 5y ago> A lot of devices are just too weak to encode anything other than H.264 Not that your point is wrong, but a lot of devices are too weak to encode/decode H264 as well. It's very recent for me to have access to second-hand hardware with H264 support and still i'm in western Europe where it's easier to come by. Though as the other commenter pointed out, if you can afford to use hardware en/decoders then it's always the better option.
- NavinF 5y agoAre you sure you're not thinking of H265? I'm kinda curious which devices don't support H264
- zinekeller 5y agoUnfortunately, hardware VP9 decoding isn't really well-supported except in high-end phones (in context of multiple decoding, single decoding works fine) due to bugs in Mediatek's implementation. There's software decoding, but that's still taxing to a phone, and transcoding to H.264 server-side but that doesn't bode well to end-to-end encryption.
- ChrisMLane 5y agoSlack calls didn't used to work on Firefox even if you bypassed their user-agent block. In recent months, after bypassing the user-agent check, calls will at least work albeit not very well. (bit laggy, long connection time)
- mattl 5y agoApple Business Manager recently stopped working in Firefox and that is a basic portal.
- ZeroGravitas 5y agoAt a guess, codecs seem the most likely explanation. Firefox has a h.264 decoder, but not an encoder I think.
- deadmutex 5y agoMaybe... Google Duo works in Firefox (and even Opera) though. Important: Google Duo is available on Google Chrome, Microsoft Edge, Firefox, Opera, and Safari. Source: https://support.google.com/duo/answer/6386089 https://support.google.com/duo/answer/6386089
- nielsbot 5y agoDoes Duo send H.264?
- fwn 5y agoAs far as I've read about Duo it seems to be AV1: https://www.xda-developers.com/google-duo-lyra-codec-better-call-quality/ https://www.xda-developers.com/google-duo-lyra-codec-better-... ...though I'm not sure whether they use it consistently.
- bhaavan 5y agoHow does this happen? AV1 encoding codec was still work in progress, and most chips don't support any hardware acceleration for this. Can we get reasonable frame rates on core CPU for av1 encoding already?
- slac 5y agoDuo uses AV1 for very low bandwidth calls. And then a mix of H.264 / VP8 / VP9 etc.. depending on many parameters. Disclaimer: worked on the product. https://blog.google/products/duo/4-new-google-duo-features-help-you-stay-connected/ https://blog.google/products/duo/4-new-google-duo-features-h...
- 5y ago
- bwindels 5y agoFirefox can require more bandwidth for WebRTC calls I think, see https://bugzilla.mozilla.org/show_bug.cgi?id=1600698 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.
- solarkraft 5y agoThis should be fixed.
- alimbada 5y agoSorry, your comment is ambiguous; "should be" as in "needs to be fixed" or as in "has been fixed"?
- sharken 5y agoThe issue is open so it can only mean that it needs to be fixed.
- sfink 5y agoIf you read to the end, it looks like the expected underlying reason is now fixed, but it hasn't been confirmed yet whether it resolved the problem. If someone knows how to reproduce, they could try it out and comment there.
- nklmilojevic 5y agoYou 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 https://bugzilla.mozilla.org/show_bug.cgi?id=1631263
- SahAssar 5y agoE2E is on by default as in all P2P webrtc calls. What you can't do is use a SFU and still get E2E. Perhaps I'm just missing something but why would you want a SFU AND E2E? Why not just use TURN in those cases (if the problem the SFU is meant to fix is routing)?
- ryanar 5y agoAn SFU lets your video/audio streams scale. If there were only ever two people, sure, you could use a TURN server if P2P failed, but if you invite 4 people on the call, an SFU will allow each person to upload their stream to the SFU which will then distribute it at various bitrates to the other people on the call.
- px43 5y agoJust to add some context for muggles such as myself who were unaware of what an SFU is, it stands for "Selective Forwarding Unit". https://webrtcglossary.com/sfu/ https://webrtcglossary.com/sfu/ https://stackoverflow.com/questions/60013467/one-to-many-live-video-strearming-webrtc-or-websocket https://stackoverflow.com/questions/60013467/one-to-many-liv...
- SahAssar 5y agoExcept that if the call is E2E then the SFU can't do things like reencode to a different bitrate. Also wouldn't the decryption keys need to be distributed to all the participants of the call via the centralized service anyway since the stream is already in progress? Or am I just being thick in not understanding how a SFU and E2E would bring all of the benefits of both?
- zamalek 5y agoNot a blocker, but certainly a consideration. Chrome and Edge both share a common ancestor: WebKit (Safari).
- dvfjsdhgfv 5y agoIt literally says "Users with non-Apple devices can join using the latest version of Chrome or Edge": does it mean users of Apple devices could join using Firefox?
- ash110 5y agoUnlikely, that'd be a very weird restriction. I think they meant Apple users would just use the FaceTime app
- traskjd 5y agoOn iOS devices the other "browsers" still host the same Safari web engine I believe. So in theory, it might work from Firefox on an iOS device. If you didn't want to use the actual app already on such a device.
- cheph 5y agoKeep giving money to a company that uses slave labour. What is the worst that can happen?
- kossTKR 5y agoThey 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.
- whereistimbo 5y agoFairphone doesn't. Fairphone goes as far as giving percentage of phone sales to factory workers.
- orbifold 5y agoA percentage of phone sales always goes to factory workers in the form of wages...
- cheph 5y agoWell not always. For example not if you are a Uyghur muslim in china. Then you don't get anything while also getting sodomized with broom sticks. But hey you know, what shall we do, I guess lets just look the other way. Besides it's just cultural differences right?
- whereistimbo 5y agoEdit: No, workers get wages when they do their job regardless of phone sales. Fairphone gives factory workers a bonus from phone sales in addition to the usual wages.
- tsujp 5y agoUnless we're talking about money that is quite literally not from any phone sales (do you count accessories and tied-in services?) e.g. laptops only, then that statement is not strictly true. I've never seen such a differentiation except for on a balance sheet. Apple (as other companies often do) sell many products of which the revenue from those sales pay for the wages of their employees. I don't think financial accounting here plays into the morals of underpaying people. Using "the money to pay these people doesn't come from this line on a balance sheet it comes from that line" is not a justification for the, while unfortunately legal, unethetical employment conditions of others.
- occz 5y agoFrom what I've heard so far about FaceTime on non-apple devices, I'm extremely unimpressed.
- southerntofu 5y agoAnd that's why we use Jitsi, Conversations, Jami... that is pieces of software that were designed to interoperate, not just work in a very specific set of circumstances on particular hardware, with a certain OS version and when the weather is right.
- birthdaydog 5y agoI use both Firefox and Jitsi, but I gotta say, Jitsi has horribly buggy Firefox support.
- asherkin 5y agoFirefox is/was really lacking in WebRTC support for non-P2P use cases - bandwidth estimation support was sub-standard until recently, there is no support for simulcast (multiple video quality encodings) when using H.264, and no E2E encryption support (which is very new to the spec). There has been a lot of back and forth on the Firefox / Jitsi situation but it does seem that most of the time the ball has been sitting in Firefox's court.
- gorjusborg 5y agoI wouldn't be surprised if that outcome is intentional. Apple has been pretty transparent (through their actions) that they don't want FaceTime and ichat to be cross platform. It could be that this exists as a piece of evidence in an anti-trust fight.
- o_m 5y agoWill Linux users using Chrome be able to use it?
- timbit42 5y agoI hope not. Personally, I'm hoping for a vaccine to prevent getting it.
- amq 5y agoThey did mention firefox during the presentation.
- machello13 5y agoThis feature also won't be available for several months, so it's possible they're planning for Firefox support but hedging their bets in case they can't get it done in time.
- Jcowell 5y agoIt’s technically available right now I believe.
- machello13 5y agoRight, I obviously meant actually released publicly and not in beta.
- tyrion 5y agoIt may seem an advantage to use the latest cutting edge features of a single platform, instead of using well established standards which are compatible with every browser. Sure, you are going to leave out some small minority of users, but you gain access to many new features. However, you are helping push the web become an increasingly centralized place, controlled by just a few entities, with interests which are very different from yours. You may think that there is no harm in doing so. Most people use Chrome anyway. And what difference can one more web app make? However, it is exactly this laziness by skilled developers, who are the only that understand the problem, which brought us to the current situation. There is no way to fix this problem, if the people that understand it do not take a stand. Next time that your manager asks you if you can have that sweet feature, instead of saying "sure, we just need to drop support for Firefox", please consider trying to explain what are the consequences in the long term. I know this isn't easy for many people, which do not feel comfortable questioning orders or plans. However, this is our responsibility. Nobody else is going to care, if we do not care.
- hartator 5y ago> you are helping push the web become an increasingly centralized place Does it? Open source standardization is a good thing. Still not sure why html/css/js engine should be the exception. No one is calling for competition for QR code, torrent protocol, or the other billion of very dominant open source projects.
- homarp 5y agobut we have multiple compilers for the same language though. And multiple OS too.
- swsieber 5y agoIt's not really open source standardization though. Google is in charge, make no mistake. Yes people can take it and tweak it, but the main feature changes are dictated by Google.
- cpeterso 5y agoHTML, CSS, JS, QR codes, and Bittorrent are data formats or protocols, not implementations.
- Devasta 5y agoWeb standards stopped mattering in 2004, these days the only browsers that need to be considered are Chrome and mobile Safari, everything else from other browsers to standards bodies is just an exercise in pretending those two browsers don't have control over the web. Those two will never be unseated; the constant addition and change of new APIs means that trying to create a new browser is a herculean task beyond the resources of all but the largest corporations, and even if you did somehow manage to do it the standards will always be retroactively set to whatever Chrome does so you'll always be playing catch up. Its not possible to compete anymore, though to be honest I'm not sure it was ever possible to.
- hinoki 5y agoEven Microsoft couldn’t do it, gave up, and just used Blink. I assume management just saw how much of each release was spent being bug compatible with Chrome and decided it wasn’t worth it.
- kevincox 5y agoMicrosoft dropping EdgeHTML was the biggest blow to the open web in many years. I really hope that Mozilla can pull some magic to keep Google from maintaining basically full control of web standards.
- behnamoh 5y agoI wish Microsoft would buy Mozilla, restart Send, and make FF great again.
- kevincox 5y agoAs much as I am losing faith in Mozilla I think acquisition by Microsoft is a losing move. Especially after we saw them dump EdgeHTML.
- moron4hire 5y agoBullshit. Microsoft adopting Chromium was the single biggest boon for the open web in many years. By reducing the friction for creating powerful web apps, it closes the gap for what is possible in competition with walled-garden app stores.
- gjsman-1000 5y agoIf you review Mozilla's business practices, constant spending on NGOs and Politics, ludicrous executive compensation, and recent layoffs of the engineering team, constant buying and starting of new projects (Pocket, Firefox OS) only to abandon them, and so on, it is clear that at least part of the story is that Firefox has been through incredible mismanagement even as they should have been in the fight for their lives.
- Seirdy 5y agoSome of the activities you described are by the Mozilla Foundation, not the Mozilla Corporation. The two have different sources of funding, so the Foundation's "spending on NGOs and politics" doesn't have any bearing on the funds used on Firefox development. The split between the two exists so that one org doesn't have the constraints of a non-profit: the non-profit Foundation can take tax-deductible donations while the Corporations can do things that a tax-deductible charity can't. I'm not a fan of some of the Corporation's recent non-FF work (Pocket acquisition, Mullvad-based VPN, etc). But saying that they're expensive and take away from FF funding is inaccurate. These projects are intended to create new revenue streams for the Mozilla corporation. I think that Mozilla having to chase new revenue streams in questionable ways (like having a proprietary service, Pocket) in an indictment on the Web's complexity and how it takes billions of dollars to build a browser. Making ethical compromises to fund continued development is an extreme but real example of the consequences of software bloat.
- seumars 5y agoSpot on. Browser competition nowadays is all about each vendor's ability to implement new standards – and in this case Firefox is clearly lagging.
- gentleman11 5y agoMore often, I find the css property I want to use is in Firefox but not chrome. Eg, some of the sideways text values are still Firefox only, forcing you to use transform rotate instead
- willio58 5y ago
- dbg31415 5y agoThat's OK, Firefox would just melt the MBP if you tried to do a streaming call on it anyway. It's my browser of choice, but it uses 40x more power to do streaming (vs. Safari), and has serious heat issues. Wish they'd fix it. Until they do, no reason for Apple to try and support it... likely Firefox can't give a user a good streaming experience on MacOS given how long this issue has been a problem and how little has been done to fix it to date.
- celsoazevedo 5y agoFirefox performance has improved a lot on my 2019 MBP over the past year or so. For video streaming, it doesn't seem to be much worse than Chrome. One of the reasons why Firefox and Chrome use more power than Safari for video streaming is that they support modern/open video codecs that don't have hardware decoding on Macs. For example, YouTube has been using VP9 for years. Until Catalina, Safari would load a h.264 video (that's why Safari used to be limited to 1080p) which has hardware decoding, while Chrome and Firefox would load a VP9 video at higher resolutions and use software decoding, using way more power than Safari. Now YouTube is starting to use AV1 and again, Chrome and Firefox supports it, but Safari doesn't.
- johnswas 5y agoMore reasons to use Firefox.
- RcouF1uZ4gsC 5y agoLooking at where Mozilla spends its money and their layoff of engineering staff, if they don’t prioritize Firefox and engineering, why should we? Also from Apple’s perspective, there may be x% of people using Firefox, but I bet every one of them has the ability to use Chrome if they wanted to, and the people that are sticking solely to Firefox aren’t the ones likely to use FaceTime anyway.
- maverick74 5y agoMeh... The way I see it: The thing is that only IT guys actually know what's going on on the IT world (most web-developers are excluded because their job requires Chrome!). As such only ITs use Firefox (and a few privacy concern and well informed people!)
- 64bittechie 5y agothis is likely because Chrome and Edge use the same underlying rendering engine as Safari - WebKit/Blink. Blink is WebKit's fork but it is mostly compatible with WebKit.
- musicale 5y agoPersonally I wish it worked with Safari, but I'm not holding my breath. For months Zoom and Teams were both very buggy for me on Firefox, and both still seem broken for me on Safari.