@Josh-Lichtung, I just tried the extension and it works great! I’m very excited about the possibilities it opens up! Thank you again!
A small issue is how to deal with words that are links. For example, in Wikipedia, many words have links to their respective articles. In the actual version of the extension we cannot add them as LingQs, right?
It’s currently ALT + left click, in a future update it will change to SHIFT + left click…
This is now submitted and will be live soon! Details here Changelog · Lichtung !
I’m working on allowing you to add your own translations next!
I found a way to use Web Reader for LingQ on pretty much any streaming service that asbplayer supports, including Netflix, NRK, etc., and even in full screen.
The problem with services like Netflix is that their subtitles aren’t selectable, so Web Reader for LingQ can’t detect them. But using asbplayer solves that:
asbplayer – Language Learning with Netflix & YouTube
asbplayer lets you load the subtitle file, making the subtitles selectable. Web Reader for LingQ then works with them just like on YouTube.
There was one problem: in full screen, Web Reader for LingQ’s popup appeared behind the video. I eventually found a full screen extension that fixes this:
Windowed Fullscreen for Videos
With this extension, you use its full screen mode and then press F11. Now both the asbplayer subtitles and Web Reader for LingQ popup appear on top of the video.
So, with these three extensions:
Web Reader for LingQ
asbplayer
Windowed Fullscreen for Videos
…you can watch almost any service that asbplayer supports, use selectable subtitles, click words for definitions, and have everything connected to LingQ.
It basically turns Web Reader for LingQ into a pretty convincing Language Reactor alternative. 
Pretty cool! 
Thank you for the updates! I am enjoying the reader. One feature I would love to see: can your extension capture left and right arrow keystrokes to navigate from lingq to lingq, like the LingQ web reader does?
Also curious. How does your extension figure out words read and report that to LingQ? Do you just look at the scroll distance on the page, or do you count based on the last-clicked lingq?
Good question @sraevsky! We don’t actually track the words “seen” or “read” with this extension. It’s effectively just a simple vocabulary overlay.
Left and right arrow navigation should be doable - let me add that to the backlog!
You absolute mad scientist. I’m going to try this out now.
I actually prefer that it doesn’t add to total words read. As I don’t like counting watching a video with subtitles as ‘reading’.
Just gave it a test with Japanese. It works surprisingly well.
Thoughts:
The biggest issue is that the extension struggles with parsing verbs (unless they are in the dictionary/plain form).
No option to click → drag → lookup.
YouTube closed captions don’t include highlights.
Extension works great with romance languages.
Thanks for the feedback Eric - I’ll take a look and get that fixed (clearly I’m a romance guy). Click to drag is on the upcoming release list. I’ll see what I can do about YouTube - this was never my intention with the extension but folks are clearly getting lots of value out of it!
@ericfromlingq @Josh-Lichtung I don’t know for Japanese, but words are highlighted just fine for me with YouTube closed captions, both normal and auto generated. 
It obviously won’t work if the subtitles are burnt into the video itself, like many language learning videos tend to do. Every place I’ve tested it on subtitles, has worked and highlighted words, as long as those subtitles are selectable.
Oh, look-up works across YouTube and other platforms. It doesn’t seem to show the highlights/colors if they are in Japanese. The tricky part w/ Japanese is parsing (this is a universal issue, across software).
Ah ok so it is just Japanese, then. I do see that there is a thread here called “LingQ for Japanese has become fundamentally unusable” So I guess not even LingQ has figured it out yet. 
Hey all,
Pushing a big update on your feedback - should be live soon.
Features
Changes
Bugs
Languages
Up next marking all words on a page as known and that verification work for arabic/thai, etc.
I don’t understand one thing, how this Lichtung app is different from LingQ? It seems identical to LingQ but with a web reader more like this Chrome extension Web Reader for LingQ, and some things less that aren’t necessary. Basically LingQ + ReadLang.
So, are you keeping this Chrome extension Web Reader for LingQ and leaving it for LingQ in the future, or developing it for your Lichtung app and then dismiss it? Once you get out from beta?
I find it interesting that we can switch away from LingQ by carrying over our own words.
If I understood it correctly.
very interesting. I see from the screenshots that you can toggle pause for every sentence like in Language Reactor? Can you repeat the same sentence over and over too? Basically for repeating/looping one sentence over and over.
I’ll have to try this. 
Yes, you can automatically pause at the beginning or end of every subtitle. As for looping the sentence, I don’t think so, but I don’t know. I honestly don’t use most of it’s features.
But it is an opensource project that has a GitHub, and you can always request this as a feature.
Amazing updates, thank you! 
crazy enough, this actually works incredibly well with the free version of Language Reactor also. give it a go. It’s kind like if Language reactor and LingQ had a kid it’s kinda trippy. The subtitle blurring and shortcut’s all work etc but it connects to the lingQ database
