giseldo/neodataset huggingface dataset:
(bug): The "Join" button and "Gathering" button are getting hidden along with member avatars in the web app when the screen width gets smaller than 600px or so.

<!---
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

This is preventing users from joining/leaving groups and joining gatherings in mobile browsers.

### Steps to reproduce

1. Visit a group you have not joined yet in Chrome on a laptop or desktop computer.
2. Reduce the width of the screen down to 600px and smaller.

### Platform information

(Device, Android/iOS version, system stats, screen size)

### App version

(App version and build number)

### What is the current *bug* behavior?

The "Join" button and "Gathering" button are getting hidden along with member avatars in the web app when the screen width gets smaller than 600px or so.

### What is the expected *correct* behavior?

The "Join" button and "Gathering" button should remain visible at all screen widths. So should member avatars in my opinion.

### Relevant logs and/or screenshots

![23](/uploads/d0720acd03fda09c211274677469b49f/23.png)

![24](/uploads/06acd9f0614a8a3a7c598bf8d230574c/24.png)

### Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Story points: 2.0
(bug): change detection not firing on comment post

<!---
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 block function appears broken for comments on posts to channels because change detection is not firing immediately.

### Steps to reproduce

1. Have your primary channel block your secondary channel.
2. Visit your primary channel as your secondary channel.
3. Comment on the first post.
4. Click on elipses and error message appears...it should appear immediately on post

### Platform information 

Chrome/Win10 and Firefox/Win10.

### What is the current *bug* behavior?

Blocked users are now able to comment on the blocker's posts to their channel.

### What is the expected *correct* behavior?

Blocked users should not be able to comment on the blocker's posts anywhere. A red error message used to and should get displayed above or below the comment informing them that the channel has blocked them.

### Relevant logs and/or screenshots

https://www.minds.com/newsfeed/940042484220698634

### Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Story points: 2.0
(bug): Comments frequently miss out last character if enter key pressed too soon

<!---
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.
--->

### Steps to reproduce

- Create a comment
- Press enter key quickly

### Platform information 

Chrome, Firefox

### What is the current *bug* behavior?

- Enter keys misses out last character

### What is the expected *correct* behavior?

- Last character remains

### Relevant logs and/or screenshots

![Screen_Shot_2019-02-06_at_8.19.47_AM](/uploads/a61440e566ed0053d1a345652f20c17d/Screen_Shot_2019-02-06_at_8.19.47_AM.png)

### Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Story points: 2.0
Images in comments are not working when clicked in web 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

When clicking through to view an image from a thread (https://www.minds.com/newsfeed/938949270826668032), it is coming up as a "post may not exist" error.  It works in the apps, but not in the web app.

Image link e.g. https://www.minds.com/media/938988244965883904

### Steps to reproduce

Go to the chat in top link, scroll down and click the image.

### Platform information 

Windows 10, Chrome, Brave

iPhone SE, Safari

### What is the current *bug* behavior?

### What is the expected *correct* behavior?

Image should display as normal on all browsers/apps.

### Relevant logs and/or screenshots

![comment_image_2](/uploads/9f7c1672afca5f4105a110102564e47f/comment_image_2.PNG)

![comment_image](/uploads/fac3b0e0fc8634a294e9e8049d185189/comment_image.PNG)

### Possible fixes

Story points: 2.0
(bug): Blog post titles not visible on Blog page (brave-browser only)

<!---
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

When browsing to the Blog page accessed from the top nav-bar, the icons of the blog posts are visible, but not their corresponding titles.

This issue was raised in the H&S convo-feed by @moonlit45 (see video below)
I was unable to reproduce this problem using the Firefox browser, nor the Chromium browser. I was however able to reproduce it on the Brave browser.


### Steps to reproduce

Using the Brave browser, click on 'Blogs' from the top nave-bar on the main feed.


### Platform information 

Version 0.59.34 Chromium (brave- default settings): 72.0.3626.81 (Official Build) (64-bit); Linux Mint 19.1 Tessa x86_64 - Kernel: 4.15.0-43-generic 


### What is the current *bug* behavior?

The blog tiles/icons appear as expected, but their corresponding titles are hidden or otherwise not visible.


### What is the expected *correct* behavior?

We should see The blog tiles/icons as well as their corresponding titles.

### Relevant logs and/or screenshots

Here is a screenshot of the problem:
![Workspace_2_519](/uploads/6e58caab36764c52afd8eb28a3bd5bbb/Workspace_2_519.png)

Here is a video of the conversation:
![moolit45](/uploads/59c5780d082f7a0bd9bd5a9a45195c61/moolit45.mp4)

### Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Story points: 3.0
(feat): add text to channels letting users know if a channel is currently subscribed to them or not

"We can tell who we subscribe to obviously. But can we have a way to tell who has subscribed back (other than the initial notification, I mean , who can keep track?). Like something that shows up on their page ( subscribes to you) or something like that?"

Requested by @Paraliege: https://www.minds.com/newsfeed/938778226857889792

Story points: 3.0
(bug): defunct "BACK TO ALBUM" button still showing on media pages for images posted to 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

Example: https://www.minds.com/media/938180190234497024

### Steps to reproduce

1. Visit a group.
2. Click on an image in a post or click on an image in the image gallery for that group.

### Platform information 

(Browser, device, system stats, screen size)

### What is the current *bug* behavior?

(What actually happens)

### What is the expected *correct* behavior?

Change the text to "BACK TO GALLERY" and link to the image gallery for that group.

### Relevant logs and/or screenshots

![17](/uploads/324ee2a6d1c4694c6b461a9b56cc354b/17.png)

### Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Story points: 3.0
(feat)[front]: Onboarding flow for a new channel takes user to "set up ethereum wallet" after you click on "Subscribe to new channels"

### Summary

Onboarding flow takes new user to the "set up ethereum wallet" post in newsfeed after clicking on "subscribe to new channels"

### Steps to reproduce

Create a new channel and click on subscribe to new channels

### Platform information 

all web app

### What is the current *bug* behavior?

When the user clicks on subscribe to new channels they are take to "set up ethereum wallet" post in the newsfeed

### What is the expected *correct* behavior?

Should deliver user to the channel selections page

### 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
(feat)[front]: Save button (check mark on profile)  is not obvious to a new user in onboarding process

When creating a new channel in onboarding process, the save button (check mark in profile) is not obvious to a new user and after adding a banner and avatar, etc, the user may not see the check mark and the user is likely to leave the page without saving and is left guessing after the channel page goes blank.

Check mark should be changed to a Save button... or use a color, or a dialogue pops in to remind to save before leaving page.

Story points: 4.0
(bug): Cannot cancel recurring payments.

<!---
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

Users are not able to cancel recurring payments

https://www.minds.com/newsfeed/951236223496462336

https://www.minds.com/newsfeed/951439130191831040

### Steps to reproduce

1. Set up a recurring payment to a test user of yours.
2. Try to cancel the payment.

### Platform information 

Replicated cross-platform web.

### What is the current *bug* behavior?

User cannot cancel a recurring transaction

### What is the expected *correct* behavior?

User should be able to cancel a recurring transaction

### Relevant logs and/or screenshots

![recurringpay](/uploads/ef26f66f756569fe6c8535cc3aa1b52b/recurringpay.mp4)

### Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Story points: 5.0
Blogs are not showing titles in Brave

<!---
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

Viewing blogs yields no title or extra data - only banner is shown 

### Steps to reproduce

View blogs in Brave

### Platform information 

Brave, Windows 10

### What is the current *bug* behavior?



### What is the expected *correct* behavior?

Should display information as it does in Chrome

### Relevant logs and/or screenshots

![blogs](/uploads/d1b10fee50b111975fcc52d879cc04f6/blogs.PNG)

### Possible fixes

Story points: 2.0
(bug): users which have been removed from a group can still post if they don't refresh

<!---
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

Users which have been removed from a group can still post if they don't refresh.

### Steps to reproduce

1. Create a group with your primary account.
2. Have your secondary account join the group.
3. Have your primary account remove your secondary account from the group.
4. Without refreshing, have your secondary account create a post in the group.

### Platform information 

Chrome/Win10

### What is the current *bug* behavior?

Users which have been removed from a group can still post if they don't refresh.

### What is the expected *correct* behavior?

Users which have been removed from a group but haven't refreshed yet should get an error message if they try to post, comment or vote on a post in the group.

### 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: 5.0
(bug): receiver address is getting cut off causing users to copy incorrect address

<!---
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 receiver address in the wallet is cut off so it does not display the entire address. This is causing users to incorrectly copy their receiver address as they think that is the entire thing.

### Steps to reproduce

1. Go to wallet
2. View receiver address on left hand panel
3. Click Addresses tab
4. Notice the address in the addresses tab is much longer

### Platform information 

Any browser


### What is the expected *correct* behavior?

You should see the entire receiver address in the left hand side of wallet.

### Relevant logs and/or screenshots

![41](/uploads/3a0d7b5f8f67a97516f045340c3d2c93/41.png)

### Possible fixes

Remove Overflow:hidden CSS rule so that it does not cut it off.

Story points: 3.0
(bug): Users are able to add more than 5 hashtags to a post by adding them manually.

<!---
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

Users are able to add more than 5 hashtags to a post by adding them manually.

### Steps to reproduce

1. Visit your channel.
2. Upload an image in the create post box.
3. Click the hashtags button.
4. Add 5 hashtags.
5. Click on the post description input field.
6. Add a 6th hashtag manually.

### Platform information 

(Browser, device, system stats, screen size)

Firefox/Win10

No error message is displayed and the user is able to create a post with 6 or more hashtags. This can also be done when editing a post.

### What is the expected *correct* behavior?

The error message should be displayed whenever it detects more than 5 hashtags in the description input field and the user should not be able to create the post. The same thing should happen when editing a post.

### 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
(feat): groups to remember if conversations is minimized if you navigate away

### Summary

If you are in a group and minimize the conversations sidebar, it should stay minimized always in all groups.

If you are in a group and keep the conversations sidebar expanded, it should stay expanded always in all groups.

### Steps to reproduce

1. Go into a group
2. Minimize the group conversations panel
3. Click on Newsfeed
4. Return to the group (group conversations is present again)
5. If you only navigate between groups, it works as it should and remembers. 

### Platform information 

iOS, MacBook air

### What is the expected *correct* behavior?

The group should remember if you had the conversations expanded or closed at all times. 

### Relevant logs and/or screenshots


![conversation_remember_last_place](/uploads/74649c986dccae6fc42270860d5217a0/conversation_remember_last_place.mov)

Story points: 10.0
(bug): group sidebar cutoff in search

<!---
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)

search something

### Platform information 

(Browser, device, system stats, screen size)

firefox, ubuntu

### 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.)

![Screenshot_from_2019-01-28_10-53-32](/uploads/287449cd9dfe1bfd89ccf008db1f3f12/Screenshot_from_2019-01-28_10-53-32.png)

### Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Story points: 1.0
(bug): Rich embed does not re-sanitize sites with poorly encoded HTML entities correctly in description

<!---
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

Full summary from a user: https://www.minds.com/newsfeed/936109459483484160

### Steps to reproduce

Post this link and look at the link preview: https://babylonbee.com/news/snopes-introduces-new-factually-inaccurate-but-morally-right-fact-check-result

### Platform information 

(Browser, device, system stats, screen size)

### What is the current *bug* behavior?

The meta info for the link isn't being displayed correctly due to not properly processing HTML entities.

### What is the expected *correct* behavior?

The meta info for the link should process HTML entities correctly and this should fix the display of the link preview meta info.

### 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
(bug): "tagged in a conversation" notifications should take the user to the part of the conversation where the comment is which contains the tag.

<!---
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

"tagged in a conversation" notifications should take the user to the part of the conversation where the comment is which contains the tag.

### Steps to reproduce

Click on a "tagged in a conversation" notification.

### Platform information 

(Browser, device, system stats, screen size)

### What is the current *bug* behavior?

It just loads the group but doesn't take the user to the place in the conversation where the comment is which contains the tag. If there have been hundreds of comments since then the user would have to scroll up and search for it.

### What is the expected *correct* behavior?

Perhaps use the same technique we just implemented for comment notifications. Take users to the section of the conversation where the comment is which contains the tag and just have a "Load Earlier" button at the top and a "Load Later" button at the bottom of the conversation window.

### 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: 20.0
(bug): Periods and commas at the end of Minds URLs are breaking the 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

This group URL with a period at the end, for example, redirects to the home page: "https://www.minds.com/groups/profile/895736713097809920/feed."

### Steps to reproduce

Visit "https://www.minds.com/groups/profile/895736713097809920/feed."

And: "https://www.minds.com/groups/profile/895736713097809920/feed,"

### Platform information 

Chrome/Win10.

### What is the current *bug* behavior?

Minds URLs with periods and commas at the end redirect to the home page.

### What is the expected *correct* behavior?

Periods and commas should not break Minds URLs. Users add them all the time in posts and comments and they end up breaking the URL.

### 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
(bug): blank counts still showing in group inviter

<!---
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)

(bug): blank counts still showing in group inviter

### Steps to reproduce

(How one can reproduce the issue - this is very important)

invite someone in a closed group

### Platform information 

(Browser, device, system stats, screen size)

ubuntu chome

### 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

no counters should be there

(Paste any relevant logs - please use code blocks (```) to format console output,
logs, and code as it's very hard to read otherwise.)

![Screenshot_from_2019-01-24_13-58-32](/uploads/1516e19142a0162ac9368bb0abbf3e91/Screenshot_from_2019-01-24_13-58-32.png)

### Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Story points: 2.0
(bug): legacy comments show duplicate on scroll

### Summary

Every time you go to a group conversation, the top of the visible thread shows duplicate comments. 

### Steps to reproduce

Go to any group and view the conversation thread.

### Platform information 

Chrome, Macbook air, iOS 10.14.1

### What is the expected *correct* behavior?

No duplicate comments ever shown.

### Relevant logs and/or screenshots

![Screen_Shot_2019-01-22_at_4.33.46_PM](/uploads/7ceb554be867f804b3c3bb25cdcc37cc/Screen_Shot_2019-01-22_at_4.33.46_PM.png)

![Screen_Shot_2019-01-22_at_4.33.29_PM](/uploads/97159aa54b3f64677fc6087ef5f4ea76/Screen_Shot_2019-01-22_at_4.33.29_PM.png)

![Screen_Shot_2019-01-22_at_4.33.34_PM](/uploads/af4f843f7102872f00f52c15d69d1f24/Screen_Shot_2019-01-22_at_4.33.34_PM.png)

Story points: 2.0
(bug): group avatar not updating in sidebar nav after updating avatar

<!---
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)

(bug): group avatar not updating in sidebar nav after updating avatar

### Steps to reproduce

(How one can reproduce the issue - this is very important)

change avatar, refresh, no change. 

### Platform information 

(Browser, device, system stats, screen size)

ubuntu, chrome

### What is the current *bug* behavior?

(What actually happens)

ideally would update live but atleast on refresh

### 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