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.

322 comments

  • 0
    Avatar
    Alexander

    Hi Mamiko,

    Thank you for helping with the test. For Test sound 2 I used a feature of modern browsers to play without showing a player, so in that respect your observation meets my expectations.

    Meanwhile, I found a statement in Apple's documentation (Safari HTML5 Audio and Video Guide) that "In Safari on iOS (for all devices, including iPad), where the user may be on a cellular network and be charged per data unit, preload and autoplay are disabled".

    In other words, Apple wants to protect users from automatically starting a stream that will drain their wallets. I can sympathize with that, but I regret there is no way for a user to tell Safari that for a particular site it's okay to start playing. The current sound in RumpelstiltskinRSS is 125 KB. I don't think this would have a noticeable effect on your bill.

    From other sources on the internet I understand this restriction was first included in iOS 6. Also, I didn't read anything about a similar restriction on other systems, like Android. So I believe this problem is specific for devices running iOS 6+.

    The bottom line is that my current approach will never work for you. But perhaps another approach will. The restriction seems to be on the download of the sound only. Once the sound is in the memory of your device (e.g. triggered by the user pressing a button), it can be reused from within the software.

    So perhaps I could make it work by refreshing only parts of the page rather than the whole thing. I'll try to make something along these lines within the next week.

  • 0
    Avatar
    hemehemekukohi

    Hi Alexander,

    I really appreciate your effort to find a problem and  solution!!! 

    And thank you for your detailed explanations about the reason why my iPhone doesn't produce a sound. Now I understand.

    I'm glad that I still have a hope!

     

  • 0
    Avatar
    Sunnysailor

    Also from my side a big thank you for your effort to make things work for all of us who use your excellent tool!

     

    All the best

    Martin

  • 0
    Avatar
    Alexander

    Hi Mamiko, hi Martin,

    Thanks for your kind words about the usefulness of the software. They are an extra stimulus to solve this issue. But most of all, I find it annoying that a core feature is broken. Being alerted or not being alerted via a sound makes a huge difference. That's why I am determined to fix it, one way or another.

  • 0
    Avatar
    Alexander

    While I don't have a device with a recent iOS version, I was able to reproduce the problem in the Xcode iOS Simulator. The current version sort of works in the iOS Simulator, so it may also work for you.

    Tap the Preferences button. On the Preferences page, scroll down to the new block "Alerts". Check "Use alert mechanism adapted to iOS 6 and later". Tap "Start checking for jobs" (make sure "Save preferences upon Start checking for jobs" is checked, or tap "Save preferences" before you tap "Start checking for jobs").

    Near the top you should now see a link "Play sound". Tap it for the initial download. You should immediately hear the sound. From now on, it's available in the memory of your device for reuse when RumpelstiltskinRSS sees a job.

    That's the theory. In practice, I have found that sometimes the sound still isn't played when it should be. I guess it is erased when memory gets low. In particular, this may happen if you switch tasks on your device. Therefore, whenever you use the device for anything else and then switch back to RumpelstiltskinRSS, I advise you tap the "Play sound" link again.

  • 0
    Avatar
    Diego Cavalcanti

    Hi! I really like the concept of your app, but i keep getting an error when i try to register a new user. It always says that my username is alrealdy taken, no matter what i write.

  • 0
    Avatar
    Alexander

    @Diego Cavalcanti - Fixed. Sorry for the inconvenience.

  • 0
    Avatar
    Diego Cavalcanti

    Thankyou! Register option working fine now, but when i try to add my rss link, even though i just copied it from the rss link, it says it's a invalid rss (it happened with a few other rss readers as well).

  • 0
    Avatar
    Diego Cavalcanti

    It's is possible to automatically open the job page when a new job shows up on the rss?

  • 0
    Avatar
    Alexander

    @Diego Cavalcanti - From the creation time I could guess which account is yours, and I see your rss link ends in a slash (/). I modified RumpelstiltskinRSS so it accepts this. For other rss readers I suggest you remove the final slash to see if that solves the problem.

    As for your suggestion to automatically open the job page, I tested this in the past but was not happy with it. With the current version, if I'm not in the mood for translating at that particular moment, or if I'm already working on a job so I can't pick a new one anyway, I can simply ignore the alert. But if the software opens the job page, it halts there and needs a manual reset to resume looking for other jobs.

  • 0
    Avatar
    Diego Cavalcanti

    Many thanks again! The app is working fine now and i just got my first job (a very nice one) thanks to your app. I'm really happy at the moment, hahaha! Got really shocked about the "OH OH OH OH" sound and i was frozen for a moment, but still got the job, hahaha. When i clicked the link, it showed an error message, tough:

     

    {
        "items": [
            {
                "name": "id",
                "error": "@",
                "path": "id"
            }
        ],
        "resourceName": "default",
        "resourcePrefix": "",
        "count": 1,
        "replacer": [],
        "isPrepared": false
    }

     

    About my suggestion, it is a feature that i don't find in any rss reader. As for my language pair, there are not many jobs at a day, so we need to be always super ultra fast and concentrated to get a job - like, clicking on the rss alert to show the job page, then running to click on the start translating button. With an automatically page open system, people wouldn't need to worry about running to the notification to open the page and then click on the button, and could concentrate on what you doing at the moment (i work as a webdesigner and get gengo jobs whenever they are avaliable. It could work as an option. Like a checkbox to show or not to show the page automatically. Thanks one more time!

  • 0
    Avatar
    Alexander

    @Diego Cavalcanti - Good to hear I made you happy. The sound is intended to raise your adrenaline level, as on Gengo's system you have to react quickly.

    I don't understand what caused the error message. The link should bring you to the workbench, which is http://gengo.com/t/workbench/12345678/ (with 12345678 replaced by the collection id). When you open the workbench, under the hood there is some extra communication between your device and Gengo's server, involving so-called JSON objects. This error message looks like such a JSON object (albeit without collection specific details). RumpelstiltskinRSS itself doesn't send or request JSON objects, though.

    If your suggestion is to automatically accept the job, I'll never include such a feature since it's against Gengo's terms. Accepting should involve at least one manual step, like pressing the Start button in the workbench. In the current approach, after the alert you have to perform two steps: opening the workbench and then pressing Start. In my experience, automatically doing the first step to save a few seconds is not as useful as it might seem, but I could include it as an option in a future version.

  • 0
    Avatar
    Diego Cavalcanti

    Hum... That's strange then.

    About the suggestion, it would be used just to open the workbench page automatically, you would still need to click to accept the job as usual.

     

    Well, thanks again, hehe.

  • 0
    Avatar
    Diego Cavalcanti

    About the error, the system got all of the job info correct, even the payment converted (very nice function btw), just the link didn't work.

  • 0
    Avatar
    Alexander

    I'll include automatic opening the workbench as an option in a future version.

    If the problem with the link persists, or if other people report the same problem, I'll have a better look at it. For now I consider it a one-off issue.

  • 0
    Avatar
    Diego Cavalcanti

    Thanks you!

    I just got three notifications, all of them with the same error. When i clicked the link, it change the url to http://gengo.com/t/workbench// with two slashs at the end. And one more detail here, this were not workbench jobs. They are open in an url called https://gengo.com/t/jobs/. Could it be the reason?

  • 0
    Avatar
    Alexander

    Thanks for your detailed observations. That's very helpful. The two slashes could mean that the collection id is "" (empty string), in other words the feed was not interpreted correctly. I added code to log some details whenever a job is seen under your or my account.

    Jobs with an attachment have their own environment other than the workbench, but the system is smart enough to redirect from the workbench style link to what it should be, so I don't think the second part of your observations is related to the problem.

  • 0
    Avatar
    Alexander

    Hi Diego,

    To figure out the collection id, RumpelstiltskinRSS looked in the feed for a URL that starts with "http://" (without s). However, in your feed it starts with "https://" (with s). I modified the code to look for both possibilities. This should solve your problem.

  • 0
    Avatar
    Diego Cavalcanti

    Hi!  Thanks for all the help! As soon as a new job arrive, i will test the link and inform to you. Sorry about all these problems, hehe. 

  • 0
    Avatar
    Alexander

    It's not a problem at all. In software development, feedback from users is essential. And while I am a user myself (I created RumpelstiltskinRSS for my own needs; making it available to others was secondary), it's only natural that there are issues related to details different from my own situation, and that these issues pop up now that the user base starts growing.

  • 0
    Avatar
    Diego Cavalcanti

    Hi. It's working fine now!

  • 0
    Avatar
    Diego Cavalcanti

    I have a question about the rss feed, i think you might know the answer. An RSS reader will only show a new job if it is avaliable at the exact time it refreshs, or it will show all jobs between the time it last refresh? I was wondering beacause sometimes i get an e-mail about a collection and the reader didn't warned me. 

  • 0
    Avatar
    Alexander

    If you set RumpelstiltskinRSS to check every 62 seconds, you will see the jobs that are available at that particular moment. It's possible that a job appears after you checked, is seen by the mail notification system, and is taken before you check again, so you will see it in your mail but not in your reader.

    If you set RumpelstiltskinRSS to check every 31 seconds, the story is a bit more complex because Gengo uses a per translator caching mechanism which "freezes" the info for a minute (to discourage checking too frequently). The bottom line is that both options (31/62) yield the same results. Why I put in the choice if it doesn't make any difference is a story on its own. You can read parts of that story in other forums.

  • 0
    Avatar
    Diego Cavalcanti

    Understood. Thank you!

  • 0
    Avatar
    Alexander

    It seems several users created multiple accounts, probably because they lost the password of the original one. Therefore, I added a 'Forgot password' option on the log in screen.

    If you want to switch back to you previous account name, just use the log out button and log back into the desired account by providing your Jobs RSS and a new password.

    At some point in the future, I will remove accounts that are apparently inactive.

  • 0
    Avatar
    Alexander

    I included an option to automatically open the job page when a new job shows up, as suggested in this forum by Diego Cavalcanti.

    I also included an optional pop-up notification, as suggested in https://support.gengo.com/entries/55053384-Tool-for-searching-through-jobs by Alicia L. Alonso.

    It is now possible to switch the sound off.

    If you want to experiment with these settings, you can use the new option "Insert dummy job" to get an alert immediately, rather than having to wait until a real job arrives.

    All these settings are on your Preferences page in the box with header "Alerts".

    If you combine different alerts (e.g., pop-up + open the job page) you may find they are conflicting and the resulting behavior is not what you want. Sorry for that. I hope there is at least one combination of settings that works for you.

    I only did limited testing, but expect each of the new options to work on all platforms. If one of the new options fails on your device, let me know. You can use the Contact link on every page of the tool.

    I removed the separate preferences for jobs for which you are a Preferred Translator, since the information whether or not you are a Preferred Translator apparently disappeared from the RSS feed.

  • 0
    Avatar
    Alicia L. Alonso

    "A job, a job!"

    Wow!! This is great. Thank you, Alexander!!! 

     

  • 0
    Avatar
    Alexander

    Thank you, Alicia, for suggesting this great feature which will probably also be helpful for others.

  • 0
    Avatar
    Nicktim

    Hey Alexander,

    First, thanks a lot for a quite useful tool. Second, i still have a few questions.

    1. Refresh rate. It is possible to use either 31 sec or 62 sec refresh rate, and as you say in the main post, Gengo is fine with translators updating their dashboard 2 times a minute. So, 31 sec works perfectly unless one simultaneously uses another rss reader, is that correct? But then, later on May 15, 2015, 22:45 you say that "Gengo uses a mechanism, which freezes the info", and that "both options (31/62) yield the same results". Doesn't this contradict the first statement?

    Is the result the same when one uses the following options and do both ways actually work without any troubles?

    a. RumpelstiltskinRSS (62 sec refresh rate) simultaneously with another rss reader (62 sec r.r.)

    b. RumpelstiltskinRSS (31 sec r.r.)

    2. Question about using RumpelstiltskinRSS on iOS device. Is it ok for the screen to be turned off while the page with the timer is processing? Or it should be always turned on in order for the user to get notification/sound?

    Thanks.

  • 0
    Avatar
    Alexander

    Hi Nicktim,

    1.

    Gengo requests you access their server no more often than twice per minute. Also, Gengo caches ("freezes") the info per translator for a minute. So it's fine with them if you look twice per minute, they just don't give each time fresh info.

    If you set RumpelstiltskinRSS to check every 31 seconds, what you get to see is:
    T=0: status at T=0 (fresh)
    T=31: status at T=0 (cached)
    T=62: status at T=62 (fresh)
    T=93: status at T=62 (cached)
    and so on.

    If you set RumpelstiltskinRSS to check every 62 seconds, what you get to see is:
    T=0: status at T=0 (fresh)
    T=62: status at T=62 (fresh)
    and so on.

    So you see there is no real difference.

    If you use another RSS reader, and set RumpelstiltskinRSS to check every 31 seconds, you will end up accessing Gengo's server more than twice per minute. (Almost twice via RumpelstiltskinRSS, and on top of that every now and than via the other reader.) Strictly speaking that's against Gengo's terms, though I don't think they will sue you for it.

    Other then the limitations set by Gengo, there is no reason why you shouldn't use multiple readers. Two or more readers won't interfere with each other. Again, RumpelstiltskinRSS will see the same info for both the 31 and the 62 setting. So it's fine to use RumpelstiltskinRSS (set at refresh rate 62) and another reader (set at r.r. 60 seconds or more). Both readers will work correctly, and the configuration is in agreement with Gengo's terms (as I understand them).

    2.

    Your browser (probably Safari) must keep running, and as far as I know that means your screen cannot be turned off. I'm aware this drains your battery, but I don't know how to avoid this.

Please sign in to leave a comment.