giseldo/neodataset huggingface dataset:
Mobile responsive activity posts missing boost option

### Summary

The tip/boost interactions on V2 activity posts are missing on responsive mobile.

### Steps to reproduce

View any activity post in a mobile browser, ensuring you have v2 posts enabled.

### Platform information 

Any mobile browser.

### What is the current *bug* behavior?

The boost icon or tip icon do not appear. They appear on large devices, just not mobile devices.

### What is the expected *correct* behavior?

Options should appear on mobile.

* [Mobile Post 1](https://www.figma.com/file/EkJej3mKP2lSzmWTLoqlXD/Minds-Design-System?node-id=390%3A2822)
* [Mobile Post 2](https://www.figma.com/file/EkJej3mKP2lSzmWTLoqlXD/Minds-Design-System?node-id=1782%3A12332)

### Relevant logs and/or screenshots

<details><summary>Activity Posts Large Display - Click to expand</summary>
![Screenshot_2022-07-20_at_09.43.28](/uploads/da813f1605dfa6ff5c151a227688a3ae/Screenshot_2022-07-20_at_09.43.28.png)
![Screenshot_2022-07-20_at_09.43.01](/uploads/5155adbabc78174cb44ed67141a4e7f3/Screenshot_2022-07-20_at_09.43.01.png)
</details>

<details><summary>Mobile responsive posts</summary>
![Screenshot_2022-07-20_at_09.43.33](/uploads/c3a88f3a9302ce30571e40a55968e543/Screenshot_2022-07-20_at_09.43.33.png)
![Screenshot_2022-07-20_at_09.43.05](/uploads/c34c590a773b9ab00dcd14fe734756f7/Screenshot_2022-07-20_at_09.43.05.png)
</details>

### Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Story points: 1.0
Comment upvotes break 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

Comment upvotes break posts - replicated on a single entity page

### Steps to reproduce

1. Go to a single entity page.
2. Upvote post.

### Platform information 

Web

### What is the current *bug* behavior?

Post breaks (see video)

### What is the expected *correct* behavior?

Should work.

### Relevant logs and/or screenshots

Video:

https://www.minds.com/newsfeed/1396274339669610499

![image](/uploads/a6734a45a9bd2b03213814a4035b4f14/image.png)

### Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Story points: 2.0
Both verification emails sent on new account creation

<!---
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

2x verification emails arrive on new account creation.

### Steps to reproduce

- Make a new account, and observe 2 emails.
- May take multiple attempts because of experiment

### Platform information 

Presume platform agnostic.

### What is the current *bug* behavior?

2 emails arrive

### What is the expected *correct* behavior?

1 email should arrive. 

### Relevant logs and/or screenshots

![image](/uploads/df6028b0a85e9942e1c4e7d335e44281/image.png)

### Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Story points: 2.0
On Mobile Web, ditch notif dropdown entirely and go straight to full page minds.com/notifications/v3

<!---
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 notif dropdown on mobile web app makes no sense because the screen is already so narrow


## What needs to be done

<!---
Clearly detail what needs to be done to achieve the goal set out above
--->




## QA

<!---
Consideration is given to how the issue will be demoed and tested prior to being deployed
--->


## UX/Design

<!---
Sufficient wireframes have been presented and understood by the development team. Full mockups are not required and re-usable components are encouraged.
--->

Current:

![image](/uploads/39b0adf44dfb70a13f8b496fd2c83db8/image.png)

Proposed:

![image](/uploads/1799995891b03c5699fe4d5126f9785f/image.png)


## Personas

<!---
Who does this user impact and why (optional)
--->


## Experiments

<!---
Experiments are not required, but it should be made clear if one is expected. If experiments are required, the hypothesis should be outlined.
--->


## 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: 1.0
Add Superminds to 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
--->
- Properly display all relevant information for Supermind transactions in the transaction ledger for both tokens and cash

## What needs to be done

<!---
Clearly detail what needs to be done to achieve the goal set out above
--->



## QA

<!---
Consideration is given to how the issue will be demoed and tested prior to being deployed
--->


## UX/Design

<!---
Sufficient wireframes have been presented and understood by the development team. Full mockups are not required and re-usable components are encouraged.
--->

* A few small modifications will need to be made to the wallet.
  * Display SuperMind inbound/outbound payments within the transactions tab for both cash and token payment.
  * As much context and possible should be added.
* Example transaction lines [Transaction lines](https://www.figma.com/file/thrGepQAxmcMGB7MoEEckM/Supermind?node-id=430%3A12581)


---

* Todo - add info about Boost modal and boost console refactors.


## 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
--->

- [ ] Wallet transaction items to reflect mockups 

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 2.0
Presentation of Supermind activity posts

<!---
Please read this!

The Definition of Ready (DoR) can be found at https://developers.minds.com/docs/handbook/how-we-work/#definition-of-ready-dor

Before opening a new issue, make sure to search for keywords in the issues
filtered by the "Type::Feature" label and verify the feature you're about to submit isn't a duplicate.
--->

## Goal

<!---
Clearly outline the goal of the issue and why we are doing it
--->
- Ensure that Supermind responses are clearly indicated aesthetically in the feeds and post pages so that users know it was a paid reply


## What needs to be done

<!---
Clearly detail what needs to be done to achieve the goal set out above
--->


## QA

<!---
Consideration is given to how the issue will be demoed and tested prior to being deployed
--->


## UX/Design

<!---
Sufficient wireframes have been presented and understood by the development team. Full mockups are not required and re-usable components are encouraged.
--->

The activity post entity will be modified slightly to differentiate it from other posts.

* [Feed context design](https://www.figma.com/file/thrGepQAxmcMGB7MoEEckM/Supermind?node-id=292%3A6516)
  * Note the 2px border around the original post as well as the inclusion of the SuperMind badge top-left.
* [Entity content design](https://www.figma.com/file/thrGepQAxmcMGB7MoEEckM/Supermind?node-id=427%3A11837)
  * The large `SuperMind` CTA otherwise visible on other post entities, should not be visible here. The likelihood of someone wanting to SuperMind a SuperMind post is limited. They may nonetheless do so if they wish, by clicking on the `S` on the activity post.

## 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
--->

- [ ] Supermind label appears on a Supermind response
- [ ] Handle the case where a Supermind is reminded, displaying both Supermind label and remind label
- [ ] Outline appears on a quoted post in a Supermind response

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 3.0
Initiate a Supermind from channel 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

- Allow users to send a Supermind request to a channel from that person's channel page

## What needs to be done

Add a Supermind call to action to all channel pages.

* A `Supermind` call-to-action will appear top-right. It will remain visible whether a user is subscribed [Subscribed visitor state](https://www.figma.com/file/thrGepQAxmcMGB7MoEEckM/Supermind?node-id=292%3A7563)or [Unsubscribed visitor state](https://www.figma.com/file/thrGepQAxmcMGB7MoEEckM/Supermind?node-id=292%3A7870) to the channel being viewed.
* The `Supermind` CTA will not be visible when displaying one’s own channel.

When a user clicks the Supermind CTA, the composer is launched and automatically opens to the Supermind payment panel. The fields are pre-filled with the originating channel name as the target, and that channel's minimums.

## 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.
--->

**[Supermind CTA on channel - prototype](https://www.figma.com/proto/thrGepQAxmcMGB7MoEEckM/Supermind?page-id=287%3A5127&node-id=292%3A7563&viewport=1715%2C-2704%2C0.5&scaling=min-zoom&starting-point-node-id=292%3A7563&show-proto-sidebar=1)**

## Personas

<!---
Who does this user impact and why (optional)
--->


## Experiments

n/a

## Acceptance Criteria

<!--
Everyone should be able to understand what is expected to be delivered
--->

- [x] Add supermind button to channel page
- [x] Pre-fill the composer with the channel to focus on 
- [ ] Playright tests

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 3.0
Web Automation: Smoke test for Playwright tests on Browserstack

## Goal

Basic smoke test to be created to run on Browser stack. 


## What needs to be done
Add test cases on:
- Login 
- Sign up (Captcha Bypass)
- Newsfeed
- Discovery
- Search
- Viewing Channel
- Settings
- Adding/Delete Tags
- Minds+ Feed
- Comment Threads
- Logout

## QA
Tests should pass locally and on CI.


## UX/Design
N/A


## Personas
N/A


## Experiments
N/A


## Acceptance Criteria

- [ ] All tests pass on CI - multiple platforms

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 8.0
Web Automation: Playwright tests Phase 2

## Goal
Have working tests with Playwright, Codeceptjs and Browserstack. 


## What needs to be done
- Integrate all three platforms with some tests for login feature
- Add CI support
- Use advance features of Playwright and Codeceptjs
- Page object model


## QA
Test locally & on CI - view videos from Browserstack


## UX/Design
N/A


## Personas
N/A


## Experiments
N/A


## Acceptance Criteria

- [ ] Full integration working for web functional tests. 

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 3.0
Email change requires refresh before seeing feed notice verify your email widget

<!---
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

Email change requires refresh before seeing feed notice verify your email widget

Note - code experiment is on

### Steps to reproduce

1. Change email
2. Nav to newsfeed
3. Observe no notice
4. Refresh
5. Observe notice and popup

### Platform information 

Web

### What is the current *bug* behavior?

No notice until you nav to the newsfeed

### What is the expected *correct* behavior?

Should see notice on navigation

### 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

Maybe we can inject into the session user `email_confirmed` false as we do on email confirmation for setting it true.

Story points: 2.0
Exportable should strip disabled user accounts from exported user lists

<!---
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

Exportable should strip disabled user accounts from exported user lists

This is not handled by the ACL because that would prevent blocking

### Steps to reproduce

There's many ways this could occur as it's a low level issue, the known way at the time of writing is to disable an account that shows up as a mutual subscriber on a channel

### Platform information 

Engine 

### What is the current *bug* behavior?

Disabled user accounts showing where they should not

### What is the expected *correct* behavior?

Disabled user accounts should be filtered on export

### 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

We should return null in the User export function like in isDeleted so that the user is stripped out on export

Story points: 2.0
Activities V2 | Group pictures look wrong then looking at list of groups from profile

<!---
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

Group profile pictures are ellipsoid

![image](/uploads/4b1d1821911043224fcb7a3979e21705/image.png)

### Steps to reproduce

1. make sure you have activities v2
2. go to look https://www.minds.com/bashynx/groups or https://www.minds.com/discovery/search?q=help&f=groups&t=all
2. note that the 

### Platform information 

(Browser, device, system stats, screen size)

### What is the current *bug* behavior?

groups pictures are ellipsoid

### What is the expected *correct* behavior?

group pictures should be round

### 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
Try to improve Metascraper Twitter Support

<!---
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

Twitter support for Metascraper is patchy - we should see if there is anything we can do to improve previews.
Take for example https://twitter.com/fotoperfeito/status/1545163618517454849?s=20&t=R_cMKzsVMu-PrUbQxKV4jw

See https://github.com/microlinkhq/metascraper/issues/260#issuecomment-1171194503 for additional information

One weird thing is that if you include the audio or video query params, an image is found https://api.microlink.io?url=https://twitter.com/Twitter/status/1483427748500717573&audio=true

Another thing to look at it why some points repeat description and title, with no author.

### Steps to reproduce

1. Try to embed https://twitter.com/Twitter/status/1483427748500717573

### Platform information 

Web

### What is the current *bug* behavior?

Twitter support is patchy

### What is the expected *correct* behavior?

Should get images if possible 

### 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

Lets try the new dedicated Twitter adapter https://github.com/microlinkhq/metascraper/issues/260

Story points: 3.0
Make Cypress tests as a blocker if fail in CI

## Goal
Make cypress tests stop the pipeline if fail. 


## What needs to be done
Change gitlab ci.


## QA
Run on CI to test.

## UX/Design
N/A


## Personas
N/A


## Experiments
N/A


## Acceptance Criteria

- [ ] Cypress tests if fail should block pipeline

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Ma

Story points: 1.0
(bug) Activities v2 | Boost 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

The padding on Boost Console posts is non-existent (except for top padding), see image below

We need to include the feed styles to the boost console activities.

And the sidebar boost styles to the boost modal preview activities. 

### Steps to reproduce

Look at the boost console while having activities v2 on, and having had a boost in past

### Platform information 

(Browser, device, system stats, screen size)

### What is the current *bug* behavior?

Boost Console posts have only top padding

### What is the expected *correct* behavior?

Boost console posts should have more padding, so it doesn't look cramped

### Relevant logs and/or screenshots

![image](/uploads/5bafcb8ed500307c94d3a224252fdda6/image.png)

### Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Story points: 2.0
Use Cassandra instead of Redis for Metascraper cache

<!---
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

Lower the amount of things we're throwing at Redis and throw rich embed responses at Cassandra instead

## What needs to be done

Migrate caching to a cassandra table.

## QA

Test cached responses.

## UX/Design

N/A

## Personas

Users who post rich-embeds

## Experiments

Tied to metascraper experiment as without it active, this wouldn't be active.

## Acceptance Criteria

- [x] New table
- [x] Cached values in Cassandra with configurable TTL (exists already)
- [x] Add in last scrape column
- [x] Add in an endpoint to purge cache for a url
- [x] Tests

## 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: 5.0
Cannot delete comments -  "G.delete is not a function"

### Summary

Cannot delete a comment. 

### Steps to reproduce
1. Open minds web.
2. Comment on any post.
3. Delete your comment.
4. Nothing happens.

### Platform information 

All staging, canary & Prod
All browsers

### What is the current *bug* behavior?

Nothing happens - console error "G.delete is not a function"

### What is the expected *correct* behavior?

Comment should be deleted

### Relevant logs and/or screenshots

![image](/uploads/c93f0df0363d2dc36d25e224ecccb2e8/image.png)

Story points: 2.0
Reduce front-end unit test flake

<!---
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

Unit test on the front-end flake frequently. We identify and either fix/skip frequently failing tests. This slows down the development process.

#### Failed Pipelines

- https://gitlab.com/minds/front/-/jobs/2722612136
- https://gitlab.com/minds/front/-/jobs/2730432405
- See https://gitlab.com/minds/front/-/issues/5300

### Steps to reproduce

Run the test command a few times. Check pipelines.

### Platform information 

CI and local stacks (front)

### What is the current *bug* behavior?

Test bed flake

### What is the expected *correct* behavior?

Ideally no flake, at least significantly less.

### 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
Back button in discovery Just For You feed returns to Top feed

<!---
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

Back button incorrectly redirects to wrong feed

### Steps to reproduce

1. Go to Just For You feed
2. Open a hero card 
3. Press back - see you're returned to Top (wrong feed)

### Platform information 

Web

### What is the current *bug* behavior?

Returned to wrong feed.

### What is the expected *correct* behavior?

- Should return to the correct feed.
- Should check this isn't happening with other feeds.
- 
### Relevant logs and/or screenshots

https://streamable.com/dy2xaw

### Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Story points: 1.0