giseldo/neodataset huggingface dataset:
Set a specific UA for Playwright

<!---
Please read this!

The Definition of Ready (DoR) can be found at https://developers.minds.com/docs/handbook/how-we-work/#definition-of-ready-dor

Before opening a new issue, make sure to search for keywords in the issues
filtered by the "Type::Feature" label and verify the feature you're about to submit isn't a duplicate.
--->

## Goal

Improve our ability to filter the playwright UA from analytics

## What needs to be done

Improve our ability to filter the playwright UA from analytics

## QA

N/A

## UX/Design

N/A

## Mobile

- [ ] Is Mobile Required?

## Personas

Data team

## Experiments

N/A

## Acceptance Criteria

- [ ] Set custom UA for playwright 
- [ ] Update @michael4tasman with the name

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 1.0
Web: Used a dot to indicate new content in Discovery

<!---
Please read this!

The Definition of Ready (DoR) can be found at https://developers.minds.com/docs/handbook/how-we-work/#definition-of-ready-dor

Before opening a new issue, make sure to search for keywords in the issues
filtered by the "Type::Feature" label and verify the feature you're about to submit isn't a duplicate.
--->

## Goal

Increase engagement and new channel discovery by increasing visits to the Discovery tab.

## What needs to be done

- Add a notification dot on the nav icon for Discovery that indicates new content.
- When the user navigates to Discovery, the dot is cleared
- The dot stays cleared for 24 hours

## QA

<!---
Consideration is given to how the issue will be demoed and tested prior to being deployed
--->


## UX/Design

<!---
Sufficient wireframes have been presented and understood by the development team. Full mockups are not required and re-usable components are encouraged.
--->

[Figma](https://www.figma.com/file/tHjd7fqgBiiTHRTNq5Ltfp/Web---Composer-and-Sidebar-updates?node-id=223%3A7879&t=89HUIWTvGeOE6Dx0-1) contains animation and hover states

![Dot_Over_Discovery](/uploads/e138f24442476533a2ab6555b971bb15/Dot_Over_Discovery.png)

**Spec sheet**

![Screen_Shot_2023-03-06_at_4.07.32_PM](/uploads/30a9777a3f20f173305baf81108359dd/Screen_Shot_2023-03-06_at_4.07.32_PM.png)

## Mobile

<!---
Does a mobile card need to be created? Any notes for mobile?
--->

- [ ] Is Mobile Required?

## Personas

<!---
Who does this user impact and why (optional)
--->


## Experiments

<!---
Experiments are not required, but it should be made clear if one is expected. If experiments are required, the hypothesis should be outlined.
--->

- Implement as an A-B experiment
- Measure visits to Discovery page


## Acceptance Criteria

<!--
Everyone should be able to understand what is expected to be delivered
--->

- [ ] Add a notification dot on the nav icon for Discovery that indicates new content.
- [ ] When the user navigates to Discovery, the dot is cleared
- [ ] The dot stays cleared for 24 hours
- [ ] Run as an experiment

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 2.0
Web: Highlight comments from Minds+ subscribers

<!---
Please read this!

The Definition of Ready (DoR) can be found at https://developers.minds.com/docs/handbook/how-we-work/#definition-of-ready-dor

Before opening a new issue, make sure to search for keywords in the issues
filtered by the "Type::Feature" label and verify the feature you're about to submit isn't a duplicate.
--->

## Goal

Increase reach and engagement for Minds+ subscribers by highlighting their comments in comment threads.

## What needs to be done

Make comments from Minds+ users stand apart from other comments by visually differentiating them.

## QA

<!---
Consideration is given to how the issue will be demoed and tested prior to being deployed
--->


## UX/Design

<!---
Sufficient wireframes have been presented and understood by the development team. Full mockups are not required and re-usable components are encouraged.
--->

[Figma](https://www.figma.com/file/QJiT80vS4yOyprLiafWfbM/Comments?node-id=107%3A1973&t=JIBcctypGnhH7h6Y-1)

**Web**

**Specs for Web**

![Screen_Shot_2023-03-06_at_2.32.39_PM](/uploads/c3e3040c29d46d2dce47583b5f387219/Screen_Shot_2023-03-06_at_2.32.39_PM.png)

![Screen_Shot_2023-03-06_at_2.18.20_PM](/uploads/8e44ed9c7ebea88bdfc503322f940d28/Screen_Shot_2023-03-06_at_2.18.20_PM.png)

**Dark Mode Example**

![Dark_Mode_1](/uploads/2333281befe7c13e6b38d30e385a08ae/Dark_Mode_1.png)

**Light Mode Example Replies Expanded**

![Light_Mode_1](/uploads/b5cdd3f8dae46101564f9c9d8a38cf0f/Light_Mode_1.png)

**Light Mode Example Comment In Replies**

![Light_Mode_2](/uploads/a2f1e5cc7e1e06925e8b1db5ae154137/Light_Mode_2.png)

**Mobile**

**Specs for Mobile**

![Mobile_Specs](/uploads/1614891dc640a5299463a8ffe12b6e76/Mobile_Specs.png)

![Light_Mode_Mobile](/uploads/eb193de66e5d3c79bced04f4a251c692/Light_Mode_Mobile.png)

**Dark Mode**

![Mobile_Share_Comments](/uploads/39ce36dc4c42f43834d70f290e24036f/Mobile_Share_Comments.png)

**Light Mode**

![Light_Mode_Mobile](/uploads/5784f0e31586ae212766402484fd1340/Light_Mode_Mobile.png)



**Mobile**

## Mobile

<!---
Does a mobile card need to be created? Any notes for mobile?
--->

- [x] Is Mobile Required?

## Personas

<!---
Who does this user impact and why (optional)
--->


## Experiments

<!---
Experiments are not required, but it should be made clear if one is expected. If experiments are required, the hypothesis should be outlined.
--->


## Acceptance Criteria

<!--
Everyone should be able to understand what is expected to be delivered
--->

- [ ] A highlight background shows on Minds+ comments
- [ ] Show a Minds+ icon next to the name of the commenter

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 3.0
UXD: Top bar alert component

<!---
Please read this!

The Definition of Ready (DoR) can be found at https://developers.minds.com/docs/handbook/how-we-work/#definition-of-ready-dor

Before opening a new issue, make sure to search for keywords in the issues
filtered by the "Type::Feature" label and verify the feature you're about to submit isn't a duplicate.
--->

## Goal

<!---
Clearly outline the goal of the issue and why we are doing it
--->

Introduce a horizontal bar like we have used in the past for full-site alerts for the purpose of educating users about the referral and commission program.

## What needs to be done

<!---
Clearly detail what needs to be done to achieve the goal set out above
--->

- Create a reusable banner 
- Update text to say "[Refer](https://www.minds.com/settings/other/referrals) sales, fans and creators for cash and token commissions"
- Enable the component to be expandable in the future for other such notices similar to how in-feed notices rotate
- Ensure clicks and dismissals can be tracked

## QA

<!---
Consideration is given to how the issue will be demoed and tested prior to being deployed
--->


## UX/Design

<!---
Sufficient wireframes have been presented and understood by the development team. Full mockups are not required and re-usable components are encouraged.

None

--->

- Component should stick to the top of the viewport on scroll until dismissed.
- Clicking the underlined text navigates to a specified URL.
- Clicking the underlined text DOES NOT dismiss.
- Clicking the x button dismisses.

https://www.figma.com/file/DQPKf1c2Vxv4EXV1JMyHu5/Top-Bar-Alert?node-id=11-2145

![Top_Bar_Alert_A](/uploads/c0f2c871487e2d802c5d450ab5acfb8a/Top_Bar_Alert_A.png)

![Top_Bar_Alert_Mob_-_16px_padding_top_and_bot](/uploads/6b7e08cb072678cc50c6effc0a84a4f1/Top_Bar_Alert_Mob_-_16px_padding_top_and_bot.png)

## Mobile

<!---
Does a mobile card need to be created? Any notes for mobile?
--->

- [x] Is Mobile Required?

## Personas

<!---
Who does this user impact and why (optional)
--->


## Experiments

<!---
Experiments are not required, but it should be made clear if one is expected. If experiments are required, the hypothesis should be outlined.
--->


## Acceptance Criteria

<!--
Everyone should be able to understand what is expected to be delivered
--->

- [ ] ...

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 3.0
Staging test payment upgrade

<!---
Please read this!

The Definition of Ready (DoR) can be found at https://developers.minds.com/docs/handbook/how-we-work/#definition-of-ready-dor

Before opening a new issue, make sure to search for keywords in the issues
filtered by the "Type::Feature" label and verify the feature you're about to submit isn't a duplicate.
--->

## Goal

Make testing on staging / prod around cash easier

## What needs to be done

Improve the testing experience.

## QA

See testing considerations.

## UX/Design

N/A

## Mobile

N/A

## Personas

Minds team members

## Experiments

N/A

## Acceptance Criteria

- [x] Allow emails with pattern anyemail+stripetest@minds.com to use test mode on Stripe
- ~~[ ] Do we want to prevent boosts from being accepted with this? TBD~~
- ~~[ ] Restrict access via VPN?~~

## Definition of Ready Checklist

- [x] Definition Of Done (DoD)
- [x] Acceptance criteria
- [ ] Weighted
- [x] QA
- [x] UX/Design
- [x] Personas
- [x] Experiments

Story points: 3.0
Remind/Supermind options are visible for comment media in modals

<!---
Please read this!

Before opening a new issue, make sure to search for keywords in the issues
filtered by the "T - Bug" label and verify the issue you're about to submit isn't a duplicate.
--->

### Summary

Remind option is visible for comment media in modals - spacing is also messed up

### Steps to reproduce

1. Post media in a comment
2. Click the media
3. See remind button
4. Note quote post has an error, reminding throws the error below

### Platform information 

Web

### What is the current *bug* behavior?

- Remind button shows
- Supermind button shows
- Buttons are misaligned

### What is the expected *correct* behavior?

- Remind button should not show in a comment context
- Supermind button should not show in a comment context (Keep banner if it works)
- Buttons should not be misaligned in a comment context
- In an activity content, all should work fine and look fine.

### Relevant logs and/or screenshots

![image](/uploads/4ee93f58ca90ea450c4537fd6b1c3234/image.png)

![image](/uploads/254043d2deed04adac3a5d1dbbe8ae31/image.png)

### Possible fixes

Hide the button, fix layout issues, double check original modals.

Story points: 2.0
Composer (Video upload / Image upload) visual bug fix

<!---
Please read this!

The Definition of Ready (DoR) can be found at https://developers.minds.com/docs/handbook/how-we-work/#definition-of-ready-dor

Before opening a new issue, make sure to search for keywords in the issues
filtered by the "Type::Feature" label and verify the feature you're about to submit isn't a duplicate.
--->

## Goal

<!---
Clearly outline the goal of the issue and why we are doing it
--->


## What needs to be done

<!---
Clearly detail what needs to be done to achieve the goal set out above
--->


Current implementation 

![image](/uploads/feb02c86baef19a02e3940f18755d5ff/image.png)



## QA

<!---
Consideration is given to how the issue will be demoed and tested prior to being deployed
--->


## UX/Design

<!---
Sufficient wireframes have been presented and understood by the development team. Full mockups are not required and re-usable components are encouraged.
--->

Link to figma -- https://www.figma.com/file/btQfIWFxuSECwpXHQ8Ark3/Visual-update---Composer-(image-%2F-vid-upload)?node-id=15%3A370

![handoff-frame-composer-image-cover-photo](/uploads/2030f6b8b6d1306778c9f17e90e799bf/handoff-frame-composer-image-cover-photo.png)

## Mobile

<!---
Does a mobile card need to be created? Any notes for mobile?
--->

- [ ] Is Mobile Required?

## Personas

<!---
Who does this user impact and why (optional)
--->


## Experiments

<!---
Experiments are not required, but it should be made clear if one is expected. If experiments are required, the hypothesis should be outlined.
--->


## Acceptance Criteria

<!--
Everyone should be able to understand what is expected to be delivered
--->

- [ ] New design implemented
- [ ] Integration tests

Adjusted reqts for mockups after chat with @chints98:
- [ ] no file size exceeded error handling in the cover photo panel (general video error handling strategy to be discussed separately)
- [ ] Filename not required
- [ ] Add ability to remove uploaded file   

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [x] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 3.0
Boost your latest post in-feed notice

<!---
Please read this!

The Definition of Ready (DoR) can be found at https://developers.minds.com/docs/handbook/how-we-work/#definition-of-ready-dor

Before opening a new issue, make sure to search for keywords in the issues
filtered by the "Type::Feature" label and verify the feature you're about to submit isn't a duplicate.
--->

## Goal

Increase Boost purchases.

## What needs to be done

Design and build an in-feed notice / promotion that invites a customer to Boost their latest post.

## QA

<!---
Consideration is given to how the issue will be demoed and tested prior to being deployed
--->


## UX/Design

https://gitlab.com/minds/minds/-/issues/3787

## Mobile

<!---
Does a mobile card need to be created? Any notes for mobile?
--->



- [x] Is Mobile Required?

## Personas

<!---
Who does this user impact and why (optional)
--->


## Experiments

<!---
Experiments are not required, but it should be made clear if one is expected. If experiments are required, the hypothesis should be outlined.
--->


## Acceptance Criteria

<!--
Everyone should be able to understand what is expected to be delivered
--->

- [x] In feed notice displays randomly (shuffled)
- [x] Single entity pages should have a query param to open a boost modal after 1 second (aka do NOT do the delay + animation as specified in designs. Just open the modal after 1 second) 
- [x] Playwright tests for opening the modal

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 3.0
Create an in-feed notice promoting Boost Partners

<!---
Please read this!

The Definition of Ready (DoR) can be found at https://developers.minds.com/docs/handbook/how-we-work/#definition-of-ready-dor

Before opening a new issue, make sure to search for keywords in the issues
filtered by the "Type::Feature" label and verify the feature you're about to submit isn't a duplicate.
--->

## Goal

<!---
Clearly outline the goal of the issue and why we are doing it
--->

Clearly communicate to users of Boost Partners through the use of an in-feed notice that prompts them to join Boost Partners.

## What needs to be done

<!---
Clearly detail what needs to be done to achieve the goal set out above
--->

Create an in-feed notice for Boost Partners

## QA

<!---
Consideration is given to how the issue will be demoed and tested prior to being deployed
--->


## UX/Design

<!---
Sufficient wireframes have been presented and understood by the development team. Full mockups are not required and re-usable components are encouraged.
--->
https://gitlab.com/minds/minds/-/issues/3703

## Personas

<!---
Who does this user impact and why (optional)
--->


## Experiments

<!---
Experiments are not required, but it should be made clear if one is expected. If experiments are required, the hypothesis should be outlined.
--->

Behind the Boost Partners epic experiment

## Acceptance Criteria

<!--
Everyone should be able to understand what is expected to be delivered
--->

- [ ] Show notice this everyone until they dismiss it
- [ ] Read More should dismiss the in feed notice

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 2.0
Gray out "Safe" audience when re-Boosting a post that was rejected for targeting "Safe"

<!---
Please read this!

The Definition of Ready (DoR) can be found at https://developers.minds.com/docs/handbook/how-we-work/#definition-of-ready-dor

Before opening a new issue, make sure to search for keywords in the issues
filtered by the "Type::Feature" label and verify the feature you're about to submit isn't a duplicate.
--->

## Goal

Increase the success rate of Boost submissions by preventing a Boost submission to an audience category for which that activity post was already rejected.

## What needs to be done

- Given a Boost is submitted to the `Safe` audience,
- and the Boost is rejected due to `Wrong audience`,
- when the user retries the Boost via the Boost console,
- then the `Controversial` audience is pre-selected,
- and the `Safe` audience selection is grayed out.

## QA

<!---
Consideration is given to how the issue will be demoed and tested prior to being deployed
--->


## UX/Design

<!---
Sufficient wireframes have been presented and understood by the development team. Full mockups are not required and re-usable components are encouraged.
--->

https://gitlab.com/minds/minds/-/issues/3788

## Mobile

<!---
Does a mobile card need to be created? Any notes for mobile?
--->

- [x] Is Mobile Required?

## Personas

<!---
Who does this user impact and why (optional)
--->


## Experiments

<!---
Experiments are not required, but it should be made clear if one is expected. If experiments are required, the hypothesis should be outlined.
--->


## Acceptance Criteria

<!--
Everyone should be able to understand what is expected to be delivered
--->

- [x] Ensure that the Boost Again link (#5915) opens the modal with the option greyed out
- [x] E2E tests
- [x] ~Listen for a query param for determine if the safe target should greyed out~
BH - Query parameter was not neccesary - I misled planning when I suggested this as I hadn't realised we were going from the Single Boost Page - which has context on whether to show with the option greyed out without the need for a query param.

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 3.0
Get E2E greenlighting

<!---
Please read this!

Before opening a new issue, make sure to search for keywords in the issues
filtered by the "T - Bug" label and verify the issue you're about to submit isn't a duplicate.
--->

### Summary

E2E is currently not greenlighting - we need to ascertain which failing tests are failing because of environmental issues and which are legitimate failures - and fix them / assemble a plan to get a greenlight.

### Steps to reproduce

Run E2E against sandbox.

### Platform information 

Web

### What is the current *bug* behavior?

Red light.

### What is the expected *correct* behavior?

Green light or a plan of action to get there, with follow-on cards.

### Relevant logs and/or screenshots

(Paste any relevant logs - please use code blocks (```) to format console output,
logs, and code as it's very hard to read otherwise.)

### Possible fixes

Note there's various connectivity issues to be considered that could cause sporadic / random flake.

Story points: 3.0
Video flickers when uploading

<!---
Please read this!

Before opening a new issue, make sure to search for keywords in the issues
filtered by the "T - Bug" label and verify the issue you're about to submit isn't a duplicate.
--->

### Summary

When uploading a video through the Composer, the video preview image flickers with upload progress.

### Steps to reproduce

- Launch the composer
- Upload a video

### Platform information 

- MacOS + Chrome

### What is the current *bug* behavior?

- A progress bar indicates progress
- The video preview image flickers

### What is the expected *correct* behavior?

- A progress bar indicates progress
- The video preview does not flicker

### Relevant logs and/or screenshots

![video_flicker](/uploads/5e15b0488c9ca4f0c31b7e52afd1a509/video_flicker.mov)

### Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Story points: 3.0
Add a share icon to comments

<!---
Please read this!

The Definition of Ready (DoR) can be found at https://developers.minds.com/docs/handbook/how-we-work/#definition-of-ready-dor

Before opening a new issue, make sure to search for keywords in the issues
filtered by the "Type::Feature" label and verify the feature you're about to submit isn't a duplicate.
--->

## Goal

<!---
Clearly outline the goal of the issue and why we are doing it
--->
Allow for comments to copied and shared

## What needs to be done

<!---
Clearly detail what needs to be done to achieve the goal set out above
--->
Add a share icon to comments. Place this icon next to thumbs and re-use the same share modal we use for activity posts.

## QA

<!---
Consideration is given to how the issue will be demoed and tested prior to being deployed
--->


## UX/Design

<!---
Sufficient wireframes have been presented and understood by the development team. Full mockups are not required and re-usable components are encouraged.
--->

[Figma](https://www.figma.com/file/QJiT80vS4yOyprLiafWfbM/Comments?node-id=2%3A1161&t=fQFpi0K33JaNUXTz-1)

**Web**

![Post_Entity](/uploads/2106cf57a462c56eb396b01bd9f3265f/Post_Entity.png)

**Reusue same modal that pops up for share post just changed title and subtitle**

![Group_41](/uploads/dbf075be0716c870d60b74ae2d2f9f65/Group_41.png)


**Mobile**

![Mobile_Share_Comments](/uploads/d912218a7803306fa6dd36a8dc19d709/Mobile_Share_Comments.png)

## Mobile

<!---
Does a mobile card need to be created? Any notes for mobile?
--->

- [x] Is Mobile Required?
## Personas

<!---
Who does this user impact and why (optional)
--->


## Experiments

<!---
Experiments are not required, but it should be made clear if one is expected. If experiments are required, the hypothesis should be outlined.
--->


## Acceptance Criteria

<!--
Everyone should be able to understand what is expected to be delivered
--->

- [ ] Add share icon and modal to all comments
- [ ] Update the share modal to say "Share this comment" instead of "Share this post"

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 3.0