Comments (2)
Sorry. It was my fault. I didn't explain extensively the ideas I've posted.
What is your use case for "[username] dice: [message]" instead of "[username] says: [message]"?
"dice" means "says" in Spanish. It was just an example. What I wanted to suggest was what the TTS reads should be customizable with variables/placeholders. Maybe someone doesn't want any word to be TTS'ed between the username and the message ([username] [message]) or maybe someone wants more than a word like "has commented" between the username and the message ([username] has commented [message]) or maybe only wants the message to be TTS'ed ([message]).
Long hold pressing a message from a user you should be able to mute them
Didn't know that you could long press and do moderation tasks. With that method the only way to mute an account from a TTS is when that account already chatted. If you could write the accounts you want to be ignored by TTS you could anticipate to it.
Is your use case you want a more visible list of who is muted (both app and user)?
As there is no visual indication on chat that a user has been TTS muted maybe a list of TTS muted accounts will be great or else the same applies from previous point as you will need that account to chat to check if is TTS muted or not or to unmute it.
If I ignore a command prefix the option to allow selected commands should be available and vice versa?
Yes. You could ignore all commands starting with "!" like !youtube !instagram !uptime .... but allow !hello command. Or vice versa. You could allow all commands starting with "!" like !hello !bye .... but ignore !youtube !instagram
Ignore a command prefix and allow selected commands or allow a command prefix and ignore selected commands the user will choose one or the other depending on how many commands the user want to ignore or allow. Added to the combination of ignore prefix and allow commands / allow prefix and ignore commands also the expected behavior should be with single options:
- Ignore a command prefix option only: Read on TTS everything except any message starting with that character.
- Ignore selected commands option only: Read on TTS everything except any message starting with that commands.
- Allow a command prefix option only: Only read on TTS the messages starting with that character.
- Allow selected commands option only: Only read on TTS the messages starting with that commands.
I am not sure I understand your last three points are they separate features or considerations for the six bulletin points you outlined?
Are considerations of the bulletin points. That was a brief explanation of what I wrote now on the above lines.
The single asterisk:
Ignore command prefix and ignore selected commands: The only use case where both should be available at the same time is when someone uses multiple command prefixes like "!" or "#" or any other character. That way you could ignore all the messages with a command prefix to be TTS'ed and ignore also selected commands with other prefixex. The same applies to allow command prefix and allow selected commands. I didn't saw anyone using multiple command prefixes on a stream but maybe someone does.
The two asterisks:
Allow selected commands should have priority over ignore command prefix. If you ignore a command prefix character and at the same time allow a selected command starting with the same character, the allowed command should have precedence over the ignored prefix and should TTS it. An example: If you allow a selected command like "!tts" but ignore the command prefix character "!". It should read any message starting with "!tts" command instead of ignore it.
from rtchat.
Work is ongoing to improve the tts engine right now. Looking over the list of ideas the ideal way to do this would be to try and keep it as simple as possible which is try because we shouldn't bury the settings like Twitch does right now. I have a few questions though as I am trying to understand each feature.
- This one may be done by muting viewer names. What is your use case for "[username] dice: [message]" instead of "[username] says: [message]"?
- Long hold pressing a message from a user you should be able to mute them, we also have some bots muted by default. Is your use case you want a more visible list of who is muted (both app and user)?
- If I ignore a command prefix the option to allow selected commands should be available and vice versa?
- I am not sure I understand your last three points are they separate features or considerations for the six bulletin points you outlined?
from rtchat.
Related Issues (20)
- Update the TTS button to set tts_channel instead if the boolean flag is true
- App bar color pallet is incorrectly set
- Remove shared_preferences dependency
- Remove the old TTS engine HOT 2
- theme data needs to be applied in other areas
- Text should be more visible on button to sign in
- Test TTS in the background HOT 2
- Add "TTS enabled"/"TTS disabled" messages HOT 1
- Disable TTS when stream goes offline HOT 2
- Disable TTS if the queue gets too long HOT 1
- Add an action button to the TTS notification that disables TTS
- Update getVocalization() to use this function
- Test against some live channels HOT 1
- [translations] add more languages
- [chat_history] visibility additions
- [notification] send a notification on disabled tts with the reason
- [notification] redraw notification not on each speak HOT 1
- TTS for subscribers only in twitch HOT 5
- Vido quality on preview HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from rtchat.