giseldo/neodataset huggingface dataset:
CodePush prompt: show prompt to update native version

<!---
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
--->

We need to communicate to users when there was a codepush that required a higher native version

## What needs to be done

<!---
Clearly detail what needs to be done to achieve the goal set out above
--->

CodePush prompt should show a dismissible info to the user that there's a new version but their native is old


## QA

<!---
Consideration is given to how the issue will be demoed and tested prior to being deployed
--->

TBD

## UX/Design

<!---
Sufficient wireframes have been presented and understood by the development team. Full mockups are not required and re-usable components are encouraged.
--->

N/A

## Personas

<!---
Who does this user impact and why (optional)
--->

N/A

## Experiments

<!---
Experiments are not required, but it should be made clear if one is expected. If experiments are required, the hypothesis should be outlined.
--->

N/A

## 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
The infeed notices are not shown correctly in some cases



### Summary

The in-feed notices are not shown correctly, on the app. 

We are not showing the notices in the correct order. For instance, the `upgrade to plus` is taking precedence over the `verify email`

Given that the upgrade notice is not implemented none of them is shown

I think that Ben reported this issue

### Steps to reproduce

Open the app with a new user

### Platform information 

both

### What is the current *bug* behavior?

notices not shown

### What is the expected *correct* behavior?

It should show the notices in the correct order

### Relevant logs and/or screenshots

-

### Possible fixes

Probably because of some ordering in the logic.

Story points: 3.0
Boost Composer: change default budget

<!---
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

(Summarize the bug encountered concisely)

### Steps to reproduce

(How one can reproduce the issue - this is very important)

### Platform information 

(Browser, device, system stats, screen size)

### What is the current *bug* behavior?

(What actually happens)

### What is the expected *correct* behavior?

(What you should see instead)

### 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

(If you can, link to the line of code that might be responsible for the problem)

Story points: 1.0
Image/Video feed are broken



### Summary

Media feeds are broken

### Steps to reproduce

Selec image or video in the feed filter

### Platform information 
both

### What is the current *bug* behavior?

![imagen](/uploads/d50198f08cdea827333045c80052286d/imagen.png)

### What is the expected *correct* behavior?

It should show the normal posts


### Possible fixes

Change renderer

Story points: 2.0
Boost Console Start Date Format is not correct



### Summary

Please follow the designs in web to show start date in boost console

https://www.figma.com/file/W2xIag64EdbWUlGAQOpVHE/Boost-Update?node-id=485%3A18241&t=wsTI7eqML2evd8j9-0


### Steps to reproduce

1. Open app.
2. navigate to a boost post in boost console
3. Notice that the start date does not match the format in designs. 

### Platform information 

V4.31 staging

### What is the current *bug* behavior?

Start date format is not like in the figma like above

### What is the expected *correct* behavior?

Start date format should be as in figma link above for web

### Relevant logs and/or screenshots

![91F3D40F-CBD8-49C5-849A-D20A1E5048E8](/uploads/276243b0d194ee0f68319aac97a5f5b6/91F3D40F-CBD8-49C5-849A-D20A1E5048E8.jpeg)

### Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Story points: 1.0
Tapping a link to a post is opening behind the comment bottom sheet



### Summary

When tapping a link to a post (inside a comment) it opens the post behind the bottom sheet 

### Steps to reproduce

Tap a link in a comment

### Platform information 

both

### What is the current *bug* behavior?

opens behind the bottom sheet

### What is the expected *correct* behavior?

A new screen should be pushed

### Relevant logs and/or screenshots

![imagen](/uploads/955ff759f0e864fd32a7a9d7b9612a63/imagen.png)

### Possible fixes

Ensure the Activity screen opens the deep links in a new screen (on root)

Story points: 1.0
Communicate upcoming Boost changes to Boosters

<!---
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

- Inform current Boosters about the upcoming changes to Boost
- And that the switchover may impact the Boost they are about to create

## What needs to be done

Add some messaging to the current Boost modal that communicates that (a) things are changing soon, and that (b) their Boost delivery may different than expected because of it.

Link copy points to: https://www.minds.com/info/blog/bid-farewell-the-boost-backlog-1445548466339057665

Given we will likely have a sizable Boost backlog of v2 Boosts when we're ready to switch to v3, @benhayward.ben proposed migrating v2 Boosts to v3 system. The user impact is that their Boosts will effectively be moved to the bidding system, in which their view numbers are not guaranteed. Customers should be aware of this possibility with their newly-purchased v2 Boosts.

![image](/uploads/7d8e86b714dd696d8cd5ff09c7dcd910/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.
--->

[Figma](https://www.figma.com/file/W2xIag64EdbWUlGAQOpVHE/Boost-Update?node-id=879%3A20716&t=BaObSlJNAm1veHmY-1)

**Web**

![Boost_Post_Web_-_Cash](/uploads/76c23489523c8681eba88bd102574a15/Boost_Post_Web_-_Cash.png)

![Boost_Post_Web_-_Tokens](/uploads/c93dc4055f3350cb357bb645ceb6b795/Boost_Post_Web_-_Tokens.png)

![Boost_Channel_Web_-_Cash](/uploads/73e9526c284d080d32bc6d889877f205/Boost_Channel_Web_-_Cash.png)

![Boost_Channel_Web_-_Tokens](/uploads/5bae1d079cfeebb3bf93ec4c9dc1907b/Boost_Channel_Web_-_Tokens.png)

**Mobile**

![Boost_Post_Mobile_-_Cash](/uploads/c2250924a3cc4378e5c7abaa0e4b778a/Boost_Post_Mobile_-_Cash.png)

![Boost_Post_Mobile_-_Tokens](/uploads/8423a2a51bc70bfa688dd2a5635f50a5/Boost_Post_Mobile_-_Tokens.png)

![Boost_Channel_Mobile_-_Cash](/uploads/54672b6a37870eb2c3196bd356ee534d/Boost_Channel_Mobile_-_Cash.png)

![Boost_Channel_Mobile_-_Tokens](/uploads/47c1c7950152239ce65032c93d39676d/Boost_Channel_Mobile_-_Tokens.png)

## 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: 2.0
Emission Breakdown Data As Displayed Within The Browser Interface's Analytics / Tokens / Reward Dashboard Is Not Available Within Corresponding Mobile Application Dashboard

<!---
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

Emission breakdown data as displayed within the browser interface's analytics / Tokens / Reward Dashboard is not available within corresponding mobile client application dashboard.


### Platform information 
Tested using Android mobile client application (version 4.31).

### Relevant logs and/or screenshots

![browser_analytics-tokens-rewards](/uploads/a45ea04b6d8596c216b23c4cf54d2b54/browser_analytics-tokens-rewards.png)<br>
<i>Analytics / token / reward dashboard as displayed within the browser interface.</i>

![mobile_analytics-tokens-rewards](/uploads/0057b5a4646d0196273a6e5e30cb8647/mobile_analytics-tokens-rewards.png)<br>
<i>Analytics / token / reward dashboard as displayed within the mobile client application.</i>

Story points: 3.0
Sometimes Keyboard does not show up on iOS when typing

### Summary

Keyboard is not showing up.

### Steps to reproduce

This is an intermittent issue. 
1. Open minds app on staging.
2. navigate to tags.
3. tap on manage tap.
4. add a new tag.
5. keyboard does not show up.
6. keyboard did not show up anywhere in the app when needed to type eg: creating a new post. 

### Platform information 

Staging

### What is the current *bug* behavior?

Keyboard did not appear
Killing app fixes it

### What is the expected *correct* behavior?

Keyboard must appear when needed

### Relevant logs and/or screenshots

![767DF2DC-F4B6-472E-B3D9-36767C47F403](/uploads/4a8deb21fad57bdd5dc52527d401c9b7/767DF2DC-F4B6-472E-B3D9-36767C47F403.jpeg)

Story points: 2.0
Orientation lock is not working on iOS



### Summary

Orientation locking is not working on iOS

 - Tested with current lock package and expo-screen-orientation

### Steps to reproduce

rotate iOS device

### Platform information 

iOS

### What is the current *bug* behavior?

orientation is not locked

### What is the expected *correct* behavior?

it should be locked/unlocked depending on the needs of the app

### Relevant logs and/or screenshots
![Simulator_Screen_Shot_-_iPhone_14_-_2023-01-25_at_11.59.19](/uploads/11bd1076d09654d887fc171d471d1cbd/Simulator_Screen_Shot_-_iPhone_14_-_2023-01-25_at_11.59.19.png)

### Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Story points: 2.0
Boost console: Use boosts delivered instead of post views

<!---
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

(Summarize the bug encountered concisely)

### Steps to reproduce

(How one can reproduce the issue - this is very important)

### Platform information 

(Browser, device, system stats, screen size)

### What is the current *bug* behavior?

(What actually happens)

### What is the expected *correct* behavior?

(What you should see instead)

### 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

(If you can, link to the line of code that might be responsible for the problem)

Story points: 1.0
Add option to report Minds+ content for violating content policy

<!---
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

Enable the community to contribute in moderating the quality of Minds+ premium content.

## What needs to be done

- Add an option to the list of Report Reasons: Violates Premium Content policy
- Display the option when reporting content that is Premium Content
- Check if the options are coming from backend

![IMG_459C75614CA1-1](/uploads/2ccc92711c7e6ed009129508ec816e05/IMG_459C75614CA1-1.jpeg)

![image](/uploads/c63b8d27c8a6c0e5fa86134dac59e9ab/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.
--->


## 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
--->

- [ ] Accepted reports de-monetize the content
- [ ] Accepted reports generate a strike
- [ ] If a user receives 3 strikes then they can no longer post to Minds+

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 3.0
Display boosts to channel pages

<!---
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
--->

As a Minds, I want to increase Boost inventory supply so that I can better fulfill the demands of customers.

## What needs to be done

<!---
Clearly detail what needs to be done to achieve the goal set out above
--->
Add a Boost slot to channel pages.
See https://gitlab.com/minds/minds/-/issues/3281 for mockups

Only for others channel.


## 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.
--->

Provided in https://gitlab.com/minds/minds/-/issues/3281

## 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)
--->

All users

## Experiments

<!---
Experiments are not required, but it should be made clear if one is expected. If experiments are required, the hypothesis should be outlined.
--->

yes, this should use the boost partners epic label (confirm if not already created).


## Acceptance Criteria

<!--
Everyone should be able to understand what is expected to be delivered
--->

- [ ] Boosts display on channel pages
- [ ] Display in the 2nd slot and then every 6 posts
- [ ] Client meta on view endpoint and snowplow is aware of the channel the boost is being displayed on

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 5.0
Display channel boosts in recommended channels slot

<!---
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
--->
As Minds, I want to add more available channel Boost inventory so that I can better meet the demands of customers.

## What needs to be done

<!---
Clearly detail what needs to be done to achieve the goal set out above
--->
Update the existing `Recommended Channels` component to include a 4th recommendation that's a Boosted channel.
Designs are provided in https://gitlab.com/minds/minds/-/issues/3666

## 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.
--->
See https://gitlab.com/minds/minds/-/issues/3666

## 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.
--->
Use the boost v3 epic label

## Acceptance Criteria

<!--
Everyone should be able to understand what is expected to be delivered
--->

- [ ] Boosts show in the recommended channels slots
- [ ] Views and correct context are tracked
- [ ] For views - look at how the [feed notice analytics](https://gitlab.com/minds/front/-/merge_requests/2155/diffs#45a4bd9f20ad6df6af964f4bfb2012ceac8878de_25_28) are being sent. DM @benhayward.ben if there's any questions

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 5.0
Update copy on Monetize modal

<!---
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

- Better communicate the existing content policy on Premium Content
- Communicate that the existing policy will be enforced

## What needs to be done

Update the copy on this modal:

> Submit this post to Minds+ Premium Content and earn a share of our revenue based on how it performs.

> [ ] I agree to the [https://www.minds.com/p/monetization-terms](Minds monetization terms) and have the rights to monetize this content.
> 
> - This content is my original content
> - This content is exclusive to Minds+
> 
> I understand that violation of these requirements may result in losing the ability to publish Premium Content for Minds+ members.

Old:

![image](/uploads/68409412d55f8e64236e244dbc780419/image.png)

New:

![image](/uploads/30928f8d6826dd285e74a0305cf01103/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.
--->

## 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
--->

- [ ] The text has been changed

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 2.0
Add Sentry details logging for CodePush events behind a feature flag

<!---
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

Debug and isolate situations where the Code-Push is not working correctly.
<!---
Clearly outline the goal of the issue and why we are doing it
--->


## What needs to be done

Add Sentry details logging for CodPush events behind a feature flag

<!---
Clearly detail what needs to be done to achieve the goal set out above
--->


## 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.
--->
N/A

## 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
--->

- [ ] ...

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 3.0
Warning for Minds Plus content on iOS in need of design work

<!---
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

The warning on iOS for Plus seems off 

- The blur may not be using blurhash correctly
- The component displaying `minds+ is not available on this platform` looks out of place and difficult to read - on web these are usually centrally aligned.
- I have no idea what the unlock button does, if the post is not viewable on iOS.
 
One thing to note is this is multi-image.

### Steps to reproduce

Look at a plus post on iOS
- make sure the test account has no minds+ options enabled
- search for `JohnG76` and scroll on his feed
- reminded locked posts have the lock not centered.
- posts with `The media could not be loaded` ave the lock not centered.
- the activity is rendered correctly at the beginning and re-rendered wrong immediately.

### Platform information 

Mobile

### What is the current *bug* behavior?

Visually unappealing

### What is the expected *correct* behavior?

Should be designed and implemented accordingly.

### Relevant logs and/or screenshots

![image](/uploads/52d9e4599efd966a1cbae678a12f9408/image.png)

### Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Story points: 3.0