…and it seems to work. Sorry for the 30 minute downtime because of that.
Related Posts:
- Server Specs The Hot-Chilli Instant Messaging service is a node on the open Jabber network, based on XMPP, the open standard for…
- Planned Pubsub/PEP migration to MySQL We are planning to migrate Pubsub/PEP (Publish-Subscribe / Personal Eventing Protocol) from Mnesia to MySQL in the very near future,…
- Jabber/XMPP Privacy Policy The Hot-Chilli team is committed to the privacy and security of your data on our servers. This includes all Internet…
- Moods now also work on secondary domains We stumbled upon this by accident - moods (or to be precise: everything which Pubsub/PEP offer) did not work on…
- Lots of new transport services There was a lot of work lately on our transports. We sent some transports into retirement, some of those transports…
2 replies on “Pubsub/PEP migration to MySQL complete”
Hi,
I am trying to figure out what specs to use for the following:
NS_DATA_FORMS: “jabber:x:data”,
NS_PUBSUB
NS_PUBSUB_OWNER:
NS_PUBSUB_ERRORS:
NS_PUBSUB_NODE_CONFIG:
On the jabber.org server these are usually of the type:
NS_PUBSUB: “http://jabber.org/protocol/pubsub”
Can you please help with the detailed specs on your hot chilli server?
Thanks.
Harsh
Sorry, I am not in the details…
Also we switched from ejabberd to Prosody in the meantime – but I think jabber.org also did. Maybe you need to talk to someone of Prosody in the Prosody channel?