giseldo/neodataset huggingface dataset:
Web: Newsfeed tabs

<!---
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
--->

To consolidate some of our discovery / curated content within a single pageview, so that users are served more relevant content at their fingertips.

A tab navigation for the Newsfeed will enable more options to present users to encourage engagement.

## What needs to be done

- Swap current Newsfeed controls (navigating between Top and Latest) with pattern below.
- Maintain and respect the same user preference for which tab to load by default when the user visits the Newsfeed

## 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.
--->

New design:

![feed-design-1.0](/uploads/e88cffda8da90aecf538d0a3530b421b/feed-design-1.0.png)


Note - do not include ellipsis menu, user is only switching between two persistent views.

## 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.
--->

n/a

## Acceptance Criteria

<!--
Everyone should be able to understand what is expected to be delivered
--->

- [ ] Tab bar is introduced for newsfeed and the Title/Dropdown block is removed.

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

UXDL

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/1ed9eacc5fdb485a19d6a0da1b288cc5/1_Boost_Post_From_Console.png)

![2_Boost_Channel_From_Console](/uploads/459cb310946af89811d40e693baae8d0/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
UXD: Indicate comment is misclassified as spam

<!---
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 community feedback on our automatic spam detection to improve the system and build trust in the community.

## What needs to be done

- Given comments in a specific thread are marked as suspected spam
- and the comments are initially hidden behind a spam wall
- when a user clicks to reveal the comments
- the user has an option to indicate that they think a specific comment is misclassified / is not spam.

## 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-comments-flow-web](/uploads/9947a54d729eac4a7815fc27b3b338df/spam-comments-flow-web.png)

![spam-comments-flow-mob](/uploads/a7c4dd2b0f857f0388b12595bcec67e4/spam-comments-flow-mob.png)

[Figma](https://www.figma.com/file/QJiT80vS4yOyprLiafWfbM/Comments?node-id=262-11702)

## 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
Automatically tag the first post a user makes

<!---
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 on-site discovery -- both by Minds staff and its community -- of first posts from newly-registered users on Minds.

## What needs to be done

- Given a channel has never made a post before,
- when the channel makes its first post,
- then add the tag `hellominds` to the activity post in the background.

## QA

<!---
Consideration is given to how the issue will be demoed and tested prior to being deployed
--->


## UX/Design

n/a

## Mobile

<!---
Does a mobile card need to be created? Any notes for mobile?
--->

- [ ] Is Mobile Required?

## Personas

New Minds user who does not already have a social circle to take part in.

## Experiments

n/a

## Acceptance Criteria

<!--
Everyone should be able to understand what is expected to be delivered
--->

- [ ] On the SearchIndexerSubscription, detect if it is a users first post, append the 'hellominds' tag to the ElasticSearch document

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 2.0
UXD: Refresh Groups home feed design

<!---
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 aggressive, confident experimentation with Groups as a vehicle for user retention by refreshing the home feed screen to use modern design system and UI.

## What needs to be done

Refresh the home feed layout for web + mobile app using the modern design system.

Include a solution for managing settings for the group.

![image](/uploads/ca6ae359308f1504e96b54a73c29428e/image.png)

Assume that functionality available on the members list screen can continue to be served by the existing page without refreshing it, since that page isn't critical to Groups usability for most users.

## 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/ejrtrI9rNJjZYUcVw8U5iS/Groups-Refresh?node-id=21%3A1152&t=8b0JMH5PdAF4aYmz-1)

![updated_groups_1](/uploads/3529f397c853c1e4ce25f0428a9cdb97/updated_groups_1.png)

![Groups_Refresh_Mobile](/uploads/2f6e8d31897bfb1bba40c68937fc95d0/Groups_Refresh_Mobile.png)

![Groups_Refresh_Mobile_2](/uploads/26c19ba714340c9fab2050ea2c93844f/Groups_Refresh_Mobile_2.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: 5.0
Video content not playing

### Summary

Video content on random posts appears to be "broken", returning only a black screen when trying to play the content. I'm told that the problem could be specfically with pre-cloudflare streams content.

### 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?

black screen

### What is the expected *correct* behavior?

(What you should see instead)

### Relevant logs and/or screenshots

the main content of this post shows the bug
https://www.minds.com/newsfeed/1213184489865510912

use this task as a running list of other such content

### Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

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/0d377391eabcc635023a82b76a6d3e4e/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
Analytics not showing earnings for past few days

<!---
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 minds+ earnings in analytics have flatlined in past few days

Reported by

- bashynx 
- timoburnham
- klara_sjo
- TomPeace

### Steps to reproduce

1. Have a channel with consistent minds+ posting/earnings
1. go here: https://www.minds.com/analytics/dashboard/earnings
2. Notice, that the earnings for Minds+ don't show for the past few days

### Platform information 

irrelevant

### What is the current *bug* behavior?

Analytics shows wrong data

### What is the expected *correct* behavior?

Analytics should show correct data

### 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
Multiplier not being counted

<!---
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

Multiplier stopped showing correct number.

Impact: Active users are not getting rewards for their additional activity on the site.

### Steps to reproduce

1. Have an account that has been posting daily
2. Look through the calendar at https://www.minds.com/wallet/tokens/rewards, and see what engagement multiplier you have
3. Notice it's been dropping, and is probably at around 1

### Platform information 

irrelevant

### What is the current *bug* behavior?

Wrong multiplier

### What is the expected *correct* behavior?

Multiplier should be correct

### Relevant logs and/or screenshots

I've looked through my profile, and I've been posting daily from 9th (besides 18th and 19th)

The multiplier went down to two on 21st, but there are weird instances of getting 1 among 3's on 5th and 19th:

![image](/uploads/08a7cc8ff8380882e8996bf1ea3c99b2/image.png)

Users who have alerted us to an issue with their multiplier

- \@bashynx
- \@fickleflame
- \@vindicator725
- \@Aragmar
- \@Yotivationnation

### Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Story points: 3.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/8d18e8e24acf12788391afb4da39a311/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
Cannot post - PDOExceptions

<!---
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

Cannot post due to PDOExceptions.

### Steps to reproduce

Try to post

### Platform information 

Web

### What is the current *bug* behavior?

Should be able to post, also reported you cannot see Boost console

### What is the expected *correct* behavior?

Should be able to post, also reported you cannot see Boost console

### 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
Chatwoot integration

<!---
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

Be able to engage live with logged-out and logged-in users to maximize retention, conversions and engagement. 

## What needs to be done

- [ ] Create logged out chat widget 

`
    <script>
      window.chatwootSettings = {"position":"right","type":"expanded_bubble","launcherTitle":"Chat with us now"};
      (function(d,t) {
        var BASE_URL="https://app.chatwoot.com";
        var g=d.createElement(t),s=d.getElementsByTagName(t)[0];
        g.src=BASE_URL+"/packs/js/sdk.js";
        g.defer = true;
        g.async = true;
        s.parentNode.insertBefore(g,s);
        g.onload=function(){
          window.chatwootSDK.run({
            websiteToken: 'hTsptQ5idnWS11PVaq1EbT1n',
            baseUrl: BASE_URL
          })
        }
      })(document,"script");
    </script>
    `
- [ ] It is required that we host the js ourselves
- [ ] Create logged in chat widget (https://www.chatwoot.com/docs/product/channels/live-chat/sdk/identity-validation)

## QA

Test button

## UX/Design

N/A - call on design if needed.

## Mobile

- [ ] Is Mobile Required?

Not initially.

## Personas

Users in need of assistance

## Experiments

https://growthbook.minds.com/features/minds-3897-chatwoot

## Acceptance Criteria

<!--
Everyone should be able to understand what is expected to be delivered
--->
- [x] Create logged out chat widget 
- [x] Create logged in chat widget (https://www.chatwoot.com/docs/product/channels/live-chat/sdk/identity-validation)
- [x] Host JS Ourselves
- [x] Ensure no tracking cookies are added

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 3.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/7d86a112429b90f8b1bde527306b9b86/image.png)

![image](/uploads/62c750db6747816e2224d0ec54e69ba3/image.png)

### Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Story points: 1.0
UXD: Customize links in 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

Enable cash advertising customers to better control the presentation of their Boosts to improve their click through rates.

## What needs to be done

- A mechanism that enables a Booster to customize the thumbnail of the link in their post.
- A mechanism to add a custom call to action (CTA) button on a Boost with a link.

## 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 Web](https://www.figma.com/file/W2xIag64EdbWUlGAQOpVHE/Boost-Update?node-id=1499%3A29311&t=MM65JewdiGMxQjlD-1)

[Figma Mobile](https://www.figma.com/file/W2xIag64EdbWUlGAQOpVHE/Boost-Update?node-id=1392%3A34632&t=e2pyN1ddfi1oOsMg-1)

## Mobile

<!---
Does a mobile card need to be created? Any notes for mobile?
--->

- [ ] Is Mobile Required?

## Personas

<!---
Who does this user impact and why (optional)
--->


## Experiments

<!---
Experiments are not required, but it should be made clear if one is expected. If experiments are required, the hypothesis should be outlined.
--->


## Acceptance Criteria

<!--
Everyone should be able to understand what is expected to be delivered
--->

- [ ] ...

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 5.0