Thanks Gaston

I created the Pharo Slack's bot for it, but I'm getting a connection
refused error when trying to set up the SlackDigest.com integration.
I'll try later.

Regards!


Esteban A. Maringolo

2015-12-02 11:05 GMT-03:00 Gast��n Dall' Oglio <gaston.dalloglio@gmail.com>:
> Hello.
>
> Just a thought ... There's a automated tool for do that (I have not tried
> yet)
>�� http://slackdigest.com/digest.html
>
> It send a DM to interested users, but maybe using Outgoing WebHooks the DM
> can be forwarded to some service to publish it.
>
>
>
> 2015-11-30 17:47 GMT-03:00 philippe.back@highoctane.be
> <philippe.back@gmail.com>:
>>
>> And I've not been looking at Slack that much.
>>
>> Digest would be we nice indeed.
>>
>> Phil
>>
>> On Nov 30, 2015 4:53 AM, "EuanM" <euanmee@gmail.com> wrote:
>>>
>>> And of course, we can stop doing it manually once threading arrives.
>>>
>>> On 30 November 2015 at 03:52, EuanM <euanmee@gmail.com> wrote:
>>> > I have been talking to the Slack dev team and they assure me that
>>> > threading is on its way - as a priority.
>>> >
>>> > I am happy to manually curate threads if someone gets a 24hour dump to
>>> > log files working.
>>> >
>>> > The best way to do this would be to have teams of curators per
>>> > channel, each doing a little curation periodically on a rota per
>>> > channel basis.
>>> >
>>> > This is an ideal task for people still getting up to speed with Pharo
>>> > internals.�� It is a great way to be exposed to stuff you don't
>>> > understand, and put your mind around it.
>>> >
>>> > This provide a starter slope for future contributors.
>>> >
>>> > On 23 November 2015 at 08:14, Yuriy Tymchuk <yuriy.tymchuk@me.com>
>>> > wrote:
>>> >> The problem is, that it is not that easy to create a ���digest��� from
>>> >> Slack, as there is no kind of grouping. Either you have to detect similar
>>> >> words in discussion, or you have to simply export everything. I don���t know
>>> >> whether it makes sense to just compose a huge email of all discussions, but
>>> >> we can try to do that.
>>> >>
>>> >> Cheers.
>>> >> Uko
>>> >>
>>> >>> On 23 Nov 2015, at 00:21, EuanM <euanmee@gmail.com> wrote:
>>> >>>
>>> >>> I agree - if we can have each 24 hours of chat archived to somewhere
>>> >>> that provides a free-text search, that would be very good.
>>> >>>
>>> >>> Up until now, I've been grabbing, editting and posting chats I find
>>> >>> of
>>> >>> interest and importance to me.�� And it seems to lend itself to design
>>> >>> discussions.�� What it's not very good at, atm, is discussion
>>> >>> threading.�� It would be great to be able to set your typing as
>>> >>> belonging to a thread., so that when it get sucked out and archived
>>> >>> that the threads were segregated.
>>> >>>
>>> >>> Does someone have a server that could receive a text dump of all
>>> >>> recent Slack messages every 12 (or 24, or 6) hours, and then make it
>>> >>> available for indexing by Google et al, and querying (via the search
>>> >>> engines) by our dev base?
>>> >>>
>>> >>>
>>> >>>
>>> >>>
>>> >>>
>>> >>> On 22 November 2015 at 13:57, Dimitris Chloupis
>>> >>> <kilon.alios@gmail.com> wrote:
>>> >>>> Just to clear something up , because I see people in slack saying
>>> >>>> goodbye,
>>> >>>> or "I cant reply right now I have something to do" . Slack is not
>>> >>>> just a
>>> >>>> real time chat, it keeps messages inside a history of 10 thousand
>>> >>>> messages.
>>> >>>> So that means you can log in Slack at any time and not lose a
>>> >>>> message. There
>>> >>>> is no reason for you to be online all time, no reason to say
>>> >>>> goodbye,
>>> >>>> goodmorning , goodafternoon. You can come and go as you please the
>>> >>>> exact
>>> >>>> same way as the mailing list.
>>> >>>>
>>> >>>> The problem arises when we exceed 10k messages, the old ones get
>>> >>>> lost and I
>>> >>>> think having a place to store them is a good idea.
>>> >>>>
>>> >>>> Also what is important is in the eye of the beholder, for example I
>>> >>>> dont
>>> >>>> care about any discussion about web development , its just does not
>>> >>>> interest
>>> >>>> me or database coding or many other things. I have learned to filter
>>> >>>> out the
>>> >>>> messages I dont care about in the mailing list and just reject them.
>>> >>>> Slack
>>> >>>> is same story, I quickly glance through its history and I can search
>>> >>>> the
>>> >>>> messages that interest me using the search bar , I can star messages
>>> >>>> that I
>>> >>>> want to keep, and I can comment on existing messages / code snippets
>>> >>>> which
>>> >>>> create a thread about that message.
>>> >>>>
>>> >>>> In the end its impossible to keep the community in one place but to
>>> >>>> have a
>>> >>>> central hub that collects all the little gems can be quite useful.
>>> >>>>
>>> >>>> On Sun, Nov 22, 2015 at 3:46 PM stepharo <stepharo@free.fr> wrote:
>>> >>>>>
>>> >>>>> Yes this would be good.
>>> >>>>> People should understand that important discussions should be via
>>> >>>>> the
>>> >>>>> mailing-list.
>>> >>>>> Emails are good because you can consume them the way you want.
>>> >>>>> I simply cannot be connected all the time. So emails are good
>>> >>>>> because I
>>> >>>>> can process them
>>> >>>>> when I decide.
>>> >>>>> Slack is good for more interactive session around debugger and
>>> >>>>> things
>>> >>>>> like that.
>>> >>>>>
>>> >>>>> Stef
>>> >>>>>
>>> >>>>>
>>> >>>>> Le 21/11/15 18:05, Stephan Eggermont a ��crit :
>>> >>>>>> Should we have a digest from slack to a mailing list?
>>> >>>>>> We are already losing messages
>>> >>>>>>
>>> >>>>>> Stephan
>>> >>>>>>
>>> >>>>>>
>>> >>>>>>
>>> >>>>>
>>> >>>>>
>>> >>>>
>>> >>>
>>> >>
>>> >>
>>>
>