Chrome extension

Description

We have two features with similar names: conversation-filters and conversation-activity-filter. It's not clear from the names they do very different things, and I think it's best to distinguish them via a different name.

I suppose rename conversation-filters to more-conversation-filters, since that's what the feature does actually. It's not adding a whole feature of c

We want to add a link to our content guidelines before a user submits a source request. This will provide users a better understanding of what the process is and what content we allow, and what not.

How to get started?

• This

While there are already lots of tests, several components are still lacking proper tests (just the one skeletal generated test). It would be nice to have tests for a lot of such components.

Update styling to match new Chrome/devtools flat design.

Description:

Provide option to keep some segment and provide a submit button below each segment as I don't want to upload the first segment. As I want the first segment but not sure about the consensus and correctness about the first segment.

Remote Functions Refactor

Overview

Remote functions exist to enable background->tab, and tab->background function delegation (i.e. Call a function in a tab, but have it run in the background and vice versa).

Refactoring has been started to make these functions interfaced and type safe.

Tasks

Grepping the codebase for remoteFunction( shows where it's still being us