50% of the Worlds Firefox users now have no supported pocket on irefox

Gerv 

You have stated elsewhere (sumo)
>  50%+ of the world can't find a Pocket button. 

and above
> AIUI, the Pocket team don't plan to continue to maintain the addon version. 

These will be the people using the other builds of Firefox.
They had a supported signed Firefox addon. The addon has since  been removed 
from AMO. So those users now have no way of installing and using Pocket at all.

Those who for instance do a *Refresh* as prompted; if for instance: Firefox is 
slow, not used for a while, or after updates; will also lose the working and 
installed Pocket extension. 

KaiRo

> I understand this is still available for locales, or Firefox builds I should 
> say, that do not integrate Pocket.

>> From what I know, that's not true. The functionality that we did test
in beta for locally storing was AFAIK disabled everywhere

I am not sure whether you are discussing the integrated version when you say 
this.

Or are you implying that of the 50%+ of the worlds Firefox users
If they had and were using the AMO signed pocket extension that the 
functionality of that has also been hobbled even though they do not have an 
integrated Pocket.   

AFAIK Google Chrome still has the old type functionality on their Pocket 
version, and I did note a user state he was migrating to Chrome because of the 
change.

It still looks to me as if  many Firefox Pocket users are losing out because of 
this integration.  

Possibly it is not just losing local saves. Am I now to understand is it 50%+ 
of worldwide Firefox users loosing Pocket support entirely.  
I am trying to confirm exactly what the situation is and Mozilla's reasoning 
for these changes. The reasoning for the changes is unclear. How to explain and 
document this for Firefox users is not easy. 

Any further explanation and clarification welcome.

Thanks John
_______________________________________________
governance mailing list
[email protected]
https://lists.mozilla.org/listinfo/governance

Reply via email to