giseldo/neodataset huggingface dataset:
Bug: Supermind reply with media only acts as a remind

### Summary

Responding to a Supermind offer with an image or video -- and no text -- does not successfully generate a Supermind offer. Instead, it simply re-minds the Supermind offer.

### Steps to reproduce

- Receive a Supermind offer
- Accept the the Supermind offer and reply with a piece of media, but no text
- Post the reply

### Platform information 

- Web

### What is the current *bug* behavior?

- The Supermind offer is re-minded
- The Supermind reply is lost

### What is the expected *correct* behavior?

- The Supermind reply is posted with the uploaded media
- See https://gitlab.com/minds/engine/-/blob/master/Entities/Activity.php#L1057. Add in check for attachments.

### Relevant logs and/or screenshots

![image](/uploads/b29f2ab757a7eb72c926ee0f999c60f6/image.png)

https://www.minds.com/superminds2/

### Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Story points: 1.0
Create global Superminds feeds

<!---
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) Easily audit live Superminds activity on the site
(2) Elevate Superminds activity and make it more discoverable

## What needs to be done

Create a global Superminds feed that collects all Superminds posts.

Sort reverse-chronologically.

Add as a new tab to Discovery.

## 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
--->

- [ ] A new tab added to Discovery for "Superminds."
- [ ] The new tab displays a feed of all Superminds posts (offers and replies).
- [ ] The posts are sorted in reverse chrono order.
- [ ] Add a feature flag
- [ ] Ensure you do not see blocked users in this feed

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 5.0
Send bulk Supermind offers to community for launch

## Goal

- Teach active Minds users about Supermind by sending them a sample Supermind to respond to.
- Enable Minds to incentivize content creation from large groups of users.

## What needs to be done

Build a mechanism that enables us to create Supermind offer campaigns that send links to all (or some) users. When a user clicks the link, a Supermind offer is generated for them. They can then respond to the Supermind offer via the normal Supermind inbound console flow.

This is a rough diagram of how it might work.

![image](/uploads/051010be73a8d60a2d74431006f0d807/image.png)

- Target list of users
- Activity post to be the root of the Supermind offer
- Value of the Supermind offer
- Status of the campaign (active, closed, ...)

Some prompts include:

- Introduce yourself :) Why are you on Minds? (Video reply)
- Rant about something crazy going on in the world right now. (Video reply)
- Take a selfie of where you are right now now matter how weird. (Photo reply)
- Introduce yourself :) Why are you on Minds? (Text reply)

## QA

<!---
Consideration is given to how the issue will be demoed and tested prior to being deployed
--->


## UX/Design

[supermind_boffer_launch.html](/uploads/357e8a229f2aca9f4f1931dd98d80bbe/supermind_boffer_launch.html)

## Personas

Core Minds users

## Experiments

n/a

## Acceptance Criteria

<!--
Everyone should be able to understand what is expected to be delivered
--->

- [x] Generate the email template (see: UX/Design above)
- [x] Email template should use utm codes (`?utm_source=minds&utm_medium=email&utm_campaign=supermind_boffer_launch`)
- [ ] Use the email campaigns hooks system
- [ ] Generate a supermind request when the link has been clicked

## 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: 5.0
Link previews stretch

<!---
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

After adding link to a post, the preview goes down, and it's necessary to scroll to see it.

<details><summary>Click to see images</summary>

![image](/uploads/2a9be5fc355d2aad515419f58d27e630/image.png)

After scrolling down:

![image](/uploads/12b2f58b0de58c80c8def3a41aa09c15/image.png)

</details>

### Steps to reproduce

1. Open composer
2. write some text
3. paste a link
4. see that the preview behaves strange

### Platform information 

Win10, Brave and Chrome, Canary

### What is the current *bug* behavior?

Link previews in composer show incorrectly with spacing

### What is the expected *correct* behavior?

No additional spacing in composer

### 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
Confirm price & authorization after pressing post, before creating Supermind offer

## Goal

Clearly communicate to a use creating a Supermind offer the amount of their offer before they commit to authorizing the charge, in order to avoid mistakes.

## What needs to be done

* [ ] On composer, when pressing Post, ensure there is a confirm modal outlining price and authorization on card

## QA

<!---
Consideration is given to how the issue will be demoed and tested prior to being deployed
--->


## UX/Design

- [Figma mock](https://www.figma.com/file/thrGepQAxmcMGB7MoEEckM/Supermind?node-id=1562%3A19944)

## 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

- [ ] On composer, when pressing Post, ensure there is a confirm modal outlining price and authorization on card
- [ ] User must accept terms before the "Confirm" button is active
- [ ] Playright test

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 3.0
Supermind creator referral flow

## Goal

Map user journeys to support the user story described below, and identify changes we want to make (e.g. to channel pages, onboarding flow, new user experience, etc.) to better enable the use case.

---

As a creator, I want to send fans from other platforms to sign up on Minds, in order to generate more Supermind offers for me.

- e.g. I have an audience on YouTube, and I want to send them to Minds to send me Supermind requests to [answer questions/fulfill art requests/record videos/get replies].

## What needs to be done

- Where will creators direct users to? Channel pages? Do we need to make changes to better satisfy the user story?
- Assuming users who are directed there are not already Minds users, what does the onboarding flow look like?

## QA

<!---
Consideration is given to how the issue will be demoed and tested prior to being deployed
--->


## UX/Design

[Referral flow map](https://www.figma.com/file/7rIyYDT1235O2pPrEBvieZ/SM-Referrals?node-id=0%3A1)

[Figma basic mockups](https://www.figma.com/file/NfZCO1DzPnw4YTzVKOu8O7/Referrals?node-id=21%3A2995) - in progress


## 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
--->

- [x] Map out the referral user flow for both creator and fans for Supermind requests
- [x] Map out edge cases for users who are new to Minds
- [x] Understand the incentive and reasoning for someone joining because of a Supermind
- [x] Ideate and draft up low-fi mockups to represent the UI flow and constraints


## Definition of Ready Checklist

- [x] Definition Of Done (DoD)
- [x] Acceptance criteria
- [x] Weighted
- [ ] QA
- [x] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 5.0
Boost rotator space appears for new users (V2)

<!---
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

Newly-registered users aren't served Boosts for their first seven days.

With V2 activities, the Boost rotator space appears at the top of the Newsfeed, and displays no Boosts.

### Steps to reproduce

- Log into Minds with a new account
- Enable V2 activities
- Navigate to the Newsfeed
- Wait ~10 seconds

### Platform information 

MacOS + Chrome

### What is the current *bug* behavior?

The Boost rotator component is loaded into the Newsfeed after a few seconds.

### What is the expected *correct* behavior?

The Boost rotator should not appear for newly-registered users (first 7 days).

### Relevant logs and/or screenshots

![image](/uploads/0fb7809cf7c7073051c46a5bfe0d6803/image.png)

### Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Story points: 3.0
Images are blurry

<!---
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

A lot of images inside activity posts are not loading past the blurry placeholder

### Steps to reproduce

- Navigate to an affected activity post, e.g. https://www.minds.com/newsfeed/1412947947158507539
- Images within groups appear to be most impacted: https://www.minds.com/groups/profile/566365153877045248/feed

### Platform information 

- MacOS + Chrome
- iPhone app

### What is the current *bug* behavior?

Web: The app loads blurry placeholder images, but never replaces them with the full images

App: The app loads blurry placeholder images, and replaces the blurs with `The media could not be loaded` message.

### What is the expected *correct* behavior?

(What you should see instead)

### Relevant logs and/or screenshots

Web: ![image](/uploads/5c8e905110f2d371b2955b0d59ed7734/image.png)

App: ![image](/uploads/64290c53cf4f634c4e958b0542a7cbd1/image.png)

### Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Story points: 0.0
Create small, reusable components for Superminds

<!---
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

Minimize duplicate work for Superminds implementation.

## What needs to be done

- Review [Superminds designs in Figma](https://www.figma.com/file/thrGepQAxmcMGB7MoEEckM/Supermind?node-id=287%3A5233) to identify small components and patterns that are reusable
- Build reusable components [in Storybook?]
- Communicate their availability to developers working on Superminds implementation.

## QA

<!---
Consideration is given to how the issue will be demoed and tested prior to being deployed
--->


## UX/Design

See: [Figma design mocks](https://www.figma.com/file/thrGepQAxmcMGB7MoEEckM/Supermind?node-id=287%3A5233)

## Personas

Minds developers

## Experiments

n/a

## Acceptance Criteria

<!--
Everyone should be able to understand what is expected to be delivered
--->

- [ ] Gradient border component is reusable
- [ ] Supermind tag component is reusable
- [ ] Supermind gradient is reusable (e.g. via class)
- [ ] Components are in Storybook

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 3.0
Implement Superminds onboarding modals

## Goal

Communicate to users who are new to Superminds what Superminds are and why they should want to engage with them.

## What needs to be done

Implement 2x separate onboarding modals.

1. For users who are offering Superminds
2. For users who are replying to Superminds requests

## QA

<!---
Consideration is given to how the issue will be demoed and tested prior to being deployed
--->


## UX/Design

- [Figma: Offering Superminds onboarding](https://www.figma.com/file/thrGepQAxmcMGB7MoEEckM/Supermind?node-id=545%3A14545)
- [Figma: Replying to Superminds onboarding](https://www.figma.com/file/thrGepQAxmcMGB7MoEEckM/Supermind?node-id=588%3A17217)

## Personas

Core users

## Experiments

n/a

## Acceptance Criteria

- [ ] Given a user has not yet engaged with Superminds as a sender, when the user first views the Superminds pricing panel in the composer, then the sender onboarding modal appears.
- [ ] Given a user has not yet engaged with Superminds as a receiver, when the user first navigates to the Superminds console inbound view, then the receiver onboarding modal appears.
- [ ] Given the user has previously viewed the sender modal, then it is not displayed again.
- [ ] Given the user has previously viewed the receiver modal, it it is not displayed again.
- [ ] We can view data in Superset to understand how many users have viewed either modal.
- [ ] Tap into dismissible widgets endpoint on engine

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 3.0
Web: Affiliates screen updates

<!---
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
--->

Improve the UX and understanding of the new affiliate earning options for users.


## What needs to be done

<!---
Clearly detail what needs to be done to achieve the goal set out above
--->

Implement changes to Affiliate screen based on early feedback to make it as clear as possible.

Core layout:
- Change text of `Earn with link` button to `Refer and earn`
- Move `Refer and earn` button higher on the page
- Move `Affiliate referral` and `Creator referral` descriptors below `Invite your friends to Minds` heading

Share sheet: Invite to Minds
- Update explainer text to `Earn for up to 1 year from when someone uses your link.`

Share sheet: Affiliate link
- Change heading to `Earn with affiliate link`
- Remove `Creator` button
- Change text to `Earn for up to 72 hours from when someone uses your link.`

## 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.
--->

![image](/uploads/00283fce5129fedd599a10b4de782c56/image.png)

[Figma](https://www.figma.com/file/NfZCO1DzPnw4YTzVKOu8O7/Affilate?node-id=1118-28566)

## 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
--->

- [ ] Changes implemented as above

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 1.0
Video in Moments are failing with error

<!---
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

Videos in moments are failing with error.

(Summarize the bug encountered concisely)

### Steps to reproduce

(How one can reproduce the issue - this is very important)
Go to moments and tap right until a video is present. Notice the error after loadind.

### Platform information 

both

(Browser, device, system stats, screen size)

### What is the current *bug* behavior?

(What actually happens)
Video play error in moments.

### What is the expected *correct* behavior?

Video to play corectly.

(What you should see instead)

### Relevant logs and/or screenshots


![Simulator_Screen_Recording_-_iPhone_14_-_2023-04-25_at_16.24.45](/uploads/3f3cf3fba0cbd01f1ebba5a1a8eb1ef1/Simulator_Screen_Recording_-_iPhone_14_-_2023-04-25_at_16.24.45.mp4)

(Paste any relevant logs - please use code blocks (```) to format console output,
logs, and code as it's very hard to read otherwise.)

```
Exception [Error: The AVPlayerItem instance has failed with the error code -12746 and domain "CoreMediaErrorDomain".] Error: The AVPlayerItem instance has failed with the error code -12746 and domain "CoreMediaErrorDomain".
    at construct (native)
    at Wrapper (http://localhost:8081/index.bundle?platform=ios&dev=true&minify=false&modulesOnly=false&runModule=true&app=com.minds.mobile:24267:64)
    at construct (native)
    at _createSuperInternal (http://localhost:8081/index.bundle?platform=ios&dev=true&minify=false&modulesOnly=false&runModule=true&app=com.minds.mobile:277620:322)
    at call (native)
    at CodedError (http://localhost:8081/index.bundle?platform=ios&dev=true&minify=false&modulesOnly=false&runModule=true&app=com.minds.mobile:277633:26)
 LOG  The AVPlayerItem instance has failed with the error code -12746 and domain "CoreMediaErrorDomain".
 LOG  The AVPlayerItem instance has failed with the error code -12746 and domain "CoreMediaErrorDomain".
```

### Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Story points: 3.0
UXD: Update affiliates screen

<!---
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
--->

Improve the UX and understanding of the new affiliate earning options for users.


## What needs to be done

<!---
Clearly detail what needs to be done to achieve the goal set out above
--->

Take the feedback from the team given in the Affiliate chat room and update the designs and copy to reflect the necessary changes to help make the options users have as clear as possible.


## 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.
--->

![image](/uploads/f7e3b722fa80f4b497c98b2cbf9abff6/image.png)

[Figma](https://www.figma.com/file/NfZCO1DzPnw4YTzVKOu8O7/Affilates?node-id=1118%3A28566&t=bTVdjWNe4ax1xHug-1)

## 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: 5.0
New link previews not loading

<!---
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

New link previews not loading

### Steps to reproduce

1. Get some random link, eg a news article
2. Try posting it
3. See that it tries loading the link, then stops
4. The preview won't work

### Platform information 

Brave, Win10

### What is the current *bug* behavior?

The link previews are not loading

### What is the expected *correct* behavior?

The link preview should load

### Relevant logs and/or screenshots



### Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Story points: 1.0