Re: Java plugin phase out timeline

hi Suril, Vidyo recently announced a plugin-free, WebRTC version of 
VidyoWeb for Firefox and Chrome:

http://www.vidyo.com/company/news-and-events/press-releases/vidyo-delivers-webrtc/

http://www.vidyo.com/products/use/

Mozilla uses Vidyo internally. I have not personally tried the new 
WebRTC client, but Mozilla's IT department is testing it and preparing 
to deploy it within Mozilla. I usually use the VidyoDesktop standalone 
client, but will switch to WebRTC when I have the chance.

chris


On 7/18/16 3:54 PM, Suril Patel wrote:
> Hi Chris,
>
> Thanks for your prompt response.  We use Vidyo, Inc. plugin, called
> VidyoWeb.
>
> In Chrome, they have a browser extension.  For Safari, IE, and FF, we
> execute NPAPI code - based on browser detection.  Edge - we detect and tell
> the customer to switch browsers :)  This is less than ideal, but WebRTC
> does not meet some of our needs - and we see very good video quality at
> lower bandwidths using this tech stack.
>
> In any case, we really want to understand the plans and align ourselves.
> This is a healthcare use case (I guess I could correspond officially from
> my corporate email), with some of our population being the elderly - so we
> want things to be easy.
>
>
> So looking at what you shared - effective March 7th, the patients who's FF
> automatically updates would not be able to sign in.
>
> 1)  Is there a transitional version planned prior to that, where upon
> update - all plugins default to a blacklist?  In other words, is there
> suppose a v51 - where upon update, VidyoWeb gets blacklisted and we need to
> send out instructions to patients to unblock or whitelist VidyoWeb?   (We
> are investigating a long term solution that is not dependent on NPAPI - but
> I just want to understand, in case management wants keep the NPAPI track
> open until the end - how we can manage messaging to users on the site and
> appropriately detect the browser to handle the various scenarios here)
>
>
> Thanks
>
> Suril
>
> On Mon, Jul 18, 2016 at 5:31 PM, Chris Peterson <[email protected]>
> wrote:
>
>> I believe Firefox 52 will completely disable NPAPI without any manual pref
>> override or whitelist (except for Flash).
>>
>> The Firefox 52 release is planned for March 7, 2017. I updated the release
>> calendar wiki:
>>
>> https://wiki.mozilla.org/RapidRelease/Calendar#Future_branch_dates
>>
>> What is the NPAPI plugin that your organization uses for video
>> conferencing? Google Hangouts? Does your organization have a solution for
>> Chrome or Edge? They don't support NPAPI plugins.
>>
>>
>> chris
>>
>>
>> On 7/18/16 2:06 PM, Suril Patel wrote:
>>
>>> Hi Benjamin (or other associate),
>>>
>>> I am trying to follow, but I think I am a little confused by the latest
>>> exchange.  We use an NPAPI plugin for Video conferencing, as part of very
>>> large (millions) consumer facing organization.
>>>
>>> Per what I understood previously, Version 52, will Beta Release on Jan 23
>>> or Jan 24.  The actual general release date - I don't see it, but I am
>>> curious.
>>>
>>> 1)  Will v52 - releasing in Q1 - by default blacklist all NPAPI plugins?
>>> 2)  Thus, the user if he wishes to use an NPAPI plugin, he will have to
>>> manually go somewhere to "enable" or "whitelist" plugins individually or
>>> is
>>> it a setting for all?  Any insights here are helpful.
>>> 3)  What is general release date for v52?
>>> 4)  I assume v53, which is April 2017 will completely disable NPAPI, with
>>> no manual override.
>>>
>>> I want to clarify - in our case, ESR versions are not part of the picture
>>> -
>>> as our audience is millions of consumers, who will follow the general
>>> release sequence of Firefox, with Auto-update (as an example, I am one of
>>> them, who recently got upgraded to v47).
>>>
>>>
>>> Thanks
>>>
>>> Suril
>>>
>>> On Mon, Jul 11, 2016 at 6:00 PM, Benjamin Smedberg <[email protected]
>>>>
>>> wrote:
>>>
>>> The Firefox release calendar can be found at
>>>> https://wiki.mozilla.org/RapidRelease/Calendar
>>>>
>>>> --BDS
>>>>
>>>> On Mon, Jul 11, 2016 at 5:38 PM, Java Dev <[email protected]> wrote:
>>>>
>>>> On Monday, June 27, 2016 at 11:36:36 AM UTC-4, Benjamin Smedberg wrote:
>>>>>
>>>>>> Actually Chris, my plan was to do this in Firefox 52, not wait for
>>>>>>
>>>>> Firefox
>>>>>
>>>>>> 53.
>>>>>>
>>>>>> --BDS
>>>>>>
>>>>>>
>>>>>
>>>>> Thank you for the quick reply. Just to clarify, what is the scheduled
>>>>> release time frame/date for Firefox version 52 which would block all
>>>>>
>>>> NPAPI
>>>>
>>>>> plugins? Also, is it still the case that users who need NPAPI support
>>>>> can
>>>>> switch to Firefox ESR 52 and keep using NPAPI plugins until May 2018?
>>>>>
>>>>>
>>>>> Best Regards,
>>>>> Alexandra
>>>>> _______________________________________________
>>>>> dev-tech-plugins mailing list
>>>>> [email protected]
>>>>> https://lists.mozilla.org/listinfo/dev-tech-plugins
>>>>>
>>>>> _______________________________________________
>>>> dev-tech-plugins mailing list
>>>> [email protected]
>>>> https://lists.mozilla.org/listinfo/dev-tech-plugins
>>>>
>>>>
>> _______________________________________________
>> dev-tech-plugins mailing list
>> [email protected]
>> https://lists.mozilla.org/listinfo/dev-tech-plugins
>>