S3.Translator

Add-ons Add-on Support
#1

Recipe

  1. Discontinued Chrome Store Foxified 2.4 at https://github.com/Noitidart/Chrome-Store-Foxified/releases or 3.4 in the Internet Archive Wayback Machine
  2. S3.Translator - Chrome Web Store 6.25
  3. any compatible web browser to which a non-signed extension can be added.

Postscript

Beware:

Essential

Do not enable instant upload; do not upload to AMO.

image
image1084×526 52.6 KB

Hint

image
image912×969 93.5 KB
  1. save to disk
  2. use Add-ons Manager to install what was saved.

Video tutorial

Silent, six minutes:

Background

Historically: when S3.Translator was removed from AMO, it was not blocked …

#2

Recipe compatibility

Firefox is not the only browser with which we can use S3.Translator from Chrome Web Store.

Tiers 1 and 2

Mozilla Firefox:

Firefox Beta will not accept unverified extensions.

Firefox Developer Edition works as expected. I’ll add a video tutorial to the opening post here.

Waterfox Classic and Waterfox Current:

Waterfox Current 2019.10:

image
image1744×1003 306 KB

image
image1744×1003 327 KB

Tier-3

Firefox 70.0.1 (20191031162409), FreeBSD-CURRENT:

image
image3200×1080 615 KB

Home-built Waterfox Classic 2019.10 (20191103135811), FreeBSD-CURRENT:

2019-11-07%2012%3A45%3A33
2019-11-07%2012%3A45%3A331049×911 140 KB

2019-11-07%2012%3A46%3A15
2019-11-07%2012%3A46%3A151111×982 129 KB

Reference

Supported build targets - Mozilla | MDN

There are three tiers of supported Firefox build targets at this time. These tiers represent the shared engineering priorities of the Mozilla project.

The term “Tier-1 platform” refers to those platforms - CPU architectures and operating systems - that are the primary focus of Firefox development efforts. …

#3

Chrome Store Foxified can convert a CRX to a signed XPI? Wow…

#4

Hmm. Honestly, it didn’t occur to me, I have not tried – bear in mind the discontinuation, and so on. In the past I was a careless user, guilty of inadvertently uploading things to AMO that were never intended for AMO – NB the essential advice above. Those things were toys for my personal use, never for distribution (although I did, just once, have an afterthought that something ‘up there’ could have been useful to someone else).

In this unusual case, I should probably advise:

  • Chrome Store Foxified must not be used to sign a product of this particular conversion.

This advice might frustrate users in environments where signed extensions are a must (where unstable platforms are disallowed) but the intention is not to frustrate.

Bottom line, without going into detail: I’d like to avoid any overflow of a storm in a teacup … I hope that you (and others) can understand …

Thanks

#5

It’s pretty simple, it changes the file ending (or maybe extracts and re-zips, still not a lot of work), uploads it to the AMO signing API and then downloads it. That’s all there is behind the conversion.

#6

I thought that conversion occurs without an upload.

The extension in this case can be simply saved to disk, or installed (unsigned):

Install%20unsigned%20(do%20not%20sign)
Install%20unsigned%20(do%20not%20sign)1093×1030 122 KB

Those two converted extensions are in my Chrome Store Foxified dashboard, neither one appears at https://addons.mozilla.org/developers/addons

The converted S3.Translator should not, probably must not be uploaded; must not be signed …

#7

AMO

Some historical context, from https://bugzilla.mozilla.org/show_bug.cgi?id=1602293#c0 (for a clone of the extension):

… S3.Translator. was removed because it offer (optional) to send every visited URL to 3rd-party server. …

From around a year ago, three Wayback Machine captures of AMO pages for the extension. In chronological order (note, the 2018-11-12 step down from 6.19 to 5.35):

  1. https://web.archive.org/web/20181002173137/https://addons.mozilla.org/en-US/firefox/addon/s3google-translator/ version 6.18
  2. https://web.archive.org/web/20181112164625/https://addons.mozilla.org/en-US/firefox/addon/s3google-translator/ version 6.19
  3. https://web.archive.org/web/20181121182443/https://addons.mozilla.org/en-US/firefox/addon/s3google-translator/ version 5.35

Captures of privacy policies:

Respectively:

If user consent is given, this add-on will show advertising on web pages.

In that case, the user’s browsing history can be accessed by a third party (ad network).

This behavior does not extend to Private Browsing mode.

ADVERTISEMENT DISABLED BY DEFAULT!

– and:

If user consent is given, this add-on will collect non-personalized browsing history.

In that case, the user’s browsing history can be accessed by a third party.

But we don’t collect cookies, password, e-mails or any other confidential info.

Only the domains (not full URLs) of the web-sites visited and nothing else.

https://bugzilla.mozilla.org/show_bug.cgi?id=1602293#c1 two days ago:

I’ve reviewed the add-ons and confirmed they are collecting ancillary user data against our policies.

Chrome Web Store

Today, for version 6.25, with added emphasis:

Collection of statistics:

If user agree, then the extension may collect non-personalized browsing history.

Such statistics are needed to improve this extension – based on domain names, a map of work priorities will be drawn up in which area it is necessary to add efforts to make the extension better.

We don’t collect cookies, password, e-mails or any other confidential info.

Only the domains (not full URLs) of the web-sites visited and nothing else!

#8

For anyone who would like to inspect the code of S3.Translator at the Chrome Web Store:

In particular, statistics_go.js:

Thanks to Rob Wu for his Extension source viewer and CRX Viewer service.

#9

http://forums.mozillazine.org/viewtopic.php?f=48&t=2829503&p=14852362#p14852362

Unauthorised collection of statistics

Signed version 6.25 for Mozilla Firefox appears to collect statistics after the end user explicitly disables collection.

Respect the preferences of your customers; please fix this. …