Add new Speaker "Katja" from Microsoft

[guidonator]

Currently just "Hedda" is available for German, could you also add "Katja"?

[jishi]

Did you mean to open this issue in the https://github.com/jishi/node-sonos-http-api?

I'd appreciate if you could create a PR adding the info in https://github.com/jishi/node-sonos-http-api/blob/master/lib/tts-providers/microsoft.js, where it needs language, sound font and gender as well.

[guidonator]

Hi. Sorry, I'm very new to github, just signed in to ask you. I thought I opened this issue in the correct place. But meanwhile, after spending several hours I am close to giving up. :( - - added file "settings.json" to configure microsoft tts - - added API Key (in quotes), "Hedda" (to be sure a working voice is used) - - in microsoft.js: - - changed uri in function generateBearerToken to ' https://westeurope.api.cognitive.microsoft.com/sts/v1.0/issuetoken' (copied from Azure Website) - - changed uri after "return request({..." to ' https://westeurope.tts.speech.microsoft.com/cognitiveservices/v1' (as suggested here: https://gitter.im/node-sonos-http-api/Lobby?at=5bd577aa3844923661adf865 ) but when trying to "say" something "IP:5005/Schlafzimmer/say/Something" always got: {"status":"error","error":"Got status 403 when invoking /cognitiveservices/v1","stack":"Error: Got status 403 when invoking /cognitiveservices/v1\n at /home/guido/node-sonos-http-api-master/lib/tts-providers/microsoft.js:88:12"} Before changing the second uri, I always got this error: {"status":"error","error":"Got status 401 when invoking /synthesize","stack":"Error: Got status 401 when invoking /synthesize\n at /home/guido/node-sonos-http-api-master/lib/tts-providers/microsoft.js:88:12\n ...and I really like the voice "Katja", but after countless tries... :( Perhaps you could give me some good advice. Thanks a lot for your great work, Guido Am Mo., 15. Nov. 2021 um 11:27 Uhr schrieb Jimmy Shimizu < ***@***.***>:

…

Did you mean to open this issue in the https://github.com/jishi/node-sonos-http-api? I'd appreciate if you could create a PR adding the info in https://github.com/jishi/node-sonos-http-api/blob/master/lib/tts-providers/microsoft.js, where it needs language, sound font and gender as well. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#75 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AVJAM67STUVGLCAPTUHIOX3UMDOAHANCNFSM5IALWLKQ> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

[jishi]

401 usually means that you don't pass any authentication info, and 403 means that the authentication is invalid or you don't have the permission to call it. I haven't worked nor tested the Microsoft integration in a long time, so I don't have any good pointers right now. The Microsoft tts is very complex to integrate against because of the bearer-token approach, and they seem to like changing things up from time to time (which is a sure way to piss people off...)

…

On Tue, 16 Nov 2021, 20:51 Guid-o-nator, ***@***.***> wrote: Hi. Sorry, I'm very new to github, just signed in to ask you. I thought I opened this issue in the correct place. But meanwhile, after spending several hours I am close to giving up. :( - - added file "settings.json" to configure microsoft tts - - added API Key (in quotes), "Hedda" (to be sure a working voice is used) - - in microsoft.js: - - changed uri in function generateBearerToken to ' https://westeurope.api.cognitive.microsoft.com/sts/v1.0/issuetoken' (copied from Azure Website) - - changed uri after "return request({..." to ' https://westeurope.tts.speech.microsoft.com/cognitiveservices/v1' (as suggested here: https://gitter.im/node-sonos-http-api/Lobby?at=5bd577aa3844923661adf865 ) but when trying to "say" something "IP:5005/Schlafzimmer/say/Something" always got: {"status":"error","error":"Got status 403 when invoking /cognitiveservices/v1","stack":"Error: Got status 403 when invoking /cognitiveservices/v1\n at /home/guido/node-sonos-http-api-master/lib/tts-providers/microsoft.js:88:12"} Before changing the second uri, I always got this error: {"status":"error","error":"Got status 401 when invoking /synthesize","stack":"Error: Got status 401 when invoking /synthesize\n at /home/guido/node-sonos-http-api-master/lib/tts-providers/microsoft.js:88:12\n ...and I really like the voice "Katja", but after countless tries... :( Perhaps you could give me some good advice. Thanks a lot for your great work, Guido Am Mo., 15. Nov. 2021 um 11:27 Uhr schrieb Jimmy Shimizu < ***@***.***>: > Did you mean to open this issue in the > https://github.com/jishi/node-sonos-http-api? > > I'd appreciate if you could create a PR adding the info in > https://github.com/jishi/node-sonos-http-api/blob/master/lib/tts-providers/microsoft.js , > where it needs language, sound font and gender as well. > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub > < #75 (comment) >, > or unsubscribe > < https://github.com/notifications/unsubscribe-auth/AVJAM67STUVGLCAPTUHIOX3UMDOAHANCNFSM5IALWLKQ > > . > Triage notifications on the go with GitHub Mobile for iOS > < https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 > > or Android > < https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub >. > > — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#75 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAYE2I3AIAR7KPV7DFGLORTUMKY2XANCNFSM5IALWLKQ> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

[guidonator]

Hi Jimmy, thanks for answering so quickly! :) So at the moment I am very.. frustrated. :( The standard-google-voice is soo awful and sounds bored-beyond-belief, voicerss sounds like voice-synthesis directly from 1995, AWS is not free (also it might be quite cheap if everything works like it should)... I also tried to check my authentication / bearer-token like described here: https://docs.microsoft.com/en-us/azure/cognitive-services/speech-service/troubleshooting Well, it seems to work if I understand the answer correctly... It also seems that the certificate expires in half a year? Or is this the API-Key..? ..basically I wanted to alarm if my window was opened too long.. slowly I think it might not be worth it.. :( Probably I should try to make an mp3 and play that... Thanks again, Guido Am Di., 16. Nov. 2021 um 21:23 Uhr schrieb Jimmy Shimizu < ***@***.***>:

…

401 usually means that you don't pass any authentication info, and 403 means that the authentication is invalid or you don't have the permission to call it. I haven't worked nor tested the Microsoft integration in a long time, so I don't have any good pointers right now. The Microsoft tts is very complex to integrate against because of the bearer-token approach, and they seem to like changing things up from time to time (which is a sure way to piss people off...) On Tue, 16 Nov 2021, 20:51 Guid-o-nator, ***@***.***> wrote: > Hi. > > Sorry, I'm very new to github, just signed in to ask you. I thought I > opened this issue in the correct place. > But meanwhile, after spending several hours I am close to giving up. :( > > > - - added file "settings.json" to configure microsoft tts > - - added API Key (in quotes), "Hedda" (to be sure a working voice is > used) > - - in microsoft.js: > - - changed uri in function generateBearerToken to ' > https://westeurope.api.cognitive.microsoft.com/sts/v1.0/issuetoken' > (copied from Azure Website) > - - changed uri after "return request({..." to ' > https://westeurope.tts.speech.microsoft.com/cognitiveservices/v1' (as > suggested here: > https://gitter.im/node-sonos-http-api/Lobby?at=5bd577aa3844923661adf865 > ) > > > but when trying to "say" something "IP:5005/Schlafzimmer/say/Something" > always got: > > {"status":"error","error":"Got status 403 when invoking > /cognitiveservices/v1","stack":"Error: > Got status 403 when invoking /cognitiveservices/v1\n at > > /home/guido/node-sonos-http-api-master/lib/tts-providers/microsoft.js:88:12"} > > Before changing the second uri, I always got this error: > > {"status":"error","error":"Got status 401 when invoking > /synthesize","stack":"Error: Got status 401 when invoking > /synthesize\n at > > /home/guido/node-sonos-http-api-master/lib/tts-providers/microsoft.js:88:12\n > > ...and I really like the voice "Katja", but after countless tries... :( > > > Perhaps you could give me some good advice. > > Thanks a lot for your great work, > > Guido > > > > > > > > Am Mo., 15. Nov. 2021 um 11:27 Uhr schrieb Jimmy Shimizu < > ***@***.***>: > > > Did you mean to open this issue in the > > https://github.com/jishi/node-sonos-http-api? > > > > I'd appreciate if you could create a PR adding the info in > > > https://github.com/jishi/node-sonos-http-api/blob/master/lib/tts-providers/microsoft.js > , > > where it needs language, sound font and gender as well. > > > > — > > You are receiving this because you authored the thread. > > Reply to this email directly, view it on GitHub > > < > #75 (comment) > >, > > or unsubscribe > > < > https://github.com/notifications/unsubscribe-auth/AVJAM67STUVGLCAPTUHIOX3UMDOAHANCNFSM5IALWLKQ > > > > . > > Triage notifications on the go with GitHub Mobile for iOS > > < > https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 > > > > or Android > > < > https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub > >. > > > > > > — > You are receiving this because you commented. > Reply to this email directly, view it on GitHub > < #75 (comment) >, > or unsubscribe > < https://github.com/notifications/unsubscribe-auth/AAYE2I3AIAR7KPV7DFGLORTUMKY2XANCNFSM5IALWLKQ > > . > Triage notifications on the go with GitHub Mobile for iOS > < https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 > > or Android > < https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub >. > > — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#75 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AVJAM65FFGTC56ZL4ZCJDO3UMK4THANCNFSM5IALWLKQ> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

[jishi]

If you don't want dynamic text to speech, and only need the same phrases spoken out, then creating your own mp3s would be far easier, yes.

…

On Tue, 16 Nov 2021, 21:43 Guid-o-nator, ***@***.***> wrote: Hi Jimmy, thanks for answering so quickly! :) So at the moment I am very.. frustrated. :( The standard-google-voice is soo awful and sounds bored-beyond-belief, voicerss sounds like voice-synthesis directly from 1995, AWS is not free (also it might be quite cheap if everything works like it should)... I also tried to check my authentication / bearer-token like described here: https://docs.microsoft.com/en-us/azure/cognitive-services/speech-service/troubleshooting Well, it seems to work if I understand the answer correctly... It also seems that the certificate expires in half a year? Or is this the API-Key..? ..basically I wanted to alarm if my window was opened too long.. slowly I think it might not be worth it.. :( Probably I should try to make an mp3 and play that... Thanks again, Guido Am Di., 16. Nov. 2021 um 21:23 Uhr schrieb Jimmy Shimizu < ***@***.***>: > 401 usually means that you don't pass any authentication info, and 403 > means that the authentication is invalid or you don't have the permission > to call it. I haven't worked nor tested the Microsoft integration in a long > time, so I don't have any good pointers right now. > > The Microsoft tts is very complex to integrate against because of the > bearer-token approach, and they seem to like changing things up from time > to time (which is a sure way to piss people off...) > > > > On Tue, 16 Nov 2021, 20:51 Guid-o-nator, ***@***.***> wrote: > > > Hi. > > > > Sorry, I'm very new to github, just signed in to ask you. I thought I > > opened this issue in the correct place. > > But meanwhile, after spending several hours I am close to giving up. :( > > > > > > - - added file "settings.json" to configure microsoft tts > > - - added API Key (in quotes), "Hedda" (to be sure a working voice is > > used) > > - - in microsoft.js: > > - - changed uri in function generateBearerToken to ' > > https://westeurope.api.cognitive.microsoft.com/sts/v1.0/issuetoken' > > (copied from Azure Website) > > - - changed uri after "return request({..." to ' > > https://westeurope.tts.speech.microsoft.com/cognitiveservices/v1' (as > > suggested here: > > https://gitter.im/node-sonos-http-api/Lobby?at=5bd577aa3844923661adf865 > > ) > > > > > > but when trying to "say" something "IP:5005/Schlafzimmer/say/Something" > > always got: > > > > {"status":"error","error":"Got status 403 when invoking > > /cognitiveservices/v1","stack":"Error: > > Got status 403 when invoking /cognitiveservices/v1\n at > > > > > /home/guido/node-sonos-http-api-master/lib/tts-providers/microsoft.js:88:12"} > > > > Before changing the second uri, I always got this error: > > > > {"status":"error","error":"Got status 401 when invoking > > /synthesize","stack":"Error: Got status 401 when invoking > > /synthesize\n at > > > > > /home/guido/node-sonos-http-api-master/lib/tts-providers/microsoft.js:88:12\n > > > > ...and I really like the voice "Katja", but after countless tries... :( > > > > > > Perhaps you could give me some good advice. > > > > Thanks a lot for your great work, > > > > Guido > > > > > > > > > > > > > > > > Am Mo., 15. Nov. 2021 um 11:27 Uhr schrieb Jimmy Shimizu < > > ***@***.***>: > > > > > Did you mean to open this issue in the > > > https://github.com/jishi/node-sonos-http-api? > > > > > > I'd appreciate if you could create a PR adding the info in > > > > > > https://github.com/jishi/node-sonos-http-api/blob/master/lib/tts-providers/microsoft.js > > , > > > where it needs language, sound font and gender as well. > > > > > > — > > > You are receiving this because you authored the thread. > > > Reply to this email directly, view it on GitHub > > > < > > > #75 (comment) > > >, > > > or unsubscribe > > > < > > > https://github.com/notifications/unsubscribe-auth/AVJAM67STUVGLCAPTUHIOX3UMDOAHANCNFSM5IALWLKQ > > > > > > . > > > Triage notifications on the go with GitHub Mobile for iOS > > > < > > > https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 > > > > > > or Android > > > < > > > https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub > > >. > > > > > > > > > > — > > You are receiving this because you commented. > > Reply to this email directly, view it on GitHub > > < > #75 (comment) > >, > > or unsubscribe > > < > https://github.com/notifications/unsubscribe-auth/AAYE2I3AIAR7KPV7DFGLORTUMKY2XANCNFSM5IALWLKQ > > > > . > > Triage notifications on the go with GitHub Mobile for iOS > > < > https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 > > > > or Android > > < > https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub > >. > > > > > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub > < #75 (comment) >, > or unsubscribe > < https://github.com/notifications/unsubscribe-auth/AVJAM65FFGTC56ZL4ZCJDO3UMK4THANCNFSM5IALWLKQ > > . > Triage notifications on the go with GitHub Mobile for iOS > < https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 > > or Android > < https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub >. > > — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#75 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAYE2I7NIBE6YK6IDXQHIFLUMK66JANCNFSM5IALWLKQ> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

[guidonator]

Well, I did this for now. Of course, having dynamic text would be way cooler as it would give way more possibilities in the future, but... since I heard the Microsoft tts voice (Katja) other voices are no longer an option ;) (Still hard to believe she is generated..) Perhaps someday I will find out how to achieve microsoft tts integration... :( Am Di., 16. Nov. 2021 um 22:11 Uhr schrieb Jimmy Shimizu < ***@***.***>:

…

If you don't want dynamic text to speech, and only need the same phrases spoken out, then creating your own mp3s would be far easier, yes. On Tue, 16 Nov 2021, 21:43 Guid-o-nator, ***@***.***> wrote: > Hi Jimmy, > > thanks for answering so quickly! :) > > So at the moment I am very.. frustrated. :( > The standard-google-voice is soo awful and sounds bored-beyond-belief, > voicerss sounds like voice-synthesis directly from 1995, AWS is not free > (also it might be quite cheap if everything works like it should)... > > I also tried to check my authentication / bearer-token like described here: > > > https://docs.microsoft.com/en-us/azure/cognitive-services/speech-service/troubleshooting > > Well, it seems to work if I understand the answer correctly... It also > seems that the certificate expires in half a year? Or is this the > API-Key..? > > ..basically I wanted to alarm if my window was opened too long.. slowly I > think it might not be worth it.. :( > > Probably I should try to make an mp3 and play that... > > Thanks again, > > Guido > > Am Di., 16. Nov. 2021 um 21:23 Uhr schrieb Jimmy Shimizu < > ***@***.***>: > > > 401 usually means that you don't pass any authentication info, and 403 > > means that the authentication is invalid or you don't have the permission > > to call it. I haven't worked nor tested the Microsoft integration in a > long > > time, so I don't have any good pointers right now. > > > > The Microsoft tts is very complex to integrate against because of the > > bearer-token approach, and they seem to like changing things up from time > > to time (which is a sure way to piss people off...) > > > > > > > > On Tue, 16 Nov 2021, 20:51 Guid-o-nator, ***@***.***> wrote: > > > > > Hi. > > > > > > Sorry, I'm very new to github, just signed in to ask you. I thought I > > > opened this issue in the correct place. > > > But meanwhile, after spending several hours I am close to giving up. :( > > > > > > > > > - - added file "settings.json" to configure microsoft tts > > > - - added API Key (in quotes), "Hedda" (to be sure a working voice is > > > used) > > > - - in microsoft.js: > > > - - changed uri in function generateBearerToken to ' > > > https://westeurope.api.cognitive.microsoft.com/sts/v1.0/issuetoken' > > > (copied from Azure Website) > > > - - changed uri after "return request({..." to ' > > > https://westeurope.tts.speech.microsoft.com/cognitiveservices/v1' (as > > > suggested here: > > > > https://gitter.im/node-sonos-http-api/Lobby?at=5bd577aa3844923661adf865 > > > ) > > > > > > > > > but when trying to "say" something "IP:5005/Schlafzimmer/say/Something" > > > always got: > > > > > > {"status":"error","error":"Got status 403 when invoking > > > /cognitiveservices/v1","stack":"Error: > > > Got status 403 when invoking /cognitiveservices/v1\n at > > > > > > > > > /home/guido/node-sonos-http-api-master/lib/tts-providers/microsoft.js:88:12"} > > > > > > Before changing the second uri, I always got this error: > > > > > > {"status":"error","error":"Got status 401 when invoking > > > /synthesize","stack":"Error: Got status 401 when invoking > > > /synthesize\n at > > > > > > > > > /home/guido/node-sonos-http-api-master/lib/tts-providers/microsoft.js:88:12\n > > > > > > ...and I really like the voice "Katja", but after countless tries... :( > > > > > > > > > Perhaps you could give me some good advice. > > > > > > Thanks a lot for your great work, > > > > > > Guido > > > > > > > > > > > > > > > > > > > > > > > > Am Mo., 15. Nov. 2021 um 11:27 Uhr schrieb Jimmy Shimizu < > > > ***@***.***>: > > > > > > > Did you mean to open this issue in the > > > > https://github.com/jishi/node-sonos-http-api? > > > > > > > > I'd appreciate if you could create a PR adding the info in > > > > > > > > > > https://github.com/jishi/node-sonos-http-api/blob/master/lib/tts-providers/microsoft.js > > > , > > > > where it needs language, sound font and gender as well. > > > > > > > > — > > > > You are receiving this because you authored the thread. > > > > Reply to this email directly, view it on GitHub > > > > < > > > > > > #75 (comment) > > > >, > > > > or unsubscribe > > > > < > > > > > > https://github.com/notifications/unsubscribe-auth/AVJAM67STUVGLCAPTUHIOX3UMDOAHANCNFSM5IALWLKQ > > > > > > > > . > > > > Triage notifications on the go with GitHub Mobile for iOS > > > > < > > > > > > https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 > > > > > > > > or Android > > > > < > > > > > > https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub > > > >. > > > > > > > > > > > > > > — > > > You are receiving this because you commented. > > > Reply to this email directly, view it on GitHub > > > < > > > #75 (comment) > > >, > > > or unsubscribe > > > < > > > https://github.com/notifications/unsubscribe-auth/AAYE2I3AIAR7KPV7DFGLORTUMKY2XANCNFSM5IALWLKQ > > > > > > . > > > Triage notifications on the go with GitHub Mobile for iOS > > > < > > > https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 > > > > > > or Android > > > < > > > https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub > > >. > > > > > > > > > > — > > You are receiving this because you authored the thread. > > Reply to this email directly, view it on GitHub > > < > #75 (comment) > >, > > or unsubscribe > > < > https://github.com/notifications/unsubscribe-auth/AVJAM65FFGTC56ZL4ZCJDO3UMK4THANCNFSM5IALWLKQ > > > > . > > Triage notifications on the go with GitHub Mobile for iOS > > < > https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 > > > > or Android > > < > https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub > >. > > > > > > — > You are receiving this because you commented. > Reply to this email directly, view it on GitHub > < #75 (comment) >, > or unsubscribe > < https://github.com/notifications/unsubscribe-auth/AAYE2I7NIBE6YK6IDXQHIFLUMK66JANCNFSM5IALWLKQ > > . > Triage notifications on the go with GitHub Mobile for iOS > < https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 > > or Android > < https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub >. > > — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#75 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AVJAM63U6AVKVNFBHQVIC6LUMLCJBANCNFSM5IALWLKQ> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.