jgruen

boop: https://github.com/mozilla/send

There are a ton of these in DDG: https://duckduckgo.com/bang

Yeah, it will sometime soon.

(source: working on it)

Hey, Screenshots person here...this is a new one to me.

My only thoughts would be the pref flip that seems to be ruled out at this point, or that you're trying to shoot an about:[SOMETHING] page for which we disable screenshots.

Otherwise, file an issue: https://github.com/mozilla-services/screenshots/issues

We're triaging in an hour or so :)

hit the hamburger menu, then Customize.

In the lower right, there should be a toggle for it.

edit: not sure if that's linux friendly

We're seeing the Edge error too, though it wasn't there in earlier QA, so it's a bit mysterious. Hopeful that we'll have some remediation soon.

Source: I work on Test Pilot

yep

We're moving to a webExtensiony future. The idea here is that we'll be a first party consumer of the webExtension APIs so we can help test/drive/expand capabilities.

Hey, we're a little behind on writing up the last few experiments unfortunately. We'll be adding full reports over the next few weeks.

So, I'm a PM at Mozilla who did an MDes in Interaction Design at CMU. I'm a dataset of one, but my experience there was absolutely worth the cost. A few notes:

- 65k is a lot, but Pittsburgh is cheap compared to the Northern California or New York or almost anywhere. Someone on the thread tossed out 65k a year in additional cost of living; this number is way off. You can get a room for < 800 bucks a month (possibly significantly less if you're willing to commute even a little). Food is cheap, there is modest but acceptable public transit, the city's pretty bikable, and there's plenty of free stuff to do etc etc. TL;DR Pittsburgh is great.

- There are lots of fellowships for grads available through CMU. I TAed Web dev and creative coding courses and IIRC, the money I got for doing so completely covered my rent and internet bill.

- If you've spent any time at all on the CMU campus, it's pretty clear the the institution is absolutely unique WRT the depth and breadth of CS, Design, HCI, Robotics, and Business talent. BTW, this list is not exhaustive. The sheer density and variety and stuff happening on campus is simply not comparable to working at a startup (which requires laser focus). A big part of the CMU experience is expanding your horizons about what's possible in ways that MOOCS (and I daresay industry) cannot.

- Also CMU grad programs place nearly EVERYBODY. It's the primary reason I went there as a chronically underpaid, semi-clueless freelancer having trouble breaking into industry. Their relationships with industry – both formal, and through causal peer/alumni connections – are pretty staggering.

All of that being said, I didn't move into a PM role until I'd spent significant time in the UX org at Mozilla learning how the sausage gets made. I definitely only started to grok the on-the-ground dynamics of product management after several years in industry, and I'm still learning every day. My sense is that most PMs have similar trajectories of transitioning into the role after time in industry. I'd be curious about whether industry would look favorably on hiring PMs directly out of school.

Containers are per-tab and isolate only tracking-related data (not bookmarks or history, for now). Also containers don't require that you open multiple instances of Firefox.

1. Hello potch! 2. Yes, this is among the most requested features we've seen so far. Containers in Test Pilot will remain in active development for the foreseeable future, so I wouldn't be surprised to see such a feature forthcoming.

Agreed. Right now we're pretty hands off about modifying default behaviors, link handling etc. Chalk this up to us wanting to be unopinionated about specific use cases, but there are definitely some optimizations to be made to shore up the situations you describe. Test Pilot is for WIP software, so don't be shy about filing issues.

Yes this, we did some brainstorming and solicited user feedback about names and decided Containers makes sense for a general audience. Docker Containers and 'Contextual Idendities' are kind of inside baseball.

Simply, our user testing (with Windows users in particular) suggests it's a feature people find useful. We're using Test Pilot to learn a bit more, that's all.

I only mentioned screen sharing because of the comment about Chrome's sharing feature (of which I was unaware, but will check out).

So the other thing with the Tracking Protection experiment is that we're soliciting feedback about how this feature breaks the web. We use a block list from Disconnect for Tracking Protection in Private Browsing and for Focus on iOS, but until now had very little understanding of how enabling this feature might affect browsing.

For the Test Pilot experiment we're asking users to tell us where and how the feature messes up websites so we can refine our Block list and improve the experience for everyone. We're already getting a lot of significant data and intend to share it soon.

Hello had browser sharing built in for awhile, but nobody used it, so we took out the feature in 49.

Test Pilot is, at least in part, a program intended to let us develop ideas in the open without the cost and complexity of shipping to millions of Firefox users. Whether or not you choose to install these experiments is entirely discretionary.

Test Pilot and all these experiments are OPT IN. You have to seek them out and install them separately from Firefox.

Actually, we've made email collection/messages entirely opt in (as the result of user feedback) :)

Edit: but we should update the privacy notice!

Page Shot, like all features in Test Pilot is opt in. We have no plans to force anything on anyone. A big part of why we built test pilot in the first place was to give us a platform to test UX without going all 'Leeroy Jenkins' on Firefox users every time we come up with a new idea.

This is an opt-in experiment in an opt in program.

The Test Pilot program is pretty small compared to the total traffic to the Wayback Machine. The Internet Archive guys were not worried about this, so I'm not either.

The No More 404s experiment, like all of Test Pilot, is totally opt-in. The whole idea is to let us try things with Firefox, get feedback and iterate quickly.

No More 404s Telemetry ping is only gathering data about how often the Add-on is fired and how often it is clicked. We (Mozilla) don't know anything about URLs. The Wayback Machine has it's own privacy protections in place that you can learn about here: https://blog.archive.org/2013/10/25/reader-privacy-at-the-in...

Also worth noting, every Test Pilot experiment comes with a brief explainer of all data collections. Here's the explainer for No More 404s:

In addition to the data collected by all Test Pilot experiments, here are the key things you should know about what is happening when you use No More 404s:

* We collect basic usage on how many times you encounter a Page Not Found error (code 404), how many times a cached version of that page exists from Archive.org, and how many times you choose to view the cached version.

* To provide cached versions of pages, we send 404 error page URLs to Archive.org. Archive.org discloses its privacy policy here (https://archive.org/about/terms.php).

* We do not collect URLs of the pages you request or the URLs we send to Archive.org.

* We may share survey results you submit to us and aggregated telemetry data related to this experiment with the Internet Archive.

We were going for an 'edge of the atmosphere' feel. Also, that hood scoop is pretty rad.

While this isn't integrated into the Test Pilot site UX for the time being, we have Discourse forums set up for all of the experiments in Test Pilot.* If you'd like to register questions or feedback ton Discourse, team members and community moderators will be monitoring the forum.

https://discourse.mozilla-community.org/c/test-pilot

*Yes, you'll need to sign in with Persona ;)

We don't know exactly what's going to happen with Tab Center--or any of these experiments--in the long run. Our goal here is to get feedback from our users to drive successive UX and engineering iterations.

Once experiments have incubated in Test Pilot for awhile, we will have a number of options depending on each experiment's overall success. We may push them over to AMO, or integrate them directly into the browser. If an experiment is really unsuccessful, we may simply cut our losses and walk away. Test Pilot should help us make these decisions more quickly and effectively.

We'll be blogging more about the overall Test Pilot pipeline in the weeks to come. Stay tuned!