This is disgustingly disrespectful and unacceptable 😡

[TomErikSmith]

I respectfully disagree. At no point have they explained any of the things you are suggesting. They have not been open or honest about what is going on at all. We have repeatedly asked for more detailed information, but the only thing that has been communicated is that “it will be fixed”, “it has been fixed”, “it will be reverted back, sorry for the delay”, “we have decided not to fix it.”

I too have accepted a certain level of bugs and issues, however this is a change to the core functionality of the service and the way it functions, and is simply unacceptable. This is something that has never existed in LingQ, it was added/introduced three months ago, they basically immediately said they will reverse it, but have been unable or unwilling to do so it seems. It is insane that they can’t just go back one day in the code to undo a mistake.

If they are refusing to fix it, that is bad… If they are unable to fix it, that is significantly worse, and should worry everyone who uses the service.

I get that for you, it is simply not something you care about, but here is an example from Juliani that perfectly illustrates the complete absurdity of this change:

@JulianiTOgo

Thank you for increasing the new words figure on my lessons by 10-20% with these complete useless hyphen words. This will take me a lot of time and attention in the future, because each time you have to figure out:

• what it means (dictionary entries are very rare)
• What a particular word of the hyphen cluster means
• If it is actually a word
• If you want to ignore the word
• If you want to save the word and then which definition and/or translation do you use.

For advanced users the hyphen issue is a nightmare…