AMO does not require a manual review nor the extension to be uploaded publicly. You can sign it through their site and then distribute it elsewhere.
Also, I don't see how you can compare browser extensions to vscode extensions. One product is aimed at your grandma, the other at software developers and doesn't have access to your email, banking and credit cards.
A streamer has to compete with every other streamer for viewers/income. They're basically trying to sell their personality / themselves to the audience. As other comments mention, the vast majority of streamers cannot do that as they have literally no viewers.
The take that it's an easy job seems very weird to me. If it's so easy, why don't you quit your job and start streaming instead?
Because whether it is easy is entirely dependent on who you are and what perspective you look at it from.
If you're a nobody with average skills, see you in a few years with sub 10 viewers, maybe. A nobody with some particular skills, still going to take a while. Exploiting a niche as a particularly charismatic nobody, you'll break through maybe in a few months. Happen to strike rich with a few clips, there is your momentum to make it happen. The vast, vast majority falls in the first category.
Oh, you're already a somebody (500+)? Yeah just play the meta, sellout a few times a year and do what you want mostly. At that point you can do the bare minimum and make it work, as long as you don't self-destruct entirely. Or actually try and make it even more difficult for newer streamers while working to 7 figures. Bonus points, all the positivity will reinforce you to do special things. Almost any problem has a solution in the form of hiring a third party, drowning it out or ignoring it at this point.
Looking at the top makes it seem like the easiest job ever, and to a degree, that is true. Looking at it from the bottom, even retail seems better.
Thanks for sharing! I really like the real time update during progress. You sometimes have to wait a very long time in Scanner before you see the result.
Couldn't crash reports be separated from other telemetry data, possibly with a dialog letting the user whether to send a crash report or not? IIRC, the dialog used to actually exist in older Firefox versions. I find the amount of data they collect[1] to be borderline creepy.
The crash reports at https://crash-stats.mozilla.org are a separate opt in bit of telemetry which is a dialog that is shown when Firefox crashes. You can opt into automatically sending them by setting browser.crashReports.unsubmittedCheck.autoSubmit2 to true. It can be true if you opted into a dialog about submitting unsubmitted crash reports.
Usage times, usage intensity, list of all extensions, country of origin. I don't understand why they'd need those to improve Firefox.
Next thing you know they might try to increase engagement time like they're some sort of social network. "Unlock the new exclusive colorway by logging in 30 days in a row." seems like something that could be implemented, seeing how they're time limited already.
(I work for Mozilla, though far from where decisions about telemetry would be made.)
Usage times and intensity are of high value when trying to improve market share. People who barely use the browser are at high risk of stopping use altogether. (For example, they might use multiple browsers, but most of their activity occurs on another and if they figure out multiple profiles or something, they'll leave altogether.) You can't do an A/B test to see what improves usage intensity if you don't measure usage intensity. Also, it's far from PII. And making it opt-in would make the stats useless; people who explicitly choose to allow telemetry are going to have vastly different usage patterns than the bulk of people who do not so choose.
Extensions are very important for crash reports. Far less than they used to be; many crashes could only happen when an extension did something specific. Extensions are now sandboxed enough that this isn't nearly as common, but if a crash signature has a high correlation with a particular extension, it can easily turn a non-actionable bug into something actionable.
Extensions for general telemetry are iffier. The info is fairly high value for things like understanding how people are using the browser and what features are popular or missing. But rare extensions also provide a lot of fingerprinting info. It's important to keep those metrics away from PII, and recorded independently so they can't be correlated.
Country of origin is pretty clearly useful. Mozilla has to allocate resources across countries, including marketing resources, but I would think it's really product management where it matters most. Users gain a lot of benefit from the browser adapting to different markets. (Screenshots have a wildly different importance in countries with Asian writing systems; Europe and especially Germany take privacy much more seriously.)
> Next thing you know they might try to increase engagement time like they're some sort of social network. "Unlock the new exclusive colorway by logging in 30 days in a row." seems like something that could be implemented, seeing how they're time limited already.
Heh. I do not want to predict what our marketing people will or won't do. I have mixed feelings about quite a few things. I'm not happy about ads appearing anywhere in the interface. But I'm also not happy about being dependent on Google ad money.
> And making it opt-in would make the stats useless; people who explicitly choose to allow telemetry are going to have vastly different usage patterns than the bulk of people who do not so choose.
First, it's a small percentage. Or believed to be a small percentage. There are some larger buckets (eg distributions that disable telemetry), but it's possible to do very rough estimates of the sizes of those through other means. And anyway, the vast majority of users are on Windows.
Second, it's fair: if you disable telemetry, you're choosing to not be considered in any telemetry-backed decision making. If you want to still be considered, then it's up to you to make your opinions heard in some other way. (Filing bugs or https://connect.mozilla.org or discussions in places like here, though note that the latter is mostly useless. Not many Mozilla people read this forum or take what is said here very seriously. And even if they do people will be vigorously arguing both sides so it's easy to pick the side you already agree with.)
There's nothing wrong with disabling telemetry. I respect the decision, and I'd certainly rather have people using Firefox with telemetry disabled than have those people not use Firefox. But it's your browser, and even the social contract by which you're using it doesn't say you owe us telemetry data.
Does the canvas need to be created and removed as it comes in and out of view? Using requestAnimationFrame() might also further improve responsiveness.
Does the canvas need to be created and removed as it comes in and out of view?
Not really. You could just create them and not bother removing them. You'd need to check if the user already had an avatar if you did that though, or you'd end up with lots of repeated avatars when you scroll up and down the page.
Yes, this is "the Llama book" -- Learning Perl. Next to read would probably be Intermediate Perl, and then probably "the Camel book", which is Programming Perl.
