This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-06-16
Channels
- # arachne (1)
- # beginners (27)
- # boot (17)
- # cider (10)
- # cljs-dev (5)
- # cljsrn (76)
- # clojure (59)
- # clojure-austin (2)
- # clojure-brasil (1)
- # clojure-greece (76)
- # clojure-mexico (1)
- # clojure-quebec (63)
- # clojure-russia (16)
- # clojure-spec (127)
- # clojure-uk (12)
- # clojurescript (72)
- # community-development (7)
- # core-async (3)
- # core-matrix (2)
- # cursive (13)
- # datomic (8)
- # emacs (4)
- # funcool (4)
- # hoplon (148)
- # immutant (5)
- # keechma (2)
- # lambdaisland (5)
- # lein-figwheel (15)
- # leiningen (20)
- # off-topic (23)
- # om (13)
- # om-next (19)
- # onyx (11)
- # planck (11)
- # re-frame (59)
- # reagent (14)
- # rum (34)
- # specter (30)
- # spirituality-ethics (16)
- # uncomplicate (5)
- # untangled (387)
- # yada (2)
There's also a homeserver being written in rust: https://www.ruma.io
I wonder if it will use the same database format, so that we could start with synapse, and switch to ruma later.
> I'd say it's influenced by synapse's schema, but not aiming for direct compability BUT: > but I imagine it will be a common use case that people will want to migrate from synapse > I think that would make sense as a separate tool that does only that conversion, as erik says
So yeah. We can stick beefy python synapse on a server. Then go to lean and cool ruma when it is finished.
@dominicm: let me know if you end up setting up a synapse
@martinklepsch: Will do.