I'll post some more details later today, but just as a basic overview of the system I am using:
It uses an XMPP account on the server that is signaled in some way (right now by receiving an email), that makes the server switch its presence. The n900 program receives this via a dbus message that it subscribes to, and then takes the appropriate action (runs a script), such as checking for email.
I might add telepathy tubes in the future so actual data can be sent too, but that would come in a later release, since I would need to look into how to do that.
I didn't realize there was this much interest. I'll probably have some time to do some cleanup on the code this weekend. I just need a name for the program. Any ideas? I'll change this to an announce thread once I come up with a name.
What would be the big advantage between having the presence being polled all the time (as is done now), with also mail being polled (infrequently)?
Or do I misunderstand how the presence is updated right now?
I would keep n900 out of the name, and go for something more platform agnostic to avoid renames down the track when you redevelop for meego and other platforms
I seem to be one of the few people who puts up with battery drain to maintain an online presence (via xmpp).
Are people going to be willing to maintain a permanent data connection?
I was toying with a script that used Google Voice free SMS for push, which would then trigger the n900 to establish a data connection to get done what needed to be done.
What would be the big advantage between having the presence being polled all the time (as is done now), with also mail being polled (infrequently)?
Or do I misunderstand how the presence is updated right now?
The xmpp protocol updates presence and receives messages via push (the client opens a connection to the server, and that connection is left open, and new messages / presences are "pushed" to the client instantly), instead of via polling, where new messages, etc are checked for every X minutes.
Email (unless you are using nokia messenging, or microsoft activesync) is received by checking for new messages every X minutes. This program will notify your phone that there is a new message, so you can receive it instantly. If you are already using a jabber client on the n900, it should use less battery than nokia messenging, microsoft activesync, or even polling.
I would keep n900 out of the name, and go for something more platform agnostic to avoid renames down the track when you redevelop for meego and other platforms
I seem to be one of the few people who puts up with battery drain to maintain an online presence (via xmpp).
Are people going to be willing to maintain a permanent data connection?
I was toying with a script that used Google Voice free SMS for push, which would then trigger the n900 to establish a data connection to get done what needed to be done.
It is probably a good idea to name it something that is platform agnostic, just to future proof the program. What about something like JabberPush? Is it a bad idea to use the protocol in the name, in case I ever support other protocols too?
I previously tried to use SMS for push, but there is no way to block SMS messages, so they don't get displayed (please correct me if I am wrong though).
cool man, and it would be awesome if it supports facebook pish notifications.
This is definitely a possibility in the future. What sort of notifications would you want? This program is mainly going to notify other programs of new information, such as notifying facebrick that you have new messages, and then let it handle it.
)
