giseldo/neodataset huggingface dataset:
NSFW filter settings entry missing

<!---
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

No entry to configure visibility of NSFW posts. There is such an entry in the web interface and only there it can be configured.

### Steps to reproduce

Choose Settings from menu. There are entries for Email and Password, but nothing for NSFW filter. In the web interface these three settings are together on one page.

### Platform information

Android, Galaxy S8+, latest version.

### App version

3.5.0

### What is the current *bug* behavior?

Users can't change NSFW visibility status from app.

### What is the expected *correct* behavior?

Users can change NSFW visibility status from app.

### Relevant logs and/or screenshots

(none)

### Possible fixes

None known.

Story points: 1.0
(bug) Reminding returns to the newsfeed after reminding.

<!---
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

@Peggy:
> One little annoyance on the new iOS release is that after I remind something from my newsfeed it doesn’t take me right back to where I was. I end up back one or two posts before it.

Have seen a few people complaining about this.

### Steps to reproduce

1. Navigate to a group on a test account 
2. Remind
3. Observe you are returned to newsfeed

### Platform information

(Device, Android/iOS version, system stats, screen size)

### App version

v3.5.0

### What is the current *bug* behavior?

User is returned to the newsfeed

### What is the expected *correct* behavior?

User should not lose their place in the group. There should be no redirection.

### 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
(Bug) Remove 'decrypting' messages from chat after regenerating messenger keys.

<!---
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 you "Regenerate messenger keys" in settings it gives you a successful prompt however when going back into messenger and sending a message comes up "decrypting" as it never logged you out of messenger to re-enter the new password.  

### Steps to reproduce

Login and regenerate messenger keys in setting and try sending a message 

### Platform information

Android APP
### App version

V3.50 (20190509)

### What is the current *bug* behavior?
Doesn't log out of messenger after regenerating keys 

### What is the expected *correct* behavior?
Log out of messenger to input new password.

### Relevant logs and/or screenshots



### Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Story points: 4.0
App freezes when tapping item under Boost notifications

Tapping on a hyperlinked item under Boost notifications causes app to freeze

### Steps to reproduce

Go to notifications > tap on the post of a completed boost > app crashes

### Platform

IOS mobile

### app release

3.5.0 201904300001

### What is the current *bug* behavior?

Tap on the boost notification and app freezes

### What is the expected *correct* behavior?

App should route user to the post that was boosted

### 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
(bug) iOS: Blacked out NSFW content - unable to click

<!---
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

@fizzymatt
> Following the most recent update, the 18+ content (on IPhone 6 SE) now appears to be blacked out, and doesn’t respond to a click / press. Is this a bug, or is there a setting I need to change?

https://www.minds.com/newsfeed/969325103049154560

### Steps to reproduce

(How one can reproduce the issue - this is very important)

### Platform information

iPhone 6 SE
 
### App version

v3.4.0

### What is the current *bug* behavior?

User cannot view NSFW content

### What is the expected *correct* behavior?

User should be able to click to view.

### 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
(bug) Cannot edit or set explicit already posted content.

UberTesters bug 29
Scenario:
1. Create a post with a hashtag.
2. Search for the created content using the hashtag.
3. Choose the 3-dot icon to set content explicit or to edit the post.

Actual result: Error message in red appears: "Can't show this post".
**Expected result: **The selected action should be conducted.

Story points: 2.0
(bug) Cannot accept group invites

<!---
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

Peggy
> When I tapped on a notification from @benhayward it went gray and didn’t take me to it

### Steps to reproduce

(How one can reproduce the issue - this is very important)

### Platform information

iPhone 7 / iOS 9

### App version

v3.4.0

### What is the current *bug* behavior?

Cannot accept group invite, sent to grey screen. 

### What is the expected *correct* behavior?

Should be able to accept the invite and use the group as expected.

### Relevant logs and/or screenshots

![Wire_2019-04-23_at_17.08.20](/uploads/648f1ca47c3ed30052493b0ddccb1660/Wire_2019-04-23_at_17.08.20.png)

### Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Story points: 2.0
(bug): Long Messages not being sent

<!---
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

Long messages are not sent, and are lost unless you happen to select all and copy before trying to send.

### Steps to reproduce

1. Send a long message (a few paragraphs worth of text)
2. It should appear as if the message is sent.
3. Press the back button
4. Re-open the chat
5. Observe your message was not sent 

### Platform information

Replicated on Android but I'd imagine it would be universal.

### App version

v3.3.0

### What is the current *bug* behavior?

Message appears to have sent until you leave and rejoin the chat.

### What is the expected *correct* behavior?

The user should be made aware if the message is too long and it should not disappear from the input box after they are warned. Ideally there should be some indicator of how many characters over the limit they are so that they can make necessary amendments.

### 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
Fix missing MText imports

<!---
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
Base UI Typography components


### Summary

Implement the base typography component following the design guidelines #3608 

I'm splitting each of the base components creation into three parts.

#### Creation
Creation of the base component initial version following what was done and agreed on the Icon one. This is composed of structure, design and single use.

#### Spread
Spread it throughout the current UI in order to understand how it can be best adapted for using in the legacy application, adapting the props and exposing the necessary component wrappers.

#### Performance
Analyze the component's performance on the benchmarking tool to understand if any additional tweaks could be made to improve it's render/update phase either through memoization or exposing new wrappers.

Story points: 4.0
Add live username checking to register screen

<!---
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 autofocus on register/login

<!---
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
Improve login and session switching transition

<!---
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
Update locales for 4.19.0

<!---
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
Update react-native-vision-camerat to 2.8.3

<!---
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
Use theme colors in captcha modal

<!---
Please read this!

Before opening a new issue, make sure to search for keywords in the issues
filtered by the "T - Bug" label and verify the issue you're about to submit isn't a duplicate.
--->

### Summary

(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
Captcha should display errors and try again

<!---
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
Remove double border in some list components

<!---
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
Unable to upload media

### Summary

User [@Clover2992](https://www.minds.com/Clover2992/) is unable to upload media via app.

### Steps to reproduce

(How one can reproduce the issue - this is very important)

### Platform information 

Minds apk, galaxy note 10+ / kernel version 4.14.190-22338387-abN975USQS7FUH7

### What is the current *bug* behavior?

When the user attempts to upload media, they are met with blank screens
![Screenshot_20210926-215524_Minds](/uploads/f0b632eac5c1dd5ab06f7d424543db93/Screenshot_20210926-215524_Minds.jpg)

![Screenshot_20210926-215518_Minds](/uploads/e455ae6efba8b416e66709c7db0e7bc2/Screenshot_20210926-215518_Minds.jpg) 

Unable to proceed further

### 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
Fix text with react-native 0.65

<!---
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
InAppBrowser: Add The Option To Change Default Browser

Currently all links are using in-app browser. This opens SafariServices/AuthenticationServices on iOS and Chrome Custom Tabs on android. But we should also give users the option to use their own browsers.

**as a user I want to be able to use my own browser when viewing links**
- given I've clicked a link for the first time, a bottom sheet should be shown in which I can select whether I want to use the in-app browser or my own browser
  - I should see a hint that I can change this behavior later in settings
  - After selecting the option, links should always use my preference
- given I want to change the default behavior of external link openings, I should see an option in settings that allows me to change this settings
  - this option should be in ___ [TBD]

Story points: 3.0
Actionsheet / active keyboard issue

### Summary

When the search input in discovery is active (keyboard displayed), tapping on the filter icon, the actionsheet is launched, but the keyboard is not killed. See screenshot below.

### Steps to reproduce

See above

### Platform information 

iOS - 4.18.0

### What is the expected *correct* behavior?

In such a case, the keyboard should be hidden, so the action sheet is fully accessible.

### Relevant logs and/or screenshots

![IMG_0642](/uploads/62f3d5ac4ef935da22cc39bf4c8dafbf/IMG_0642.PNG)

### Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Story points: 1.0
Test update process for 4.18

<!---
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
Can't reach the server error in notifications


![Simulator_Screen_Shot_-_iPhone_12_-_2021-09-16_at_16.41.12](/uploads/2c150fd1bfedfe452cb2b5d1e31e27b6/Simulator_Screen_Shot_-_iPhone_12_-_2021-09-16_at_16.41.12.png)
### Summary

Seems to happen in new accounts or when there is no notifications to show

Story points: 2.0
Video upload issues

## Summary

When you capture a portrait video directly on the app, there are multiple issues.

1. Immediately after posting, the dimensions are wrong and the post says There was an error displaying the media. This is really bad UX and makes the user think something broke, as the video has an error message and does not play.

![IMG_7882](/uploads/6d6294ed10da1f202d64baddbee8baa6/IMG_7882.PNG)



2. After a few minutes, the error message goes away. However, the dimensions are still incorrect on the thumbnail, and when you play the video, it converts to portrait but is squashed into landscape dimensions.

![IMG_7883](/uploads/58a262c3b84a3f1fb14fa2ecdff6c496/IMG_7883.PNG)

Story points: 3.0
Notification issues

## Summary

- Issues with notifications in the latest build.

## Issue 1

- Can only see two notifications in the All notifications tab for the @mindsplus account, despite knowing there are thousands. When you filter to specific notification types, you see more of them. Video is too large to upload.

## Issue 2

- Within the notification tabs, there are multiple issues with spacing causing things to overlap

**Screenshots**

![IMG_7885](/uploads/2481d2de4ad5d957e86a1eee6083ae30/IMG_7885.PNG)

![IMG_7884](/uploads/107121354d702891dfc99dd42868fe86/IMG_7884.PNG)

Story points: 3.0
Enable the search, discovery and comments on play store version

<!---
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