This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-08-30
Channels
- # announcements (3)
- # asami (20)
- # babashka (15)
- # beginners (47)
- # biff (25)
- # calva (11)
- # catalyst (2)
- # cider (11)
- # clojure (24)
- # clojure-brasil (3)
- # clojure-europe (21)
- # clojure-norway (34)
- # clojure-uk (2)
- # clojurescript (9)
- # clr (2)
- # datomic (10)
- # fulcro (14)
- # hyperfiddle (58)
- # introduce-yourself (1)
- # jobs (3)
- # malli (5)
- # meander (6)
- # missionary (4)
- # nbb (30)
- # off-topic (6)
- # podcasts-discuss (1)
- # shadow-cljs (13)
- # slack-help (5)
- # tools-build (4)
- # vim (20)
- # xtdb (20)
Confidentiality That’s the sound of a can of worms being opened. There may be no end to this issue. It’s massive for me and for my clients. Immeasurable really. For me Do I open source my code? For my clients How do I make sure they have a safe space in which to work? There’s lots of overlap in these questions.
For #1: I don’t have to think about it until I have something useful to share. Life is indeed a platform — and it needs a lot of exercise before it’s generally useful. For #2: At the moment, I don’t know. Attorney-Client privilege is likely as good as it gets for confidentiality. I’ve been imagining dongles for encryption/local store and and and. What I do know is that people can’t do the internal courtyard work if they spend all their time and energy walking the castle walls, peeping through the crenellations.