I would like to share with all of you good news that RSS rate limiter has been changed from 300 seconds to 60 seconds.
This change was released yesterday - 16th of February.
Once again, we apologize for the inconvenience caused during this whole process and thank you for your patience and understanding.
Maria Dąbrowska
Edited by maria.dabrowska
6
Heyke
Gengo support just told me they are aware of the problem and working on it.
Edited by Heyke
3
gruenlilie
Same here, still not working, 14 hours now. :(
Edited by gruenlilie
2
Rica Tero
Hi everyone!
We are experiencing a technical issue. Due to this, RSS will not be available today and over the weekend.
We apologize for this inconvenience. Our engineering team is working hard to resolve this issue as soon as possible. We humbly ask for your understanding and patience on this matter.
2
InmaDG
Hi Rica,
Thanks for letting us know, even Feeder has sent an email warning of possible problems. I hope it will be solved ASAP 😢
1
Heyke
Thank you Rica!
1
Rica Tero
Let's keep our fingers crossed, Inma.🧡
I will post an announcement in the platform and update here in the forum if I get any news soon. Take care everyone and stay safe!
Edit: You're welcome, Heike. This is the only thing I can about this matter. 😥
Edited by Rica Tero
10
InmaDG
Morning Rica,
Any news about the RSS problem?
2
Rica Tero
Hi Inma!
I apologize for the late response as I just got back to work today. According to the team, the issue with the RSS is now fixed. However, there's an update that they set up a rate limit for RSS request.
Thank you again everyone for your patience and understanding on this matter! 🧡
Edited by Rica Tero
4
erik.rothoff
@Rico Tera what are the new limits?
1
Rica Tero
Hi Erik. 😊
I'm waiting the reply from the team about the rate limit. I will update here once I got the answer. Thank you.
3
gruenlilie
Hi, it has been working for me an hour ago, but since then it has stopped working again :/
4
erik.rothoff
@Rico Tero, If you access an RSS feed more than once in a minute, it will show an error instead of the cached version. This makes it difficult to add the feed to an RSS reader. If you click on the feed link in the dashboard, it will open in your browser. If you try to add this link to your RSS reader within a minute of opening it in your browser, the reader will get an error and think the link is invalid. Instead it should just return the cached version of the RSS feed?
4
doker
My RSS reader shows a red cross after each update. This has never happened before.
Edited by doker
0
Rica Tero
Hi everyone! According to the team, the reason for the error is too frequent RSS requests. They set it up to be one access/ minute/ user. If you exceed it, it will return as an error.
If that's not the case for you and you still have the error, please elaborate it here and I will do my best to ask answers from the team.
Thank you. 😊
5
doker
But there was the same limit before and there were no errors. What exactly has changed?
1
Rica Tero
Gengo's caching feature only allows now the RSS feed readers to place one request per 60seconds maximum. Before it allows two (2) requests. If you place only one, but still got error, can you send me some screenshots at v-Rica.Tero@lionbridge.com? I will forward this to the engineering team and see why it's happening. Thank you!
Edited by Rica Tero
9
erik.rothoff
@Rica Tero the RSS literally shows an error, instead of the cached results. This is breaking a lot of RSS readers and causing confusion
4
jak
I have my reader set up to pull the feed every 63 seconds but get hit with the 429 error regardless.
4
gruenlilie
Same here, I tried 60, 65 and 120sec. Message is "no rss feed found"
Also tried setting up the reader from scratch.
Edited by gruenlilie
5
fudesaki
I've just received an email from Lionbridge Community Team stating that "Due to some system issues, the engineering team made temporary changes to the RSS again. They said to set up the interval to 600 seconds per 1 request." I wonder if 600 is a typo for 60... If not, this would be double the email notification system after 5 minutes.
Edited by fudesaki
5
gruenlilie
After that mail, I set it to 600sec, but it still doesn't get a connection. It has been trying for some hours now.
4
Leon
Two days ago it was working for me and I could grab some jobs, but since yesterday, still not a single one...
1
Rica Tero
Hi everyone! I am still waiting for an update from the engineering team. They said to set up the interval to 600 seconds. I've asked Maria's help to set up a meeting with them to clarify this situation and understand what and why this happened.
Again, we apologize for the inconvenience on this matter. We are grateful for the understanding and patience you've given us about this issue.
10
InmaDG
Thank you very much Rica,
This problem is taking a long time to be solved, and the latest request from the support team to set alerts to 600 seconds is like having no alerts at all.
Hopefully you will be able to give us some good news soon!
16
erik.rothoff
@Rico Tero I'm the owner of feeder.co, an RSS reader used by many Gengo users. Can you forward my email erik@feeder.co so I can give some input on what's wrong with the current implementation?
6
SagaGemini
@Rica Tero Any news at all?
-1
Rica Tero
Hi everyone!
I apologize that it took a long time to have an update about the RSS issue. We have sent out an email about it. I will also share it here in case someone didn't receive it.
The engineering and community management team had an in-depth talk about the issue this week. Previously, the system only allowed two requests per 60 seconds maximum. However, we did not have a well-built tool that could restrict all translators from violating the system's loopholes.
The increasing number of translators abusing this led to more frequent system issues (e.g., gateway error, slowness, etc.). We are not perfect, but we continuously do our best to improve and fix the system's current issues.
Our solution, for now, is the temporary change we emailed last week. The interval you need to set is 600 seconds per one(1) request maximum. If you try to request more than once or less than the interval we set, it will have an error.
They also told us that some translators use bad RSS feed readers requesting more than once, leading to errors. If this is unintentional, please check your settings or contact your RSS feed reader provider to check it.
We understand it could be more optimal, but this is our current solution. Again, this is temporary, and the engineering team is working to resolve the issues to reduce the interval time. Our team is watching out for the implications and will discuss the possible workaround we can do. We are also looking for another way to give out job notifications in the future.
We are grateful for your continued patience and understanding on this matter.
@erik - I've sent you an email about your comment. I can't forward your email to the engineering team, but I will gladly pass the inputs you have to them. Please email me or share it on this thread. Thank you!
Edited by Rica Tero
10
Heyke
With an interval of 600 seconds, it is pointless to pay for an RSS feed because simply refreshing the page will get you more jobs.
6
SagaGemini
And it will get you next to no jobs since some people are obviously using auto-refresh bots.
support
188 comments
Hello everyone,
I would like to share with all of you good news that RSS rate limiter has been changed from 300 seconds to 60 seconds.
This change was released yesterday - 16th of February.
Once again, we apologize for the inconvenience caused during this whole process and thank you for your patience and understanding.
Maria Dąbrowska
Gengo support just told me they are aware of the problem and working on it.
Same here, still not working, 14 hours now. :(
Hi everyone!
We are experiencing a technical issue. Due to this, RSS will not be available today and over the weekend.
We apologize for this inconvenience. Our engineering team is working hard to resolve this issue as soon as possible.
We humbly ask for your understanding and patience on this matter.
Hi Rica,
Thanks for letting us know, even Feeder has sent an email warning of possible problems. I hope it will be solved ASAP 😢
Thank you Rica!
Let's keep our fingers crossed, Inma.🧡
I will post an announcement in the platform and update here in the forum if I get any news soon. Take care everyone and stay safe!
Edit: You're welcome, Heike. This is the only thing I can about this matter. 😥
Morning Rica,
Any news about the RSS problem?
Hi Inma!
I apologize for the late response as I just got back to work today. According to the team, the issue with the RSS is now fixed. However, there's an update that they set up a rate limit for RSS request.
Thank you again everyone for your patience and understanding on this matter! 🧡
@Rico Tera what are the new limits?
Hi Erik. 😊
I'm waiting the reply from the team about the rate limit. I will update here once I got the answer. Thank you.
Hi, it has been working for me an hour ago, but since then it has stopped working again :/
@Rico Tero, If you access an RSS feed more than once in a minute, it will show an error instead of the cached version. This makes it difficult to add the feed to an RSS reader. If you click on the feed link in the dashboard, it will open in your browser. If you try to add this link to your RSS reader within a minute of opening it in your browser, the reader will get an error and think the link is invalid. Instead it should just return the cached version of the RSS feed?
My RSS reader shows a red cross after each update. This has never happened before.
Hi everyone!
According to the team, the reason for the error is too frequent RSS requests. They set it up to be one access/ minute/ user. If you exceed it, it will return as an error.
If that's not the case for you and you still have the error, please elaborate it here and I will do my best to ask answers from the team.
Thank you. 😊
But there was the same limit before and there were no errors. What exactly has changed?
Gengo's caching feature only allows now the RSS feed readers to place one request per 60seconds maximum. Before it allows two (2) requests. If you place only one, but still got error, can you send me some screenshots at v-Rica.Tero@lionbridge.com? I will forward this to the engineering team and see why it's happening. Thank you!
@Rica Tero the RSS literally shows an error, instead of the cached results. This is breaking a lot of RSS readers and causing confusion
I have my reader set up to pull the feed every 63 seconds but get hit with the 429 error regardless.
Same here, I tried 60, 65 and 120sec. Message is "no rss feed found"
Also tried setting up the reader from scratch.
I've just received an email from Lionbridge Community Team stating that "Due to some system issues, the engineering team made temporary changes to the RSS again. They said to set up the interval to 600 seconds per 1 request."
I wonder if 600 is a typo for 60...
If not, this would be double the email notification system after 5 minutes.
After that mail, I set it to 600sec, but it still doesn't get a connection. It has been trying for some hours now.
Two days ago it was working for me and I could grab some jobs, but since yesterday, still not a single one...
Hi everyone!
I am still waiting for an update from the engineering team. They said to set up the interval to 600 seconds. I've asked Maria's help to set up a meeting with them to clarify this situation and understand what and why this happened.
Again, we apologize for the inconvenience on this matter. We are grateful for the understanding and patience you've given us about this issue.
Thank you very much Rica,
This problem is taking a long time to be solved, and the latest request from the support team to set alerts to 600 seconds is like having no alerts at all.
Hopefully you will be able to give us some good news soon!
@Rico Tero I'm the owner of feeder.co, an RSS reader used by many Gengo users. Can you forward my email erik@feeder.co so I can give some input on what's wrong with the current implementation?
@Rica Tero Any news at all?
With an interval of 600 seconds, it is pointless to pay for an RSS feed because simply refreshing the page will get you more jobs.
And it will get you next to no jobs since some people are obviously using auto-refresh bots.