giseldo/neodataset huggingface dataset:
Remove the 'front-5229-activities' experiment flags

<!---
Please read this!

The Definition of Ready (DoR) can be found at https://developers.minds.com/docs/handbook/how-we-work/#definition-of-ready-dor

Before opening a new issue, make sure to search for keywords in the issues
filtered by the "Type::Feature" label and verify the feature you're about to submit isn't a duplicate.
--->

## What needs to be done

<!---
Clearly detail what needs to be done to achieve the goal set out above
--->

Remove to 'front-5229-activities' flag and remove the legacy activity component

## QA

<!---
Consideration is given to how the issue will be demoed and tested prior to being deployed
--->
TBD

## 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)
--->
Devs :nerd: 

## Experiments

<!---
Experiments are not required, but it should be made clear if one is expected. If experiments are required, the hypothesis should be outlined.
--->
...

## Acceptance Criteria

<!--
Everyone should be able to understand what is expected to be delivered
--->

- [ ] Remove the 'front-5229-activities'

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 5.0
Update boost modal to support paying with Cash

<!---
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
--->

Adding the ability to pay for Boosts in cash will increase revenue by monetising boosts via opening boost functionality to non token holders.

## What needs to be done

<!---
Clearly detail what needs to be done to achieve the goal set out above
--->

- Outcome from https://gitlab.com/minds/front/-/issues/5819

## QA

<!---
Consideration is given to how the issue will be demoed and tested prior to being deployed
--->

Testing the end to end flow

## UX/Design

<!---
Sufficient wireframes have been presented and understood by the development team. Full mockups are not required and re-usable components are encouraged.
--->

To be provided from https://gitlab.com/minds/front/-/issues/5819

## 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.
--->

Yes

## Acceptance Criteria

<!--
Everyone should be able to understand what is expected to be delivered
--->

- [ ] Frontend changes
- [ ] E2E tests

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 3.0
Single-image quote posting - can't open images in modal

<!---
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

Quote posts with single images don't allow the user to view the image in modal, there was a similar issue that happened for multiple images - https://gitlab.com/minds/front/-/issues/5802

### Steps to reproduce

- View [a quote post with single image](https://www.minds.com/newsfeed/1434299950975422479)
- Click an image

### Platform information 

- win10 + Brave

### What is the current *bug* behavior?

- Nothing happens

### What is the expected *correct* behavior?

- The clicked image opens in a modal view, similar to what happens on multi-image quote post - https://www.minds.com/newsfeed/1434300062447439886, or single image normal post
- Add E2E tests to verify modal opens for single & multi regular & quote posts. 

### Relevant logs and/or screenshots

### Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Story points: 3.0
Complete Metascraper Migration

<!---
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

Complete Metascraper Migration

## What needs to be done

- Migrate Twitter Sync.
- Migrate YT Sync previews.

## QA

Test Twitter sync and YT sync with previews still works.

## UX/Design

N/A

## Personas

YT and Twitter sync users.

## Experiments

Metascraper feat flag - Q. should we make another feat flag? 

## Acceptance Criteria

- [ ] Migrate YT previews.
- [ ] Migrate Twitter Sync previews.
- [ ] New feature flag

## Definition of Ready Checklist

- [x] Definition Of Done (DoD)
- [x] Acceptance criteria
- [ ] Weighted
- [x] QA
- [x] UX/Design
- [x] Personas
- [x] Experiments

Story points: 3.0
Adjust growthbook hasVariation function 'variation' input to default from 'on' to true

<!---
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
--->
The experiment hasVariation() function has 2 inputs. One is the experiment name and the other is an optional value. Currently the optional value is by default set to a string `'on'` but a Growthbook update has changed the way it works and we should now set it to a boolean `true` by default instead.

## What needs to be done

<!---
Clearly detail what needs to be done to achieve the goal set out above
--->
- change the default value from `'on'` to `true`
- Wherever we are already using `experimentsService.hasVariation()`, if it doesn't already have a 'variation' input, add one: `'on'`

## QA

<!---
Consideration is given to how the issue will be demoed and tested prior to being deployed
--->
Active experiments

## 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)
--->
n/a

## 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
--->

- [ ] experimentsService.hasVariation() fx second input defaults to `true` instead of `'on'`

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 1.0
Change connect Twitter modal to spawn in a new tab

<!---
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

Keep original tab open when loading Twitter auth modal

## What needs to be done
 
## QA

Test connect Twitter modal

## UX/Design

<!---
Sufficient wireframes have been presented and understood by the development team. Full mockups are not required and re-usable components are encouraged.
--->

## Personas

Users connecting Twitter

## Experiments

N/A

## Acceptance Criteria

- Evaluate design and what we want to do - continue button on success? Or keep design as is and just have it open the composer after you confirm.
- Make it spawn a new tab
- From engine - force close of the window with a fallback like https://gitlab.com/minds/engine/-/merge_requests/1161/diffs#1a4bca06fe1f05bdcca4c489a5cb2655b159643c_0_40
- May need polling logic to check for config updates as we will not get told by Twitter if there was a success.

## Definition of Ready Checklist

- [x] Definition Of Done (DoD)
- [x] Acceptance criteria
- [ ] Weighted
- [x] QA
- [x] UX/Design
- [x] Personas
- [x] Experiments

Co

Story points: 3.0
In-feed composer heights are messed up when images are present

<!---
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

In-feed composer heights are messed up when images are present

### Steps to reproduce

1. Upload an image in composer.
2. Close modal and see the in-feed composers displaying of the post.

### Platform information 

Web, replicated Firefox/Ubuntu

### What is the current *bug* behavior?

In-feed composer looks messed up

### What is the expected *correct* behavior?

- Can deactivate prompt should show if in dirty state
- .reset() should run on modal close
- Should look like in-modal composer.
- Should not have title.
- Should not have huge spacing at the bottom.

### Relevant logs and/or screenshots

![image](/uploads/e705b178058f54b61c705da3770f63a3/image.png)

### Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Story points: 3.0
Experiment: Alternative Supermind button

## Goal

Increase Supermind purchases.

## What needs to be done

Implement a new design for Supermind buttons on SEPs. Run an experiment with two variations:

- Control: Current large Supermind buttons
- Variation 1: New small Supermind button with general `Get replies from creators like` messaging (refer: Mock A)

## QA

<!---
Consideration is given to how the issue will be demoed and tested prior to being deployed
--->


## UX/Design

[Figma](https://www.figma.com/file/MUyXGJQIa3YyexedXHd99W/Supermind-Experiments?node-id=76%3A6754)

![image](/uploads/8d9be170bd1989162d72ccb626d63259/image.png)

## Personas

<!---
Who does this user impact and why (optional)
--->


## Experiments

This should be rolled out as an experiment, evenly distributed amongst logged-in users.

## Acceptance Criteria

<!--
Everyone should be able to understand what is expected to be delivered
--->

- [ ] A/B test using (A) from above screenshot as variant
- [ ] Experiment added on growthbook

## Definition of Ready Checklist

- [x] Definition Of Done (DoD)
- [x] Acceptance criteria
- [x] Weighted
- [x] QA
- [x] UX/Design
- [x] Personas
- [x] Experiments

Story points: 3.0
Experiment: Prompt to Supermind when writing a comment

## Goal

As a user making comments, I want my comments to get attention and engagement from their target.

Goal: Increase Supermind offers.

## What needs to be done

Hypothesis: Users who comment on activity posts of other creators are likely customers of Supermind. We can use the commenting flow to introduce the benefits of Supermind and increase Supermind offers.

Build a prompt that displays when a user is writing a comment that asks them to turn their comment into a Supermind. The prompt can only appear for top-level comments.

- Time the prompt after (a) the user has begun typing a comment, and (b) 5 seconds have passed.
- The prompt appears once for a user during a logged in session.
- Once the prompt has appeared, it will not appear again.

Clicking the prompt launches the Supermind offer screen, and pre-populates the composer afterward with the text that was input into the comment before they pressed the `Upgrade` button.

When the Supermind is posted, the comment input box is reset to blank.

If the Supermind is NOT posted and the Supermind offer / composer is closed, the comment input box is NOT reset to blank.

## QA

<!---
Consideration is given to how the issue will be demoed and tested prior to being deployed
--->


## UX/Design

[Prototype](https://www.figma.com/proto/MUyXGJQIa3YyexedXHd99W/Supermind-Experiments?page-id=0%3A1&node-id=2%3A2355&viewport=-1876%2C226%2C1&scaling=scale-down&starting-point-node-id=2%3A2355)

![image](/uploads/1de5ab4e7547e5ba5ecd6e29807d9f77/image.png)

## Personas

People who follow creators

## Experiments

This change is proposed as an experiment and should be A-B tested. We want to measure:

- How many times does a user see this
- How many times does a user click this
- How many times does this convert into a Supermind purchase

## Acceptance Criteria
<!--
Everyone should be able to understand what is expected to be delivered
--->
- [ ] Only for text comments.
- [ ] For top-level comments only.
- [ ] Agree snowplow events naming convention with @michael4tasman .
- [ ] Manually add trackView event for `"see-supermind-popup"` (https://gitlab.com/minds/front/-/blob/master/src/app/modules/media/components/video-player/player.service.ts#L160)
- [ ] Manually add trackClick event for `"click-supermind-popup-button"` (https://gitlab.com/minds/front/-/blob/master/src/app/modules/media/components/video-player/player.service.ts#L160)

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 5.0
Youtube missing from settings page

<!---
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

Youtube option is missing from the settings page.

### Steps to reproduce

1. Go to settings page, see no yt option under content settings

### Platform information 

Web

### What is the current *bug* behavior?

Missing option

### What is the expected *correct* behavior?

Re-add option without need for feature flag

### Acceptance Criteria
- [ ] Re-add option in settings without feature flag requirement
- [ ] Stretch Goal: e2e tests for settings option

### 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
New avatar not reflected on new posts

### Summary

When my avatar is changed, neither posts created after the update, nor existsing posts reflect the change in avatar.
![image](/uploads/14349f7640bff5d5124464df09ecfca0/image.png)

Current avatar: ![dogs](/uploads/dae144f1522877e7e943d275b2638113/dogs.jpg)
Old avatar: ![selfie](/uploads/6c44f42267a27888ffcb8d35f0654852/selfie.jpg)

### Steps to reproduce

- change avatar
- create new post

Also tried was refreshing, as well as logging out and back in

### Platform information 

Windows 11, Google Chrome.
Bug was reproduced using Chrome, but was originally reported from Brave.

### What is the current *bug* behavior?

Avatar is not reflected on posts.

### What is the expected *correct* behavior?

icontime should be in the avatar url

Story points: 1.0
Multi-image quote posting - can't open images in modal

<!---
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

Quote posts with multiple images don't allow the user to view the images in modals

### Steps to reproduce

- View [a quote post with multiple images](https://www.minds.com/newsfeed/1424507434050785297)
- Click an image

### Platform information 

- MacOS + Chrome

### What is the current *bug* behavior?

- Nothing happens

### What is the expected *correct* behavior?

- The clicked image opens in a modal view

### Relevant logs and/or screenshots

![image](/uploads/619f3380c64f494ebbdb0c174bdbce71/image.png)

### Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Story points: 3.0
Make Stripe iframe 500px

<!---
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

Temporary patch for https://gitlab.com/minds/minds/-/issues/3457?work_item_id=116404432

Make Stripe iframe 500px height as a temporary solution to enable users to add their bank cards who have to go through security measures that go beyond the given height of the iframe (I believe it's currently 150px).

### Steps to reproduce

Try enter a card with 3DSecure - unsure how to effectively replicate this with test cards.

### Platform information 

Web

### What is the current *bug* behavior?

Stripe iframe is too short to complete for some users with some banks.

### What is the expected *correct* behavior?

Height should be taller

### Relevant logs and/or screenshots

![image](/uploads/00d52004c5d18e8d7532ba1542cb73bc/image.png)

### Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Story points: 2.0
Fix failing notification test

<!---
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

Notification test failing.

### Steps to reproduce

Run test suite.

### Platform information 

Web.

### What is the current *bug* behavior?

Notif tests failing.

### What is the expected *correct* behavior?

Should pass.

### 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

Looks like we're not actually posting supermind replies now we added in the confirmation modal - we go to the confrim modal pre posting and then log out to check the post was a success.

Story points: 1.0
Duplicate feed items in Supermind Console

<!---
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 feed items appearing in Supermind Console

### Steps to reproduce

- Open Supermind Console with one offer
- Scroll down quickly before loading is finished

### Platform information 

Web

### What is the current *bug* behavior?

Seeing duplicate feed items in Supermind Console.

### What is the expected *correct* behavior?

Should not see duplicate feed items in Supermind 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: 1.0
Cannot send tokens to a user who has no account connected

### Summary

Sending tokens to a user who does not accept cash should be allowed.

### Steps to reproduce

1. Open web app.
2. Login successfully.
3. Navigate to a channel with no account.
4. Select superminds.
5. Tap Tokens.

### Platform information 

Chrome

### What is the current *bug* behavior?

Throws error

### What is the expected *correct* behavior?

Should let you send tokens

### Relevant logs and/or screenshots

![image](/uploads/c5f9e13107dcdb3fc2f53698a451315f/image.png)

Story points: 1.0
Supermind state does not include a post no longer exists state

<!---
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

There's no handling for Superminds that are not found - they show as lines in the console.

** THIS APPLIES TO WEB AND MOBILE**

### Steps to reproduce

1. Create a Supermind 
2. Delete the post

### Platform information 

Web / Mobile

### What is the current *bug* behavior?

Lines show

### What is the expected *correct* behavior?

Lines should not show like that - either:

- We should have a Supermind state like failed for when this happesn
- We should be filtering out null entities on client side and just not showing them
- We should design a placeholder "This post is unavailable" section.

### Relevant logs and/or screenshots

![image](/uploads/93ebe7ead607583258176fce32d8c831/image.png)

### Possible fixes

See correct behavior for ideas

Story points: 2.0
E2E tests failing to compile

<!---
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

E2E tests seem to be failing to compile since the merge of https://gitlab.com/minds/front/-/merge_requests/2052, despite that MR having a green light

Example failure https://gitlab.com/minds/front/-/jobs/3103443985

### Steps to reproduce

Run e2e

### Platform information 

CI / Dev

### What is the current *bug* behavior?

Tests wont compile.

### What is the expected *correct* behavior?

Compiling tests

### 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