giseldo/neodataset huggingface dataset:
Cash validation failure for Supermind offer prevents token tab from being submitted

<!---
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

Cash validation failure for Supermind offer prevents token tab from being submitted. This is more of an issue than it may initially appear because if you raise your min cash amount, the default supplied is 

### Steps to reproduce

1. Make an offer to nemofin
2. In cash set the token amount to 9, check agree to terms so if the amount was enough, it would submit
3. Click token tab, try to submit - you cannot.

### Platform information 

Web

### What is the current *bug* behavior?

Cannot submit when the form visually is valid, because the cash offer is too low (even though we're on the token tab)

### What is the expected *correct* behavior?

- You should be able to submit the token page when everything on the token page is valid, even if the cash page has validation errors.
- You should be able to submit the cash page when everything on the cash page is valid, even if the token page has validation errors.
- **TO DISCUSS** Should the amounts default to the minimum for the user you have selected (as users may set custom minimums) - this made this issue much more apparent however there are UX considerations either way - we should discuss in planning and come to an agreement. If this task is brought in ad-hoc we should discuss in standup.

### Relevant logs and/or screenshots

https://streamable.com/6fx5xw

### Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Story points: 3.0
Update Engagement Reward Documentation

<!---
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

The end-user documentation for the engagement rewards is currently fragmented and requires reviewing. 


## What needs to be done

Based upon the following official Minds articles and posts, I am recommending that the existing "increasing the power of voting" blog article is amended with the information that is currently provided within the following posts, as well as the blog article being updated when any further applicable changes are implemented and if appropriate, any relevant support platform based articles are also updated (ie. the image that is displayed within the "how to earn daily token rewards" support platform article).

<b>Reference:</b><br>
* Increasing The Power of Voting: An Experiment In Community-Powered Curation For Engagement Rewards (Minds Blog Article)<br>
https://www.minds.com/minds/blog/increasing-the-power-of-voting-an-experiment-in-community-po-1285662908121878541

* Temporary Engagement Reward Suspension For Group And Paywalled Based Posts (Minds Support Post)<br>
https://www.minds.com/newsfeed/1345509971835490310

* Downvotes Will No Longer Be Part Of The Engagement Score Calculation (Minds Support Post)<br>
https://www.minds.com/newsfeed/1375939325258108937

* How To Earn Daily Token Rewards (Minds Support Platform Article)<br>
https://support.minds.com/hc/articles/4402704245268-how-to-earn-daily-token-rewards


## 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
--->

- [ ] ...

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 3.0
Prompt users to connect a bank account when accepting cash Supermind offer

## Goal

As Minds, I want to send cash Supermind offers to creators, regardless of whether or not they've previously connected a bank account.

As a user, I want to accept a cash Supermind offer and collect the offer.

## What needs to be done

Handle cash Supermind offer charges when the recipient has not already connected a bank account. https://gitlab.com/minds/minds/-/issues/3409

Add a step into the Supermind reply flow when the offer is for cash and the recipient has not previously connected to a bank account.

1. View Supermind console
2. Click accept on a cash offer
3. `New`: Prompt to connect a bank account
4. Compose the reply

## QA

<!---
Consideration is given to how the issue will be demoed and tested prior to being deployed
--->


## UX/Design

[Figma prototype](https://www.figma.com/proto/thrGepQAxmcMGB7MoEEckM/Supermind?page-id=287%3A5127&node-id=2381%3A27571&viewport=470%2C192%2C0.03&scaling=min-zoom&starting-point-node-id=287%3A5128&show-proto-sidebar=1&hide-ui=1)

![image](/uploads/56e214ce1350c7c97e722c3145d3eb82/image.png)

## Personas

Creators

## Experiments

n/a

## Acceptance Criteria

- [ ] Feature flag to be enabled from sender side
- [ ] Finish implementation of https://gitlab.com/minds/engine/-/merge_requests/1147/diffs
- [ ] Users can send cash Supermind offers to anyone, regardless of whether or not they've previously connected a bank account.
- [ ] Given a recipient has not previously connected a bank account, and they've received a cash Supermind offer, when they click to accept the offer, then they are prompted to connect their bank account via toast error message
- [ ] Given the stripe connect account has been connected, then the recipient can continue to compose a Supermind reply.

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 5.0
Prompt users to oauth with Twitter when Supermind offer requires it

## Goal

As a user, I want to connect Minds with Twitter oauth so that I can satisfy requirements of Twitter Supermind offers.

## What needs to be done

Add a step into the Supermind reply flow when the offer requires Twitter oauth and the target user has not previously oauthed with Twitter.

1. View Supermind console
2. Click accept
3. `New`: Prompt to oauth with Twitter
4. Compose the reply
5. [Post the reply to Minds + Twitter](https://gitlab.com/minds/minds/-/issues/3476)

## QA

<!---
Consideration is given to how the issue will be demoed and tested prior to being deployed
--->


## UX/Design

[Figma prototype](https://www.figma.com/proto/thrGepQAxmcMGB7MoEEckM/Supermind?page-id=287%3A5127&node-id=2381%3A27571&viewport=470%2C192%2C0.03&scaling=min-zoom&starting-point-node-id=287%3A5128&show-proto-sidebar=1&hide-ui=1)

![image](/uploads/94fd07557c26deab8d832b68a1784ec4/image.png)

## Personas

Creators

## Experiments

n/a

## Acceptance Criteria

- [ ] Given a recipient has not previously oauthed with Twitter, and they've received a Supermind offer that requires Twitter repost, when they click to accept the offer, then they are prompted to oauth with Twitter.
- [ ] Given the prompt has been completed, then the recipient can continue to compose a Supermind reply.
## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 5.0
Multi-image quote posting - can't open images in modal

<!---
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

Quote posts with multiple images don't allow the user to view the images in modals

### Steps to reproduce

- View [a quote post with multiple images](https://www.minds.com/newsfeed/1424507434050785297)
- Click an image

### Platform information 

- MacOS + Chrome

### What is the current *bug* behavior?

- Nothing happens

### What is the expected *correct* behavior?

- The clicked image opens in a modal view

### Relevant logs and/or screenshots

![image](/uploads/1c7feb0056a7f3711be6ef7a150ae216/image.png)

### Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Story points: 3.0
Add recipient's username in the body of Supermind emails

## Goal

Some users have reported that they have multiple Minds accounts, and that Supermind offers in their email are not communicating which account received the offer.

## What needs to be done

Add the recipient's username to the body of Supermind emails, inserting a new paragraph line above the main body of the email.

## QA

<!---
Consideration is given to how the issue will be demoed and tested prior to being deployed
--->


## UX/Design

![image](/uploads/59b55a289a29af7f88d7d81c0610cd17/image.png)

## Personas

Creators 

## Experiments

n/a

## Acceptance Criteria

- [ ] The recipient's username appears in the body of all Supermind emails.

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 2.0
Add "7 days to reply" language to the bottom of the offer modal: Mobile

## Goal

Communicate the functionality of Supermind to users as they engage with the product.

## What needs to be done

Display a message at the bottom of the offer screen that communicates:

> The recipient will have up to 7 days to reply. You may cancel the offer at anytime

## QA

<!---
Consideration is given to how the issue will be demoed and tested prior to being deployed
--->


## UX/Design

![image](/uploads/63be1d341db3207916a0ab007d76672c/image.png)

## Personas

<!---
Who does this user impact and why (optional)
--->


## Experiments

n/a

## Acceptance Criteria

- [ ] The message appears at the bottom of the offer screen

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 1.0
Keyboard overlays Supermind onboarding modal

### Summary

The Supermind onboarding modal can be obstructed by the keyboard.

### Steps to reproduce

- ???

### Platform information 

Android

### What is the current *bug* behavior?

- The Supermind onboarding modal appears
- The keyboard stays on top of it

### What is the expected *correct* behavior?

- The Supermind onboarding modal appears
- The keyboard is closed

### Relevant logs and/or screenshots

![image](/uploads/8d4587d73f4449ef319e684621667636/image.png)

### Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Story points: 1.0
Can't reply to Supermind on mobile

### Summary

I get a confusing toast message when replying to Martin's supermind offer.

### Steps to reproduce

- Tap "Accept" in the Supermind console for a text reply Supermind (e.g. https://www.minds.com/newsfeed/1424486167453110275)
- Complete a response and add an image
- Post the response

### Platform information 

- iOS 16 + latest TestFlight build

### What is the current *bug* behavior?

A toast message is displayed:

> The Supermind request is not in the correct status to perform the requested action

### What is the expected *correct* behavior?

(What you should see instead)

### Relevant logs and/or screenshots

![IMG_4848](/uploads/3f281a5fb0bcc6e09e2e569130a0564d/IMG_4848.PNG)

### Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Story points: 1.0
Resolve restricted account situation on Stripe

<!---
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
--->

Our current Stripe Connect system is very out of date, and it's hard to keep up with the requirements. We need to investigate moving to Express or updating the current system. Most of our biggest creators have restricted accounts. :/


## What needs to be done

<!---
Clearly detail what needs to be done to achieve the goal set out above
--->

Either build a flow for them to update or move to stripe express. Ideally creators can use their existing stripe accounts so that Minds doesn't have a single point of failure. 

**Helpful link**: https://stripe.com/docs/api/account_links/create

## 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.
--->
[minds-3455-restricted-fix](https://growthbook.minds.com/features/minds-3455-restricted-fix)

## Acceptance Criteria

<!--
Everyone should be able to understand what is expected to be delivered
--->

- [ ] PoC implementation
- [ ] Future tasks built out

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 3.0
Minds logo is misaligned on email template in Protonmail

### Summary

The Minds logo in our updated email template gets misaligned when the email template is viewed in Protonmail. (Maybe others.)

### Steps to reproduce

- Sign up for a Minds account, using an email address connected to Protonmail.
- Open up one of the initial onboarding emails (e.g. email verification).
- Click the `Load` button in Protonmail to load remote content (images).

### Platform information 

- MacOS + Chrome
- Windows + Brave

### What is the current *bug* behavior?

- The Minds logo is loaded
- The logo is LEFT-aligned on the page

### What is the expected *correct* behavior?

- The Minds logo is loaded
- The logo is CENTER-aligned on the page

### Relevant logs and/or screenshots

![image](/uploads/4f1bb7f48b5361e8304cb3f2db39e9ba/image.png)

### Possible fixes

I've worked around this in versions of the template I use in SendGrid. I add this CSS to the `<td>` tag that contains the image:

>  `display: flex; justify-content: center;`

Story points: 1.0
Add Supermind badge to Supermind offer posts

## Goal

Differentiate Supermind offer posts to indicate they're Superminds and add context that reduces confusion.

## What needs to be done

Add the `Supermind` badge to Supermind offer posts

----

Currently, a Supermind REPLY is differentiated by:

- A `Supermind` badge appears in the top-right corner
- The quoted post has a colored outline

For Supermind OFFER posts, we want:

- A `Supermind` badge appears in the top-right corner
- NO coloration of the quoted post (if there even is one)

## QA

<!---
Consideration is given to how the issue will be demoed and tested prior to being deployed
--->


## UX/Design

![image](/uploads/993176fd55c175ebf1af12a92c68afac/image.png)

## Personas

Fans

## Experiments

n/a

## Acceptance Criteria

- [ ] Given a post has a related Supermind offer, when the post is displayed, then a `Supermind` badge appears in the top-right corner of the post (same position as the same badge on Supermind replies)

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 1.0
Can't remind posts on Canary - Desktop

<!---
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 trying to remind posts in Canary on desktop, I am unable to because I get [object Object]

### Steps to reproduce

1. Enter canary
2. Try reminding something (shouldn't matter if from feed or permalink page)
3. See you get object object error

### Platform information 

Windows 10, Brave and Chrome

### What is the current *bug* behavior?

Impossible to remind posts, because I get object Object error

### What is the expected *correct* behavior?

Reminding posts should be possible

### 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
Supermind console freezes app

### Summary

Navigating to the Supermind console crashes the app for Jack.

### Steps to reproduce

- Launch the app
- Log in as `@supermind1`
- Tap the `Supermind` option in the main navigation menu

### Platform information 

iphone 11 iOS 15.6.1

### What is the current *bug* behavior?

The app freezes and screen goes white.

### What is the expected *correct* behavior?

The Supermind console appears and displays Supermind offers.

### Relevant logs and/or screenshots

![RPReplay_Final1664572893](/uploads/4803a24fc36a7778b7be06c0b58656f9/RPReplay_Final1664572893.MP4)

### Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Story points: 1.0
When clearing/closing Supermind offer screen, the composer remains

### Summary

Some debatably confusing behavior when clicking a Supermind button and then dismissing the Supermind offer screen.

### Steps to reproduce

- Tap the Supermind button on any post
- The Supermind offer screen appears
- Tap the `Clear` button to close the Supermind offer screen

### Platform information 

- iOS app

### What is the current *bug* behavior?

- The Supermind offer screen closes
- The composer remains, in a quote post state

### What is the expected *correct* behavior?

- Given the Supermind offer screen is initiated from a Supermind button that's NOT the composer,
- when the user taps the `Clear` button,
- then the Supermind offer screen closes
- and the user returns to the screen where they started

### Relevant logs and/or screenshots

![RPReplay_Final1664573036](/uploads/137360406106c6ac67101f2eaa9c61df/RPReplay_Final1664573036.mov)

### Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Story points: 2.0
Supermind offer screen shudders when opened

### Summary

When opening the Supermind offer / payment screen, the screen appears to shudder / flutter briefly.

### Steps to reproduce

Tap the Supermind button on any activity post.

### Platform information 

- iOS app

### What is the current *bug* behavior?

The Supermind offer screen appears, and shudders slightly.

### What is the expected *correct* behavior?

The supermind offer screen appears smoothly.

### Relevant logs and/or screenshots

![Studder_issue](/uploads/51a10b215a7d5d1a5a612d8494eed6e1/Studder_issue.mov)

### Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Story points: 3.0
Supermind badge appears twice on Supermind replies

### Summary

On Supermind replies, the Supermind badge is appearing twice.

### Steps to reproduce

View a Supermind reply in the mobile app.

### Platform information 

- iOS app
- Android app (?)

### What is the current *bug* behavior?

The Supermind badge appears on both the initial offer message and the reply message.

### What is the expected *correct* behavior?

Supermind label should appear only on the Supermind reply.

### Relevant logs and/or screenshots

![image](/uploads/52b63fa020645dce47ff628395cbb9b9/image.png)

### Possible fixes

![image](/uploads/5638815febe06979bb76778365396a63/image.png)

Story points: 1.0
Improve toast message when an invalid Supermind reply is posted

## Goal

Clearly communicate to a Supermind replier that their post doesn't meet the requirements of the offer.

![image](/uploads/88894c645ddfe9406b330f767250e681/image.png)

## What needs to be done

- Given a Supermind reply does not meet the requirements of the offer,
- when the replier presses the `Post` button,
- throw the appropriate toast message (outlined below),
- and don't post the message.

| Requirement | Message                                             |
|-------------|-----------------------------------------------------|
| Image       | This Supermind offer requires an image in the reply |
| Video       | This Supermind offer requires a video in the reply  |

## QA

<!---
Consideration is given to how the issue will be demoed and tested prior to being deployed
--->


## UX/Design

Use standard toast messages.

## Personas

Creators

## Experiments

n/a

## Acceptance Criteria

- [ ] The appropriate toast message is thrown to indicate the Supermind reply is invalid with regards to the requirements of the offer

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 1.0
After adding credit card info, the Add New Card modal appears again

### Summary

After adding credit card info, the Add New Card modal appears again.

### Steps to reproduce

- Start a Supermind offer
- From the Cash tab, under `Payment Method`, select `Add new card`
- The `Add New card` modal appears
- Add details to add a new card
- Click `Save Card`

### Platform information 

- MacOS + Chrome

### What is the current *bug* behavior?

- The card details are saved
- The modal appears again in an empty state

### What is the expected *correct* behavior?

- The card details are saved
- The `Add New Card` modal closes
- The user sees the Supermind payment modal with the newly-added card already selected

### Relevant logs and/or screenshots

![image](/uploads/e8d9ea61141a54c0935fcb10ffb3ec52/image.png)

### Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Story points: 3.0