giseldo/neodataset huggingface dataset:
Reset the unread count when opening notifications and scroll up on refresh



## Goal

The unread notifications count should be reset when opening the notifications screen

## What needs to be done

 - [ ] Reset the unread count when fetching data from the server in the notifications screen
 - [ ] Scroll up when the list is refreshed by tapping the tab icon

## QA

- Check that the red dot disappears when opening the notifications tab
- Check that the list is scrolled up when refreshing by tapping the tab icon again

## UX/Design

-


## Personas

- Improve the UX of the notifications screen


## Experiments

none


## Acceptance Criteria

 - [ ] Reset the unread count when fetching data from the server in the notifications screen
 - [ ] Scroll up when the list is refreshed by tapping the tab icon

## Definition of Ready Checklist

- [x] Definition Of Done (DoD)
- [x] Acceptance criteria
- [x] Weighted
- [x] QA
- [x] UX/Design
- [x] Personas
- [x] Experiments

Story points: 2.0
Display in-app notifications for Superminds

## Goal

Communicate to Supermind users on both sides (fan, creator) important updates about a Supermind offer.

## What needs to be done

Display relevant notifications in the in-app notification notification dropdown / window. Notifications click through to a relevant screen.

| Event                            | Notified user | Clicks to                    | Push notification copy                                |
|----------------------------------|---------------|------------------------------|-------------------------------------------------------|
| Sender sends a Supermind offer   | Sender        | n/a                          | n/a                                                   |
| Sender sends a Supermind offer   | Recipient     | Supermind console > Inbound  | @channelName sent you a Supermind offer               |
| Receiver declines an offer       | Sender        | Supermind console > Outbound | @channelName has declined your Supermind offer        |
| Receiver accepts an offer        | Sender        | Activity post URL            | You got a Supermind reply from @channelName           |
| 24 hours before an offer expires | Recipient     | Supermind console > Inbound  | Don't forget to review @channelName's Supermind offer |
| An offer expires                 | Sender        | Supermind console > Outbound | @channelName missed your Supermind offer              |

## QA

<!---
Consideration is given to how the issue will be demoed and tested prior to being deployed
--->


## UX/Design

[Notification component (Figma)](https://www.figma.com/file/thrGepQAxmcMGB7MoEEckM/Supermind?node-id=1024%3A23254)

## 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
--->

- [ ] Supermind notifications appear view with a Supermind-specific icon.
- [ ] Supermind notifications click through to a relevant page/screen.
- [ ] Add a single supermind request screen and navigate from the notifications

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 3.0
Channel screen reseting when navigating back



### Summary

The channel screen is reloaded when navigating back from an activity screen

This only happens on the channel screen of the root navigator and it is a regression on the current develop branch


### Steps to reproduce

- Open a channel in the root navigator by searching and tapping a channel
- scroll
- Tap on a post
- navigate back
- the channel screen is reset and the scroll position is lost

### Platform information 

Both

### What is the current *bug* behavior?

Screen is reset

### What is the expected *correct* behavior?

It should return to the screen and keep the scroll position

### Relevant logs and/or screenshots

-

### Possible fixes

TBD

Story points: 2.0
Images zoomed in / cropped improperly

<!---
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

There have been complaints about wrong crop / zoom on some pictures:
- https://www.minds.com/newsfeed/1409438524943372302
- https://www.minds.com/newsfeed/1409510338369425424

### Steps to reproduce

1. Make sure you are using 4.27 version of app on android device
2. Navigate to channel of Kantrel7
3. Scroll down
4. Notice that some pictures are zoomed in (when you open the image, you can see it properly

### Platform information 

Android (Used Honor 9 for testing)

### What is the current *bug* behavior?

Images get cropped

### What is the expected *correct* behavior?

Images should show fully

### Relevant logs and/or screenshots
<details><summary>Channel of Kantrel7</summary>

![XRecorder_Edited_26082022_152150](/uploads/54816e7aa27b9615ad246cc18620d986/XRecorder_Edited_26082022_152150.mp4)

</details>

<details><summary>Channel of chicagorist</summary>

![XRecorder_26082022_162021](/uploads/4253eea0a6cb3f5687ee2ae16fe526d2/XRecorder_26082022_162021.mp4)

</details>

### Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Story points: 3.0
Account switching breaks after opening app from push notification

<!---
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

I opened app today from push notification, and I noticed later, I am not able to switch users.

### Steps to reproduce

1. Tag yourself with different account (eg lvl3 comment)
2. Open the push notification
3. Get to the feed, and try switching accounts
4. See if you are able to switch accounts

### Platform information 

Iphone, app v 4.27

### What is the current *bug* behavior?

Account switching breaks

### What is the expected *correct* behavior?

Account switching should not break

### Relevant logs and/or screenshots

<details><summary>Video of my attempt</summary>
![Video](/uploads/2155cbbf63930c4710f4cade3ea117ec/Video.mp4)
</details>

### Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Story points: 2.0
Comment Store is recycled by other posts on the feeds


### Summary

The activities components are reusing the comments store when they are recycled. This is showing the comments of the first posts where comments were opened  

### Steps to reproduce

- Open a feed
- Open the comments of many posts for a few screens
- you will start to see comments from other posts

### Platform information 

both

### What is the current *bug* behavior?

The comments store is recycled so the comments components is showing the comments of the wrong post

### What is the expected *correct* behavior?

A new store should be created

### Relevant logs and/or screenshots

-

### Possible fixes

Ensure to avoid reusing the same store when an activity component is recycled on the feed list

Story points: 2.0
Remove "Username will be released back to the public" from Delete Channel Prompt

### Summary

From https://gitlab.com/minds/front/-/issues/5417 :

Deleting your account currently does not release your username back to the public. Many users have deleted their accounts expecting to create a new account by the same username and start over. Remove "Username will be released back to the public" from Delete Account prompt until this is fixed.

User just reached out to me, that they are able to see this meessage on mobile, could we fix it to Mirror desktop?

![image](/uploads/e8ce4ccc115fccf9824e8a1b794b75f1/image.png)

Story points: 0.0
UX analysis, business logic, and technical analysis for in-app user verification

## Goal

Validate and provide implementation guidance for in-app mobile phone user verificaton

## What needs to be done

UX design and review, e2e business logic for verification flow, technical analysis, design, and technical spike.

## QA

N/A

## Acceptance Criteria

- [ ] ...

## Definition of Ready Checklist

- [x] Definition Of Done (DoD)
- [x] Acceptance criteria
- [x] Weighted
- [x] QA

Story points: 8.0
Highlights items repeated or showing more than 3



### Summary

In some cases, the highlight section of the newsfeed is showing more than 3 items

### Steps to reproduce

Seems to be happening in different scenarios but one is switching users

### Platform information 
both

### What is the current *bug* behavior?

Repeated or too many items

### What is the expected *correct* behavior?

it should show 3 items

### Relevant logs and/or screenshots

![Simulator_Screen_Shot_-_iPhone_13_-_2022-08-18_at_10.46.50](/uploads/2bcf81611ec1190ae7a513745067f904/Simulator_Screen_Shot_-_iPhone_13_-_2022-08-18_at_10.46.50.png)

### Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Story points: 3.0
[GAT] I want to filter the search section and select the filter option. After tapping on the filter option, the app gives an error message

### Summary

I want to filter the search section and select the filter option. After tapping on the filter option, the app gives an error message.

### Steps to reproduce

Launch the Minds application
Login
Tap search icon from bottom nav bar
Tap on the filter
Select any type
Observe the user gets an unexpected error message

### Platform information 

Android 12.0 12 | OnePlus 8

### What is the current *bug* behavior?

I want to filter the search section and select the filter option. After tapping on the filter option, the app gives an error message.

### What is the expected *correct* behavior?

Users can search filter without any error and the exact filter result will be visible to the users.

### 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: 2.0
[GAT] "Can't reach server showing stored data" error occurs when the user blocks an account and tries to access the account

### Summary

"Can't reach server showing stored data" error occurs when the user blocks an account and tries to access the account.

### Steps to reproduce

Pre-requisite: You're following some accounts and channels. There is a moment on the home page.
Open the AUT and sign in.
Tap on any moment.
Tap on the three dots and tap on "Block".
Tap on the account name at the top of the moment and observe

### Platform information 

Android 12.0 12 | OnePlus 9 Pro

### What is the current *bug* behavior?

Error message is displayed 

### What is the expected *correct* behavior?

No error message should display

### 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: 2.0
[GAT] User can create an empty tag under Your tags-> Manage tags

<!---
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

User can create an empty tag under Your tags-> Manage tags

### Steps to reproduce

Open the AUT and sign in.
Tap on the search tab.
Tap on Your tags
Tap on manage tags.
Tap on Add.
Tap on the + icon without entering anything.
Notice the list

### Platform information 

Android 12.0 12 | OnePlus 9 Pro

### What is the current *bug* behavior?

User can create an empty tag under Your tags-> Manage tags

### What is the expected *correct* behavior?

User should enter something in the tag

### 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: 2.0
New Moment -> Photo -> Edit -> Crash

### Summary

The app crashes when trying to Edit a photo taken during the "New Moment" creation.

### Steps to reproduce

1. Go to the Home screen.
2. Press the "New Moment" button.
3. Take a photo.
4. Press the Edit button in the top right corner of the screen.
5. The app crashes.

### Platform information 

* Minds for Android v4.26
* Motorola
* Moto G7 Power
* 720 x 1570 pixels
* Android version 10 (QPOS30.52-29-7-6)

### What is the current *bug* behavior?

The app crashes.

### What is the expected *correct* behavior?

I suppose the Edit button will allow applying some kinds of edits to the photo.

### Relevant logs and/or screenshots

None. Sorry.

### Possible fixes

None.

Story points: 3.0
New Moment -> Photo -> Download -> Crash

### Summary

The app crashes when trying to Download a photo taken during the "New Moment" creation.

### Steps to reproduce

1. Go to the Home screen.
2. Press the "New Moment" button.
3. Take a photo.
4. Press the Download button in the top right corner of the screen.
5. The app crashes.

### Platform information 

* Minds for Android v4.26
* Motorola
* Moto G7 Power
* 720 x 1570 pixels
* Android version 10 (QPOS30.52-29-7-6)

### What is the current *bug* behavior?

The app crashes.

### What is the expected *correct* behavior?

The picture taken a moment ago is saved to the device's storage.

### Relevant logs and/or screenshots

None. Sorry.

### Possible fixes

I have noticed that manually giving the app the storage access permission on the Android system level stops the app from crashing and the picture is stored on the device's storage as expected. So, it seems the app instead of checking if it has the storage permissions just tries to access it.

Story points: 2.0
H&S closes on android when uploading pictures.

### Summary

(Summarize the bug encountered concisely)

### Steps to reproduce

1. Use android device
2. Click `Help` button in settings or Menu
2. Create a new ticket through in-app browser
3. Try uploading attachments
4. See the result

### Platform information 

Android

Does not happen on iphone

### What is the current *bug* behavior?

Inapp browser crashes on upload

### What is the expected *correct* behavior?

Inapp browser should not crash on upload

### Relevant logs and/or screenshots

![XRecorder_31102022_123119](/uploads/32b9ff6d208ff3d2148cdf0ac8e7b11a/XRecorder_31102022_123119.mp4)

### Possible fixes

Debug and if no imediate fixes, replace in-app browser with external browser

Story points: 3.0
Initiate a Supermind from channel page

<!---
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 users to send a Supermind request to a channel from that person's channel page

## 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.
--->
* There are to be two modifications with respect the channel page.
* `SuperMind CTA`
  * A `SuperMind` call-to-action will appear top-right. It will remain visible whether a user is subscribed [Subscribed visitor state](https://www.figma.com/file/thrGepQAxmcMGB7MoEEckM/Supermind?node-id=457%3A13518)or [Unsubscribed visitor state](https://www.figma.com/file/thrGepQAxmcMGB7MoEEckM/Supermind?node-id=303%3A9203) to the channel being viewed.
  * The `SuperMind` button will not be visible when displaying one’s own channel.
  * **[Unit supermind from channel - prototype](https://www.figma.com/proto/thrGepQAxmcMGB7MoEEckM/Supermind?page-id=287%3A5127&node-id=303%3A9203&viewport=-9081%2C5560%2C1&scaling=min-zoom&starting-point-node-id=303%3A9203&show-proto-sidebar=1)**
* New filter option
  * A new `Type` filter option should be made available, allowing users to filter a channel feed by `SuperMind` - this will display all SuperMind content relative to the channel. [New channel filter type](https://www.figma.com/file/thrGepQAxmcMGB7MoEEckM/Supermind?node-id=455%3A12901)

## 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

- [ ] Add supermind button to channel page
- [ ] Pre-fill the composer with the channel to focus on 
- [ ] Playright tests

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 1.0
Presentation of Supermind activity posts

<!---
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
--->
- Ensure that Supermind responses are clearly indicated aesthetically in the feeds and post pages so that users know it was a paid reply


## 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.
--->
The activity post entity will be modified slightly to differentiate it from other posts.

* [Feed context design](https://www.figma.com/file/thrGepQAxmcMGB7MoEEckM/Supermind?node-id=334%3A12267)
  * Note the 2px border around the original post as well as the inclusion of the SuperMind badge top-left.
* [Entity content design](https://www.figma.com/file/thrGepQAxmcMGB7MoEEckM/Supermind?node-id=453%3A12635)
* Note the inclusion of the new `S` / `Supermind` action within the post toolbar.


## 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
--->

* [ ] Supermind label appears on a Supermind response
* [ ] Handle the case where a Supermind is reminded, displaying both Supermind label and remind label
* [ ] Outline appears on a quoted post in a Supermind response

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 2.0
Implement Supermind 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
--->
-- Build out settings screen for users to manage Supermind related settings such as minimum offer thresholds 


## 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.
--->

* [Supermind Settings Prototype](https://www.figma.com/proto/thrGepQAxmcMGB7MoEEckM/Supermind?page-id=287%3A5127&node-id=974%3A17359&viewport=-9081%2C5560%2C1&scaling=min-zoom&starting-point-node-id=974%3A17359&show-proto-sidebar=1)
* There is no ability to enable or disable this feature.
* Supermind will be available to all users.
* Supermind settings is contained within `Settings` > `Account` and offers the user the ability to define a minimum offer amount for both USD and Tokens.
* Where the user does not have a connected bank account, they will be prompted from within settings to connect their bank account, before then being able to define a minimum USD offer.
* Supermind settings will be linked also from the `Supermind console`.
* Token values less than one may not be entered.
* Cash (USD) values less than $10 may not be entered.


## 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 options for token and USD minimums in Settings using existing backend endpoint
* [ ] Default to: 1 token, 10 USD
* [ ] Prevent user from entering values lower than: 1 token, 10 USD

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 3.0