-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Mycroft's blocking of curse words ****
interfere with searches and other functionality
#1221
Comments
(This is actually a real bug despite my newness to the project and its unusual nature.) |
I ran into this too. Would be much better to have it just as an option instead of as a default. |
This was up for discussion last week, I think the conclusion was to make changes to allow this to be turned off. @matheuslima can you comment on this? |
I am from Jersey and swear a lot, this is a problem for me too. |
any progress on this issue? the censoring is really annoying. |
Hey I wasn't around when this issue first got raised so wasn't part of those discussions, but this is actually the Google STT service that we use doing the censoring. Would need to see if there's a flag we can set on the requests to turn it off. If anyone knows already, please chime in. |
From a very brief skim of this issue I've been able to determine the following:
What I tried to do as a workaround was implement a new
This then requires support in the
(At this point my microphone stopped working with Mycroft for some strange reason, and nothing I did could get it to pick up the microphone again, so I couldn't continue testing) This didn't work - the |
I tested the google STT module and profanity filter seems to be off by default, but requires one self to have a google cloud account to use. The API used by the Mycroft backend (which is not the google cloud Speech to Text service, but another of Google's older APIs) always has it enabled and doesn't allow turning it off if I recall correctly. A config setting is probably a good idea though. Default should be off in my opinion. |
this issue probably should be moved to selene repo since thats where STT happens this setting is not supported by the speech recognition package, but can be enabled/disabled if you use the api directly to disable profanity filter see https://github.com/OpenVoiceOS/ovos-stt-plugin-chromium , this is what we use in the ovos local backend (no mycroft needed for ovos plugins) |
Closing Issue since we're archiving the repo |
(For this bug report
####
will indicate my own self-selected censorship, as I don't know the policies of this project regarding cursing.****
will indicate Mycroft censoring words.)While testing a skill I realized that somewhere in the parsing of my input it’s turning detected curse words into asterisks, such as the query "
####
you" being interpreted as “****
you”. This may be a reasonable default, but I want to play albums that contain explicit titles, and this feature breaks that functionality.This seems to affect the core, not just a third party skill:
Steps to reproduce:
####
you." (If you were searching for a song title you could be saying something like, "hey Mycroft, play####
the police by NWA")Observed behavior:
Mycroft reports and interprets "
####
you" as "****
you."Expected behavior:
Mycroft doesn't censor curse words, as they're necessary for playing songs with explicit titles. Optionally, this should be a configurable and documented behavior.
The text was updated successfully, but these errors were encountered: