notjack
2018-3-8 10:59:26

it’s bizarre to me that people put so much emphasis on how slack vs irc is about “open protocols” when slack runs on just as open a protocol as irc does (http) and that choice of protocol is the source of slacks killer feature for me: I don’t have to install, configure, setup, or administer anything whatsoever to use it on my computer, it just works like any other website


notjack
2018-3-8 10:59:46

¯_(ツ)_/¯


joelmccracken
2018-3-8 15:42:44

can anyone build a slack client?


joelmccracken
2018-3-8 15:43:20

(there’s also the lack of history for communities like this one that makes non-paid-slack a PITA)


githree
2018-3-8 15:49:22

I wonder if gitter wouldn’t be a better choice for open source project like racket


joelmccracken
2018-3-8 15:56:37

im not sure how the two match feature-for-feature


joelmccracken
2018-3-8 15:56:46

but it would seem better to me


notjack
2018-3-8 18:54:15

@joelmccracken I don’t see why not, the API lets you read and write messages


notjack
2018-3-8 18:55:17

also I actually like that message history is off by default


joelmccracken
2018-3-8 18:57:36

welp


joelmccracken
2018-3-8 18:58:04

maybe there really is no issue?


joelmccracken
2018-3-8 18:58:23

notjack
2018-3-8 19:04:52

I’d say the issue is way more about the cultures slack and irc each came from as opposed to anything about the tech or protocols


joelmccracken
2018-3-8 19:08:22

I just assumed you couldn’t make a fully-featured client


joelmccracken
2018-3-8 19:08:36

it just reminds me a lot of what twitter did years ago


notjack
2018-3-8 19:09:09

I wonder if you can make a fully-featured server and plug wee-slack into it


joelmccracken
2018-3-8 19:10:31

oh thats interesting


notjack
2018-3-8 19:12:00

I suppose in theory you must be able to right? if the api exposes enough stuff for wee-slack to work, the endpoints must be well spec’d enough that you could make your own implementation of them


joelmccracken
2018-3-8 19:12:31

unless it specifically was designed to not be usable, then idk why you couldn’t


notjack
2018-3-8 19:12:37

I’m wildly speculating though, and far too lazy to actually analyze the docs and find out


zenspider
2018-3-8 20:29:13

@greg have you used the emacs slack client? I haven’t set it up yet. Feel like ERC? I’m quite tired of how much slack eats memory and battery


greg
2018-3-8 20:32:06

@zenspider No I haven’t tried it. I’m actually fine with Slack as a browser tab (not via Electron “native” app). And for something like this Racket group the memory and battery is OK-ish (for me).


greg
2018-3-8 20:33:42

The main thing about Slack I like vs. IRC is the ability to edit messages. If I make a typo I can fix it, instead of typing a Vim command. :slightly_smiling_face:


zenspider
2018-3-8 20:33:51

yeah. I’m using the osx client and electron is certainly the problem.


greg
2018-3-8 20:34:09

See like right there, I typed “live” instead of “like” and I just edited it. :slightly_smiling_face:


greg
2018-3-8 20:36:16

As I mentioned above, I have two main buckets: emacs and browser. That’s it. I like my writing/programming stuff in emacs, and my browsing/communicating stuff in the browser. And I’m happy. That’s just me.


zenspider
2018-3-8 20:43:39

I like to push almost all of that to emacs. I don’t do mail in it anymore because the IMAP support wasn’t there (and mail.app is actually pretty damn good)… but comms + code + shell == emacs for me


zenspider
2018-3-8 20:43:54

(has the IMAP story improved in emacs?)


samth
2018-3-8 21:35:58

@mflatt I don’t know if you get the AppVeyor emails, but currently it has both test failures with unsafe operations and a segfault while running places tests


stamourv
2018-3-8 21:51:34

@zenspider: Been using wanderlust with IMAP for years, and it’s working fine for me.


mflatt
2018-3-9 01:16:06

@samth I didn’t figure out how to subscribe to the AppVeyor results, but I’ve pushed repairs


samth
2018-3-9 02:05:09

@mflatt hooray, it now passes (and I usually track the results using the #notifications channel here)