Requiring OmniAuth

 Identity and Privacy, Technology  No Responses »
Aug 312011
 

A small note in the “in case I need this again” category.

I’m writ­ing a Sinatra app and want to add Twit­ter OAu­th for sign­ing in. A good way to do this appears to be with the omniauth gem but I ran into an issue. require 'oa-oauth' is the doc­u­mented way to require the right gem, but the error I was get­ting was ‘require’: no such file to load — oa-oau­th (Load­Er­ror), des­pite hav­ing installed the gem. I use RVM to con­trol the Ruby envir­on­ment, so also checked I’d installed the gem with the RVM ver­sion set to the ver­sion of Ruby I was using (1.9.2). Hunt­ing around I found a par­tial answer on the issues list. Par­tial, because the answers there did­n’t help, but the sug­ges­tion to try bundle show omniauth did. Bundle came back with Could not find gem ‘omni­au­th’ in the cur­rent bundle.

The answer turned out to be to edit the Gem­file to add gem omniauth to it, then run­ning bundle install. After that, bundle show omniauth found the gem, and require 'oa-oauth' in my Ruby app worked as well.

Syncing Google Calendar and Tungle

 Rants, Technology  No Responses »
Aug 232011
 

I came across this weird prob­lem recently, where my Tungle account (tungle.me/laurenwood) was only syn­chron­iz­ing some of the events on my Google cal­en­dar. I checked they were set to the right cal­en­dar (yes), marked as busy (yes), and still could­n’t find the answer. 

This is an issue that quite a few people have had. Appar­ently what’s going on is that Google cal­en­dar sup­ports three types of avail­ab­il­ity for events: free, busy, and tent­at­ive. In the UI on the browser and on the Android they only show the free (avail­able) and busy. BUT, when you cre­ate an event on the Android cal­en­dar, it’s assigned the “tent­at­ive” status. I have no idea why, since I added those events to the cal­en­dar myself, they’re not invit­a­tions that I still have to accept or decline. And the fact that there appears to be no way to change the status once the event has been cre­ated just makes it worse. I tried chan­ging the status manu­ally to “busy” in both the browser and the Android cal­en­dar app but that did­n’t work. The only thing that did work was to delete the event and recre­ate on the desktop.

For­tu­nately tungle imple­men­ted a fix — you can choose to mark the sup­posedly tent­at­ive appoint­ments as “busy”. Here’s hop­ing any oth­er apps I may wish to sync with my Google cal­en­dar also imple­ment this feature.

/* ]]> */