There sure seem to be a bunch of censored users who want a browser extension that does something useful for them.
Shouldn't we try to act on that signal?
My suggestion:
We must differentiate our products so that there is no confusion about which is intended for censored users and which is intended for uncensored users.
But since we already have the tech required to create and publish a wasm-powered extension, maybe we can quickly create a new extension, aimed at censored users, which provides some value?
Obviously, the dream would be to create an extension that provides Lantern's core censorship circumvention functionality. If that's not possible, what else can we do that might be valuable?
@myleshorton pointed out that https://github.com/getlantern/product/issues/30 reveals an opportunity:
There sure seem to be a bunch of censored users who want a browser extension that does something useful for them.
Shouldn't we try to act on that signal?
My suggestion:
We must differentiate our products so that there is no confusion about which is intended for censored users and which is intended for uncensored users.
But since we already have the tech required to create and publish a wasm-powered extension, maybe we can quickly create a new extension, aimed at censored users, which provides some value?
Obviously, the dream would be to create an extension that provides Lantern's core censorship circumvention functionality. If that's not possible, what else can we do that might be valuable?