See more at: http://www.lingq.com/learn/es/workdesk/item/6409782/reader/#sthash.kbt0gAH0.dpuf

What is this? Why does it keep messing up my lingqs and how do I get rid of it?

Thank you

edit: irrelevant post^^

@Paule: Since two or three weeks this appears often if you copy text from the LingQ website and paste it somewhere. I find it very annoying two.

Yes, this is annoying. This automatic addition of ‘see more at -’ does not result in a message ‘see more at -’ being added to my texts. It just results in me wasting several seconds deleting the message.

Indeed!

Here it is in action:

Colin’s quote following a mere cut and paste:
Yes, this is annoying. This automatic addition of ‘see more at -’ does not result in a message ‘see more at -’ being added to my texts. It just results in me wasting several seconds deleting the message. - See more at: See More At: Http://Www.Lingq.Com/Learn/Es/Workdesk/Item/...

I suspect it has something to do with LingQ disappearing from the Google search engine.

It seems to have appeared around the time people pointed out that LingQ wasn’t coming up in their Google search, which was one way of accessing the site.

Aaaah, “this”!^^

“It just results in me wasting several seconds deleting the message. - See more at: See More At: Http://Www.Lingq.Com/Learn/Es/Workdesk/Item/...

Same here. Sometimes I don´t understand LingQ´s “marketing”.
People who like LingQ will create links to the site anyway…these “automatic additions” make LingQ look desperate (imo)

I have no idea why this is appearing when you copy and paste text but it is not by design. Nor does it have anything to do with what happened with Google. We are once again appearing in search results.

We are looking into it.

Hmm… I suspect it’s the line in buttons.js that says:

{a=" - See more at: “+k+”";

or perhaps st.js

){a=" - See more at: “+k+”";if(!e.test(p)&&!j.test(p)

It’s hard to tell with your minified Javascript

It had to do with a third-party sharing widget we are using. It was somehow automatically adding that tag. We have pushed a fix so that should no longer happen. Thanks for reporting this!

1 Like