giseldo/neodataset huggingface dataset:
Improve messaging for rejected boosts

<!---
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

Ambiguous messaging in the Boost Console is creating confusion when boosts get refunded due to high volumes of boost orders.

![image](/uploads/2d126d087816267024331e67a87ae241/image.png)

## What needs to be done

Change the language displayed in the Boost Console, from:

> Your boost was rejected: Onchain payment failed or High Boost backlog

To:

> Due to high boost backlog, your tokens have been auto-refunded.

## QA

<!---
Consideration is given to how the issue will be demoed and tested prior to being deployed
--->


## UX/Design

n/a

## Personas

Core users who boost

## Experiments

n/a

## Acceptance Criteria

- [ ] Given a boost order is rejected due to high boost backlog, the message above is displayed in the boost console.

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 2.0
Spike: Create NIP for Delegated Event Signing

<!---
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
--->

Investigate how a Minds custodial Nostr public key can be paired to a user owned keypair. 

## What needs to be done

<!---
Clearly detail what needs to be done to achieve the goal set out above
--->

This task is to investigate what is involved to achieve the goal above.

## QA

<!---
Consideration is given to how the issue will be demoed and tested prior to being deployed
--->

N/A


## UX/Design

<!---
Sufficient wireframes have been presented and understood by the development team. Full mockups are not required and re-usable components are encouraged.
--->

N/A

## Personas

<!---
Who does this user impact and why (optional)
--->

Nomads

## 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
--->

- [ ] Further tasks and/or implementation plan

## 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: 3.0
Implement in-feed notices in app (all)

<!---
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

Synchronize in-feed notice communication experience between the web and mobile app.

## What needs to be done

Implement in-feed notices in the mobile app using the backend logic endpoint developed for the web app.

1. Setup Channel
2. Verify Uniqueness
3. build-your-algorithm
3. Push Permissions
4. Update Tags 

## QA

<!---
Consideration is given to how the issue will be demoed and tested prior to being deployed
--->


## UX/Design

- [In-feed activity notice mobile](https://www.figma.com/file/EkJej3mKP2lSzmWTLoqlXD/Minds-Design-System?node-id=815%3A9478)


## Personas

- New users

## Experiments

No experiment

## Acceptance Criteria

- [ ] In-feed notices appear in the app [when their conditions are met](https://docs.google.com/spreadsheets/d/1FHWiKdYobssgXQt8Cc6l3IyiFwjWnf2_jCc-ObHUsuM/edit?usp=sharing)
- [ ] Only one in-feed notice appears in the feed at a time

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 5.0
Email verification in-feed notice

<!---
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 communicate to users that they need to verify their email address, and make it easy for them to do so.

## What needs to be done

Implement the `Verify your email address` in-feed notice on the mobile app.

## QA

<!---
Consideration is given to how the issue will be demoed and tested prior to being deployed
--->


## UX/Design

- [Figma mocks](https://www.figma.com/file/EkJej3mKP2lSzmWTLoqlXD/Minds-Design-System?node-id=815%3A9478)

Screenshot for reference, see Figma mocks for latest spec.

![image](/uploads/52d18a1590b69ad73c0388c6b00338eb/image.png)

## Personas

New users

## Experiments

No experiment for this change specifically, but this change should be rolled out before experimenting with code-based email verifications (https://gitlab.com/minds/minds/-/issues/3296).

## Acceptance Criteria

<!--
Everyone should be able to understand what is expected to be delivered
--->

- [ ] Given a user has not already verified their email address, when they visit the Newsfeed, then the `Verify your email address` in-feed notice appears.
- [ ] Given the `Verify your email address` in-feed notice appears, when the user clicks the `Re-send email` button, then a new email verification link is sent to the user's email address.

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 2.0
Code-based email verifications in mobile app

<!---
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

Implement code-based email verifications in the mobile app and make the verification part of the initial onboarding flow, before a user reaches the Newsfeed.

## What needs to be done

- Implement code-based email verification flow to the mobile app new user onboarding.

## QA

<!---
Consideration is given to how the issue will be demoed and tested prior to being deployed
--->


## UX/Design

- [Figma designs](https://www.figma.com/file/zKXef5Dyr3CiCEhTjALkzl/Mobile-Onboarding-Quirk?node-id=0%3A1)

Screenshot for quick reference, see Figma mocks for latest spec.

![image](/uploads/77900c9a95b7dc0bf9ef2867ce53ce8f/image.png)

## Personas

- New users

## Experiments

Code-based verification should be tested versus existing link-based email verification, measuring for % of signups that result in email verification.

## Acceptance Criteria

- [ ] Given a user is creating a new account in the app, and the user has already filled out the fields on `Join Minds` screen, and all fields are valid, when the user clicks the blue `Join Minds` button, then a code-based verification email is sent to the user's email address, and the user is navigated to the code-based `Verify Account` screen.
- [ ] When the user is navigated to the code-based `Verify Account` screen, then the user's cursor is automatically positioned in the `Verification code` text field, and the keyboard defaults a numeric layout.
- [ ] Given the user is on the code-based `Verify Account` screen, and the user inputs an invalid code, when the user taps `Verify` button, then the "Invalid code" error is displayed adjacent to the code field.
- [ ] Given the user is on the code-based `Verify Account` screen, and the user inputs a VALID code, when the user taps `Verify` button, then the email address is verified and the user is navigated to the Newsfeed.

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 3.0
"Actions Taken" stats on content-policy page are not accurate

<!---
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

The `minds.com/content-policy` page has statistics for Actions Taken, Appeals, and Actions Overturned in the past 30 days. Currently, this reads "0" for all values.

### Steps to reproduce

Visit https://minds.com/content-policy , scroll to bottom.

### Platform information 

Brave browser on Ubuntu

### What is the current *bug* behavior?

Values show "0"

### What is the expected *correct* behavior?

Values show actual actions taken, etc.

### Relevant logs and/or screenshots


### Possible fixes

Story points: 1.0
Boost inventory: Add boosts to Discovery

<!---
Please read this!

The Definition of Ready (DoR) can be found at https://developers.minds.com/docs/handbook/how-we-work/#definition-of-ready-dor

Before opening a new issue, make sure to search for keywords in the issues
filtered by the "Type::Feature" label and verify the feature you're about to submit isn't a duplicate.
--->

## Goal

Increase boost inventory.

## What needs to be done

Add in-feed boost placements to the Discovery > Top feed, using the same spacing logic as used on the Newsfeed.

Note: This does NOT include the Boost rotator.

## QA

<!---
Consideration is given to how the issue will be demoed and tested prior to being deployed
--->


## UX/Design

No new design, the in-feed boosts should appear the same way they would on the Newsfeed.

## Personas

Core users

## Experiments

We should roll this out as an experiment to see if it negatively impacts engagement on the Discovery feed.

## Acceptance Criteria

- [ ] In-feed boosts appear on the Discovery > Top feed with the same frequency as they appear on the Newsfeed
- [ ] The boost rotator does not appear on Discovery > Top

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 3.0
Switch channel recommendations to Vitess

<!---
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
--->

Change 'friends of friends' ElasticSearch to be on Vitess

## What needs to be done

<!---
Clearly detail what needs to be done to achieve the goal set out above
--->

See above

## QA

<!---
Consideration is given to how the issue will be demoed and tested prior to being deployed
--->

Recommendations display.

## UX/Design

<!---
Sufficient wireframes have been presented and understood by the development team. Full mockups are not required and re-usable components are encouraged.
--->

N/A

## Personas

<!---
Who does this user impact and why (optional)
--->

users

## Experiments

<!---
Experiments are not required, but it should be made clear if one is expected. If experiments are required, the hypothesis should be outlined.
--->

Yes

## Acceptance Criteria

<!--
Everyone should be able to understand what is expected to be delivered
--->

- [ ] Refactor elasticsearch 'friends of friends' logic to point to vitess
- [ ] Add in experiment
- [ ] Spec tests

## 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
Create page with links to tools to aide development

<!---
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

Aide development and usage of SKALE tasks such as https://gitlab.com/minds/engine/-/issues/2349

## What needs to be done

Create docs page with info for development

## QA

N/A

## UX/Design

N/A

## Personas

Developers of SKALE MINDS system

## Experiments

N/A

## Acceptance Criteria

- [ ] Docs pages
- [ ] Blockexplorer
- [ ] Usage examples
- [ ] Explanations

## 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: 0.0
Display a modal of mutual subscribers to be displayed when clicking 'other' on `m-channel__mutualSubscriptions`

<!---
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
--->

Now we have 'also subscribed to' blocks on channels, we want to expand to be able to see more than 2 results. 

## What needs to be done

<!---
Clearly detail what needs to be done to achieve the goal set out above
--->

We already have a modal that displays for subscribes on notifications, this is just a time ordered list. Modify this modal to support mutual 'also subscribed to'. The backend needs a slight tweak to support pagination.

## QA

<!---
Consideration is given to how the issue will be demoed and tested prior to being deployed
--->

The modal display when relevant.

## 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)
--->

Subscribers.

## Experiments

<!---
Experiments are not required, but it should be made clear if one is expected. If experiments are required, the hypothesis should be outlined.
--->

M/A


## Acceptance Criteria

<!--
Everyone should be able to understand what is expected to be delivered
--->

- [ ] Click on the component will launch a modal (same as what is currently used to display who up-voted a post) and list any mutual subscriptions, or redirect to a channel.
  * [ ] clicking directly on a channel handle will direct the user to that channel
  * [ ] clicking on `x others` or any of the avatars will launch a the modal.
- [ ] Backend to support pagination. ie `LIMIT 12,20` in the SQL statement will offset to 20-32 results.

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 3.0
Show toast message before launching modal if email verification is required to complete modal actions

<!---
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

Reduce UX clumsiness by warning user about email verification requirement before they try to do something that requires email verification.

## What needs to be done

Throw a toast message instead of opening a modal, if the modal action requires email verification.

Examples:

- [Verifying phone number](https://gitlab.com/minds/front/-/issues/5568)
- [Creating an activity post](https://gitlab.com/minds/engine/-/issues/2209)

## QA

<!---
Consideration is given to how the issue will be demoed and tested prior to being deployed
--->


## UX/Design

Message:

> You must confirm your email address

## Personas

- New users

## Experiments

None

## Acceptance Criteria

- Given a user hasn't verified their email address,
- when the user clicks something that generates a modal,
- and that modal's action requires email verification,
- then prevent the modal from displaying,
- and throw a toast message that indicates that email verification is required.

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 3.0
Notifications feed jumps when closing image overlay

<!---
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 on the notifications screen and viewing an image in an overlay view, when closing the image overlay, the notifications feed jumps.

### Steps to reproduce

- Navigate to the notifications feed
- Scroll the notifications until the app has to load more in
- Scroll down to a notification that includes an image
- Double-tap the image to view the image in an overlay
- Swipe the image to close it

### Platform information 

- iPhone 12 Mini w/ latest Testflight build

### What is the current *bug* behavior?

- The image is dismissed
- The feed jumps and the user loses their position

### What is the expected *correct* behavior?

- The image is dismissed
- The feed scroll position is unchanged

### Relevant logs and/or screenshots

![RPReplay_Final1656646300](/uploads/d25565dfba0805c44b49aa4e37861e88/RPReplay_Final1656646300.mov)

### Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Story points: 3.0
(bug) Verify your email address emails broken on Hotmail and Outlook

<!---
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

Emails prompting users to verify their email are broken in outlook and hotmail, like so:

![image](/uploads/45219bfa39d9cbd7c504a509107cb415/image.png)

and it points to `https://` link

### Steps to reproduce

1. Create account or request verify email
2. Look at the email in outlook or hotmail

### Platform information 

Tested on:
- Thunderbird 91.10.0 (64-bit)
- Microsoft® Outlook® for Microsoft 365 MSO (Version 2205 Build 16.0.15225.20278) 64-bit 

### What is the current *bug* behavior?

(What actually happens)

### What is the expected *correct* behavior?

(What you should see instead)

### 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
Minds videos don't load when embedded

<!---
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

Minds videos embedded on Corbett Report website do not load / are not playable.

### Steps to reproduce

- Log out of Minds
- [Visit this page on Corbett Report website](https://www.corbettreport.com/category/videos/page/4/).
- Scroll the page to see posts with video embeds.
- Observe the posts with Minds videos embedded:
  - Episode 415 - The Global Digital ID Prison
  - Interview 1708 – New World Next Week with James Evan Pilato
  - The Future of Censorship (video)
- Try to play the video

----

- Log into Minds
- [Visit this page on Corbett Report website](https://www.corbettreport.com/category/videos/page/4/).
- Scroll the page to see posts with video embeds.
- Observe the posts with Minds videos embedded:
  - Episode 415 - The Global Digital ID Prison
  - Interview 1708 – New World Next Week with James Evan Pilato
  - The Future of Censorship (video)
- Try to play the video

### Platform information 

MacOS + Chrome

### What is the current *bug* behavior?

While logged out of Minds:

The video frame is not loaded in completely (it looks mostly blank, aside from the title).

The video is not playable.

---

While logged into Minds:

The video frame loads in the Minds UI (navigation, avatar, alert bar).

### What is the expected *correct* behavior?

Whether logged in or logged out:

The video embed should load entirely, including a thumbnail image and play button.

Video is playable.

### Relevant logs and/or screenshots

![image](/uploads/1fc11d8f4e7e918ae0ffae607cb159a1/image.png)

![image](/uploads/a8011974fff40fd41f11e76ee0ab364c/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 in-feed notices to Discovery feed

<!---
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 onboarding experiments with the Discovery > Top feed by bringing Newfeed features targeted at new users to the Discovery feed.

## What needs to be done

Enable all in-feed notices to appear on the Discovery > Top feed, by the same logic with which they can currently appear on the Newsfeed.

For reference, [this is the order in which activity posts are expected to appear](https://docs.google.com/spreadsheets/d/1FHWiKdYobssgXQt8Cc6l3IyiFwjWnf2_jCc-ObHUsuM/edit#gid=0) (same as Newsfeed).

## QA

<!---
Consideration is given to how the issue will be demoed and tested prior to being deployed
--->


## UX/Design

No Design

## Personas

This change is targeted at new Minds users who are curious about the network and want to connect with people with similar interests.

## Experiments

While this change is related to enabling experiments, it is not an experiment itself -- this can be rolled out to 100% of the audience.

## Acceptance Criteria

- [ ] Given an in-feed notice appears on the Newsfeed, and I have not yet dismissed the notice or otherwise completed the criteria that dismiss it, when I visit the Discovery feed, then the same in-feed notice is presented in the same position.

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 3.0