Fork me on GitHub
#off-topic
<
2015-06-22
>
arrdem03:06:55

Anyone use racket and care to give some getting started pointers?

ambrosebs05:06:40

arrdem: use drracket

ambrosebs05:06:54

arrdem: or where you after something specific?

isauredv14:06:57

Hi Tj!:thumbsup:

joelkuiper18:06:42

Very rough draft of A very short introduction to semantic web https://joelkuiper.eu/semantic-web

joelkuiper18:06:55

I might even be working on a YESQL inspired SPARQL library … 😉

sveri18:06:56

anyone up building a performant slack alternative?

joelkuiper19:06:14

@sveri: I’ve had this idea for a slack focused on content aggregation and sharing, rather than chat

joelkuiper19:06:44

@sveri: sort of like Google Reader/RSS in its good years, but with more “social” bs in it 😛

joelkuiper19:06:16

rebuilding slack shouldn’t be that hard though, you can just use IRC and build a web gui around it 😛

sveri19:06:20

@joelkuiper: I guess it's more the UI and phone integration that attracted so much

sveri19:06:35

plus some useability goodies

joelkuiper19:06:55

yeah, might be an interesting use case to try React Native + ClojureScript for

sveri19:06:38

combined with sente and any storage on the backend

sveri19:06:59

then use phonegap and get phone integration for free

sveri19:06:05

almost 😄

joelkuiper19:06:29

it writes itself 😛

joelkuiper19:06:54

storage would just be IRC and dumping the logs somewhere.

joelkuiper19:06:02

no reason to reinvent a proven piece of tech

sveri20:06:54

joelkuiper: Not sure how one would have a notion of teams in IRC though, something like clojurians->off-topic and someotherteam->off-topic should be possible

joelkuiper20:06:37

well the hacky thing would either be to set up different IRC servers for different teams, or prefix the IRC channels with a non-public ID

joelkuiper20:06:15

or just make channels as uuid’s and fix the mapping somewhere else

sveri20:06:29

joelkuiper: I like the mapping most I guess, prefixing leads to string parsing which is like blaeh 😄 Different servers need some manual handling

sveri20:06:46

Although, using docker one could automate that process and it might scale better simple_smile

joelkuiper20:06:22

it’s not like the initial latency to having a new team is much of a problem

joelkuiper20:06:31

several minutes would still be acceptible

joelkuiper20:06:37

enough to spin up a container of sorts

joelkuiper20:06:58

and IRC servers are relatively light

sveri20:06:01

true, I like that. using an image you can spin up one in like one or two seconds

sveri20:06:11

I think about that some more tonight simple_smile

joelkuiper20:06:27

cool, I’m relatively busy but we can always chat more simple_smile

sveri21:06:01

@joelkuiper: I wonder about things like file support, and, I just thought about jabber, which always supports a wide variety of protocols

sveri21:06:14

maybe that would be the better technology, backendwise

joelkuiper21:06:35

hmm possibly, never really looked into Jabber, but it (c)would make sense

sveri21:06:04

I wonder what slack uses as a backend

sveri21:06:15

jabber offers a lot regarding user handling

joelkuiper21:06:26

maybe a custom thing, dunno what slack uses

arrdem21:06:10

Check out slack's API docs

arrdem21:06:17

they do a pretty good job of dogfooding their message formatting

arrdem21:06:33

and it's a fairly reasonable like six or seven message type JSON encoding as well