Extension: Rooster Observer - Edit LingQs for all lesson words

Hey @jpp025
Thanks for the feedback

It should be populated with all the ‘Blue’ words in the lesson.

If you have no ‘Blue’ words the list will be empty.

The “Get Hints” button will just show options like the ‘New Words’ column. Only the new word’s hints are loaded at the start. Is there a problem with the current/known hints not appearing in Korean? Let me know.

This version of Observer can only find 500 words. If your first ‘Blue Word’ is the 501st word or later you won’t see anything in the menu.

Great to hear! It’s all slowly coming together now.

1 Like

For some reason, it’s not. I defiantly have at least one word ( 시간입니다 ) that is blue in the first 500 words (it’s in the second-ish sentence).

I also tried a lesson with mostly blue words all over the first page.

The hints don’t seem to be appearing (?) I see what would look like grammar tags in LingQ (grey boxes).
There might be a problem with current/known hints not appearing in Korean.

Here is the before and after of clicking the “Get Hints” button:

Also, are those grey looking “tags” supposed to disappear when you click on them?

P.S. Love the “Drag me” message on the pop-up! Definitely helps!

Screenshot 2023-08-20 at 07.00.18

Note: All of the above is in relation to LingQ Observer.

1 Like

Hello @jpp025

This may be to do with how words are sourced. Is it a long lesson? I’m guessing that 500 words are returned not in any particular order.

I will investigate this issue and get back to you.

If you click a tag it will remove that grammar from the word. This removes it for all future users too. Treat it with respect. Remember to press save after removing or adding a tag!

I’ll look at making some more friendly design choices in the future.

When I have looked into that Korean bug I’ll send you a message about how to install the no limit version.

Thanks for your feedback!

1 Like


I fixed this problem. Basically LingQ expects character encoding in the URL for asian languages. (See the first 2 lines of first picture) Now we have another problem. Somehow Korean has 76 hints for this word. Shall we limit it to say the most popular 6? (See second picture). Third picture is a bit of a meme where i show all 76 hints. Haha. I’ll push a fix for this within the hour and also a fix for the colors dropping off the other boxes.

Edit: Patch is now live → I also increased word limit to 750.

1 Like
  • First one was shorter: 11 LingQ pages

  • Other one I checked was longer: 40 pages

Thank you for your hard work and for being so responsive! :smiley:

1 Like

Oh, this is cool to know!

Yes, the “Get hints section” seems to be working much better now!

this is likely due to the fact that Korean is a very context heavy language, so users are creating LingQs for words in a variety of ways:

  • Direct meaning of word
  • Context-dependent meaning of word
  • The above types of meanings + additional grammar or word endings their word had
  • the root word of the word they’re linking + the above + every possible direct meaning of the word
  • Etc.

I’m used to this, so it doesn’t bother me as much. What would be great through your extension is getting the 6 most popular meanings to get a better idea of the LingQ I want to create for whatever learning stage I’m in.

So, it makes sense to limit it to the most popular meanings, even though it can be an incorrect meaning or not quite formatted the way I may want overall. For the type of language learning I tend to do, I can always consult multiple resources (like dictionaries, Reddit, etc.), but having a place to start is great!

^^ This gives you a good idea what the meanings section looks like for Korean learners, lol ^^

Like I said I’ve gotten used to it and actually appreciate it (though sometimes it would be nice if an advanced Korean learner went through this every so often to avoid to much clutter for users over time—not every personal meaning needs to public :laughing: but it’s better than no community dictionary at all.

Still zero resutls under the “New Words Category for me” but the “Current Lingqs” and the “Known Lings” improved with the “Hints” (as I mentioned, so progress!!)

But, like I mentioned previously, I seem to get lingQs using Observer Lite (as long as I toggle off Observer while I’m using Observer Lite—otherwise nothing shows up for Observer Lite, but it makes sense that the Observer extension would interfer with the Observer Lite extension)

P.S. I figured this might be the case which is why I immediately closed my tab instead of saving anything when I clicked on the tag, and it disappeared :laughing: So, glad I didn’t save that!

Also being able to resize the windows is another great user feature I just noticed!

Again, thank you for your hard work on these extensions! Super exciting stuff!

1 Like

This is definitely a issue for longer lessons. Basically… LingQs have ‘Ids’ assigned to them and are returned in order they were first created. ‘paljon’ (a lot) always returns first for me in Finnish, this could be based on the first person ever to LingQ that word or the first word that you LingQed. I’m not sure yet. (sorry about being technical here, I just wanted you to know why the problem may still exist)

My solution here is to fetch the entire word list, reorganize it by new words first and then slice it to the free version word limit. There is also another mechanism that exists that I’m looking into, which should be released today… An option to toggle LingQs for entire lesson or LingQs for current page.

Here is an idea which I’ll let you get back to me on. Do you want new LingQs to start with a column and when you enter the definition it would be like

Direct Meaning: "your text here"
Context derived meanings: "your text here"
Root word: "your text here"
Root word meanings: "your text here"

This could be a toggle-able setting and allow user input to change the column names.

Hopefully the upcoming Wikipedia import function reduces the need for this!

Observer Lite can see 2000 words opposed to Observer’s 750 which is likely why you are seeing results.

todo for 1.20

→ Fix for word limit → get new words first
→ Columns for new LingQs
→ Native button
→ Settings menu
→ Get more Hints for new words
→ Show extended hints in a scrollable menu
→ Show LingQs for this page only


I’ll be pushing patch 1.20 within the hour with some of the things mentioned above. (Its lunch time and I want to get this patch out)

→ I have increased the word limit on Observer for testing purposes. (more than LITE)
→ Ability to add columns to LingQs

→ Get More and ALL hints for a word (Not really all, it displays 6 or 30 in popular descending order)

→ Added Rooster Observer Button to the menu

Should be live in 30 mins.

Edit: → Patch 1.24 is now up on Firefox with the word restriction entirely removed

Yes! This would be great! (Had to sleep on this because it was later in the evening for me)

Yes! Hopefully!

Note: I have noticed for Korean that it can be very tricky to get good definitions consistently from one source (though I have been very happy with Papago for free definitions overall — with some caveats and DeepL for free limited use. But, they mainly excel in translating sentence by sentence).

I note this because I have noticed “Wikitionary” and Navar Dictionary don’t always pull up results for Korean words consistently. So I look forward to seeing how the Wikipedia import function performs for Korean.

Makes sense!

Great idea! I think there might be more to me not being able to see this column (unless it counts the word count for this as “lifetime links” and seriously have a lot of links built up as a LingQ user, lol).

I’m still just seeing a blank box in the “NEW WORD” section like before:

This works great! I was having trouble picturing it (how it would work/process) until you added it. “Line Starters” is user-friendly wording, and I like it a lot!

Had to un-install and reinstall to get the updated version (guess my audio updates aren’t set right or something). These buttons work great. Also, love this!

Side note/complete guess: But it seems like clicking “More Hints” can result in hint results that seem a bit better and less cluttered with the word appearing in Korean Characters (Hangeul) within the meaning!

So you may be on to something here:

It may take a good while to get those popular definitions that aren’t exactly the best weeded out. (This may make things tricky with an "add all blue LingQs in one click feature that I thought I saw somewhere in one of the posts. Since, the most popular will continue to be the most popular, even though it may not be the best definition.)

Nice! Makes things easier!

1 Like

Dictionaries coming in the next update (just need to figure out how to design this damn UI to be user friendly!)

Audio when you click on the word at the top and the fragment should be out tomorrow too.

Ok. I’ll increase the limit to something dumb in the next update and we will see if it works.

Im thinking about a dropdown box where you just select the line starters that you want in the LingQ. With 1 button to add all if you want.

Maybe i"ll display the ‘All Hints’ result in a separate popup for that word. like a Grid or Rows. Then can close it instead of leaving 30 hints clogging up the screen.

I don’t think its happening soon. We just need to use our best judgment right now.

1 Like

I like this idea! Then it offers more customization for users who may want more/fewer columns.

Other potential column ideas:

  • Hanja: [“common Hanja in South Korea written as 父母 for parents, 學生 for students, and 學校 for school.”]
  • Phonetic: [Note: This would allow users to create their own pronunciations of the word, or what I would love to use is the “Phonetic Hangeul” of words so I can use Korean characters to create the pronunciation “hints” for Korean words because romanization/transliteration throws me off as a beginner learner. Could also be called “Pronunciation”]

Ex. Of Phonetic Hangeul: Word: 전화 [Phonetic: 저놔]

1 Like

Hey roosterburton,

Would you be able to make a LingQ extension to easily customize keyboard/mouse-button hotkeys for this site, easy enough to use for non-scripters?


Hi @Vardan_Yervadian

I can look at this but I’ll need some help. I don’t use the shortcuts currently. Can you tell me what there are currently shortcuts for and how to access the keybindings on this site?

1 Like

I second this, if there could be a way to modify keyboard shortcuts that would be unreal!

This post has a breakdown of the current shortcuts if it helps.

1 Like

That’s great. I’ll check it out and see how the settings are applied. It might involve a manual remapping and disable of the old keys, or could be something as simple as change ‘X’ key to ‘Y’.

1 Like

@Vardan_Yervadian @mhast

It is definitely possible to remap these keys in an easy popup menu. It’s on the todo!

It would be saved in local storage which means that would need to set them for every different browser you use. Could also save preferences in some database but that’s out of scope for this.

1 Like

That’s incredible, I would 100% use this addon if you are able to create it… it would be a total game changer for me. Thanks for all your hard work, all of these addons are great and I’m excited to check out what comes next.


I’m looking at it right now, might get a version out today.

edit: → something like this


second edit: → The keyboard events are happening directly from the javascript and not via a keydown in the html. What this means is… It is absolutely possible to remap any key. The caveat is that I need to actually reprogram all of those functions individually. Which is quite painful… and time consuming.


For the first version of the script I’ll do some simpler ones like change the tts key and the toggle translation button. Stay tuned on the main web extensions page.

third edit: → Please let me know which keybindings you actually use and i’ll include those in the first version.

1 Like


→ The word limit bug has been solved.
→ You will now see all words for any size lesson.

Nerd notes

→ The script encountered errors when there was no data available on a word it was trying to see.
→ We now check if no data and just display no selectable buttons nothing for that word
→ Full individual word count for a lesson is listed in the console.



→ Observer Lite has been merged into Observer
→ Now displays all words, even if no options
→ Slight graphics upgrade

Nerd notes

→ ObserverLITE was also having the same problems, I merged the scripts to be more efficient.


Yes!! I have all the boxes! Great work!

1 Like