
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

¯_(ツ)_/¯

can anyone build a slack client?

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

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

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

but it would seem better to me

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

also I actually like that message history is off by default

welp

maybe there really is no issue?


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

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

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

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

oh thats interesting

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

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

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

@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

@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).

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:

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

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

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.

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

(has the IMAP story improved in emacs?)

@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

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

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

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