Jon Zenor
Jon's Portal to the web
RSS
  • Home
  • Projects
  • Photography
  • Writing
  • Contact Me

Google

Syncing Facebook, Plus, Twitter, and Linkedin via “If This Then That” (ifttt)

Sep 14 2011

Syncing Facebook, Plus, Twitter, and Linkedin via “If This Then That” (ifttt)

Google plus has been a great service so far, cleaner and easier to use than facebook. I personally prefer the streamlined interface. But there is a problem, a huge problem, not many people want to leave what they are comfortable with. Facebook works well and is very popular, making it hard to leave.

So what can those of us who want to embrace this new technology do? Either we have to be extremely redundant, posting our messages multiple times, or find some type of syncing service.

One limitation of Google Plus is that they have no APIs to post to plus from outside. You cannot send an SMS message, or have facebook update your plus status.

Several plugins and systems have emerged to take your Google Plus status and push them to Twitter and Facebook. But even those have been lacking in that none of those solutions would work from the mobile web app or the phone apps.

Today, however, I found a solution to all of these problems! A mixture of two services. The first service, which we will discuss briefly, is called plu.sr zipl.us. This service simply takes your Google Plus public feed and turns it into an RSS feed.  You just use a special URL with your Google Plus ID in it.

The main part of this plan is found in a service I found today called “If This Then That.”  This service is awesome and worth exploring.  IFTTT allows you to create multiple conditional statements that work to connect two of the many channels available.  Channels are basically APIs to different sites, such as Facebook, Twitter, RSS, YouTube, InstaPaper, etc.  The service is really easy to set up, so let’s get to it.

The Instructions

The first step (assuming you already registered for ifttt) is to get your Ziplus ID.  Go to plus.google.com and click on your name next to your profile pic.  Then in the URL grab the really long number, this is your id.

Now go to If This Then That and create a new task.  Click on the word “This” and select the RSS feed icon, then select the trigger “New Feed Item”.  For the URL enter  http://plu.sr/feed.php?plusr=117243117130917765448 (but use your really long number, not mine) http://zipl.us/JonZ/feed (but use your ziplus username, not mine).

Next hit the Create Trigger button, then click the word “That” to set the action that happens when the trigger is triggered.

Select the Facebook, Twitter, or Linkedin icon and follow the directions to activate the channel on your account.

If you select Facebook or Twitter you will have to choose the action item.  Select “Create a Status Message” and enter {{EntryContent}} {{EntryURL}} in the box.

If you are setting this up for Twitter then you will want to use {{EntryTitle}} instead, as the plu.sr service uses a truncated version of your status message for the title.

That’s it, you are done!

You will have to remake the task per service you want to update, and the tasks are only checked every 15 minutes, so it is not instant, but it works.  Within 15 minutes of making a public post to Google plus from the web or your phone it will be sent to the services you set up.

On your task list you can click the right arrow button to view more details and then there is a check now button you can hit.  Hit this to test that your task works without waiting 15 minutes.

Hopefully with this mini tutorial you can get your Google plus status messages going to facebook and twitter, as have an understanding of how ifttt works so you can create other tasks.

Have any unique ideas for ifttt tasks?  Share them in the comments below!

Update 18 January 2012

Due to Google Plus API changes, plu.sr no longer works.  I found a different service that works the same way called zipl.us.

By Jon • Tech, Web • 2 • Tags: Android, Google, Google Plus, ifttt, iPhone

Jul 13 2011

Hello Plus, Goodbye Facebook!

This week I finally got invited to Google Plus! The system Google is making to take on the social networking world. I have messed with it for a few days and am fairly impressed with it.

Not everything is as polished as Facebook, but give it time and I am sure it will catch up. The service is still in a very early stage of testing.

I’m confident enough in the service that I am going to try to make the switch entirely off of Facebook. I will be updating my facebook status still sometimes because I still use Twitter and it updates my FB status for me, but other than that I will be sticking with Plus.

Hangouts are fun!

Hangouts are a group video chat system, pretty neat actually. Once you announce you are going to be “hanging out” and with which circle (or group) you want to hang out, anybody from that circle can jump in or out at will.

No Annoying Apps!

One great thing about Plus, there are not a million farm town requests waiting for me when I login! Sure the Facebook flash games are fun, but a social network is not supposed to be a gaming network.

Should you switch?

The question about whether you should switch entirely or not is up to you. Plus is not nearly as popular as Facebook yet, meaning you will have less of your friends on there. I would suggest giving it a couple of days and really mess around with it before you decide. If you want an invite, just let me know! (Link below) :)

Profile URL Shortener

Google is against making things easy sometimes, so your profile ID will be nothing but a huge number. Instead you can shorten it with a service called gplus.to.  You can create a unique URL that will forward to your plus URL.  Try it out! My URL is gplus.to/JonZenor.

What are your thoughts on plus so far? Think it will have a chance of pulling users away from Facebook?

By Jon • Tech, Web • 0 • Tags: Facebook, Google, Plus

May 7 2011

Wave in a Box (WIAB) on OSX

I love Google Wave, I think it is a great technology for offices that need to colaborate things together.  When Google announced that it was shutting down the project, my hopes in Google got dashed and it actually kinda depressed me for a bit. (yeah, I’m a geek, I know…)

Wave in a Box, to the rescue?

When I heard that you could install Google Wave on your own system, I got a little excited again, and this weekend I finally took the time to install it on my mac. Only to be disappointed again.

Wave In a Box is not to the level that Google Wave was when they canned the project. Right now you can make a wave, and add gadgets, add replies to each wave, and add other participants to the wave. But that is it. No playback history or even profile management (so no avatar to distinguish who is who). WIAB also does not have the polished feel that Wave has.  Plus the biggest disappointment, is that waves do not save yet.

No Saving Waves

There are 2 methods to save waves, (called delta’s). The first is in memory, this works great, is quick, and is what is recomended. But if it is in memory then as soon as you restart the server software, all of your wave data is gone.

They give you the option to save to the file system, (hard drive), which saves your waves even if you restart the server, but there are 2 negatives. The first, is they warn that this will likely crash the server. The second, and severe downside to the file system, is they plan on using a completely different setup in a later release, and they warn that when you upgrade the server you will lose all data that is saved.

So no matter how you cut it, you will not be able to use WIAB for anything serious right now. If I had known this before I started I likely wouldn’t have wasted my time.

But, alas, I did, so hopefully others can learn from my exerience. So here you go, here is how I did it, step by step instructions.

Step by Step installation (OS X)

For the first part you can pretty much follow the directions on the WIAB website, but I will walk you through anyway just so there is no confusion.

1. Download Mercurial and install it

2. Open Terminal

Type “Terminal” in the search bar.

3. Make the directories

Go to where you want to install wave, we will use your home directory, then make a new folder

user@computer:$ cd ~
user@computer:$ mkdir wave
user@computer:$ cd wave

Optionally you can install Mongo DB at this point, make a directory in wave called “dependencies”, download Mongo, unzip it inside the dependencies directory, rename it to “mongodb”, then in another terminal window launch with “sudo ./mongod”. This will be used to store usernames instead of using the file system, but the 32 bit version is limited to 2 GB of storage.

4. Download Wave-Development

user@computer:$ mkdir wave-development
user@computer:$ cd wave-development
user@computer:$ sudo hg clone https://wave-protocol.googlecode.com/hg/ wave-protocol

Note 1: when using sudo you will have to enter your admin account password
Note 2: If you are having trouble with the “hg” command, check that you installed mercurial correctly (from step 1)

5. Take a Mountain Dew break.

250 Mega bytes of Google awesomeness are being downloaded, so take a break, grab a Mountain Dew, and read my other blog at Eternal Truth Ministry.

6. Build Wave in a box

user@computer:$ cd wave-protocol
user@computer:$ ant

7. Take a Bejeweled break

This build took me about 5 and a half minutes, so relax with some Bejeweled 2 or check out the projects I am working on. (shameless advertising FTW!)

7. Configure Wave

user@computer:$ sudo cp server.config.example server.config
user@computer:$ sudo ant -f server-config.xml
user@computer:$ sudo vi server.config

Here you will have to use your mad vi skills (or another editor) to change some variables in the config file.

The wave_server_domain is the appearance of how your name looks, i.e. jon@local or jon@zenorsoft.com

# Domain name of the wave server
wave_server_domain = mysite.com

Next change the address used to access your server. The first value, http_frotend_public_address is any URL allowed to access your server. If you only access this from one machine then leave it as localhost:9898, but if you want to access it from any computer in your network add the ip address of the machine.

http_fronend_address is the default value, but I had trouble accessing the site from any URL that did not match the frontend_address.

# A comma separated list of address on which to listen for connections.
# Each address is a comma separated host:port pair.
http_frontend_public_address = localhost:9898, 192.168.1.101:9898

# Default value: values passed to http_frontend_public_address.
http_frontend_addresses = 192.168.1.101:9898

Next we change the variable that tells the system where to save user accounts. If you are just testing this and do not need it to save then you can leave it as memory, which will be erased when you restart the software. If you installed mongo db then use “mongodb”, otherwise use “file”.

# Currently supported account store types: fake, memory, file, mongodb
account_store_type = file

Here is the sucky part. delta_store_type is where the waves are saved. If you are just playing around keep it at memory. If you really want to use the WIAB server use file, but take notice of the warning they give you that upcoming changes will make you lose your wave data no matter what.

# Currently supported delta store types: memory, file
# Note: file system support is experimental. Your server may crash. And the file format is
# not stable and shouldn't be relied upon for long-term storage yet; upcoming changes will
# require you to blow away your data.
delta_store_type = file

Finally, make sure you comment out the line that wants to include the federation server configs.

# To enable federation, edit the server.federation.config file and include it here.
# Or run ant -f server-config.xml server-federation-config
# If not using the server-config.xml ant script - it is possible just to comment the line.
#include = server.federation.config

Save and quit the config file.

8. Start the wave server (YAY!)

From the ~/wave/wave-development/wave-protocol/ directory run this command

user@computer:$ sudo ./run-server.sh

If there are errors then the script will stop running and give a bunch of warnings. If everything stays running then your server is setup. Now go to your browser and type in the address to your server using port 9898 (localhost:9898 or the ip to the server) and enjoy your own personal wave in a box.

Accessing from the Net

The last thing I tried (for 3 hours and then failed) to do is access the wave server from the net. No matter what I tried for port forwarding or anything else I could not get this to work…. Maybe it is because I am running a qwest modem (which is also a router) and then going to my Linksys router? Both devices allow for port forwarding, but are on different networks and no combination I tried would work.

But that is just my rant and has nothing to do with this tutorial. If you have any ideas, though, let me know. ;)

By Jon • Tech • 3 • Tags: Google, Google Wave, Mac, OS X, Tutorial, Wave

Subscribe

  • Facebook
  • Twitter
  • YouTube
  • Flickr
  • RSS Feed

Tags

Android autobiography Best Buy biography captcha Computer Upgrades ETM Facebook Family Following God forum Google Google Plus Google Wave hardware bad luck hobbies ifttt Introduction iPhone Linkedin Mac malikai New Years OS X Plus radio controlled rc car Resolution Tech Fail tumblr Tutorial Version 2.0 Walmart Wave

Meta

  • Log in
  • Entries RSS
  • Comments RSS
  • WordPress.org
© Jon Zenor 2013
Powered by WordPress • Themify WordPress Themes