"Laconica is built on PHP/MySQL open source software."
Given all the hullabaloo about twiter scaling, rewrites, etc, I thought it would be clear by now that a database driven website is not a good architecture for twitter-like messaging system.
Given all the hullabaloo about twiter scaling, rewrites, etc, I thought it would be clear by now that a database driven website is not a good architecture for twitter-like messaging system.
Those who don't understand are doomed to re-invent. Poorly.
I'm speaking specifically of "PubSub", where you can publish your updates and they get sent out only to subscribers.
Note that twitter does not otherwise match a conventional IM message, nor does it match a conventional conference room. It does precisely match the PubSub use case, and I still hope to see something based on that. Laconica isn't wrong to ignore it, per se, but they will end up having to do (or have already done) a lot of very, very redundant specification as a result of ignoring it. (I'd think they'd still have been better off taking an existing XMPP server, fixing the pubsub to do what they want, and building from there.)