giseldo/neodataset huggingface dataset:
Badges skewed in channel about tab

<!---
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

(Summarize the bug encountered concisely)

### Steps to reproduce

(How one can reproduce the issue - this is very important)

### Platform information 

(Browser, device, system stats, screen size)

### What is the current *bug* behavior?

(What actually happens)

### What is the expected *correct* behavior?

(What you should see instead)

### Relevant logs and/or screenshots

(Paste any relevant logs - please use code blocks (```) to format console output,
logs, and code as it's very hard to read otherwise.)

### Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Story points: 1.0
Group list is loading many times on android and the group screen is frozen

<!---
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

(Summarize the bug encountered concisely)

### Steps to reproduce

(How one can reproduce the issue - this is very important)

### Platform information 

(Browser, device, system stats, screen size)

### What is the current *bug* behavior?

(What actually happens)

### What is the expected *correct* behavior?

(What you should see instead)

### Relevant logs and/or screenshots

(Paste any relevant logs - please use code blocks (```) to format console output,
logs, and code as it's very hard to read otherwise.)

### Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Story points: 2.0
Reviewed comments issues

Small issues after reviewing the changes for https://gitlab.com/minds/mobile-native/-/issues/2970

- [x] Ellipsis icon is to close to the send icon in the comments input
- [x] Close icon is not aligned
- [x] Touchable of votes is also opened the full-screen view of the post on android
- [x] When selecting the image and video gallery option the selector is closing right after it is shown (iOS)

Story points: 1.0
Comments: options for ellipsis button in comment input

- [x] Tapping the ellipsis within the comment inout, launches the media gallery. The intention was to also include 'Mark as explicit' which is currently omitted. Is it still important to include the explicit option when adding a comment (ref -> https://www.sketch.com/s/242fed11-027a-48de-b053-6d4cc89bed75/a/1avzDp)
- [x] In addition to 'select photo/video from gallery', can we also include an option to 'take picture/video'?

Story points: 1.0
Unable to download images (Minds version of app)

### Summary

User @lykanthrocide unable to download images from Minds version of app

### Steps to reproduce

(How one can reproduce the issue - this is very important)

### Platform information 

LG Stylo 6, Android 10

### What is the current *bug* behavior?

"Error downloading file" message

### What is the expected *correct* behavior?

(What you should see instead)

### Relevant logs and/or screenshots

(Paste any relevant logs - please use code blocks (```) to format console output,
logs, and code as it's very hard to read otherwise.)

### Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Story points: 1.0
Tappable area on the comment ellipsis is quite small

<!---
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

(Summarize the bug encountered concisely)

### Steps to reproduce

(How one can reproduce the issue - this is very important)

### Platform information 

(Browser, device, system stats, screen size)

### What is the current *bug* behavior?

(What actually happens)

### What is the expected *correct* behavior?

(What you should see instead)

### Relevant logs and/or screenshots

(Paste any relevant logs - please use code blocks (```) to format console output,
logs, and code as it's very hard to read otherwise.)

### Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Story points: 1.0
Build and release it for Android and iOS

<!---
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

(Summarize the bug encountered concisely)

### Steps to reproduce

(How one can reproduce the issue - this is very important)

### Platform information 

(Browser, device, system stats, screen size)

### What is the current *bug* behavior?

(What actually happens)

### What is the expected *correct* behavior?

(What you should see instead)

### Relevant logs and/or screenshots

(Paste any relevant logs - please use code blocks (```) to format console output,
logs, and code as it's very hard to read otherwise.)

### Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Story points: 2.0
Add verify email bannel if onboarding FF is off

<!---
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

(Summarize the bug encountered concisely)

### Steps to reproduce

(How one can reproduce the issue - this is very important)

### Platform information 

(Browser, device, system stats, screen size)

### What is the current *bug* behavior?

(What actually happens)

### What is the expected *correct* behavior?

(What you should see instead)

### Relevant logs and/or screenshots

(Paste any relevant logs - please use code blocks (```) to format console output,
logs, and code as it's very hard to read otherwise.)

### Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Story points: 1.0
User with unverfied email can't upload media

<!---
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

(Summarize the bug encountered concisely)

### Steps to reproduce

(How one can reproduce the issue - this is very important)

### Platform information 

(Browser, device, system stats, screen size)

### What is the current *bug* behavior?

(What actually happens)

### What is the expected *correct* behavior?

(What you should see instead)

### Relevant logs and/or screenshots

(Paste any relevant logs - please use code blocks (```) to format console output,
logs, and code as it's very hard to read otherwise.)

### Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Story points: 1.0
Disable functionality on store version of the app

<!---
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

(Summarize the bug encountered concisely)

### Steps to reproduce

(How one can reproduce the issue - this is very important)

### Platform information 

(Browser, device, system stats, screen size)

### What is the current *bug* behavior?

(What actually happens)

### What is the expected *correct* behavior?

(What you should see instead)

### Relevant logs and/or screenshots

(Paste any relevant logs - please use code blocks (```) to format console output,
logs, and code as it's very hard to read otherwise.)

### Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Story points: 3.0
Comments: The comment count is not displayed

<!---
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

(Summarize the bug encountered concisely)

### Steps to reproduce

(How one can reproduce the issue - this is very important)

### Platform information 

(Browser, device, system stats, screen size)

### What is the current *bug* behavior?

(What actually happens)

### What is the expected *correct* behavior?

(What you should see instead)

### Relevant logs and/or screenshots

(Paste any relevant logs - please use code blocks (```) to format console output,
logs, and code as it's very hard to read otherwise.)

### Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Story points: 1.0
Comments: The close button (x) is missing from the top-right of the comment area

<!---
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

(Summarize the bug encountered concisely)

### Steps to reproduce

(How one can reproduce the issue - this is very important)

### Platform information 

(Browser, device, system stats, screen size)

### What is the current *bug* behavior?

(What actually happens)

### What is the expected *correct* behavior?

(What you should see instead)

### Relevant logs and/or screenshots

(Paste any relevant logs - please use code blocks (```) to format console output,
logs, and code as it's very hard to read otherwise.)

### Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Story points: 1.0
Join/Leave button in groups is too large

<!---
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

(Summarize the bug encountered concisely)

### Steps to reproduce

(How one can reproduce the issue - this is very important)

### Platform information 

(Browser, device, system stats, screen size)

### What is the current *bug* behavior?

(What actually happens)

### What is the expected *correct* behavior?

(What you should see instead)

### Relevant logs and/or screenshots

(Paste any relevant logs - please use code blocks (```) to format console output,
logs, and code as it's very hard to read otherwise.)

### Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Story points: 1.0
Mobile comments review

The new comments are looking very good on mobile. Few minor observations are listed below, that would be good to address before releasing the build.

For reference please see the original designs here -> https://www.sketch.com/s/242fed11-027a-48de-b053-6d4cc89bed75/a/mZq7DV

- [x] The close button (x) is missing from the top-right of the comment area. (#2955)
- [x] The comment count is not displayed (to the right of comments) (#2954)
- [x] If the user chooses to close the comments pane by tapping on the outer area at the top of the screen, the elements underneath the overlay are 'tappable'. In this case, the comments pane should disappear only, any the underlying elements shold not be tappable. (#2962)
- [x] The tappable area on the comment ellipsis is quite small. Could this area be increased, as it takes me multiple attempts to action it.
- [x] When viewing the comment action sheet, the user should be able to exit the sheet simply by tapping the outer area. Currently the only exit option is to tap 'cancel'. (#2962)
- [x] Please reduce the line spacing ever so slightly between the channel name and time ago value in the comment. (d741d7062c4b568965c2f322454f5d95522795a8)
- [x] If in the event there are zero comments on a post, and the user taps the comment icon from within their feed, could we activate the keyboard and focus on the comment input? (dc7038082e8da0fb25682d13f8d26f42890fab34) 
- [x] On the comment input, the tappable area around the ellipsis is very small and should be increased so it is more accessible. (5198a5d4e2dbfed837e19177aa5f5b9d779df2e6)
- [x] Tapping the ellipsis within the comment inout, launches the media gallery. The intention was to also include 'Mark as explicit' which is currently omitted. Is it still important to include the explicit option when adding a comment @ottman @jotto141 (ref -> https://www.sketch.com/s/242fed11-027a-48de-b053-6d4cc89bed75/a/1avzDp) (#2967)
- [x] In addition to 'select photo/video from gallery', can we also include an option to 'take picture/video'? (#2967)
- [x] When viewing a reply to long comment, the following issue is observed. (c8e631ab3ede9aa355ef0295b07688431f336501) ![IMG_1352](/uploads/ac96200358299483bc993e7debb9ad7b/IMG_1352.PNG)


cc @markeharding @jotto141 @ottman 
Looks great all round! It should be a big step forward to release the new comments.

Story points: 2.0
Implement focused comment navigation on new comments

<!---
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

(Summarize the bug encountered concisely)

### Steps to reproduce

(How one can reproduce the issue - this is very important)

### Platform information 

(Browser, device, system stats, screen size)

### What is the current *bug* behavior?

(What actually happens)

### What is the expected *correct* behavior?

(What you should see instead)

### Relevant logs and/or screenshots

(Paste any relevant logs - please use code blocks (```) to format console output,
logs, and code as it's very hard to read otherwise.)

### Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Story points: 2.0
Refactor Groups screen to use new comments

<!---
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

(Summarize the bug encountered concisely)

### Steps to reproduce

(How one can reproduce the issue - this is very important)

### Platform information 

(Browser, device, system stats, screen size)

### What is the current *bug* behavior?

(What actually happens)

### What is the expected *correct* behavior?

(What you should see instead)

### Relevant logs and/or screenshots

(Paste any relevant logs - please use code blocks (```) to format console output,
logs, and code as it's very hard to read otherwise.)

### Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Story points: 2.0
Unable to edit while tags are in place

### Summary

Posts cannot be edited while tags are present in the post. "Error: duplicate tags" message.

### Steps to reproduce

(How one can reproduce the issue - this is very important)

### Platform information 

app 4.7, android 10

### What is the current *bug* behavior?

Error message, "duplicate tags"

### What is the expected *correct* behavior?

(What you should see instead)

### Relevant logs and/or screenshots

(Paste any relevant logs - please use code blocks (```) to format console output,
logs, and code as it's very hard to read otherwise.)

### Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Story points: 1.0
Investigate slowdown in groups

<!---
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

Sometimes when opening a group it seems like the render method is fired too many times causing a noticable slowdown.

https://www.minds.com/newsfeed/1190457842802561024

### Steps to reproduce

(How one can reproduce the issue - this is very important)

### Platform information 

iPhone 6s

### What is the current *bug* behavior?

Slowdown when scrolling

### What is the expected *correct* behavior?

It should be fluid unless loading, ideally with a draggable loading indicator unless there is any reason not to have one.

### 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
Notifications and Messenger dots not aligned on Android

<!---
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

(Summarize the bug encountered concisely)

### Steps to reproduce

(How one can reproduce the issue - this is very important)

### Platform information 

(Browser, device, system stats, screen size)

### What is the current *bug* behavior?

(What actually happens)

### What is the expected *correct* behavior?

(What you should see instead)

### Relevant logs and/or screenshots

(Paste any relevant logs - please use code blocks (```) to format console output,
logs, and code as it's very hard to read otherwise.)

### Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Story points: 1.0
Updated and unified timestamp conventions

Time ago timestamps are displayed inconsistently throughout the web and mobile applications.

Please see below a clarification of how these dates should be displayed across mobile and web.

Dates can be displayed in one of two contexts:

1. Feed view. Utilise time ago values in the following short format.

* `8s` = '8 seconds ago'
* `30m` = '30 mins ago'
* `22h` = '22 hours ago'
* `Jun 14` = 'Anything that 24 hours or older. Do not display the year, where it is the current year'
* `Dec 25 2020` = 'Date from the previous calendar year'

2. Post context: When displaying a post outside of a feed, the full date/time should be displayed.

* `Jan 14 2021 · 1:42 am` / `14 Jan 2021 · 17:01`.

(Ideally the date time should be localised accordingly). e.g. FR -> `le 5 avril · 17:01`, DE -> `15. Juni 2021 · 15:22` etc...

![Screenshot_2021-06-15_at_15.26.43](/uploads/2054712560c5e6de3933e1811f1d0230/Screenshot_2021-06-15_at_15.26.43.png)

![Screenshot_2021-06-15_at_15.25.53](/uploads/d91d0540c3c094c97b64b47f4c510ce8/Screenshot_2021-06-15_at_15.25.53.png)

Story points: 3.0
Put initial hashtag selector behind the onboarding-october-2020 FF

<!---
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

(Summarize the bug encountered concisely)

### Steps to reproduce

(How one can reproduce the issue - this is very important)

### Platform information 

(Browser, device, system stats, screen size)

### What is the current *bug* behavior?

(What actually happens)

### What is the expected *correct* behavior?

(What you should see instead)

### Relevant logs and/or screenshots

(Paste any relevant logs - please use code blocks (```) to format console output,
logs, and code as it's very hard to read otherwise.)

### Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Story points: 1.0
Crash on discovery screen for thumbs without protocol

<!---
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

(Summarize the bug encountered concisely)

### Steps to reproduce

(How one can reproduce the issue - this is very important)

### Platform information 

(Browser, device, system stats, screen size)

### What is the current *bug* behavior?

(What actually happens)

### What is the expected *correct* behavior?

(What you should see instead)

### Relevant logs and/or screenshots

(Paste any relevant logs - please use code blocks (```) to format console output,
logs, and code as it's very hard to read otherwise.)

### Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Story points: 2.0
Permaweb is only available for plus users on mobile

<!---
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

(Summarize the bug encountered concisely)

### Steps to reproduce

(How one can reproduce the issue - this is very important)

### Platform information 

(Browser, device, system stats, screen size)

### What is the current *bug* behavior?

(What actually happens)

### What is the expected *correct* behavior?

(What you should see instead)

### Relevant logs and/or screenshots

(Paste any relevant logs - please use code blocks (```) to format console output,
logs, and code as it's very hard to read otherwise.)

### Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Story points: 1.0