notify.io prototype

[Jeff Lindsay]

Finally got it online and working in a production-esque environment ... the long-polling stuff is interesting behind a proxy because you need to up read/send timeouts or it stops working. ANYWAY:

http://notify.io

There you can sign in with Google, download the prototype client in Python (has some dependencies). Run the client and then use the debug form to send notifications. The API is mostly there, the history doesn't quite work right, there isn't any enforcement of api_keys and accepting new notifications from sources. But the core pretty much works: running the client, POST to a URL and you get a local Growl.

I have a designer also working on a design for it. Will share more when there is more. Let me know if you get it working!

--
Jeff Lindsay
http://webhooks.org -- Make the web more programmable
http://shdh.org -- A party for hackers and thinkers
http://tigdb.com -- Discover indie games
http://progrium.com -- More interesting things

[Brian Dunnington]

nice. since i dont have a Mac, here is a super simple example of using
GNTP (Growl for Windows) instead of Growl/Mac. (just replace the [YOUR
KEY HERE] part with the appropriate value. here is a screenshot of it
in action.

(this is my first ever attempt at writing any Python code, so dont
laugh at it too much. i basically just took the simply Python client
that is downloadable from notify.io and swapped out the GrowlNotifier
stuff with the GNTP stuff from here: http://github.com/kfdm/gntp )

[Jeff Lindsay]

Hah, nice! The goal is to not need a client, or rather, make each
notifier the client. Right now we're working on growl/mac, but I think
the growl/win developer is on here, so maybe we'll see direct support
there too.

On Thursday, October 8, 2009, Brian Dunnington

[Brian Dunnington]

> ...I think the growl/win developer is on here, so maybe we'll see direct support
> there too.

i know he is one here for sure - because he is me =)

i realize that the end goal is to not need a client at all, but this
lets me try out notify.io right now (just like the sample python
script does for Growl/Mac users).

when the API is stable and documented, it would be pretty easy to add
support to GfW. it already supports the concept of 'subscribing' to
notifications, so these would just be another source to subscribe to.

[briandunnington]

i know you said that not everything is quite working yet, you didnt
specifically mention if the 'Sender Settings' should be working or
not? when filling out the sender fields, the Save button doesnt do
anything.

i wanted to try out sending notifications from another source other
than the Debug test form at notify.io. you mentioned that the API was
'mostly there' - is there any documentation on what the urls/
parameters are?

i would like to dig into building support into Growl for Windows, so
any info you can provide would be most helpful. thanks.

[Jeff Lindsay]

The sender stuff isn't there, so it doesn't care who the source is (api keys are meaningless atm). I just got back from a trip, so I'll prob get this in this week. For now, you can send notifications with:

POST api.notify.io/notify?hash=(hash)

Pass the post params for the various fields in the eventual JSON object to the client.

Just FYI, the ideal endpoint will look like this:

POST api.notify.io/v1/notify/(hash)?api_key=(key)

[Brian Dunnington]

thanks for the info.

i wrote a quick client in C# to listen for messages so that i could
drop it into Growl for Windows to support notify.io once the API is
finalized. i am about to release a new version of Growl for Windows
(v2.0), so the notify.io support can easily go out in v2.next.

[Jeff Lindsay]

Sweet! I'll keep everybody posted.

[Abi Raja]

Hey guys,

Sorry for the late response. School's been keeping me busy...

This is great stuff! It would be awesome if it was integrated into GFW. 

Jeff, is the source for the website online? Are you using Google App Engine? I have some time to hack on it. Which part needs to be worked on?

- Abi

2009/10/13 Jeff Lindsay <prog...@gmail.com>

[Jeff Lindsay]

http://github.com/progrium/notify-io

Just pushed an update tonight that prevents notifications from arbitrary sources unless approved. Next steps would be to handle replaying notifications missed once approved (prob just the first one and/or link to the log for the rest) and sending an email for approvals.

Next things on the todo basically just include starting to make it look better (full design coming soon by friend), write better docs, build some example apps, and that's about it.

For Brian, the API is ready to use now as previously described:
POST api.notify.io/v1/notify/(hash)?api_key=(key)

-jeff

[Brian Dunnington]

Thanks for the update, Jeff. I noticed the urls had changed yesterday,
so i updated my test client and everything looks to be working again.

I also started work on a Wave robot that you can add to your Wave's
that monitors the conversation and sends appropriate notifications to
notify.io. it only works with my own notify.io account/email address
at the moment, but i will open it to all addresses once i finish
making sure the rough edges are cleaned up.

[Jeff Lindsay]

That's really cool! I'd love to include it in the set of examples I want to have available.