This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-04-27
Channels
- # announcements (9)
- # aws (1)
- # aws-lambda (12)
- # babashka (18)
- # beginners (37)
- # calva (27)
- # clerk (15)
- # clojure (16)
- # clojure-conj (13)
- # clojure-europe (44)
- # clojure-germany (3)
- # clojure-norway (27)
- # clojure-uk (1)
- # cursive (6)
- # data-science (24)
- # datahike (7)
- # datomic (40)
- # fulcro (5)
- # hoplon (33)
- # hyperfiddle (9)
- # introduce-yourself (6)
- # jobs (1)
- # lsp (22)
- # nbb (2)
- # off-topic (15)
- # pathom (37)
- # pedestal (3)
- # polylith (7)
- # portal (1)
- # re-frame (7)
- # releases (1)
- # remote-jobs (1)
- # rewrite-clj (6)
- # sci (1)
- # scittle (1)
- # xtdb (7)
Yes, today and hopefully tomorrow too
Good morning!
månmån
if I needed to create some locally unique ids based off of existing ids that I didn't want to keep, do you think hash (https://clojuredocs.org/clojure.core/hash) would work or should I go to MD5 or SHA1?
My ids are all around 10 characters long, but I'd like the further pseudonymise them. (part of an overall defense in depth on the data, including, keeping it safe from leaking)
I use https://cljdoc.org/d/io.github.nextjournal/valuehash/0.1.10/doc/readme as a generic hashing library. But if your ids are all strings then clojure.core/hash should work just fine.
https://clojurians.slack.com/archives/C03S1KBA2/p1644083293795019 hash is not guaranteed to be stable across restarts
doesn't matter that much, we have lots of great open source alternatives anyway. It's so strange to me why they didn't just open source it.
It's not easy to open source something after the fact. (Disclaimer: not in the product team, so I'm making general claims here)
It will open up some business models (eg third-party hosting) that were not possible before this announcement.
Interesting. I did not think of that.
I started something a long time ago which fell over due to the licensing so it’s relatable although tbh a bit passé personally
@U054UD60U How, though? I guess it could be an issue if it relies on a highly proprietary library or something, but what else?
I have not idea, but it could contain licensed interlectual properties or the source contains some company secrets you'd like to redact first etc. It's just more complicated than switching a github repo to "public" :)
I'm interested in seeing the code from several perspectives One is writing a distributed system The other is writing a database (and datalog implementation) And I'm really curious to see a full on system developed by Rich, because it's probably the way he intended the language to be used. Could learn something 🙃
I'd expect a lot of transducers 😉