My little PresenceRouter Mac OS X application, designed to allow you to route your Plazes geopresence to web services like Twitter, Facebook and Fire Eagle, now allows you to route your Plazes geopresence to, well, Plazes.
If this seems like it has the potential to create infinite loops of presence routing you are right. But there is method to my madness: yesterday saw the unveiling of Plazes.net, a new developer-focused branch of Plazes that’s completely concentrated on developing the “geopresence engine” aspect of Plazes.
In other words, if you’re a regular everyday person looking to manage your geopresence, Plazes.com is still your destination. But if you’re a developer looking to bake geopresence support into your application, then you’ll find a new home at Plazes.net.
For the time being, the two branches of Plazes are separate: while you can import your historical Plazes.com geopresence stream into Plazes.net, presences you create in one will not exist in the other; there are two separate data streams.
So that’s why I’ve added “Plazes support” to PresenceRouter: you can now do any of the following:
- Use Plazes.net as you PresenceRouter data source, routing your Plazes.net presence information instead of your Plazes.com presence information.
- Route your Plazes.com presence to Plazes.net, allowing you to continue to use Plazes.com as your “mothership,” but echoing your presence stream to Plazes.net.
- Conversely, route your Plazes.net presence to Plazes.com.
So whereas before Plazes was only a source for PresenceRouter geopresence, it can now be a destination as well. Indeed you can even route your Plazes.com presence back to Plazes.com, to another account, if you can figure out a reason why that would be useful.
Grab PresenceRouter v2.7 if you want to try this out for yourself.