giseldo/neodataset huggingface dataset:
Empty Boost console feeds show "Create a post" instead of "No boost" message

<!---
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

Empty Boost feeds (both Feed & Sidebar) display a `Create a post` button. The UX of this is a bit awkward -- for now we should just display `No posts` message like we do on web.

### Steps to reproduce

- Log in with an account with no Boosts
- Navigate to the Boost console

### Platform information 

- iOS app
- Android app

### What is the current *bug* behavior?

- A `Create a post` message + button appears

### What is the expected *correct* behavior?

- A `No boost` message appears

### Relevant logs and/or screenshots

Mobile app:

![IMG_B9F314549CDE-1](/uploads/24a78038f762345166b0706bbbc56158/IMG_B9F314549CDE-1.jpeg)

Mobile web:

![image](/uploads/2fcc9dfc69a4f776f395e9b736fe7f73/image.png)

### Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Story points: 2.0
When hiding a post in the Boost rotator, the Boost rotator appears blank

<!---
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 hiding a post in the Boost rotator, the Boot rotator appears blank.

### Steps to reproduce

- Visit the Newsfeed
- Click the ... menu on a post in the Boost rotator
- Choose to hide the post

### Platform information 

MacOS + Chrome

### What is the current *bug* behavior?

- The Boost is removed / hidden
- The Boost rotator appears blank

### What is the expected *correct* behavior?

- The Boost is removed / hidden
- The Boost rotator advances to display the next available Boost

### Relevant logs and/or screenshots

![image](/uploads/16ebecbea1b6338fb58fedfdc136fe63/image.png)

### Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Story points: 2.0
Audience shows as "Mature" on "Review your Boost" screen

<!---
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 label `Mature` is displayed under the selected Audience on the `Review your Boost` screen (last screen during purchase process).

### Steps to reproduce

- Start a new Boost
- Select the `Controversial` audience
- Get to the `Review your Boost` screen

### Platform information 

- iOS
- Android

### What is the current *bug* behavior?

- The selected audience is labeled `Mature`

### What is the expected *correct* behavior?

- The selected audience is labeled `Controversial`

### Relevant logs and/or screenshots

![IMG_73C19A98E32C-1](/uploads/4ccd2dfef406f1c369f89de969ec8f9f/IMG_73C19A98E32C-1.jpeg)

### Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Story points: 1.0
Link to Boost content policy with rejection message in Boost console

<!---
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

Provide sufficient disclosure / communication about a Boost rejection so that the user is not confused.

## What needs to be done

Add a `Learn more` link to the Boost rejection reason in the Boost console.

Link to here: https://support.minds.com/hc/en-us/articles/11723536774292-Boost-Content-Policy

## QA

<!---
Consideration is given to how the issue will be demoed and tested prior to being deployed
--->


## UX/Design

![image](/uploads/db71e53bcbefe5fe09c6e8e1d8237f30/image.png)

## Mobile

<!---
Does a mobile card need to be created? Any notes for mobile?
--->

- [x] 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
--->

- [ ] Add the link in above
- [ ] Learn more to go to zendesk (ryan to add)
- [ ] If the rejection reason was invalid audience, Display "Boost again" which would open the boost modal.

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 2.0
Boost transactions display wrong text in the Wallet

<!---
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

Boost transactions in the wallet appear as Boost offers to `@mindsboost`.

### Steps to reproduce

Case 1:
- Create a Boost in V3

Case 2:
- Reject the Boost

### Platform information 

MacOS + Chrome

### What is the current *bug* behavior?

- Transactions appear in the wallet
- The transactions appear as

`Off-Chain Boost Offer to @mindsboost`

`Off-Chain Boost Offer from @mindsboost`

### What is the expected *correct* behavior?

- Transactions appear in the wallet
- The transactions appear as

`Off-Chain Boosted Content`

### Relevant logs and/or screenshots

![image](/uploads/8998d29215b2f982ada99b1f809b1bd4/image.png)

### Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Story points: 2.0
Email & Push notifications link to Boost console with selected post

<!---
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

Give users the best context when tapping CTAs on emails and push notifications.

## What needs to be done

When tapping a CTA on a Boost-related email and/or push notification, we should navigate the user to the Boost console with the relevant post displayed exclusively (e.g. how Supermind emails work).

## 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.
--->

## Mobile

<!---
Does a mobile card need to be created? Any notes for mobile?
--->

- [x] 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
--->

- [ ] Introduce new single view page
- [ ] Notifications and emails to link to the single page
- [ ] Ensure the ACL is restricted to only the boost owner
- [ ] Designs to mirror supermind single page

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 5.0
Move Blocklists to Vitess and integrate with boost 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

Don't show users content from channels they've blocked.

## What needs to be done

- Give User A has blocked Channel Y,
- and Channel Y creates a Boost,
- when User A views Boosts,
- then Channel Y's Boosts are not served.


### Schemas

TBD (user_blocklist)

## 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.
--->

## 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
--->

- [ ] Migrate Block table from Cassandra -> Vitess
- [ ] Boost query should join against new Vitess block list

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 5.0
Duplicate emails being sent - investigate & fix

<!---
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

Reports of duplicate emails being sent or no emails being sent.

### Steps to reproduce

Unknown as of yet - need to triage.

### Platform information 

Platform web

### What is the current *bug* behavior?

Reports of dupe emails and emails not coming through

### What is the expected *correct* behavior?

Emails should come through and not be duplicated

### Relevant logs and/or screenshots

![image](/uploads/21a8219048cab1e756ce715aa31fd6df/image.png)

### Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Story points: 3.0
Preserve UTM codes in link previews

<!---
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 marketers to measure the impact of posting on Minds / Boosting on Minds.

## What needs to be done

When an activity post contains a link with UTM parameters, and a link preview is added to the post, then the link preview should maintain the UTM parameters.

Currently, UTM parameters are preserved if the user clicks the URL address in the post, but not if the user clicks the link preview.

Example post: https://www.minds.com/newsfeed/1467274467364311058

![Untitled](/uploads/a5cc1499eba70b06e2e789265766cad5/Untitled.png)

## 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.
--->

## Mobile

<!---
Does a mobile card need to be created? Any notes for mobile?
--->

- [x] 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
--->

- [ ] Ensure we use the raw link instead of the canonical url

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 1.0
Custom fields for Mautic segmenting

<!---
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 more focused communications w/ Minds community through Mautic.

## What needs to be done

Add attributes to contacts that enable creating Mautic segments.

| Custom field                            | Goal                                           | Done |
|-----------------------------------------|------------------------------------------------|------|
| KITE segment                            | Engagement, Minds+ subscriptions, Resurrection | [x] |
| Last Boosted: Cash                      | Boost buys, Research                           | [x] |
| Last Boosted: Token                     | Boost buys                                     | [x] |
| Last posted                             | Engagement, Boost buys                         | [x] |
| Token balance                           | Minds+ subscriptions                           | [x] |

## 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.
--->

## 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
Boost text updates (mobile)

<!---
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
--->

Simplify bottom bar text on boost.


## What needs to be done

<!---
Clearly detail what needs to be done to achieve the goal set out above
--->





## QA

<!---
Consideration is given to how the issue will be demoed and tested prior to being deployed
--->


## UX/Design

<!---
Sufficient wireframes have been presented and understood by the development team. Full mockups are not required and re-usable components are encouraged.
--->

[Figma](https://www.figma.com/file/W2xIag64EdbWUlGAQOpVHE/Boost-Update?node-id=863%3A19887&t=W4VuvJ1FXi8LTFLu-1)

**Web**

![U_dated_Boost_Post_Mobile_-_Cash](/uploads/fcf1ddf2e69a62ccb768da681bdd0656/U_dated_Boost_Post_Mobile_-_Cash.png)

![Updated_Boost_Post_Mobile_-_Tokens](/uploads/fd212146e67d0643fb9696f63c9d3ccf/Updated_Boost_Post_Mobile_-_Tokens.png)

![Updated_Boost_Post_Web_-_Review_Boost_Cash](/uploads/96e6557db2c8466b9f570ee8bd9e7a49/Updated_Boost_Post_Web_-_Review_Boost_Cash.png)

## Mobile

<!---
Does a mobile card need to be created? Any notes for mobile?
--->

![Updated_Boost_Post_Mobile_-_Cash](/uploads/343f4d4090c3f898469dab4cc7274b7e/Updated_Boost_Post_Mobile_-_Cash.png)

![Updated_Boost_Post_Mobile_-_Tokens](/uploads/39ad6f666f0942eea62816a8b6a0f336/Updated_Boost_Post_Mobile_-_Tokens.png)

![Updated_Boost_Post_Mobile_-_Review_Boost_Cash](/uploads/df7b1867aabf5571089d94c81313048b/Updated_Boost_Post_Mobile_-_Review_Boost_Cash.png)

- [x] 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: 3.0
Holding rewards show as zero in wallet

<!---
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

Holding rewards show as zero in wallet

![image](/uploads/7c3327ec1d0e0c9a3157f6935e4e8a11/image.png)

### Steps to reproduce

1. Have some on-chain tokens
1. Look into your wallet

### Platform information 

Brave, Win10

### What is the current *bug* behavior?

Wallet shows zero in holding section

### What is the expected *correct* behavior?

Wallet should show proper amount in holding section

### 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)

### UX Design

[Figma](https://www.figma.com/file/tBOvE8yIILW49vECySCLpZ/Earnings?node-id=163%3A2911&t=lKTi6szGDxu4oxNk-1)

**Web**

![Holdings_Web](/uploads/c8a193a51a50fac0c3f96b18dd15445c/Holdings_Web.png)

**Mobile**

![Holdings_Mobile](/uploads/007076d67b04fcda7692e2292d753e6f/Holdings_Mobile.png)

Story points: 1.0
"Access denied" when posting bitchute links

<!---
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

"Access denied" when posting bitchute links:

![image](/uploads/71902dab5688546b8175685fbee7ab83/image.png)

### Steps to reproduce

1. Post a link to bitchute video
2. See it has access denied in it

I posted 5 different link examples (one of them works) to this hashtag: https://www.minds.com/discovery/search?q=%23testbitchute&f=latest&t=all

### Platform information 

Any

### What is the current *bug* behavior?

Access denied instead of preview

### What is the expected *correct* behavior?

Should see the preview

### 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: 0.0
Controversial Boost doesn't appear in new Boost Console

<!---
Please read this!

Before opening a new issue, make sure to search for keywords in the issues
filtered by the "T - Bug" label and verify the issue you're about to submit isn't a duplicate.
--->

### Summary

I've made a few test Boosts in V3 on Staging. One Boost is not appearing in my Boost Console.

The Boost is of this activity: https://www.minds.com/newsfeed/1458689744366997519

I targeted the `Controversial` audience, with a 1 token boost for 1 day.

Differences between this and Boosts that did show up in my Boosts Console:

- Different activities were Boosted
- This one targeted `Controversial` while others targeted `Safe`

### Steps to reproduce

- Boost this post: https://www.minds.com/newsfeed/1458689744366997519
- Target the `Controversial` audience
- Boost for 1 token over 1 day

### Platform information 

- MacOS + Chrome

### What is the current *bug* behavior?

- The Boost does not appear in the Boost Console

### What is the expected *correct* behavior?

- The Boost does appear in the Boost Console, in a `pending` state

### Relevant logs and/or screenshots

![image](/uploads/11ead106aca83bfe5e81c7e52aa3c225/image.png)

### Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Story points: 1.0
Guest mode is redirecting to /login

<!---
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

Guest mode is redirecting to /login.

### Steps to reproduce

- Log out of Minds
- Navigate to minds.com

### Platform information 

- MacOS + Chrome
- Windows + Brave

### What is the current *bug* behavior?

- The Guest Mode homepage loads
- Quickly after, the user is redirected to /login

### What is the expected *correct* behavior?

- The Guest Mode homepage loads
- The user is NOT redirected to /login

### Relevant logs and/or screenshots

You can view this behavior at the beginning of this user test video.

https://dashboard.userbrain.com/shared/lv26jq3l8p97

### Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Story points: 2.0
Register form does not display warning of invalid character use

<!---
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 register form does not a display warning when an invalid character is input to the `Username` field.

### Steps to reproduce

- Navigate to https://www.minds.com/register
- Input an invalid character in the `Username` field, e.g. `{`

### Platform information 

- MacOS + Chrome
- Windows + Brave

### What is the current *bug* behavior?

- The Register modal changes size as if something changed.
- There's no warning about the invalid character.

![image](/uploads/92faab2f10d9732bd59e286de46f24db/image.png)

### What is the expected *correct* behavior?

- The Register modal does NOT change size.
- There's a warning about the invalid character used.

![image](/uploads/eae55d7479ca5c8eb713f96988f15d87/image.png)

### 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