giseldo/neodataset huggingface dataset:
UX&D: Update boost console

## Goal

Specify necessary updates to the [Boost Console](https://www.minds.com/boost/console/newsfeed/history) to accommodate changes associated with boost bidding.

---

- As a core Minds user, I want to know the status of my open boost orders (waiting approval, approved, running, completed)
- As a core Minds user, I want to know the performance of my past boost orders
- As a core Minds user, I want to access receipts for open and past boost orders

## Old Designs

- [Old redesigns](https://www.figma.com/file/a6D0Zvdvsf4HzZdlyviFNt/Boost-Console?t=We4qGGHVzPKEdPV6-0)
- [Current boost console](https://www.minds.com/boost/console/newsfeed/history)

## Personas

A core Minds user.

## UX Design

- Updated designs (made copy changes from post-> feed. Channel -> sidebar). Added cancel action for pending boost requests. 
- https://www.figma.com/file/W2xIag64EdbWUlGAQOpVHE/Boost-Update?node-id=485%3A18241

**Web Post (Feed) Boost**

![All](/uploads/222470c4e6ed7cac386f6608606f9f9a/All.png)

![Pending](/uploads/b2a27cfd1959b6676ba6d461707cb141/Pending.png)

![Approved](/uploads/2dd9834f9a73b424dcf5156bb3c60951/Approved.png)

![Completed](/uploads/9a6b24988f40b8089b0571776cc299de/Completed.png)

![Rejected](/uploads/6d8df52f7e9441fae142b549b5019aa1/Rejected.png)

**Web Channel (Sidebar) Boost**

![All](/uploads/6ffd0b6a56a325e8e7effb7e65c95cbb/All.png)

![Pending](/uploads/7c8a1dcc5e2992a47675e47b26973ed2/Pending.png)

![Approved](/uploads/6bbe5ccea195e48fc4e63f37973ef7d2/Approved.png)

![Completed](/uploads/c44dc1621e1fa38dd3acfedba5bf7664/Completed.png)

![Rejected](/uploads/7268dbbb74191165b613357a8ab61cb5/Rejected.png)

**Mobile Post (Feed) Boost**

![All](/uploads/94aee24bb0f42e04ffef67a40e8bb25b/All.png)

![Pending](/uploads/39324530ec473eced017ad5eec141b50/Pending.png)

![Approved](/uploads/71ad447b772393f6ce84685341c0f98e/Approved.png)

![Completed](/uploads/e36011907846e7825e8ab4132eea1f68/Completed.png)

![Rejected](/uploads/7f5f68d04b4e5f75ad57e87caf21554d/Rejected.png)

**Mobile Channel (Sidebar) Boost**

![All](/uploads/f47d1aad20c3099f52f2bae088765f01/All.png)

![Pending](/uploads/2f2d7268a7a9466c44cc6bfab7c2d79d/Pending.png)

![Approved](/uploads/a08d7c50d5783caa4eaf899ca7949fda/Approved.png)

![Completed](/uploads/8269f502cd3c7d7b69b90af118105a78/Completed.png)

![Rejected](/uploads/0c717fd8081921733b050c14a6381765/Rejected.png)

## Acceptance Criteria

<!--
Everyone should be able to understand what is expected to be delivered
--->

* [x] Web UX & visuals for the user story (described above)
* [x] Mobile UX & visuals for the user story
* [x] Developer feedback on feasibility
* [x] User feedback on usability

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 8.0
Update language in Supermind onboarding modals to remove cash references

## Goal

Remove references to cash in the Supermind onboarding modals, since sending cash is not currently supported in the iOS app.

## What needs to be done

Update both the (1) fan onboarding and (2) creator onboarding modals with the following copy.

#### Fan onboarding
- Headline: `Get replies from your favorite creators by sending them token offers.`
- Set an offer amount: `Send an offer of tokens. The creator earns the offer amount when they reply.`

#### Creator onboarding
- How to earn: `Fans send offers, which you earn by simply replying. Minds collects just a 10% platform fee (vs. 30% fees on other platforms), and our payment processor charges a small fee per transaction. See terms & conditions.`

## QA

<!---
Consideration is given to how the issue will be demoed and tested prior to being deployed
--->


## UX/Design

![Consumer_Info__Mobile_-_iOS_](/uploads/f42b62a332ee381879754c755704e6b1/Consumer_Info__Mobile_-_iOS_.png)

![Creator_Info__Mobile_-_iOS___1_](/uploads/c7f9c379177f0ccb62c2ffa60bd45c4a/Creator_Info__Mobile_-_iOS___1_.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: 3.0
Add refund policy checkbox to Boost purchase modal

## Goal

Avoid users making cash purchases without knowing, and get agreement on refund policy.

## What needs to be done

Add a checkbox to the cash tab of the boost modal that asks users to agree to the refund policy.

## QA

<!---
Consideration is given to how the issue will be demoed and tested prior to being deployed
--->


## UX/Design

Add a checkbox to the bottom of the CASH tab in the boost modal with the following text.

> I understand this cash transaction is non-refundable once the boost is approved

![image](/uploads/30a2ea04af70559cb64d0a4b1ec4b00c/image.png)

![image](/uploads/581f59045c635d79bcab0eba7924393a/image.png)


## Personas

<!---
Who does this user impact and why (optional)
--->


## Experiments

n/a

## Acceptance Criteria

- [ ] Given the user is on the CASH tab of the boost modal, a checkbox appears with the message spec'd above
- [ ] While the checkbox is disabled, the `Boost Post` button is disabled
- [ ] The checkbox is disabled by default
- [ ] Fix E2E tests that this breaks
- [ ] Unit test

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 2.0
Uniqueness verification rollout

## Goal

1. Onboard new & active users into the uniqueness verification flow
2. Don't disrupt rewards earnings for active users

## What needs to be done

Design UX & visual solutions for prompting users into new mobile app verification flow. Replace existing UIs that verify users with phone numbers.

### User Flow

Note: Videos were recorded with old copy. Refer to Figma + screenshots below for final copy.

![Web to Mobile Handoff](/uploads/b9f3460f9ff0ecd6b19f01d6f2c5ff0b/Screen_Recording_2022-12-06_at_2.22.03_PM.mov)

![Mobile Verification](/uploads/18389b2e200fe4e175d5b758701fc0c1/Screen_Recording_2022-12-06_at_2.24.18_PM.mov)

[Figma Mockups](https://www.figma.com/file/buCViQPMNyQUNCdtDYUTbL/In-App-User-Verification?node-id=308%3A1321&t=zMZwxyNxZt06WdFy-1)

### Screens

![image](/uploads/4430d5d85c03a7c58f52fd29bba83a4a/image.png)

![image](/uploads/908ed7141b83d6fd8b24851fe832a80e/image.png)

![image](/uploads/cf05f4b36317cbfa6af251491f8aa5a2/image.png)

- [ ] Onboard users who have already verified via phone number
  - [x] In-feed notice?
  - [ ] Email?
  - [ ] In-app notification?
- [x] New user onboarding steps
- [x] [Join rewards flow in the Wallet](https://www.minds.com/wallet/tokens/rewards)

![image](/uploads/519ae9d69e682b1f3e7a6caf80add9a2/image.png)

![image](/uploads/a281723769d3982838bc509c696595f1/image.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: 5.0
UX&D: Clarify expectations with Twitter connection for Supermind

## Goal

As a user responding to a Supermind, I want to know why Minds is requesting permission to post on my behalf and know that nothing is being posted just by connecting w/ Twitter oauth.

As a user responding to a Supermind, I want to visualize what will be posted to Twitter before agreeing to it.

## What needs to be done

Spec improvements to the UX of flows related to posting Superminds to Twitter to address the user stories above.

- Flow 1: Connecting to Twitter oauth before responding to a Supermind offer that requires Twitter repost. (Happens once for a user.)
- Flow 2: Reposting a Supermind respond to Twitter. (Can happen multiple times for a user.)

## Personas

Creators

## UX Design

**Flow 1**

![Twitter_Permission_Explanation](/uploads/a27a88a84a6c869b97fe1eec5e48ea70/Twitter_Permission_Explanation.png)
![Mobile_Supermind_-_Accept_Confirm](/uploads/9b0a3fcbc5a418914030fbc5c86a7042/Mobile_Supermind_-_Accept_Confirm.png)


**Flow 2**

Web

![Updated_Creator_View_Reply_Confirmation__Twitter_Required_](/uploads/61b292255eb0f48980327ac0b849f83b/Updated_Creator_View_Reply_Confirmation__Twitter_Required_.png)

Mobile

![Updated_Creator_View_Reply_Confirmation_Mobile__Twitter_Required_](/uploads/3ed96f5aec89c76dfa83152dd04d5f19/Updated_Creator_View_Reply_Confirmation_Mobile__Twitter_Required_.png)

## Acceptance Criteria

* [x] Web UX & visuals for the user story (described above)
* [x] Mobile UX & visuals for the user story
* [x] Developer feedback on feasibility
* [ ] User feedback on usability

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 5.0
Deep-link to composer

## Goal

As Minds staff, I want to run a marketing campaign with registered users to drive conversations on Minds.

## What needs to be done

Create a mechanism to navigate a logged-in user to the Newsfeed with the composer already opened, and focused. The link may or may not contain text (e.g. a hashtag) to be prefilled in the composer body.

![image](/uploads/2b640d02888053e5fdd512a836d00c94/image.png)

## Personas

- Minds marketing
- Active users

## Acceptance Criteria

- [ ] Web UX & visuals for the user story (described above)
- [ ] Mobile UX & visuals for the user story
- [ ] Developer feedback on feasibility
- [ ] User feedback on usability

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 3.0
Change Supermind cash offer minimum to $1

<!---
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

Currently the Supermind cash offer minimum is $10. We should change that to $1


## What needs to be done

<!---
Clearly detail what needs to be done to achieve the goal set out above
--->

Change minimum to $1


## QA

<!---
Consideration is given to how the issue will be demoed and tested prior to being deployed
--->
Price is lowered to $1 and accepted on backend too.

## UX/Design

<!---
Sufficient wireframes have been presented and understood by the development team. Full mockups are not required and re-usable components are encouraged.
--->

None


## 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.
--->
N/A

## Acceptance Criteria

<!--
Everyone should be able to understand what is expected to be delivered
--->

- [ ] Default price is lowered to $1 for a cash Supermind

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 1.0
Loading indicators not displayed while media is uploading

<!---
Please read this!

Before opening a new issue, make sure to search for keywords in the issues
filtered by the "T - Bug" label and verify the issue you're about to submit isn't a duplicate.
--->

### Summary

Loading indicators do not appear on images or videos while uploading in the composer. The `Post` button is grayed out and inactive, but it there is not indicator to the user to explain why.

### Steps to reproduce

- Launch the composer from the Newsfeed
- Upload an image or video

### Platform information 

- MacOS + Chrome

### What is the current *bug* behavior?

- The media uploads
- No loading indicator appears while loading

### What is the expected *correct* behavior?

- The media uploads
- A loading indicator appears while loading

### Relevant logs and/or screenshots

![image](/uploads/e3474f1e5b9dacc8ab25df5bcbe67fdb/image.png)

### Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Story points: 3.0
Twitter Sync broken

<!---
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

Investigate twitter sync - big channels have no posts since around 15th of November

### Steps to reproduce

Check large channels

### Platform information 

Runner

### What is the current *bug* behavior?

Posts aren't syncing

### What is the expected *correct* behavior?

Posts should sync.

### 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 button on own posts should not pre-populate own channel name

### Summary

When clicking a Supermind button on your own post, the Supermind dialog appears and pre-populates the `Target` field with your own channel name.

### Steps to reproduce

- Navigate to an activity post you own
- CLick the Supermind button on the activity post (large button, or activity bar button)

### Platform information 

- Web

### What is the current *bug* behavior?

- The Supermind screen pre-populates my own channel name in the `Target` field

### What is the expected *correct* behavior?

- The `Target` field should be left blank when clicking Supermind buttons from my own posts

### Relevant logs and/or screenshots

![image](/uploads/65a14e8254fdf251a46a9786d3218f44/image.png)

![image](/uploads/be72fc1c1fffa130f90c697b0f830bd6/image.png)

### Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Story points: 2.0
Add "subscribes to Y" columns to contacts in SendGrid

<!---
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 marketing team to email subscribers of popular Minds channels to, for example, share Superminds the popular channels have replied to.

## What needs to be done

Add columns to SendGrid contacts list for:

- Subscribes to `ottman`
- Subscribes to `IanCrossland`
- Subscribes to `timcast`
- Subscribes to `zubymusic`
- Subscribes to `klara_sjo`
- Subscribes to `Aragmar`

In SendGrid, we can build segments with these columns.

## QA

<!---
Consideration is given to how the issue will be demoed and tested prior to being deployed
--->


## UX/Design

n/a

## Personas

Minds staff

## Experiments

n/a

## Acceptance Criteria

- [ ] In SendGrid, Minds is able to create contact segments that reach specifically active users who subscribe to the above popular channels.

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 3.0
Resource issues with K8ssandra causing high latency

<!---
Please read this!

A Superhero should only be declared for critical site outages or issues. Please read https://developers.minds.com/docs/handbook/how-we-work/superhero before creating an issue.

Issues created using this template automatically page on call developers.

The Superhero board can be found at https://gitlab.com/groups/minds/-/boards/1388364?&label_name[]=Type%3A%3ASuperhero.
--->

### Is minds.com down?

Partially

### What is the issue?

High DB Latency, very slow performance.

### What username are you logged in with?

Any

### Console logs

![image](/uploads/3b8c22217e56b167ba5dd7c4f7a7537f/image.png)

Story points: 2.0
No rewards payout 2022-11-10

<!---
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

Missing rewards payout for 2022-11-10

### Steps to reproduce

See no rewards were paid out.

### Platform information 

Platform agnostic.

### What is the current *bug* behavior?

No rewards paid out.

### What is the expected *correct* behavior?

Should be paid out at the earliest possible time.

### Relevant logs and/or screenshots

![image](/uploads/dc69d08f3eefa5df12ac7ca83354c5f9/image.png)

### Possible fixes

Probably need to verify the job didn't run, then re-run.

Story points: 0.0
Remove copyright text from Minds emails

<!---
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.
--->


# Bounce back to 2023

### Summary

Email Template has year 2021 in the footer

### Steps to reproduce

1. Trigger an official email from minds (eg, superminds one)
2. Notice that year in footer is 2021

### Platform information 

not relevant

### What is the current *bug* behavior?

Year 2021 in footer, not 2023

### What is the expected *correct* behavior?

Remove the copyright from the emails footer

### 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
Display Supermind Replies with Offers

<!---
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

(1) More clearly indicate that a Supermind offer is targeted at an individual, and (2) clearly connect Supermind offer posts with their related replies.

## What needs to be done

### In feeds

- Update the display of PENDING Supermind offers to indicate the intended target.
- Update the display of ACCEPTED Supermind offers to include the reply below the offer.

### On single entity post pages

- Update the display of PENDING Supermind offers to indicate the intended target.
- Update the display of ACCEPTED Supermind offers to include the reply below the offer.

## QA

<!---
Consideration is given to how the issue will be demoed and tested prior to being deployed
--->


## UX/Design

[Figma](https://www.figma.com/file/thrGepQAxmcMGB7MoEEckM/Supermind-%5B*%5D?node-id=2584%3A29348)

![Supermind_Offer__Text_Post____Pending_Reply](/uploads/6e0bb9d313667de19335ff60a4e5e39a/Supermind_Offer__Text_Post____Pending_Reply.png)
![Supermind_Offer__Quote_Post____Pending_Reply](/uploads/e3a14f1d53483319c920b6821143c8b0/Supermind_Offer__Quote_Post____Pending_Reply.png)
![Supermind Text Reply](/uploads/e8b3e0e7eae8272aa18ad78028ac6cef/Reply.png)
![Supermind Quote Reply](/uploads/585dc1e8bdc1d4c6126e8b9275ff54ba/Reply.png)

## Personas

Core Minds users

## Experiments

n/a

## Acceptance Criteria

<!--
Everyone should be able to understand what is expected to be delivered
--->

- [ ] Backend to hydrate the context of the supermind request
- [ ] Frontend to display "Supermind to X" for supermind requests
- [ ] Frontend to have a 'View supermind" link if a supermind has been replied to

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 3.0
Navigate user to create account, when trying to create supermind from logged out state

<!---
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 user does not already have a Minds account, and tries creating a Supermind at a creator, they won't be able to.
- For token, they will not be able to create a post
- For cash, tehy will not be able to add the card successfully

We should fix that, and redirect user to a registration flow

### Steps to reproduce

1. Go to minds.com/channel in incognito
2. try creating a supermind offer for the channel
3. see that it't not possible, but also it's not clear why

### Platform information 

desktop

### What is the current *bug* behavior?

It's possible to attempt creating supermind, and no proper error is thrown

### What is the expected *correct* behavior?

User should be prompted with the auth modal when pressing supermind button in a logged out state

### 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