-
Notifications
You must be signed in to change notification settings - Fork 65
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
A few issues I have with recent changes. #20
Comments
I agree with everything you mentioned..... I'm at work, but tomorrow I can tackle these "problems". The URL parameter is a good idea, but it's "for us" that know how to do it... it's a bit hard for "Normal" users but I think I will add that and the "msg" parameter to the README file... |
@AConcernedThirdParty Thanks for the code feedback. I was on a coding spree that night and i totally agree it could be done better.
I did that for fun, will remove it. From now on only show related content.
Chrome used to ask permission at every load. I find it more immersive not to be asked every time, it's distracting from the whole Samaritan vibe. Speech url parameter could totally be done but how should a regular POI reddit fan know how to add or remove param?
The only other way is too make a separate json file and add them dynamically. This, I will totally do. |
I've tackled most of these issues. I've not done the "microphone URL parameter" thing... I've found something cool: http://samaritian.herokuapp.com/ And I'm done for today... :) |
Question Bro. If you know about the problems existing. Why don't you take On Sat, Jun 25, 2016 at 2:40 PM, Rodrigo Graça [email protected]
|
Question Bro. If you know about the problems existing. Why don't you take On Fri, Jun 24, 2016 at 7:50 AM, AConcernedThirdParty <
|
He just said he is out of country |
Not criticising the changes made - In fact I think they're brilliant ideas, but I have problems with a few things.
Firstly, in speech.js, I have a feeling that a few phrases may not be in tune with the theme of the show, (i.e. phrases Samaritan would say). For example, "Say my name", "Heisenberg".
Secondly, I believe the user should get a choice as to whether speech recognition is activated on each page load. Granted, the user is asked whether to grant Samaritan access to their microphone on first load (by the browser), but it's not asked afterwards. Perhaps only enabling it through the "speech" url parameter?
Thirdly, a few formatting/file location problems.
Finally, it'd be nice if a .woff, in addition to the .ttf is added. This would allow the MagdaCleanMono font to show up on Firefox/IE/Other browsers not supporting .ttf.
I would write some code and tackle a few of these issues, but I'm currently out of the country and typing this up on my mobile.
The text was updated successfully, but these errors were encountered: