DISQUS

Scribkin: What I Need is a Universal Receptor Protocol

  • DuckofDeath87 · 1 year ago
    XMPP. It is all about presence. Couple that with offline message retrieval (XEP-0013) and filetransfers (XEP-0096)
    In theroy, a blog could also have a XMPP account. It could "message" its subscribers. if the server supported it, the server could send one message to a lot of folks.

    My understanding is that it handles meta data well. I have never heard of it being use like this, but I think it could work. Couple it with a completely different GUI than most normal IM clients and you would be in business!

    Best of all, the hard part is already done! There are already xmpp servers running.
    There would still be a lot of work to get what you want, but I feel that your main thing is the push protocol, and XMPP gets that done.
  • Phil Glockner · 1 year ago
    Sweet! In fact, I used to manage an XMPP-enabled server at my last job, a product called CommuniGate Pro (basically an Exchange server clone). We weren't using that part of the software and it wasn't documented well, but definitely supported.

    Thanks for giving me a direction to start looking in. I had completely forgotten about it. I guess that reveals an embarrassing lack of research on my part.
  • DuckofDeath87 · 1 year ago
    I did a little more research. If you can find an XMPP server that supports
    some certain extensions, you would be nearly to your goal of the open
    receptor!

    Namely,
    http://www.xmpp.org/extensions/xep-0060.html
    http://www.xmpp.org/extensions/xep-0049.html
    http://www.xmpp.org/extensions/xep-0002.html
    http://www.xmpp.org/extensions/xep-0030.html

    Some of those sound like it would really help your protocol. Especally that
    subscribe publish one.
  • Phil Glockner · 1 year ago
    Oh man, very cool. I wish I was more of a developer, this is really good stuff. Thanks for digging up the links!