giseldo/neodataset huggingface dataset:
Paywalled status quotes crunched

<!---
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
--->
Make the whole "unlock" button visible on paywalled status quote posts

## What needs to be done

<!---
Clearly detail what needs to be done to achieve the goal set out above
--->
This is happening on quotes of paywalled status posts
sidebar/minimal mode:
![image](/uploads/679d9e4191f1bc6127291a0ec6ed3a57/image.png)


feed: 
![image](/uploads/4de7be96fe327fbf1da34968751b5d9c/image.png)

## QA

<!---
Consideration is given to how the issue will be demoed and tested prior to being deployed
--->
quotes of paywalled statuses should have enough space so the entire 'unlock' button is visible

## 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)
--->
all 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.
--->
n/a

## Acceptance Criteria

<!--
Everyone should be able to understand what is expected to be delivered
--->

- [ ] quotes of paywalled statuses look normal in the feed and sidebar in activities v1
- [ ] quotes of paywalled statuses look normal in the feed and sidebar in activities v2


## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 2.0
Withdrawals getting stuck PENDING

<!---
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

Many withdrawals seem to be getting stuck in pending and not coming through to the admin queue.

### Steps to reproduce

Unknown

### Platform information 

Engine runners?

### What is the current *bug* behavior?

Withdrawals get stuck pending and are not moved to pending approval - tokens do seem to be debited.

### What is the expected *correct* behavior?

Should auto-move through to pending_approval

### 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

initially we thought that this may relate into locks but it's not clear that this was the cause.

Story points: 0.0
NSFW locked post in sidebar is aligned wrong.

<!---
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

Image:

![image](/uploads/a8b474f88bc6b4d37289f7dde1f8338b/image.png)

### Steps to reproduce

1. Make sure you don't have NSFW posts unlocked
2. Go to this post: https://www.minds.com/newsfeed/1399779053900140552
3. See that the "I am over 18 years of age" is aligned wrong

### Platform information 

Activities v1 AND v2

### What is the current *bug* behavior?

Bad alignment on NSFW unlock button in sidebar

### What is the expected *correct* behavior?

I am over 18

### 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
Regression: Comments go out of line horizontally

### Summary

Comments go out of line horizontally

### Steps to reproduce

1. Open minds web.
2. Navigate to Feed.
3. Tap on Comments button on a post with comments.
4. Notice that long comments are going out of line. 

### Platform information 

iPhone SE - Chrome

### What is the current *bug* behavior?

Comments are getting truncated horizonatally.

### What is the expected *correct* behavior?

Comments should wrap inline successfully. 

### Relevant logs and/or screenshots

![image](/uploads/45ba03d9a52c9c81c9d44c21c446da89/image.png)

Story points: 3.0
See Latest Posts button not scrolling back to top of newsfeed

<!---
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

(Summarize the bug encountered concisely)

See Latest post button is not scrolling to the top of the newsfeed when clicked.

![Screen_Recording_2022-07-28_at_12.23.22_PM](/uploads/d7323993a13d3cd3ea20b79bb1efc07c/Screen_Recording_2022-07-28_at_12.23.22_PM.mov)

### Steps to reproduce

(How one can reproduce the issue - this is very important)

1. Scroll deep in newsfeed with active subscriptions
2. Wait until there are latest posts to load
3. Click see latest posts and see where the scroll takes you.

### Platform information 

(Browser, device, system stats, screen size)

iOS, macbook, brave browser

### What is the current *bug* behavior?

(What actually happens)

See summary

### What is the expected *correct* behavior?

(What you should see instead)

See latest posts button should always take you to very top of newsfeed with new posts loaded

### 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
Remove horizontal scroll on homepage

<!---
Please read this!

Before opening a new issue, make sure to search for keywords in the issues
filtered by the "T - Bug" label and verify the issue you're about to submit isn't a duplicate.
--->

### Summary

A horizontal scroll bar appears on the homepage.

### Steps to reproduce

- Log out
- Navigate to minds.com

### Platform information 

- Windows + Chrome
- MacOS + Chrome (w/ scrollbars displayed enabled)

### What is the current *bug* behavior?

- The page is slightly wider than the viewport.
- A horizontal scroll bar appears.

### What is the expected *correct* behavior?

- The page is not wider than the viewport.
- No horizontal scroll bar appears

### Relevant logs and/or screenshots

![image](/uploads/250a765bc68dcb487e0f1ba2d927eaa1/image.png)

### Possible fixes

Set the width of the background image behind the header to `100%` (instead of the current `100vw`).

Or investigate why `100vw` is not behaving as expected.

Story points: 1.0
Retire 'minds-button-user-dropdown' and 'm-modal--ban components'

<!---
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
--->
Keep our code base clean by removing redundant components.

The `minds-button-user-dropdown` and `m-modal--ban` components are only used in the pro footer (which is only realistically accessible on a pro site on mobile web).

## What needs to be done

<!---
Clearly detail what needs to be done to achieve the goal set out above
--->
- [ ] Replace the dropdown (and thus the ban modal) with `m-channelActions__menuButton` component.
- [ ] Once we do this we can also delete the `m-modal--ban` component and its related BanModule.

## QA

<!---
Consideration is given to how the issue will be demoed and tested prior to being deployed
--->
Make sure the pro footer channel menu component still works

## 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)
--->
Developers

## 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
--->

- [ ] Old dropdown menu replaced with new one
- [ ] Old dropdown menu deleted
- [ ] Old ban modal deleted

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 2.0
Minor alignment and copy issues

<!---
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
--->
Make sure the site looks polished

## What needs to be done

<!---
Clearly detail what needs to be done to achieve the goal set out above
--->
- [ ] badges in channel About page not flush with left side
- [ ] friendlycaptcha not flush with left side of register
- [ ] The green highlighter on marketing pages is not working and should be removed
- [ ] Composer NSFW tab spacing below link is cramped
- [ ] Branding page padding above title is cramped
- [ ] Two-factor form recovery code link shouldn’t be in the form of a question

<details><summary>Click to see screenshots</summary>
![image](/uploads/a1b507ad484a4b699b9a91af36abceaf/image.png)
![image](/uploads/b07c83d797da54bd6350773465311469/image.png)
![image](/uploads/c58f973aad11f5404da9dd6ed174f537/image.png)
</details>


## QA

<!---
Consideration is given to how the issue will be demoed and tested prior to being deployed
--->
Visual assessment

## 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, unless we want to replace the green highlighter on marketing pages with something else

## Personas

<!---
Who does this user impact and why (optional)
--->
Detail-oriented 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.
--->
N/a

## Acceptance Criteria

<!--
Everyone should be able to understand what is expected to be delivered
--->

- [ ] All items listed above have been addressed

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 2.0
Consistent onboarding form font size

<!---
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
--->
Make a good first impression on new users

## What needs to be done

<!---
Clearly detail what needs to be done to achieve the goal set out above
--->
- Make sure the onboarding "Setup Channel" form fields are the same size

Right now the Display name is smaller than the bio.
![image](/uploads/a6e14ad9f2db588bc6f98f4af756c73e/image.png)

## QA

<!---
Consideration is given to how the issue will be demoed and tested prior to being deployed
--->
Onboarding "setup channel" form inputs are consistently sized

## 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)
--->
- New users going through onboarding

## 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
--->

- [ ] Font size for inputs on onboarding forms is consistent

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 1.0
Refactor boost console so we can remove legacy button component

<!---
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 unnecessary `minds-button` component from codebase

## What needs to be done

<!---
Clearly detail what needs to be done to achieve the goal set out above
--->
- refactor the `minds-button` being used in the boost console and use `m-button` instead

## QA

<!---
Consideration is given to how the issue will be demoed and tested prior to being deployed
--->
Make sure the refactored button still does what it is supposed to do

## 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)
--->
Developers

## 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
--->

- [ ] `minds-button` component instance replaced with `m-button`
- [ ] `minds-button` component deleted

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 1.0
Remove unused youtube migration components

<!---
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
--->
Many features of the youtube migrator are no longer used. We should remove the unused code.

## What needs to be done

<!---
Clearly detail what needs to be done to achieve the goal set out above
--->
Remove unused youtube migrator files. The only ones still relevant should be `m-youtubeMigration` and `m-youtubeMigration__connect`.

## QA

<!---
Consideration is given to how the issue will be demoed and tested prior to being deployed
--->
Remaining youtube migration components should still work

## 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)
--->
Developers

## 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
--->

- [ ] unused youtube migration code removed

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 1.0
Remove Connect Wallet/Balance component from mobile web top bar

<!---
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 wallet+balance button from the mobile web top menu.

## What needs to be done

<!---
Clearly detail what needs to be done to achieve the goal set out above
--->

Remove the wallet connect+balance component form the header.

![image](/uploads/4b08a7fc5ca5cb8d9d5b84e7ab00358a/image.png)

## QA

<!---
Consideration is given to how the issue will be demoed and tested prior to being deployed
--->


## UX/Design

n/a

## Personas

n/a

## Experiments

n/a

## Acceptance Criteria

<!--
Everyone should be able to understand what is expected to be delivered
--->

- [ ] Remove Connect Wallet/Balance component from mobile web top bar
- [ ] When search is focused, the notification bell + avatar are not pushed off screen

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 1.0
Tapping body of post should open full post page

<!---
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 it easier to get to an individual activity post page with comments.

## What needs to be done

From feed views, make activity posts (v2 only) click to the single activity post URL.

## QA

<!---
Consideration is given to how the issue will be demoed and tested prior to being deployed
--->


## UX/Design

Example activity post in a feed. Magenta areas indicate clickable areas that would navigate the user to the single post page.

Media post:

![image](/uploads/af6c98c6f09bcd0d5f33050fd8ab929e/image.png)

Text post:

![image](/uploads/4c5e2c68f56624ec5a23a02740b596ef/image.png)

## Personas

Core users

## Experiments

- ???

## Acceptance Criteria

- [ ] Reflect only on v2 component
- [ ] When a user clicks any portion of the activity post not already dedicated to another action, then the user is navigated to the single activity post page.
- [ ] If the user clicks and drags (e.g. to highlight text), then the user is NOT navigated to the single activity post page.
- [ ] If the user middle-clicks the new click area, then the single activity post page is opened in a new tab.
- [ ] If the user hovers over the new click area, then the mouse cursor displays a `cursor: pointer;` style.

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 3.0
Distinguish Quote Post from Remind counters and display Quote 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

Make quote posts more accessible from the originating post.

## What needs to be done

On a standalone activity post page, display counters + buttons separately for reminds and quote posts.

Clicking the `quoted posts` button displays a modal displaying the related quote posts.

## QA

<!---
Consideration is given to how the issue will be demoed and tested prior to being deployed
--->


## UX/Design

Screenshot below for reference. [See Figma mocks for latest design spec](https://www.figma.com/file/oYPYya9Z4G5wqgLvdKDbOB/Activity-Post-revised-%5BWeb%5D?node-id=191%3A3451).

![image](/uploads/2c658ed6a9917aea2da0a2b0deac584c/image.png)

## Personas

Core users.

## Experiments

n/a

## Acceptance Criteria

- [x] Re-enable https://gitlab.com/minds/engine/-/blob/master/Core/Feeds/Events.php#L76
- [x] Improve caching controls, update cache on every quote post
- [x] Add a feature flag so we can control 
- [x] Given a post has been quoted in a quote post, when viewing the activity post page for the originating post, then a counter is displayed for the total number of times it's been quoted in quote posts.
- [x] Given the quote post counter is displayed, when the user clicks on the counter, then a modal appears with the contents of the quoted posts displayed.

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 5.0
Remind count not showing in feeds (V2 activities)

<!---
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

Remind counts are not showing on posts in the Newsfeed with the v2 activities.

### Steps to reproduce

- [View Timcast's feed](https://www.minds.com/Timcast/)

### Platform information 

All

### What is the current *bug* behavior?

- Remind counts are not displayed on the activity posts.

### What is the expected *correct* behavior?

- Remind counts are displayed alongside the remind icon, like upvote counts.

### Relevant logs and/or screenshots

![image](/uploads/888a27b6eb59169dd3065b40b39c7c34/image.png)

### Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Story points: 2.0
Don't show top post push notif for your own 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

Bill reports getting Top Post push notifications for content he published.

### Steps to reproduce

Presumably...

- Use an account that doesn't follow anyone posting new content
- Post your own content
- Wait 24 hours for a Top Post notification

### Platform information 

- Android app

### What is the current *bug* behavior?

- A Top Post push notification is sent for content you authored

### What is the expected *correct* behavior?

- A Top Post push notification is never sent for content you authored

### 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

- Exclude with 'must_not' from the Elastic query
- Ensure logging on CLI job to aid with testing

Story points: 2.0