giseldo/neodataset huggingface dataset:
Cannot Boost blog entities

<!---
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

Blog entities can not be boosted currently - only the activity in your "all" filtered channel page or a global feed like the newsfeed and discovery.

# Areas of known failure
- SEP (we seem to be linking through to the entity guid for blogs rather than the GUID when clicking timestamp, thus it fails).
- Blog page.
- Blog filtered channel feed.

### Steps to reproduce

Try to boost a blog from either the filtered channel feed by blog OR from the actual blog page its self.

### Platform information 

Web, likely mobile too.

### What is the current *bug* behavior?

Cannot Boost a blog from these places because it is not an activity.

### What is the expected *correct* behavior?

**TBC** - options include

- Have a check in the boost endpoint that looks up linked activities for Blogs and boosts that.
- Export the activity GUID with the blog and Boost the activity GUID from the front end
- Get rid of Boost buttons for these entities / warn on click / redirect to the activity if possible.
- Anything else?

### Relevant logs and/or screenshots

![image](/uploads/6b1ac25c1b35ae185971781b23c55e91/image.png)

### Possible fixes

Some efforts were undertaken during the development of #3773 (despite being outside of the AC) which are [outlined here](https://gitlab.com/minds/minds/-/issues/3773#note_1299114625) to make the filtered channel page show activities for Boosts - however, this was not possible as there is no indexed value that uniquely identifies blogs under `minds-search-activity`. It was then noticed that this also applies to Boosting directly from the blog page.

Story points: 3.0
Add Boost to SEPs

## Goal

As a Minds, I want to increase Boost inventory supply so that I can better fulfill the demands of customers.

As a creator, I want to earn revenue from Boost partners by serving Boost inventory on my pages.

## What needs to be done

Add a channel boost slot to sidebar on desktop SEPs.

## 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=624%3A15232&t=2b8qBAuf6eUwpZrw-1)

**SEP Channel Boost in Sidebar**

![SEP_Channel_Boost_Sidebar](/uploads/1e5457d815cc20903ee06706a1c3d783/SEP_Channel_Boost_Sidebar.png)

## Personas

<!---
Who does this user impact and why (optional)
--->


## Experiments

<!---
Experiments are not required, but it should be made clear if one is expected. If experiments are required, the hypothesis should be outlined.
--->
Use the boost partner experiment

## Acceptance Criteria

- [x] Display one single boost on the single entity pages
- [x] Do not display the boost if the the content owner has disabled serving boosts
- [x] Ensure client meta 'served by' is set

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 3.0
Cant make posts into minds+

<!---
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 wanted to post something into plus, but was unable to because of internal server error

### Steps to reproduce

1. Try creating a post (image or text)
2. See that you get an error on trying to submit (checkbox checked, hashtags added)

### Platform information 

win10, brave

### What is the current *bug* behavior?

Cant post into plus

### What is the expected *correct* behavior?

Should be able to post into plus

### Relevant logs and/or screenshots

![image](/uploads/912ec087eee44e2fb443df5910c1d4d2/image.png)

### Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Story points: 0.0
UXD: Hide suspected spam comments

<!---
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 impact of spam by hiding comments that are suspected of spam.

## What needs to be done

We can automatically identify that comments are spam with a high degree of accuracy, but still want human review before they're removed from the site. When a comment is automatically identified as spam -- but before human review -- we should hide the comments from view, and enable the community to show the comments and give feedback about whether or not the automatic spam detection was accurate.

[We got some feedback from the community about a feature like this here](https://www.minds.com/newsfeed/1437588985613389832).

## 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.
--->



![spam-desktop-flow](/uploads/058ece18040f14aabed0e0de627a8868/spam-desktop-flow.png)

![spam-mobile-flow](/uploads/9dbfd27935547e929725a41d77217e02/spam-mobile-flow.png)


## Mobile

<!---
Does a mobile card need to be created? Any notes for mobile?
--->

- [ ] Is Mobile Required?

## User testing

<!---
Who does this user impact and why (optional)
--->

- Link to draft -> https://www.notion.so/chints98/Minds-spam-comments-userbrain-test-draft-e4c52c7020ce4e499f4a48c578bf7532?pvs=4

## 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

UXD:

Story points: 3.0
UXD: Used a dot to indicate new content in 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 engagement and new channel discovery by increasing visits to the Discovery tab.

## What needs to be done

Use a notification dot on the nav icon for Discovery that indicates new content.

## 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/tHjd7fqgBiiTHRTNq5Ltfp/Web---Composer-and-Sidebar-updates?node-id=223%3A7879&t=89HUIWTvGeOE6Dx0-1) contains animation and hover states

**Web**

![Dot_Over_Discovery](/uploads/c4e132ea648beeba812c61bfe14a8c21/Dot_Over_Discovery.png)

**Spec sheet Web**

![Screen_Shot_2023-03-06_at_4.07.32_PM](/uploads/1f02f93952a39391b744d590d1f7d493/Screen_Shot_2023-03-06_at_4.07.32_PM.png)

**Mobile**

![Search_Mobile](/uploads/0dc88b6fc66a4fbc85e040e4459b166d/Search_Mobile.png)

**Spec sheet Mobile**

![Search_Mobile](/uploads/dfc1d9f410826792fa2766a5a9919ce6/Search_Mobile.png)

## 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: 2.0
UXD: Update Boost Console location in mobile settings

<!---
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
--->


## 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/jscTsxloVCRPwAm4LM2E6g/Navigation-Links-Update?node-id=24%3A309&t=FHCMY2tLdWUZwjNV-1)

**Surface the 'Boost' setting above Supermind on mobile**

![Menu](/uploads/db685295296ee6ba81ae9ada6cfdf0da/Menu.png)

**Remove 'Boost Console' setting option under settings**

![Remove_Boost_Console_setting](/uploads/54f0e225cce5871f9a8014ad12d411c3/Remove_Boost_Console_setting.png)



## 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: 2.0
Migrate new user marketing emails to Mautic

<!---
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

Move new user onboarding emails to Mautic for more rapid testing and iteration cycles.

## What needs to be done

Stop sending the following emails from the backend, and start sending them from Mautic.

- Welcome to Minds
- What do you think of Minds?
- Get paid for your posts
- Friends help friends

## 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
--->

- [ ] Stop sending the emails cited above from the backend
- [ ] Coordinate with Ryan to start sending those emails from Mautic

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 1.0
Record click events on links in activity posts

<!---
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

Improve Boost ROI by being able to report on how many clicks Boosts drive.

## What needs to be done

Record click events for links in activity posts.

Successful link clicks include:

- Clicking a link in the body of an activity post
- Clicking a link preview in an activity post
- Clicking to load/play an embed from a link (e.g. playing an embedded YouTube video)

If the activity post appears as a Boost, the click event should have context relating clicks to that Boost so that the Boost results can report clicks.

## 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
--->

- [x] Create a new topic for click events
- [x] Boosts should subscribe to the topic and update the boost summaries. Add a new column for clicks. 

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 5.0
Oldest Expired supermind was created on 4th January

<!---
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 looked into superset table for Supermind, and it seems like we have not had an expired Supermind for a while. Latest expired supermind was created on 4th January.

Checking supermind console, I can see that console claims a supermind has been expired, but in the apis it's status 1, Created

### Steps to reproduce

Check Superset and see no Superminds have been expired since 4th of Jan.

### Platform information 

Runners

### What is the current *bug* behavior?

Runners seem to be erroring out stopping new Superminds from being marked as expired.

### What is the expected *correct* behavior?

Should run without error.

### 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

See below comment

Story points: 2.0
Update Boost Settings UI to introduce new setting options

<!---
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

- Add value to Minds+ subscription prop
- Give Minds+ customers more control of their content
- Give content owners more control over how their content is presented
- Enable eligible customers to earn more from Boost partners by enabling more lucrative audience targeting

## What needs to be done

Enable Minds+/Pro subscribers to disable Boosts on their content, including channel pages, SEPs, etc.

Bonus if the control is exposed to non-subscribers and used as a point of converting to a Minds+ subscriber.

Give all users an option to enable/disable Controversial Boosts from appearing on pages they own (channel pages, SEPs, etc.).


## 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.
--->

See https://gitlab.com/minds/minds/-/issues/3699

## 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)
--->
Boosters

## Experiments

<!---
Experiments are not required, but it should be made clear if one is expected. If experiments are required, the hypothesis should be outlined.
--->
Boost partner epic

## Acceptance Criteria

<!--
Everyone should be able to understand what is expected to be delivered
--->

- [ ] UI implemented adhering to designs on https://gitlab.com/minds/minds/-/issues/3699
- [ ] Implement new configuration column value for boost serving
- [ ] Settings page should call a new endpoint that returns specific boost settings

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 5.0
UXD: Reorganize Boost navigation links

<!---
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

Make links to Boost console accessible and consistent with other patterns on the app / site.

## What needs to be done

Spec placements of Boost links in app / site navigation. Spec where links go to.

## 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/jscTsxloVCRPwAm4LM2E6g/Navigation-Links-Update?node-id=7%3A326&t=FHCMY2tLdWUZwjNV-1)

**Old Design**

![Old](/uploads/f879360c047e6cf98334f63310761f38/Old.png)

**New Design: Boost button will now open up the boost console similar to the Supermind button**

![New](/uploads/70a0ed71f3db0651cfe643b16dc2f8bd/New.png)

**Have an A/B test to show a profile dropdown with Boost Console swapped for Boost Channel**

![Profile_Dropdown](/uploads/5bd16196cd8d2dc393f76f08c8b00431/Profile_Dropdown.png)

## 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: 3.0
App crashes when opening camera for human detector

<!---
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

Michael Robinson reports that the Minds app crashes on his phone when opening the camera for the human detector.

### Steps to reproduce

- Launch the human detector
- Click `Continue` to navigate to the camera screen

### Platform information 

- Android I think

### What is the current *bug* behavior?

- The app crashes

### What is the expected *correct* behavior?

- The app opens the camera to read the numbers the user wrote down

### Relevant logs and/or screenshots

Michael Robinson may be able to provide diagnostics

### Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Story points: 3.0
Verification code notification covers the "Continue" button

<!---
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 in-app verification code notification covers the `Continue` button in the human detector and it's not obvious how to proceed.

### Steps to reproduce

- Launch the human detector
- Receive the in-app notification with the verification code

### Platform information 

- iPhone 12 Mini + iOS 16

### What is the current *bug* behavior?

- The `Continue` button is hidden behind the in-app notification

### What is the expected *correct* behavior?

- Design to recommend

### Relevant logs and/or screenshots

![image](/uploads/6239330c592edfb254c44b0a5155af5d/image.png)

### Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

- Move the Continue button to the bottom.
- Make the toast more visible.

Story points: 3.0
OCR can't read my writing

<!---
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 can't get the OCR for human detector to detect my writing.

I've not been able to complete the process with various attempts at writing the code.

### Steps to reproduce

- Start human detector
- Receive the verification code notification
- Write down on paper the verification code
- Tap "Continue"
- Fit the verification code into the box

### Platform information 

iPhone 12 Mini + iOS 16

### What is the current *bug* behavior?

The process times out without recognizing the verification code I wrote.

### What is the expected *correct* behavior?

The app detects the verification code I wrote and proceeds.

### Relevant logs and/or screenshots

![image](/uploads/995cfbf0cf7a2f24a097bbda241f2545/image.png)

![IMG_5FD82B54EF35-1](/uploads/4e7e57a849a25d900bd31c1cc698eab7/IMG_5FD82B54EF35-1.jpeg)

### Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Story points: 5.0