11

RumpelstiltskinRSS is a web based RSS reader for your Gengo Jobs RSS. After some one-time steps, you can use any browser on any device to alert you for new jobs. As a bonus, RumpelstiltskinRSS does some filtering for you so you will only be alerted if the size and level of the job meet your preferences, taking the time of day into account.

I optimized RumpelstiltskinRSS for my own needs, but tried to make it so that it can be used by all translators. You can find RumpelstiltskinRSS at http://rumpelstiltskin.appje.nl/rss/. For a description how to use it, follow the Introduction link.

Note that you can set the refresh interval to either 31 or 62 seconds. Use 31 for optimal chances to grab a job, without breaching Gengo's demand to access your Jobs RSS at most twice per minute. Or use 62 to test if RumpelstiltskinRSS suits you, while still running your current RSS reader (set to check at most once per minute) on another device.

309 comments

  • 0
    Avatar
    Cheryl

    For the sound issue, I stumbled upon the problem in Firefox, at least. Turns out, after an update, a box that should NOT be ticked (prevent popups from playing audio) was ticked. It's under options>privacy&security in the 'Permissions' section.

  • 0
    Avatar
    Alexander

    Hi Cheryl - thanks for pointing this out. One of these days I'll add a line about this on the FAQ page.

  • 0
    Avatar
    Cheryl

    Hi! The sound issue is fixed. Now, the RSS only does one check and doesn't repeat, I tested it while staying on the page, as well as running in the background. It counts down the 31 seconds and stops. I have to manually refresh to get it to recheck.

    Thanks!

  • 0
    Avatar
    Cheryl

    I also just saw that there is a limit of 2 checks per minute for jobs- does that mean 2/minute by USER or by PLATFORM? For example, can I run the RSS feeder on my laptop AND my iPhone at the same time (which could feasibly be more than 2/minute).Or is this more to eliminate people from just hitting refresh every couple seconds?

  • 0
    Avatar
    Alexander

    Hi Cheryl - Good to hear the sound issue is fixed.

    I'm not sure why the page doesn't refresh. I did not change the underlying code recently, and in a quick check today it worked fine for me.

    I do know the option "To play the alert sound, use mechanism adapted to iOS 6 and later" comes with instabilities. This is the main reason why I created the iOS and Android app versions. I designed both of them to recover from any unexpected situations. They keep retrying no matter what. So if you keep experiencing problems in the browser version, consider using one of the app versions instead.

    About the limit of 2 checks per minute, that's a limitation on Gengo's side. As far as I know, it's per user, not per IP address. However, RumpelstiltskinRSS is smart enough to handle multiple requests from as many devices as you wish without violating Gengo's limitation. It does so by caching the Jobs RSS info during the time interval you set (31 or 62 seconds). So it's okay to run RumpelstiltskinRSS on both your laptop and your iPhone.

    In fact, Gengo uses a caching mechanism as well. Your Jobs RSS info is refreshed by Gengo only once per minute, so checking more frequently doesn't give you any advantage.

  • 0
    Avatar
    Cheryl

    You are amazing, Alexander! Thanks- I'll uncheck the ios 6 box and see if that helps...

    yep, seems to have fixed it! Thanks again!
    Cheryl

  • 0
    Avatar
    Cheryl

    HI Alex,

    The sound has gone from my feed reader again- I inserted the dummy job to test and here's what I see before it goes to the workbench. Thanks for any advice! (the box about iOS 6 is NOT ticked...-))

  • 0
    Avatar
    Alexander

    Hi Cheryl,

    Perhaps the sound is suppressed by the browser because going to the workbench means leaving the page that produces the sound. Try unchecking the option to go to the workbench, or using a larger interval (say 5-10 seconds) as described on the FAQ page under "Why doesn't the sound alert work?" (Step 4).

    In the iOS and Android app versions, the combination of sound alert and going to the workbench should work fine.

  • 0
    Avatar
    Cheryl

    It's been working fine at 1 second since we last talked.- that's the only reason I wondered. Has there been some update to something somewhere.

    If I set my time to 5 seconds, I'll never get a job, lol. Even at one second, I only get around 50% of the jobs I try for.

    Thanks!

  • 0
    Avatar
    Alexander

    I did not change anything recently that could be related to this issue. Perhaps something beyond your and my control has changed in the connection between your computer and my server, so the sound takes more time to load.

    Again, the app versions are much more reliable. That's why I created them in the first place.

  • 0
    Avatar
    Cheryl

    Your FAQ is amazing- I followed the steps for working on Firefox, and it's fixed! Thanks!

  • 1
    Avatar
    Alexander

    One user reported recently that at times the Android app version of RumpelstiltskinRSS stops functioning abruptly. You can tell this has happened if the "Next check: ..." time is incorrect. (It should be close to the current time. If it is, say, one hour ago, then the app has stopped functioning at that time.)

    I checked the Android developers documentation and found that as of Android 8.0 certain restrictions apply for processes like the one I use to keep the app in touch with my server. Fortunately, the documentation also says how to make the app compliant with these restrictions.

    Most likely, I will publish an updated version within 1 or 2 weeks.

  • 0
    Avatar
    Alexander

    I think I solved the issue I mentioned in my previous post, but I cannot test the fix on my own device, since the problem is related to Android 8.0 and higher and I am using an older version. So I set up an "internal test program" (as Google calls it) where you can try if the fix works for you.

    If you want to help testing, please contact me and mention the email address (@gmail.com) you use for downloading from Google Play so I can place that email address on the testers whitelist. After that, I will send you the instructions how to join the program and download the test version.

  • 0
    Avatar
    Alexander

    Due to some problem that I don't want to spend too much time on, distribution via the "internal test program" did not work. So I just published the untested updated app and will see what happens.

    Apart from the issue with Android 8.0 and higher, I also addressed some other details. Most notably, I added support for choosing your own sound from a range of system sounds, similar to what has been possible already for a long time in the iOS app.

    To use it, visit your Preferences page, and under "Alerts for iOS/Android app", "Android app only" check "Play system beep ..." and select the name of the sound you want in the menu.

  • 0
    Avatar
    Alexander

    The recent fix did not fully solve the Android 8.0 related issue for the user who reported it. Worse, for another user it actually broke things (under Android 9). And yet another user contacted me recently about interruptions under previous Android versions when the app is in the sleep mode.

    So I will revert to my original plan: distribute a test version via an "internal test program", and only when that seems to work fine, publish it in the usual way. I think I understand what went wrong with my first attempt to use this internal test program, so I will try again within a few days.

    Also within a few days I will publish a version without the recent "fix" but with support for playing the system sound of your choice, for it seems that part works fine.

    Again, if you want to help testing, please contact me and mention the email address (@gmail.com) you use for downloading from Google Play so I can place that email address on the testers whitelist. After that, I will send you the instructions how to join the program and download the test version (and how to restore the official version if the test version does not work for you).

  • 0
    Avatar
    Alexander

    I just published an Android app version without the "fix" for Android 8.0 that broke things under Android 9. I left the support for Android system beeps in place. Again, I was not able to test this version since my device doesn't run Android 9.

    So, should you update or not (yet)?

    If you installed the recent "fix" and cannot login anymore, there is nothing to lose so I advise you update right away (and let me know if it works).

    If you are using Android 9 but did not install the recent "fix", I suggest you wait until I can confirm this new version runs well under Android 9 (apart from the issue the previous version was supposed to fix).

    If you are using Android 8 or lower I think it's save to update, but you still may want to wait and see if no new problems pop up. The single feature why you may not want to wait is the support for Android system beeps.

  • 0
    Avatar
    Alexander

    Alas, the recent update doesn't work under Android 9 either.

    The good news is that distribution via the "internal test program" now works fine, and thanks to several testers, I found a workaround. I plan to publish an update shortly that will function properly under Android 7 and lower, acceptable under Android 9 and higher, and either properly or acceptable (I'm not sure yet) under Android 8.

    The cause of the problem under Android 9 seems to be a subtle error in my code that I haven't fully tracked down yet, but that is apparently fatal when combined with SDK (Software Development Kit) version 28. Up to recently, I used SDK 26, which is apparantly much more forgiving for this subtle error in my code, but as of November 1 (next Friday!), all apps that are uploaded to Google Play should be built using SDK 28 or higher.

    So I plan to publish a version using SDK 26 when it is still possible, and then continue testing until I know how to make it work using SDK 28. If you want to help with the final testing of this temporary solution, contact me directly.

  • 0
    Avatar
    Alexander

    The most recent version was tested under Android versions 5, 7, 8, 9 and even 10, and the results were great, so I made it available for everyone on Google Play. In fact, I already did that yesterday, just in case Google's definition of "November 1" is different from mine (due to a difference in time zone), but only now did I find time to post this message.

    While I feel confident this version is useful enough for everyone, the tests also revealed a few minor issues that I was not aware of before. Of course, I will try to resolve these issues in a future version.

    All in all, I think setting up this "internal test" was a good thing to do, and I plan to do it more often. But also when there is no such test, if you hit on a problem with RumpelstiltskinRSS, feel free to contact me about it. I will see what I can do for you, and most likely this will also help other users.

  • 0
    Avatar
    Cheryl

    HI Alexander, Since Wed/Thursday of last week, I continually get 'can't find server' or 'server timeout' or (for the first time) 'not enough storage (on the server)'. Are these because you've been tweaking and it's checking for jobs at times when you're working? Any ideas if that's not the case? Thanks!

  • 0
    Avatar
    Alexander

    Hi Cheryl,

    Thanks for reporting this. This is weird. I did make a few changes on my server last week, but that was in a separate test environment. I just checked, and the scripts in the regular environment are still those I put there on October 21.

    As of October 21, my scripts do produce error messages under certain circumstances, but not those you mention. The only error messages you can get from my scripts currently are "Could not reach Gengo" and "There was a problem contacting Gengo", and you should not see them too often.

    The Android and iOS apps don't produce error messages either. They just display what my server tells them to display. So I have no clue where these messages come from. The next time you see it, could you send me a screenshot?

  • 0
    Avatar
    Cheryl

    here you go-

  • 0
    Avatar
    Alexander

    Thanks for posting the screenshot and sorry for responding late. I prepared a quick answer but apparently forgot to post it.

    My quick answer was that I suspected the message came from my provider rather than from within my scripts, but I would be away from my computer for a few days so I would only have a better look at it later on.

    Today, I contacted my provider about this "storage allocation" message and they confirm there was a temporary issue on their side recently, which should have been resolved now. If you see it again, please let me know right away and I will inform them about it, so they can have a look at the very moment when it is happening.

  • 0
    Avatar
    Alexander

    I prepared a new RumpelstiltskinRSS Android app test version. Visit rmpl.nl/test to learn how to get and test it, and how to switch back to the regular version once you are done testing.

    Like I said in a previous post (October 29, 2019 21:56), as of November 1 Google requires apps to be built using SDK 28 or higher but there was some subtle issue that forced me to stick to SDK 26. I think I solved it, but once I replace the current regular version there is no way to go back, so I want to wait with that until the fix has been thoroughly tested.

    So for the next few months, I plan to publish any new release as an "internal test". This one has no new features, yet it is a huge step forward. Not only did I leave SDK 26 behind, I also migrated to the AndroidX libraries. In plain English this means I use the latest and greatest building blocks Google currently provides, adding to the reliability of the app.

    So I am very curious how this "internal test" version works for you. It should run under any Android version later than 4.0, so there is a wide range to be tested. Please give it a try and let me know about your findings!

  • 0
    Avatar
    Cheryl

    Hi Alex,

    Working on Windows 10, firefox. The sound works on tests (insert dummy job), but 3 times today it didn't work on a 'real' job. I've been sitting at my computer and the only way I saw the job was when the tab switched from RSS to Workbench. Ideas for a fix? It's been working fine since the beginning of November. I don't know if the android changes you're implementing have anything to do with it (I doubt it, really). Thanks for any help!

  • 0
    Avatar
    Alexander

    Hi Cheryl,

    Thank you for reporting this issue.

    Part of the Android changes required changes on my server as well, so I updated the scripts last weekend. Of course, I may have introduced a bug that way. But then again, that bug should also affect the dummy job notification. Did you repeat the test with the dummy job after last weekend?

  • 0
    Avatar
    Cheryl

    Yes, just before I posted my comment, lol! Thanks!

  • 0
    Avatar
    Alexander

    I tested with Firefox for Mac. There happened to be a job, and the sound worked fine. Please contact me directly and mention your account name so I can test with the exact settings you use.

  • 0
    Avatar
    Cheryl

    Done. BTW, it just happened again while I was working on something else on my computer.

  • 0
    Avatar
    Cheryl

    Hi, I haven't heard back. I don't know if no new jobs are coming through because of the holidays or if my feeder is working correctly.  I retested with a dummy job and it worked fine again, so please let me know. Thanks!

  • 0
    Avatar
    Alexander

    Hi Cheryl

    Didn't you receive the email I sent on December 17, 17:20:53 GMT+01:00?

    In short, even using exactly your settings I can't reproduce this issue, and the only cause I can think of is that tight memory on your computer interferes with "When a new job is found, after 2 seconds go to workbench and halt".

    The sound takes some time to load. About 1 second on my computer, but perhaps more than 2 on yours. So when the browser starts loading the workbench and needs even more memory, it may decide to cancel the process that should start the sound.

    In the case of the dummy job, a nonsense collection ID is used so Gengo replies with an easy to load page that does not interrupt the sound. And in my tests, there is enough memory so loading the workbench does not conflict with playing the sound.

    There are 2 ways to test this theory.

    -1- When testing with the dummy job, change the collection ID 12345678 in "Use collection ID 12345678 to test this feature" into the ID of a collection you actually translated in the past and see if that reproduces the problem (since the dummy job now triggers the browser to load a “heavy” page).

    -2- In "When a new job is found, after 2 seconds go to workbench and halt", specify a larger interval (let's say 5 seconds) and see if that solves the problem for real jobs (even though such a long interval may not be what you want).

    I just switched on logging for your account to see when and how many jobs are found.

Please sign in to leave a comment.