giseldo/neodataset huggingface dataset:
Invalid feed:algorithm is settable via URL

<!---
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

Invalid `feed:algorithm` is settable via URL leading to broken feeds that cannot be reset by refreshing or clicking away.

### Steps to reproduce

1. Go to https://www.minds.com/newsfeed/subscriptions/broken-feed-1231231
2. Note no feed loads.
3. Click discovery.
4. Click back on home, note it takes you to the broken URL again
5. load `/` - takes you to the broken URL again.

### Platform information 

Web - likely platform agnostic.

### What is the current *bug* behavior?

Feeds broken if user goes to an invalid link with an invalid feed type.

### What is the expected *correct* behavior?

Feed should reset to default and local storage value should be purged.

### Relevant logs and/or screenshots

https://streamable.com/iih0hb

### Possible fixes

https://gitlab.com/minds/front/blob/dcb1406a62f26de588187146f856ca5be8913db0/src/app/modules/newsfeed/feeds/subscribed.component.ts#L153

Story points: 1.0
Cannot open dropdowns in composer and blogs (Canary)

<!---
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 open dropdowns in composer and blogs

### Steps to reproduce

1. Enter Canary and hard refresh (do it manually)
2. Open composer
3. Try to expand submenu such as for visibility 

### Platform information 

- Replicated Firefox Ubuntu.
- Also replicated by @manishoo on Mac, browser unknown.
- Likely platform agnostic.

### What is the current *bug* behavior?

Dropdown sub-menu does not open.

### What is the expected *correct* behavior?

Sub-menu should open.

### Relevant logs and/or screenshots

![image](/uploads/8b36121ebc972f9d4f0296aa6f143c41/image.png)

### Possible fixes

https://gitlab.com/minds/front/-/commit/6131f49cf5bd6c886212da7494758450a186cf1f#note_972671132

Story points: 2.0
Add entity_type to view events

<!---
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
--->

Tasmans life will be made easier if we just apply 'entity_type' with the view events. We already supply entity_guid.


## What needs to be done

<!---
Clearly detail what needs to be done to achieve the goal set out above
--->

Apply 'entity_type' from the analytics service.

## 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.
--->


## 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
--->

- [ ] Entity 'view' events should also supply the 'entity_type' field 

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 1.0
Make tweaks to activity-v2 component

<!---
Please read this!

The Definition of Ready (DoR) can be found at https://developers.minds.com/docs/handbook/how-we-work/#definition-of-ready-dor

Before opening a new issue, make sure to search for keywords in the issues
filtered by the "Type::Feature" label and verify the feature you're about to submit isn't a duplicate.
--->

## Goal

<!---
Clearly outline the goal of the issue and why we are doing it
--->

@markeharding to provide minor changes to activity-v2 component

## What needs to be done

- Autoplay (muted) Minds videos if the user has autoplay enabled

Part of the task

## QA

<!---
Consideration is given to how the issue will be demoed and tested prior to being deployed
--->

To be done later

## 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
--->

- [ ] @markeharding's changes

## 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: 2.0
Clean up phone verification modal

## Goal

The phone verification modal is a visually quite messy. Spacing issues need to be addressed to improve the overall look and feel of the modal.

## What needs to be done

<details><summary>Click to see the current state</summary>
![Screenshot_2022-05-27_at_13.17.11](/uploads/0daa0908e15fa5c6b4f85561d8918b4f/Screenshot_2022-05-27_at_13.17.11.png)
</details>

## UX/Design

* Use action button shown in the designs
* Note the spacing used between the input and action
* Note the font size / line-high and spacing

- [Designs on Figma](https://www.figma.com/file/LSv6C89wDLNf47Wy7elFHs/Wallet-%5BWeb%5D?node-id=1%3A1077) 



## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 1.0
Cleanup feature 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.
--->

## Goal

<!---
Clearly outline the goal of the issue and why we are doing it
--->

Cleanup ended experiments

## What needs to be done

<!---
Clearly detail what needs to be done to achieve the goal set out above
--->

See acceptance criteria

## QA

<!---
Consideration is given to how the issue will be demoed and tested prior to being deployed
--->

N/A

## UX/Design

<!---
Sufficient wireframes have been presented and understood by the development team. Full mockups are not required and re-usable components are encouraged.
--->

N/A

## Personas

<!---
Who does this user impact and why (optional)
--->

Developers

## Experiments

<!---
Experiments are not required, but it should be made clear if one is expected. If experiments are required, the hypothesis should be outlined.
--->

:smirk: 


## Acceptance Criteria

<!--
Everyone should be able to understand what is expected to be delivered
--->

Allow the below experiments have one. Keep the variant and remove the controls. 

- [ ] Remove 'front-5474-search-polling'
- [ ] Remove 'front-4089-polling'
- [ ] Remove 'channel-recommendations'
- [ ] Remove 'channel-gallery'
- [ ] Remove 'boost-prompt-2'
- [ ] Remove 'engine-2966-holding-rewards'
- [ ] Remove 'trending-tags-v2'
- [ ] Remove 'top-feed-2'
- [ ] Remove 'new-user-boosts'
- [ ] Remove 'minds-3092-unseen-discovery-top'
- [ ] Remove 'engine-2966-holding-rewards'
- [ ] Once on production, remove from growthbook

## Definition of Ready Checklist

- [x] Definition Of Done (DoD)
- [x] Acceptance criteria
- [ ] Weighted
- [x] QA
- [x] UX/Design
- [x] Personas
- [x] Experiments

lan

Story points: 3.0
Enable activities v2 flag

<!---
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
--->
Start to conduct the activities v2 experiment

## What needs to be done

<!---
Clearly detail what needs to be done to achieve the goal set out above
--->
- Final audit of activities v2 
- Turn on `front-5229-activities` flag for canary users so we can get feedback on it

## QA

<!---
Consideration is given to how the issue will be demoed and tested prior to being deployed
--->
It's already been QA-ed

## 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.
--->
`front-activities-5229`

## Acceptance Criteria

<!--
Everyone should be able to understand what is expected to be delivered
--->

- [ ] Complete one final visual pass of activities v2
- [ ] Enable the flag

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 0.0
Audit components and create storybook list

<!---
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
--->
Create a spreadsheet that categorizes our components so we can make plans for storybook

## What needs to be done

<!---
Clearly detail what needs to be done to achieve the goal set out above
--->
- [ ] Go through all of our components
- [ ] Categorize them in a spreadsheet according to whether they are legacy, are used in multiple places, where they are used, if they serve the same function as other components, what general functions they serve, etc.
- [ ] remove the legacy ones
- [ ] Make list of issues to consolidate similar components
- [ ] Propose list of functional groupings, and possibly new (more reusable) components that could be created 

## QA

<!---
Consideration is given to how the issue will be demoed and tested prior to being deployed
--->
Make sure nothing was broken by removing legacy components.


## 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.
--->
None

## Acceptance Criteria

<!--
Everyone should be able to understand what is expected to be delivered
--->

- [ ] Spreadsheet that contains details of our components
- [ ] Additional ad-hoc lists relating to findings that were revealed during the audit

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 5.0
Finish refactoring rogue dropdowns

<!---
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
--->
Finish what was started in https://gitlab.com/minds/front/-/merge_requests/1873 .

Dropdown menus should all use the `m-dropdownMenu` and `m-dropdownMenu__item` components. 
## What needs to be done

<!---
Clearly detail what needs to be done to achieve the goal set out above
--->
- [ ] Go through the dropdowns that haven't been refactored yet and refactor them
- [ ] remove the legacy dropdown menu components and styles

## QA

<!---
Consideration is given to how the issue will be demoed and tested prior to being deployed
--->
Look at a bunch of dropdowns

## 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.
--->
None

## Acceptance Criteria

<!--
Everyone should be able to understand what is expected to be delivered
--->

- [ ] Dropdowns should all be using the same component

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 5.0
Add stories to storybook

<!---
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
--->
Continue to populate storybook with components that we have that are simple, re-used standalone components


## What needs to be done

<!---
Clearly detail what needs to be done to achieve the goal set out above
--->
Add these to storybook:
- [x] Toggle
- [x] MindsAvatar
- [x] Tags: DiscoveryTagButton
- [x] Tags: Content settings > tags
- [x] Tags: Onboarding tags 

- [ ] Tags: DiscoveryTagWidget
- [ ] Tags: Sidebar suggestions
- [ ] Tags: Channel tags

Plan ahead: 
- [x] Create and utilize reusable mock api responses.

## QA

<!---
Consideration is given to how the issue will be demoed and tested prior to being deployed
---
Look at storybook - unlikely to affect the way components are working 

## UX/Design

<!---
Sufficient wireframes have been presented and understood by the development team. Full mockups are not required and re-usable components are encouraged.
--->
N/A

## Personas

<!---
Who does this user impact and why (optional)
--->
Developers

## Experiments

<!---
Experiments are not required, but it should be made clear if one is expected. If experiments are required, the hypothesis should be outlined.
--->
None

## Acceptance Criteria

<!--
Everyone should be able to understand what is expected to be delivered
--->

- [ ] Components listed above in storybook

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 3.0
Unclear which deeplink app is the PWA vs Native App

### Summary

Found by @ottman 

### Steps to reproduce

1. Open minds web on browser.
2. Tap on Switch to minds app.
3. Notice that two apps appear which is incorrect - Issue 1.
4. Notice that clicking on one of them does not take you to the app. 

### Platform information 

Android Chrome
Galaxy S20 5G - Android 12

### What is the current *bug* behavior?

- Should only show one minds app 
- Should take you to the app when selected successfully.
- Screen overlapping needs to be fixed

### What is the expected *correct* behavior?

- PWA  app should have "Web" in logo and "Web" in title

### Relevant logs and/or screenshots

![image](/uploads/42db4201fc8cb64e456f0dc7c1a24d16/image.png)

Story points: 1.0
Add public keys to About section on minds

<!---
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
--->

Display a users public nostr key in the about section of their channel page to allow interested users to explore to technology. 

## What needs to be done

<!---
Clearly detail what needs to be done to achieve the goal set out above
--->

Display nostr public key and DID link on about section of channel. An API request will need to be made to `/.well-known/nostr?name={{username}}` in order to get the public key. Only do this on the about tab.

## QA

<!---
Consideration is given to how the issue will be demoed and tested prior to being deployed
--->

N/A

## UX/Design

<!---
Sufficient wireframes have been presented and understood by the development team. Full mockups are not required and re-usable components are encouraged.
--->

Add a new section under 'DID', labelled 'Nostr'.

## Personas

<!---
Who does this user impact and why (optional)
--->

Digital nomads

## 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
--->

- [ ] Fetch and display a users nostr public key
- [ ] Make the DID link to `{{username}}/did.json`

## 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: 2.0
Add links to nostr for posts without text

<!---
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
--->


## 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.
--->


## 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: 0.0
Incorrectly escaped group description on edit

<!---
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

https://www.minds.com/newsfeed/1102269572180463616

### Steps to reproduce

1. Make a group
2. Add `''""` into the description
3. Go to edit the grouo

### Platform information 

Cross-platform web

### What is the current *bug* behavior?

Group description shows unescaped/escaped string

### What is the expected *correct* behavior?

It should show the quotes

### Relevant logs and/or screenshots

![image](/uploads/8b22d90dad250a2d3dee59b67c96dbe8/image.png)

### Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Story points: 2.0
ETH balance not showing

<!---
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

FireChief is reporting his ETH balance doesn't show - nor does mine.

https://www.minds.com/newsfeed/1101678470079238144

Happens in new UX also

### Steps to reproduce

1. Have ETH In your connected wallet with a matching receiver address.
2. See ETH balance is 0 on the wallet page

### Platform information
 
Replicated Firefox

### What is the current *bug* behavior?

Cannot see ETH balance

### What is the expected *correct* behavior?

Should be able to see ETH balance

### Relevant logs and/or screenshots

![image](/uploads/849606feac9ef6ee9fa8a9230b8e2e3b/image.png)

### Possible fixes

Check that it isn't being rounded down to 0.

Story points: 2.0
Channels subscriptions, subscribers and public groups lists

- [x] Groups count from API
- [x] Public groups list API endpoint
- [x] Common generic entities list component with infinite scrolling capabilities
- [x] Groups list page from API
- [x] Subscribers list page
- [x] Subscriptions list page

Clarifications about groups list page: https://gitlab.com/minds/front/-/issues/2793#note_327913039

Story points: 1.0
Wrong redirect in 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

Both locally and on the review sites I've found that going to `/boost/console/content/create` automatically redirects to `/boost/console/sidebar/create`, which is incorrect and doesn't allow you to create a boost, since it doesn't find content.

### Steps to reproduce

Go to the boost console, click on the "Sidebar" link in the topbar.

### Platform information 

any

### What is the current *bug* behavior?

It redirects to `/boost/console/sidebar/create`

### What is the expected *correct* behavior?

It shouldn't redirect

### Possible fixes

Find and fix the redirect


Story points: 2.0