4 ms·
Very nice, from a quick look this looks closer to my design sketches for an open social network than the earlier contenders. It wasn't entirely clear from a qu
by e12e 14y ago
Very nice, from a quick look this looks closer to my design sketches for an open social network than the earlier contenders.
It wasn't entirely clear from a quick look at the wiki: What is postgresql used for? Metadata on media? How is authentication handled?
Apologies if I overlooked some obvious documentation (I confess I haven't looked at the code).
Are there any good comprehensive design overview documents?
I'd be interested in how much would be needed to (re)implement a stand alone version, running on a single technology for easy low-scale deployment (eg: running xmpp, mediaserver and api(?)-server all on top of nodejs, or via simple go-based servers)?
- imaginator 14y agoPostgreSQL is used for storing channels (users posts, subscriptions, etc.) and metadata on media. Authentication is handled by the XMPP server - Prosody, ejabberd, OpenFire, etc. The XMPP protocol is documented on https://buddycloud.org/wiki/XMPP_XEP https://buddycloud.org/wiki/XMPP_XEP, and the HTTP API on https://buddycloud.org/wiki/Buddycloud_HTTP_API https://buddycloud.org/wiki/Buddycloud_HTTP_API. Right now if you want to use a single technology I think the best would be to use nodejs: the channels server and HTTP API are running on it. The problem will be the XMPP server (I don't think node-xmpp can handle that). The media server is written in Java, so a complete rewrite would be needed (but the media server is optional). And I'd love to see all of that in Go, but last time I checked its XMPP libraries were not usable enough for what we'd need.