giseldo/neodataset huggingface dataset:
Link previews seem to not work

<!---
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

Link previews seem to not work

### Steps to reproduce

1. Pick a link (list bellow)
2. Try posting it
3. see it stops loading after almost minute of tring to fetch preview

- `https://gab.com/bashynxHasBeenTaken/posts/107633575284884185` < this got me an unknown error
- `https://twitter.com/Uugher7/status/1623988168813862912` < this got me an unknown error
- `https://www.youtube.com/watch?v=w6YqZ8-1uwk` < this got me an error
- `https://www.bitchute.com/video/Wz71iokDJSc/` < no preview, error
- `gab.com` < worked
- `bashynx.com` < worked
- `https://gab.com` < worked
- `https://gab.com/bashynxHasBeenTaken` < did not work, error

### Platform information 

Brave, Chrome, Win10, Prod

### What is the current *bug* behavior?

Links seem to be not loading previews

### What is the expected *correct* behavior?

Links should load previews

### 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
Missing top border for boosted posts

<!---
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 border between boosted posts and other content

### Steps to reproduce

1. Put staging on
2. Make sure you can see boosts and recommended channels module
3. Scroll down and see missing border
4. Should be able to see it for other boosts

### Platform information 

Web.

### What is the current *bug* behavior?

No border.

### What is the expected *correct* behavior?

- Should have border.
- **SHOULD NOT ADD DOUBLE BORDERS TO BOOST FEED**

### Relevant logs and/or screenshots

![image](/uploads/30ed296e866cc26721bbc3e22f3028b1/image.png)

![image](/uploads/04ea35f9d71813ee9a28fcd34303c4c9/image.png)

### Possible fixes

Styling issue may be at newsfeed layer as boost feed still looks fine

Story points: 1.0
Add CPM to Boost console for completed 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

Help customers understand the ROI of their Boosts by displaying the CPM (cost per thousand views) of a completed Boost.

## What needs to be done

Add the calculated CPM to the Boost console view of _completed_ Boosts.

A CPM result could look something like...

- $3.00
- 5 tokens

Include a tooltip (on hover) with the following copy:

> CPM is the cost per 1,000 views (cost per mille)

## 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=1212%3A26260&t=DiAvRB18So68wqB0-1)

![Completed](/uploads/711a7fdae357d1d2cae482172870e93d/Completed.png)

![Completed](/uploads/bafa434aa7d5e85de1a4b5507cb71335/Completed.png)

![Completed](/uploads/eb131315a35c921c97618987453ca35e/Completed.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
--->

- [ ] Display the CPM client side to 2 decimal places
- [ ] Token CPMs will be displayed as token amounts
- [ ] Only display the CPM for completed boosts

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 1.0
Boost feed pagination is 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

Boost feed pagination is broken.


### Steps to reproduce

Go https://www.minds.com/discovery/boost/feed

Try to scroll. Can't.

### Platform information 

Web, probably effects mobile too.

### What is the current *bug* behavior?

Pagination is broken.

### What is the expected *correct* behavior?

- Pagination should work in the feed - note currently `has_more` is returning `null`.
- [TBC] Pagination should work when anywhere between 1 result and all results are stripped due to blocked users.
- [TBC] Same as above for banned users presuming we have migrated banned users from Vitess and stripped them from the feed.

### Relevant logs and/or screenshots

![image](/uploads/979ebfdb8eb13ee2f76217b45245364e/image.png)

### Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Story points: 2.0
Gray out "Safe" audience when re-Boosting a post that was rejected for targeting "Safe"

<!---
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 the success rate of Boost submissions by preventing a Boost submission to an audience category for which that activity post was already rejected.

## What needs to be done

- Given a Boost is submitted to the `Safe` audience,
- and the Boost is rejected due to `Wrong audience`,
- when the user retries the Boost via the Boost console,
- then the `Controversial` audience is pre-selected,
- and the `Safe` audience selection is grayed out.

## 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.
--->

**Web **

[Figma](https://www.figma.com/file/W2xIag64EdbWUlGAQOpVHE/Boost-Update?node-id=1102%3A25649&t=WprtCMu8cpC8kssY-1)

![Greyed_Out_Boost_Post_Web_-_Audience_Selection_3](/uploads/a43f9ba29d5bbb16da8bc4f79eb6e096/Greyed_Out_Boost_Post_Web_-_Audience_Selection_3.png)

**Mobile**

[Figma](https://www.figma.com/file/W2xIag64EdbWUlGAQOpVHE/Boost-Update?node-id=1102%3A25652&t=WprtCMu8cpC8kssY-1)

![Greyed_Out_Boost_Post_Mobile_-_Audience_Selection](/uploads/e9c6c21bee65f73c47b323f6582c3493/Greyed_Out_Boost_Post_Mobile_-_Audience_Selection.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
--->

- [ ] ...

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 1.0
Boost your latest post 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

Increase Boost purchases.

## What needs to be done

Design and build an in-feed notice / promotion that invites a customer to Boost their latest post.

## 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.
--->

Link to figma file - https://www.figma.com/file/dknG3y2PhgoXZZ3tzKCpN4/Boost-(in-feed-notice)---Latest-post?node-id=1%3A2

![boost-late-post-in-feed-web-assets](/uploads/66892109d32edd3e9b7504fec18b7907/boost-late-post-in-feed-web-assets.png)

![boost-late-post-in-feed-mob-assets](/uploads/62f3dd4317972470edfd4d2d7cf51d4e/boost-late-post-in-feed-mob-assets.png)

##### Desktop designs 

![feed-notice-boost-post-web](/uploads/ab0259b7a3560825060cf8af36d8508c/feed-notice-boost-post-web.png)

![feed-notice-boost-post-SEP](/uploads/6193bd1c643ed908bafcd840dad3bc85/feed-notice-boost-post-SEP.png)

![feed-notice-boost-post-web-boostModal](/uploads/619a0e2d936e3736092d510c7535dcd8/feed-notice-boost-post-web-boostModal.png)


##### Mobile  designs 

![feed-notice-boost-post-mobile](/uploads/a6ce0cd67c3199e293e95bdd4670d64b/feed-notice-boost-post-mobile.png)

![feed-notice-boost-post-SEP-mob](/uploads/e73e63625ea58d5b6d844b2b4add84e9/feed-notice-boost-post-SEP-mob.png)

![feed-notice-boost-post-Modal](/uploads/04d34f7a7113626931615f7b5c6b6013/feed-notice-boost-post-Modal.png)


Prototype -

![minds-proto-latest-post-infeed-notice](/uploads/8884222dd84b16b748cd1a0d5b38112c/minds-proto-latest-post-infeed-notice.mov)


## 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.
--->

Current copy to be used - Boost your latest post

In a future issue, we intend to run a small experiment where we try out the two copy variants above, to measure which message performs best in terms of conversion.

## 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
Vertical video displays in widescreen player

<!---
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

Some vertical videos (9:16) are displayed in widescreen (16:9) video players.

### Steps to reproduce

I've had this occur multiple times, but not 100% on the repro steps. What I think can repro is...

- Launch the composer
- Upload the video
- **As soon as the video is uploaded and the `Post` button is active, click `Post` to create the post**
- Wait for the video to finish transcoding

(Waiting to click `Post` AFTER transcoding appears to avoid this bug.)

### Platform information 

MacOS + Chrome

### What is the current *bug* behavior?

The vertical video is displayed in a horizontal player.

[Example](https://www.minds.com/newsfeed/1469420770860994572)

### What is the expected *correct* behavior?

The vertical video is displayed in a vertical player.

[Example](https://www.minds.com/newsfeed/1469422004548407312)

### Relevant logs and/or screenshots

Example: https://www.minds.com/newsfeed/1469413508574613516

![image](/uploads/a1b2bb94ebc89a16fe26264d3aef4294/image.png)

### Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Story points: 3.0
Video flickers when 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

When uploading a video through the Composer, the video preview image flickers with upload progress.

### Steps to reproduce

- Launch the composer
- Upload a video

### Platform information 

- MacOS + Chrome

### What is the current *bug* behavior?

- A progress bar indicates progress
- The video preview image flickers

### What is the expected *correct* behavior?

- A progress bar indicates progress
- The video preview does not flicker

### Relevant logs and/or screenshots

![video_flicker](/uploads/bdbe7e038f6360e4172236e5998fe45a/video_flicker.mov)

### Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Story points: 3.0
Content policy and refund policy links in boost modal are not clickable

<!---
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

Can't click these links: 

![image](/uploads/ab70b6419eac5401a5697ac3c0c6f951/image.png)

Content policy should link: https://support.minds.com/hc/en-us/articles/11723536774292-Boost-Content-Policy

Refund policy should link: https://www.minds.com/p/terms

(I believe there was agreement both should point to same spot)

### Steps to reproduce

1. Try boosting
2. Get to the last screen
3. Test links on bottom

### Platform information 

(Browser, device, system stats, screen size)

### 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
Boost v3 | On-Chain boost stuck in pending on-chain confirmation

<!---
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 have made an on-chain boost a few days ago. It's still stuck in pending on-chain confirmation

Etherscan: https://etherscan.io/tx/0x482769b6634c481377ac6bacf1fe753584f62a5c85a43a779128bfd13e3779a8

![image](/uploads/79eb89e41d33922356d7bcd5ba954e70/image.png)

### Steps to reproduce

1. Make onchain boost
2. see it will get stuck

### Platform information 

(Browser, device, system stats, screen size)

### 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: 3.0
Cannot boost from channel page with filters

<!---
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

It is not possible to boost from the channel page with video / image filters apply

### Steps to reproduce

1. Go to your channel
2. Filter by images or video
3. Try to boost a post

### Platform information 

Web

### What is the current *bug* behavior?

Cannot boost, you see the below error

### What is the expected *correct* behavior?

Channel feed filters should return activity posts using the 'custom_type' field rather than type=object:image

### Relevant logs and/or screenshots

![image](/uploads/ee219b19b6fd3c7e39ddbad217e9851c/image.png)

### Possible fixes

This is because the endpoint returning the entities is returning image entities and not activities.

Story points: 2.0
Discovery > Suggested users is blank for anon users

<!---
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

https://www.minds.com/discovery/suggestions/user is empty for logged-out users.

### Steps to reproduce

- Log out
- Navigate to https://www.minds.com/discovery/suggestions/user

### Platform information 

- MacOS + Chrome

### What is the current *bug* behavior?

- The page appears empty with a "Load more" button
- Clicking the button does nothing

### What is the expected *correct* behavior?

- When opening the page, the Login modal should appear

### Relevant logs and/or screenshots

![image](/uploads/b71e59b900552bca5c073f9954a9a585/image.png)

### Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Story points: 1.0
Make comments shareable

<!---
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 comments more viral potential by making them shareable.

## What needs to be done

Enable comments to be easily shared via copy/pasting a link, and via re-mind function.

## 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
--->

- [ ] ...

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 3.0
Cleanup Gitlab Feature Flags

<!---
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
--->
Remove the legacy features flags that we still have on gitlab. Also remove all the old unleash/feature code.

## What needs to be done

<!---
Clearly detail what needs to be done to achieve the goal set out above
--->
Search for existing frontend and backend flags. Remove these from the code.

## QA

<!---
Consideration is given to how the issue will be demoed and tested prior to being deployed
--->
QA will be required here

## 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

## 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)
--->
Devs :nerd: 

## 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
--->

- [ ] All legacy features flags are removed from backend **AND** frontend
- [ ] Unleash code removed
- [ ] Remove from settings.example.php

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 5.0
UXD: Highlight comments from Minds+ subscribers

<!---
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 reach and engagement for Minds+ subscribers by highlighting their comments in comment threads.

## What needs to be done

Make comments from Minds+ users stand apart from other comments by visually differentiating them.

## 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/QJiT80vS4yOyprLiafWfbM/Comments?node-id=107%3A1973&t=JIBcctypGnhH7h6Y-1)

**Web**

**Specs for Web**

![Screen_Shot_2023-03-06_at_2.32.39_PM](/uploads/e22f2753e6fdb1a59a1df48e56456f52/Screen_Shot_2023-03-06_at_2.32.39_PM.png)

![Screen_Shot_2023-03-06_at_2.18.20_PM](/uploads/f793d0eb4b215bd579ba28aecf1fc2bc/Screen_Shot_2023-03-06_at_2.18.20_PM.png)

**Dark Mode Example**

![Dark_Mode_1](/uploads/b0ea93e0af4b67f32a003c88fa46b4f7/Dark_Mode_1.png)

**Light Mode Example Replies Expanded**

![Light_Mode_1](/uploads/560d4a82861a00b4469384e82342b47d/Light_Mode_1.png)

**Light Mode Example Comment In Replies**

![Light_Mode_2](/uploads/e4e6f82e22b22f5f07ee84efba45e9d0/Light_Mode_2.png)

**Mobile**

**Specs for Mobile**

![Mobile_Specs](/uploads/7f02cd4e5c5079d4a4bc0199562c3281/Mobile_Specs.png)

![Light_Mode_Mobile](/uploads/c5606239ffcfddf29f069a7878111f01/Light_Mode_Mobile.png)

**Dark Mode**

![Mobile_Share_Comments](/uploads/8e3681722d4e7da5d66a29d5b42fafdd/Mobile_Share_Comments.png)

**Light Mode**

![Light_Mode_Mobile](/uploads/c4539f2150e85ae93496a367e14e8f03/Light_Mode_Mobile.png)



**Mobile**

## 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
--->

- [ ] ...

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 3.0