31–40 of 89 posts
This is cool! I recently tried to use VoiceOver on my iPhone and it’s… astonishingly difficult to use for just text to speech! One minor request: I realize the form page itself is very minimal, but this would be much more usable on a phone if you set the font-size of the input to at least 16px, and a reasonable viewport meta tag eg ` `
command-line version: curl -L https://per.quest/$URL | mpv - # or aplay etc.
ffplay https://per.quest/$URLNeat! Could you add speed controls, a download audio option, download audio as mp3/webm/etc, and options for different voices? Why is there no donation option for this project? Why not add a email signup for updates/news? What are your options for micro monetization?
But in my opinion I think that you should make the website fully work without the use of client-side JavaScript.
Not that I dislike JavaScript, in fact, I love it. And it's great! But there are several reasons I think that this would make sense doing.
Here is a detailed explanation for "why":
The website already works without the use of client-side JavaScript, only not the index.
If you for example go to: https://per.quest/https://example.com it will work just fine and redirect you to the generated MP3 file.
But if you put https://example.com inside of that input on the website index and have JavaScript disabled it simply won't work. There also is no notice that it does not work without JavaScript enabled.
The solution to this is simple and I think that it would not be hard to change the way you are getting the user given URL from your back-end. What I think would make more sense doing is to just make it work using a URL query parameter.
For example: https://per.quest?url=https://example.com
... which would then allow you to make use of HTML forms, and simply add the "name" attribute to the input with the value set to "url".
So, this would then work in both cases: when the user hit enter and/or pressed a button inside of the form.
Hope that you will agree with me on this!
When I put in https://localhost:443, I get audio for the default nginx page, which matches what the internet archive has for that url: https://web.archive.org/web/20210620003533/http://localhost/
But putting http://localhost returns the audio from per.quest's home page.
This is cool! I recently tried to use VoiceOver on my iPhone and it’s… astonishingly difficult to use for just text to speech! One minor request: I realize the form page itself is very minimal, but this would be much more usable on a phone if you set the font-size of the input to at least 16px, and a reasonable viewport meta tag eg ` `
Nowadays, works just fine.
how is this made?
Step 2. Text to Speech (eg. Mozilla DeepVoice)
Both libraries open-source and free.
You can do the same in our iOS App: https://apps.apple.com/us/app/id1535903742
Browse to any page and click on "Listen Now" in the app (including logged in page)