This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-01-17
Channels
- # admin-announcements (4)
- # aws (26)
- # beginners (88)
- # boot (132)
- # cljs-dev (4)
- # cljsrn (35)
- # clojars (11)
- # clojure (41)
- # clojure-art (33)
- # clojure-austin (1)
- # clojure-chicago (4)
- # clojure-dev (3)
- # clojure-russia (2)
- # clojured (3)
- # clojurescript (9)
- # community-development (19)
- # datomic (34)
- # devcards (2)
- # editors-rus (4)
- # hoplon (29)
- # leiningen (4)
- # music (2)
- # off-topic (21)
- # om (69)
- # other-lisps (1)
- # perun (6)
- # re-frame (1)
- # reagent (9)
- # spacemacs (3)
- # yada (13)
https://discourse.mozilla-community.org/t/matrix-and-irc-mozillians-custom-client/2911
@martinklepsch: That’s a very interesting link, lots of good stuff in there (like: https://discourse.mozilla-community.org/t/matrix-and-irc-mozillians-custom-client/2911/6)
But yeah, they seem quite interested in Matrix. They want a shiny UI to slap on IRC. And I think that Matrix seems to fit the bill for them.
In #C053K90BR we are pushing the idea of having a set of "identifiable" Clojure devs, using https://keybase.io as a way to do it. Basically the problem stems from the fact that @micha wanted to have verifiable and signed artifact (as you never know the authenticity of what you are downloading)
and it is a sacrosanct (we say in my country) need, that is why #C053K90BR will probably integrate something like that, but ok, @micha can explain it better to who is interested in pitching in ideas/contributions
To associate an identity behind a signing key so that we can trust it