I didn’t mind — ^W is not hard to type — but it does strike me as slightly odd that this seems to have been a conscious choice: “It is based on BitListen by Maximillian Laumeister”, which requests you click anywhere to unmute (https://www.bitlisten.com/).
Google Chrome has changed its autoplay policy in the past few years [0] -- sites now require typically user interaction before they're allowed to start the audio context.
You can see this in the page's code [1] -- line 157 and further.
I was surprised to hear the page start playing right away though. Maybe Chrome's "whitelisting" has become more permissive..? See this [2] as well.
If I remember correctly, back at the time they adapted BitListen into Listen to Wikipedia, Chrome's policy permitted autoplaying sound.
The "click anywhere to unmute" notification was something I added some time later, after the new autoplay policy, so that people wouldn't think the website was soundless or that sound was broken.
Neat, although with Wikipedia dealing largely with sentence-based text, I was hoping for something that does text-to-speech. It would be cool if for each edit a voice would read the article title and the updated sentence(s).
You can get a rough overview of the changes per minute looking at https://codepen.io/Krinkle/full/BwEKgW which listens to the event stream. (scroll to the bottom of the page, its seems slightly broken right now)
This shows ~300 edits per minute on en.wikipedia (5 a second) right now.
~1500 edits per minuites on all sites (25 a second)
There's an irc channel (#en.wikipedia on irc.wikimedia.org) that just lists edits as they happen - i always found it helped me appreciate the scale of things.
I remember there was a website or app which let you listen to wikipedia articles whose subject was near you, based on geolocation info. Anyone remember what it was?
I seem to get about 50 or so entries that play, then nothing for many minutes. If I refresh, I get another burst of entries. Possibly HN is hugging the site to death?
I was hoping this would be a way to listen to Wikipedia articles like audiobooks. Unfortunately, the iPhone screen reader is not optimized for reading Wikipedia:
- It reads footnote links ("one", "fourteen", etc)
- It reads years like numbers ("One thousand, seven hundred and fifty six" instead of "seventeen fifty six").
- It reads introductory metadata, warnings, etc.
- It reads tables.
- It read image captions.
Ideally it wouldn't do any of these things. Basically, it reads the screen from top to bottom, which isn't what a human would do if you asked somebody to read a Wikipedia article to you. If anyone knows a good way to synthesize Wikipedia to speech, that would be so nice!
EDIT: I wonder if Apple would reject such an app from the App Store because it would compete with ebooks.
> I wonder if Apple would reject such an app from the App Store because it would compete with ebooks.
They would not, unless you went out of your way to violate App Store guidelines. There are currently hundreds of iOS "reader" apps that allow users to consume ebooks[1], graphic novels, articles from Wikipedia and similar sites (i.e. wikiHow), etc.
36 comments
[ 3.0 ms ] story [ 98.4 ms ] threadYou can see this in the page's code [1] -- line 157 and further.
I was surprised to hear the page start playing right away though. Maybe Chrome's "whitelisting" has become more permissive..? See this [2] as well.
[0] https://developers.google.com/web/updates/2017/09/autoplay-p...
[1] http://listen.hatnote.com/
[2] https://developer.mozilla.org/en-US/docs/Web/Media/Autoplay_...
The "click anywhere to unmute" notification was something I added some time later, after the new autoplay policy, so that people wouldn't think the website was soundless or that sound was broken.
This shows ~300 edits per minute on en.wikipedia (5 a second) right now. ~1500 edits per minuites on all sites (25 a second)
Repo at https://github.com/skhg/listen-to-wikipedia
- It reads footnote links ("one", "fourteen", etc)
- It reads years like numbers ("One thousand, seven hundred and fifty six" instead of "seventeen fifty six").
- It reads introductory metadata, warnings, etc.
- It reads tables.
- It read image captions.
Ideally it wouldn't do any of these things. Basically, it reads the screen from top to bottom, which isn't what a human would do if you asked somebody to read a Wikipedia article to you. If anyone knows a good way to synthesize Wikipedia to speech, that would be so nice!
EDIT: I wonder if Apple would reject such an app from the App Store because it would compete with ebooks.
They would not, unless you went out of your way to violate App Store guidelines. There are currently hundreds of iOS "reader" apps that allow users to consume ebooks[1], graphic novels, articles from Wikipedia and similar sites (i.e. wikiHow), etc.
[1] https://en.wikipedia.org/wiki/Comparison_of_iOS_e-reader_sof...
You can find more information about the project here: https://en.wikipedia.org/wiki/Wikipedia:WikiProject_Spoken_W...
Its the best artificial voice available in the wild right now I think, it is a pretty good experience.
And another, but for Twitter: https://iora.live (disclaimer: I'm the author)
Fortunately there are bots that detect and revert those.
Also, site is not secure (no https).
You would have to click all 40 checkboxes manually otherwise...