giseldo/neodataset huggingface dataset:
Refactor membership tiers

We need to adapt our paywalls to the new membership tiers ui. They should function like our old paywall / subscription tier

General
- [x] add a paywall tier dropdown to the monetize options on the new compose page
- [x] @jotto141 's note: so in the monetize section of composer, we need a below section that pulls any memberships that creator has already set up so they may easily post the content to those people only. @michaelfbradley
- [x] When a user creates or edits a post, they should be able to assign either a specific amount or select a membership tier
- [x] Make sure subscribers who have access to the tier can see content for their subscription level
- [x] Subscribers should access to all tiered content up to their subscription level



@markeharding @ottman what about tiers that exceed the single entity paywall amount? Should supporters get access to that if their tier contribution covers the individual cost? Or do we want to keep single amounts separate.

I am making an assumption here that 15 dollar subscriptions get access to 5, 10 and 15 dollar tiers

@michaelfbradley we need some input on the ui for creators assigning their content to a specific tier.

Story points: 2.0
Implement Shop tab for Pay Phase 2

Just adding the Support tiers for pay to the Channel Tiers

https://design.minds.com/hosted/web/michael/front%232070-pay/#artboard2

Ignore the service requests, those are for phase 3

As a consumer
- [x] Show the Memberships tiers on the new grid under the shop tab
- [x] Select button, Selected to subscriber and unsubscribe from the theirs
- [x] Confirm 
- [x] Reusable Panel version of the Support Tiers
    - [ ] Show the number of posts assigned to Support tier and the number of members
    - [ ] Enable payment options
    - [ ] Recurring transactions only
    - [ ] Wallet balance and Top up that should open the buy tokens dialog
- [x] Subscriber tiers
 
As a owner
- [x] Edit tiers
    - [ ] Edit opens the tier editor
    - [ ] Delete should confirm
- [x] Delete tiers
- [x] Subscriber tiers
   - [ ] Subscriber filters
   - [ ] Message to individual users should open messenger to that user
   - [ ] Message all will be handled in a later version once we redo messenger

General
- [x] Behind the pay feature flag
- [ ] Shop tab should only show up when the flag is one and when the user has tiers setup 
- [x] Use the new message designs for success, error, validation messages
- [x] Light mode / Dark mode
- [ ] E2E Tests
- [ ] Unit tests

Questions for @michaelfbradley and @markeharding 
What do we want to do about the other currencies, the current mocks only allows us to select from Token and USD
It looks like we should just add them to the list under method?

We need. a cancel or a back button to go back to the list.

Story points: 5.0
Implement the Feed tab for the new Channels

https://design.minds.com/hosted/web/michael/front%23-channel/#

Implement the new feed tab (read only mode, edit functionality is in another card)

- [x] Should handle route (/, /images, /videos, /blogs)
- [x] Feed activities in the new activity poster and pageable in the modal pager. can deactivate guard.
- [x] Using shared tab and layout pane (as main newsfeed) CSS
- [x] Show a count of scheduled posts (as a visual indicator that a channel has scheduled content
- [x] Add in a filter to feed
- [x] Channel information pane
- [x] Shop pane with current subscription tiers
- [ ] ~~Link to See All items in the Shop~~ (to be done when we enable Shop tab)
- [x] Responsive
- [x] "channels" feature flag
- [ ] ~~e2e tests~~
- [ ] ~~unit tests~~

Story points: 16.0
Create a reusable UI Component for filtering feeds

@michaelfbradley added a new filter widget to the channel feeds https://design.minds.com/hosted/web/michael/front%23-channel/#artboard0. This will provide our filtering options like we currently have for our feed algorithms, date ranges, and other media filter types. He still needs to design this component.

This is the card for making that filter a reusable, extensible component that we can use to power any feed.

- [x] Implement the filtering options with the new design
- [x] Light mode / Dark mode
- [x] Reusable filter component for any feed
- [ ] E2E tests
- [ ] unit tests
- [x] Responsive

Story points: 4.0
Rebrand the new support tier in our new Wire modals

Add in the Shop language onto the currency tabs of the new wire modal and in the channel sidebar

- [x] Selecting a support tier should check the repeat monthly box
- [x] "Subscriptions Tiers" should be change to "Support Tiers"
- [x] Read channel sidebar Support Tiers from new endpoint
- [x] Explore shop should take the user to the channel's shop page
- [x] Read Pay modal Support Tiers from new endpoint


Story points: 1.0
2020 Roll out Notifications View, tab inconsistencies

https://walrus.minds.com/notifications

Some icons have labels some do not. Votes label is flush with icon while All label has space between icon and label

- [ ] All icons should have labels or none should
- [ ] icon position and space should be consistent between tabs

![image](/uploads/82aead3b4fb17d7e8c0b4cc1ef5b5e52/image.png)

Story points: 2.0
Add a new blog composer style window

- [ ] Reuse the new compose modal and as much CSS (tabs, windows, buttons) as we can
- [ ] When clicking the "Create Blog" button, the editor should open up in a new modal window
- [ ] Editing a blog should be set in a new modal window
- [ ] All the existing blog widgets (NSFW, Monetize, Hashtags, Schedule, License) should update the blog
- [ ] Blogs should work in the existing modal pager and clicking them on the activity feeds should open the modal pager. Test this thoroughly, but if there's more work to be done, we'll create a separate card
- [ ] E2E tests
- [ ] Unit tests

MR
https://gitlab.com/minds/front/-/merge_requests/899

Story points: 20.0
Fixed Height boost issues

- https://walrus.minds.com/newsfeed/1061846855375249408
- https://walrus.minds.com/newsfeed/1090832425635254272
- https://walrus.minds.com/newsfeed/1090841986483769344
- https://walrus.minds.com/newsfeed/1090898826357788672
- https://walrus.minds.com/newsfeed/1090929320278085632

Story points: 2.0
Autoplay videos don't garbage collect property and too many causes them to stop streaming

@markeharding had to disable the autoplay here https://gitlab.com/minds/front/-/commit/6e3297cf9c1f14a6f2ea4a91f32848fbc019610f

From Zulip:

```
John: Re the video play.... I think the problem is super long time to load video. I cannot tell if it is network isue or on our side, but I am using 100Bm service

Bill Ottman: It is a minds bug has to be

John: WE need to address the jitsi 2 user issue also

Mark Harding: Chrome has a socket limit of around 6 players, looks like when you scroll past these aren't being garbage collected properly

Mark Harding: I don't think it's a quick fix so we might want to temporarily disable if it's a big issue

John: I tested on Peggy's mac on FF and it was also a problem

Bill Ottman: Mark Harding said:

I don't think it's a quick fix so we might want to temporarily disable if it's a big issue

yes disable until fully working
```

It also looks like ngx-player removed the types from their component so we might be able to get rid of our forks while we're at it


We need to verify that pro users get this functionality as well. 

Here's where projecthttps://gitlab.com/minds/engine/-/blob/master/Entities/User.php#L983

Story points: 4.0
Wallet 2.0 ETH address not reliable

Something isn't working in the wallet-v2.service's `getEthAccount()` function `await this.web3Wallet.getCurrentWallet()`.  

The ETH settings component is supposed to conditionally show one's ETH balance and a button to buy Ether, based on whether the wallet service detects an ETH address. But the balance/button aren't always showing, even if you have an ETH address.

@jotto141  says: 
- "ETH balance is reading 0 despite having MetaMask synced, connected and containing a balance"
- "It is working after i unlinked and then reconnected my Metamask. We should make sure people with existing ETH addresses set up don't need to do that -- if they do, we should tell them somehow."

Story points: 1.0
hellominds tag being incorrectly applied

<!---
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

hellominds tag is being incorrectly applied whenever a user posts.

### Steps to reproduce

See hellominds feed - unsure how to replicate locally.

### Platform information 

Web

### What is the current *bug* behavior?

Users who have posts are appearing

### What is the expected *correct* behavior?

Only users first posts should appear

### Relevant logs and/or screenshots

![image](/uploads/aba2da33f5bfa4ea05266bbad991e1ba/image.png)

### Possible fixes

As highlighted by @markharding perhaps we should migrate the check for whether a user has made post to an ES count query as it's possible the ACL is stripping things out the way we are currently getting it. This is just an idea though, the issue could be something else. It could be for example, scheduled posts showing in that query.

Story points: 2.0
Web: Create Boost flow from 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

Enable users to create Boosts (channel + activity Boosts) from the Boost console so that more Boosts can be made.

## What needs to be done

Enable a user to create a Boost from the Boost console.

- Channel Boost (can use existing "Boost channel" modal)
- Activity Boost (can use new "Boost latest post" flow)

## QA

<!---
Consideration is given to how the issue will be demoed and tested prior to being deployed
--->


<!---
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=1289%3A23979&t=4NEzNgVJFOP9qobH-1)

![1_Boost_Post_From_Console](/uploads/0db527111a5bf92445347e43b2314ec0/1_Boost_Post_From_Console.png)

![2_Boost_Channel_From_Console](/uploads/1c8d42dc334bb158d418534151d20d51/2_Boost_Channel_From_Console.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
--->

- [ ] Display the InFeed notice for the Boost Latest Post

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 2.0
Many requests firing for Boost entities on page load (currently sandbox only)

<!---
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

Duplicate reqs

### Steps to reproduce

1. Load sandbox
2. See request spam to entities endpoint for boosts as per screenshot

### Platform information 

Web

### What is the current *bug* behavior?

Request spam

### What is the expected *correct* behavior?

Should not have request spam

### Relevant logs and/or screenshots

![image](/uploads/92022b8b399dd835824e121fa9c8b0e5/image.png)

### Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Story points: 3.0
Temporarily remove upload custom thumbnail option from composer videos

<!---
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
--->
Temporarily remove upload custom thumbnail option from composer videos

It is not working due to issues addressed in https://gitlab.com/minds/minds/-/issues/3911

## What needs to be done

<!---
Clearly detail what needs to be done to achieve the goal set out above
--->
Comment it out but leave the code until we decide whether it's worth keeping

## QA

<!---
Consideration is given to how the issue will be demoed and tested prior to being deployed
--->
custom thumbnail option from composer videos

## 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?
--->

- [x] Is Mobile Required?

## Personas

<!---
Who does this user impact and why (optional)
--->
Video-uploading creators

## 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
--->
- [ ] Composer custom thumbnail option for videos is commented out

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 0.0
Minds+ comment highlight highlighting the comment notifications

<!---
Please read this!

Before opening a new issue, make sure to search for keywords in the issues
filtered by the "T - Bug" label and verify the issue you're about to submit isn't a duplicate.
--->

### Summary

Minds+ comment highlight highlighting the comment notifications

### Steps to reproduce

1. get a notification for comment from Minds+ accont
2. see that it's colored like a comment would

### Platform information 

irrelevant

### What is the current *bug* behavior?

comments highlighted in notifications

![Screenshot_2023-04-03_at_17.14.01](/uploads/f763af1e4001bc3030deaca0a390bca2/Screenshot_2023-04-03_at_17.14.01.png)

### What is the expected *correct* behavior?

comments only highlighted in comments

### 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
Inconsistent Character Case Within Channel Based Boost Horizontal Three-Dot Menu

<!---
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 recently implemented channel based boost horizontal three-dot menu contains the "Hide post" option. This option includes a lower case "p" at the beginning of the word "post" whereas all the other options each word with an upper case letter.

### Platform information 

Platform neutral. Browser interface.

### What is the current *bug* behavior?

Inconsistent case

### What is the expected *correct* behavior?

Sentence case for all 

### Relevant logs and/or screenshots
![issue_front_5947](/uploads/abe726d49c752a6d48a5f11eeeb1726c/issue_front_5947.png)<br>
<i>Channel based boost horizontal three-dot menu examples.</i>

Story points: 1.0
Remove "Pending transfers" from wallet

<!---
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
--->

Increase comprehension of the wallet by removing the "Pending transfers" number from the Cash tab. It's confusing and not helping.

## What needs to be done

<!---
Clearly detail what needs to be done to achieve the goal set out above
--->

Remove the Pending transfers section from the cash tab of the wallet.

![image](/uploads/288279455fc5c9299afb03b946f2e861/image.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
--->

- [ ] The pending transfers column is removed from Cash wallets

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 1.0
No subscriber badge appears next to username in comments if user is Pro subscriber

<!---
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

We now highlight comments of Minds+ users and show their Minds+ subscriber badge next to their name.

If a user is subscribed to Minds Pro, they also enjoy this benefit, but their subscriber badge does not appear.

### Steps to reproduce

View a comments thread with a comment by a Minds Pro subscriber.

e.g. https://www.minds.com/newsfeed/1480596801789628432

### Platform information 

- Web

### What is the current *bug* behavior?

- The comment is highlighted
- No subscriber badge appears for Minds Pro subscribers

### What is the expected *correct* behavior?

- The comment is highlighted
- A Minds Pro subscriber badge appears next to the username of Pro subscribers
- A verified badge would be displayed if the user is verified

### Relevant logs and/or screenshots

![image](/uploads/30c1d5d96c4df1f7e37af72729535389/image.png)

![image](/uploads/d8060591babe577bd8f15c3f02895966/image.png)

### Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Story points: 1.0
E2E fixes

<!---
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

Deflake E2E

### Steps to reproduce

(How one can reproduce the issue - this is very important)

### 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
Web: Modify referral cookie logic

<!---
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
--->
In order to expand the affiliates program, we wish to be able to use the referral links for logged in users too. The tags can then be used to attribute the referrer. 

## What needs to be done

<!---
Clearly detail what needs to be done to achieve the goal set out above
--->

See AC below

## 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)
--->
Affiliates

## 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
--->

- [x] Referral cookies will be overwritten by the last referral link visited
- [x] Referral cookies will expire after 72 hours
- [x] Referral cookies should work for existing logged in users
- [x] Integration tests for ensuring the cookie logic is as above

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 3.0
Free trial offer in wire modal for USD

<!---
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

Free trial offer in wire modal for USD

### Steps to reproduce

Open modal to wire a channel and hit the USD tab

### Platform information 

Web

### What is the current *bug* behavior?

See free trial offer

### What is the expected *correct* behavior?

Should see no such offer - plus modal should have this [TBC]

### Relevant logs and/or screenshots

![image](/uploads/ae3ec1ddbef3970c265fdfbe913a346f/image.png)

### Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Story points: 1.0
Verify uniqueness notice has no constraints on when to show beyond experiment

<!---
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

Verify uniqueness notice has no constraints on when to show beyond experiment

### Steps to reproduce

With feat flag on see notice every time regardless of whether you're verified.

### Platform information 

Engine

### What is the current *bug* behavior?

Notice shows every time, blocking other notices.

### What is the expected *correct* behavior?

If you're verified it should not show

### Relevant logs and/or screenshots

![image](/uploads/28e896c7ba2305b49fa3a55570b0cd9e/image.png)

### Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Story points: 1.0