giseldo/neodataset huggingface dataset:
IAP: Enable in-app purchase for app in stores Android (optional iOS)

<!---
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

Provide in-app purchase support to app.

<!---
Clearly outline the goal of the issue and why we are doing it
--->


## What needs to be done

- Enable in-app purchase for app in stores Android (optional iOS)

<!---
Clearly detail what needs to be done to achieve the goal set out above
--->


## QA

MR: [2180](https://gitlab.com/minds/mobile-native/-/merge_requests/2180)
<!---
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?
--->

- [ ] 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: 2.0
IAP: Install native package for in-app purchase

<!---
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

Provide in-app purchase support to app.

<!---
Clearly outline the goal of the issue and why we are doing it
--->


## What needs to be done

- Install react-native-iap 

<!---
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.
--->

## 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: 2.0
Editing posts updates wrong timestamp

### Summary

Editing posts updates wrong timestamp

### Steps to reproduce

1. Have a post on your timeline
2. Edit post
3. save
4. Notice timestamp is now 1s

### Platform information 

Android, 4.32.4

### What is the current *bug* behavior?

Editing updates wrong timestamp (bumps the post)

### What is the expected *correct* behavior?

The publish timestamp should be same

### Relevant logs and/or screenshots

![XRecorder_11032023_181120](/uploads/effe51ccaac866eeff6beacc4118eb90/XRecorder_11032023_181120.mp4)

### Possible fixes

-

Story points: 2.0
Double click on profile picture, makes profile open twice

### Summary

Double click on profile picture, makes profile open twice

### Steps to reproduce

1. Go to your burger menu
2. Doubleclick pfp
3. See that your profile is opened twice (can be seen on video bellow)
4. Notice you don't see suggestions

### Platform information 

Android, 4.32.4

### What is the current *bug* behavior?

Double click opens profile twice

### What is the expected *correct* behavior?

Profile should open once, despite double click

### Relevant logs and/or screenshots

![XRecorder_11032023_180312](/uploads/6fd573270d329df60e9ee7a823fe1e0a/XRecorder_11032023_180312.mp4)

### Possible fixes

- investigate how to prevent double tap (optional) maybe a central touchable component.

Story points: 3.0
Hashtag dropdown hidden behind keyboard

### Summary

The keyboard hides the hashtag dropdown

### Steps to reproduce

1. Create a post
2. Navigate to tags
3. Start typing
4. Notice you don't see suggestions

### Platform information 

Android, 4.32.4

### What is the current *bug* behavior?

Tag suggestions hidden

### What is the expected *correct* behavior?

Tag suggestions should be visible

### Relevant logs and/or screenshots

![image](/uploads/22c1c1087939e259bc4b014eb416b5ca/image.png)

### Possible fixes

- at least wrap everything in a ScrollView. Ideally maintain the dropdown after focus.

Story points: 2.0
Remove Minds+ monetization option from post editor



### Summary

It should not be possible to make a post minds+ after it has been published/

### Steps to reproduce

1. Have account with Minds+ and an existing post
2. Edit a post
3. Add a hashtag, and choose to monetize with Minds+
4. Save

### Platform information 

Android, 4.32.4

### What is the current *bug* behavior?

It's possible to attempt to add Minds+ on edit

### What is the expected *correct* behavior?

The button to add Minds+ should not apprear.

### Relevant logs and/or screenshots

-

### Possible fixes

-

Story points: 2.0
CPM values are incorrectly calculated

### Summary

CPM Values are incorrect. Reported by @jotto141 

### Steps to reproduce

1. Open minds app
2. Perform a boost
3. navigate to boost console once boost is completed
4. check for CPM values


### Platform information 

minds production

### What is the current *bug* behavior?

CPM Value is incorrect

### What is the expected *correct* behavior?

CPM value should be correct. Should be 0.34 for first boost in screenshot. 

### Relevant logs and/or screenshots

![C991E3E1-DFAD-4709-A3A6-50C2173C6D6A](/uploads/282c26b46a545e6c8870099b151af632/C991E3E1-DFAD-4709-A3A6-50C2173C6D6A.png)

Story points: 1.0
Refactor images using expo-image



## Goal

Refactor all the images of the app from FastImage to expo-image. 

This should improve the performance and memory consumption of the app. expo-image also supports blurhash out of the box and it improves the image caching.


## What needs to be done

- Replace FastImage with expo-image
- Ensure to use the blurhash when available
- Remove custom blurhash implementation

## QA

Smoke test around all the images displayed in the app

## UX/Design

-

## Personas

UX

## Experiments

-


## Acceptance Criteria

- [ ] All instances of Image or FastImage should be replaced
- [ ] The blurhash functionality should work as expected in the activities

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 8.0
Revenue share dropdown does not show in Wallet > Cash > Earnings

<!---
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

Revenue share dropdown does not show in Wallet > Cash > Earnings

### Steps to reproduce

1. Go to Wallet > Cash > Earnings on desktop and mobile
2. Compare the two tabs on devices
3. Notice that Revenue Share (with everything it should include) is missing on mobile

### Platform information 

Android, 4.32.3

### What is the current *bug* behavior?

Revenue Share is not showing on mobile

### What is the expected *correct* behavior?

Revenue share should show on mobile

### Relevant logs and/or screenshots

![image](/uploads/03bdb9c9a755d2382c3d0c46f5a2ecd0/image.png)

### Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Story points: 2.0
"Connect Bank +" Shows on Wallet > Cash > Settings, and prompts old onboarding flow.

<!---
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

"Connect Bank +" Shows on Wallet > Cash > Settings, and prompts old onboarding flow.

### Steps to reproduce

1. Create a new account
2. Go to Wallet > Cash > Settings
3. See on top right side, Connect Bank+

### Platform information 

Android, 4.32.3

### What is the current *bug* behavior?

Connect Bank+ shows when it should not

### What is the expected *correct* behavior?

Connect Bank+ not showing

### Relevant logs and/or screenshots

![image](/uploads/edf7ea58275495992c8bcfce55fcabac/image.png)

### Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Story points: 2.0
Allow updating stripe data at Wallet > Cash > Settings

<!---
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

On Desktop, it's possible to update stripe details from Wallet > Cash > Settings.

Mobile lacks this option:

![image](/uploads/0e2ece2d00f0a8b0508f09645d99ee9a/image.png)


## What needs to be done

<!---
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.
--->

## 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
Channel feed remains blank

### Summary

Channel profile and other users channels do not load and remain blank

### Steps to reproduce

1. Open mobile app
2. Navigate to a channel

### Platform information 

Staging v4.32.1

### What is the current *bug* behavior?

Channel feed remains blank

### What is the expected *correct* behavior?

Channel feed should load successfully

### Relevant logs and/or screenshots

![FullSizeRender](/uploads/75b0e74b065c27b206e66e34973996cd/FullSizeRender.MOV)

Story points: 2.0
CodePush release - 4.32.4

<!---
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
--->
CodePush release - v4.32.4


## What needs to be done

<!---
Clearly detail what needs to be done to achieve the goal set out above
--->
Run a smoke test and review all already tested tasks from staging environment.

#4815
#4805
#4806
#4791  
#4653 
#4654
#4802
#4795

## QA

<!---
Consideration is given to how the issue will be demoed and tested prior to being deployed
--->
- Base store version: v4.32.1
- Codepush environment: staging

## 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?
--->

- [ ] 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: 1.0
Crash when typing on comment's input


### Summary

App is crashing when typing a comment

It is related to this issue

https://github.com/facebook/react-native/issues/35590

### Steps to reproduce

Create a comment and type a long text

### Platform information 

Android, mostly android 13 and/or Samsung devices

### What is the current *bug* behavior?

App slowness/crash

### What is the expected *correct* behavior?

Users should be able to type comments without crashes

### Relevant logs and/or screenshots

-

### Possible fixes

Disable text autocomplete as a workaround.

Story points: 2.0
Composer: video source gets deleted when cancelling edit

<!---
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

"If I have a video and start to edit it, but then close down the editing composer, it appears that it then deleted the source video but keeps the entity?"

### Steps to reproduce

- post a video
- go on your channel feed
- click edit post
- dismiss the composer and click discard
- notice that the video won't play anymore and a "There was an error displaying a media" error will be shown

### Platform information 

all

### What is the current *bug* behavior?

video source gets discarded on edit

### What is the expected *correct* behavior?

video source shouldn't be touched

### 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.)

![image](/uploads/45e7c3c2a039699064bdbdddff428124/image.png)

### Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Story points: 5.0
Mob: 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/add012c31eef87c02e80c95cf5ca2e8e/Dot_Over_Discovery.png)

**Spec sheet**

![Screen_Shot_2023-03-06_at_4.07.32_PM](/uploads/f86a54c93c6cc6c39ad3f4bc2f6c9f8c/Screen_Shot_2023-03-06_at_4.07.32_PM.png)

## Mobile

**Mobile**

![Search_Mobile](/uploads/333001a6637a3743b1756337e6e72409/Search_Mobile.png)

**Spec sheet Mobile**

![Search_Mobile](/uploads/0fa6ea35ef7c2b7e745fb2631f7ad682/Search_Mobile.png)

<!---
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

- 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
--->

- [ ] ...

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 5.0
Mob: Update Boost Console location in mobile settings

<!---
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
--->


## 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/jscTsxloVCRPwAm4LM2E6g/Navigation-Links-Update?node-id=24%3A309&t=FHCMY2tLdWUZwjNV-1)

**Surface the 'Boost' setting above Supermind on mobile**

![Menu](/uploads/fd1aa79c08455f4861c5191c6e5245b5/Menu.png)

**Remove 'Boost Console' setting option under settings**

![Remove_Boost_Console_setting](/uploads/4a91a22cc33ec1a0f39e202f348ec88a/Remove_Boost_Console_setting.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
--->

- [ ] ...

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 2.0
Mob: 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/93c9228cbb34bd9d3e7688775cd67a63/Screen_Shot_2023-03-06_at_2.32.39_PM.png)

![Screen_Shot_2023-03-06_at_2.18.20_PM](/uploads/5e59379e37603ba868893fcdb416b1c6/Screen_Shot_2023-03-06_at_2.18.20_PM.png)

**Dark Mode Example**

![Dark_Mode_1](/uploads/3466e158a91d163822c6d77985494a80/Dark_Mode_1.png)

**Light Mode Example Replies Expanded**

![Light_Mode_1](/uploads/e8882571a92613b030b6cd631d7a1622/Light_Mode_1.png)

**Light Mode Example Comment In Replies**

![Light_Mode_2](/uploads/0f888dda2411e147d8175f1b6630e11b/Light_Mode_2.png)

**Mobile**

**Specs for Mobile**

![Mobile_Specs](/uploads/114f459e5d9f15ecd185fb1d604cf0a3/Mobile_Specs.png)

![Light_Mode_Mobile](/uploads/554d648f19d31cd43f7cd968655a1c5d/Light_Mode_Mobile.png)

**Dark Mode**

![Mobile_Share_Comments](/uploads/427edc4f3136e5c47de26c0ad4de84ba/Mobile_Share_Comments.png)

**Light Mode**

![Light_Mode_Mobile](/uploads/eab52d5a3eb227143051c16efeba2b87/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
--->

- [ ] ...

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 2.0