Análise de alexcq
Avaliado em 5 de 5
por alexcq, há 4 meses631 análises
- Avaliado em 5 de 5por Usuário 14022344 do Firefox, há 19 horas
- Avaliado em 5 de 5por Usuário 19621835 do Firefox, há 3 dias
- Avaliado em 4 de 5por Usuário 18960744 do Firefox, há 8 dias
- Avaliado em 5 de 5por Usuário 19681471 do Firefox, há 12 dias
- Avaliado em 5 de 5por Vormix_Sv, há 17 dias
- Avaliado em 5 de 5por Usuário 17896262 do Firefox, há 18 dias
- Avaliado em 5 de 5por Yubel, há 19 dias
- Avaliado em 5 de 5por geegamr, há 20 dias
- Avaliado em 5 de 5por Usuário 19661319 do Firefox, há 24 dias
- Avaliado em 5 de 5por Usuário 16948111 do Firefox, há 24 diasWorth it just for the precise percentage on the reviews, rather than the fuzzy review category, which can be bombed.
- Avaliado em 5 de 5por AxolotlFae, há um mêsThis plugin saves me a lot of time switching between tabs to compare sites. I'm fine with the VaporLens feature and would like it to stay. If you have to, just make it an opt-in feature
- Avaliado em 5 de 5por Usuário 19647462 do Firefox, há um mês
- Avaliado em 5 de 5por Usuário 19640117 do Firefox, há um mês
- Avaliado em 5 de 5por ZeroUnderscoreOu, há um mês
- Avaliado em 5 de 5por Ibadullah, há 2 meses
- Avaliado em 5 de 5por oprypin, há 2 meses
- Avaliado em 5 de 5por Smartik1, há 2 mesesTo address the concern around the newly requested permission for Website Content (which also freaked me out), the code is posted on GitHub. I checked the changes, the change was made by the same guy who has been developing this since early 2023. Nothing malicious was added to the code and the data type is not what we all think it is. Here is the definition Firefox provide for the Website Content permission:
"Covers anything visible on a website – such as text, images, videos and links – as well as anything embedded like cookies, audio, page headers, request and response information."
I'd emphasize that this is separate from the Browsing Activity category, which this plugin does not ask for. The very next change committed was a check whether the game is in your library, so it is possible the permissions were for this:
"in_library": {
"message": "In Library",
"description": "Indicates that the user owns this product"
},
That being said, it would have been good if the dev explicitly clarified why the permission request is there, either on the extension install page or within GitHub to put everyone's mind at ease. - Avaliado em 5 de 5por catwithlonghair, há 2 meses
- Avaliado em 5 de 5por Kacp3rowsky, há 2 meses
- Avaliado em 5 de 5por Deo, há 2 meses