Neither is IRC but that has not stopped irc users from creating bots that
keep track of a irc channel's message history in logs that are
automatically uploaded to websites searchable by google. Unlike Slack , IRC
is even worse not even it does not store the last 10k messages , it does
not even store ANY message , yet it's by very far the most popular chat
client for open source projects

Proving that even the worse idea can be turned to the best idea very easily
On Fri, 13 Jan 2017 at 10:18, Sven Van Caekenberghe <s...@stfx.eu> wrote:

> so it is not a good idea for an open source project, as I feared.
>
> > On 13 Jan 2017, at 09:15, Dimitris Chloupis <kilon.al...@gmail.com>
> wrote:
> >
> > It eventually disappears , it keep the last 10.000 messages
> >
> > No it's not publicly visible   quite the contrary , Slack prioritize
> privacy because it's meant to be used by teams working on commercial
> projects which are the ones more likely to pay for a slack subscription.
> >
> > If you want to search as a teams's history you need to gain access as a
> guest or a member , in both cases you will need an invite. So it makes
> little sense for Slack to give Google Acess to its teams history.
> >
> > If you as a team want to have unlimited messages then you will need to
> pay for the Slack subscription.
> >
> > Of course none can stop us from creating a bot that will copy the
> messages to an HTML website , that Google can search, hence lifting the 10k
> limit as well. Or even better commit those messages to a github repo that
> can be loaded as a project inside a Pharo image
> > On Fri, 13 Jan 2017 at 10:05, Sven Van Caekenberghe <s...@stfx.eu>
> wrote:
> > so it is not publicly available/visible/indexable ?
> >
> > so everything written there basically disappears ?
> >
> >
> >
> > > On 13 Jan 2017, at 09:01, Dimitris Chloupis <kilon.al...@gmail.com>
> wrote:
> >
> > >
> >
> > > Slack encrypts the message history and it only stores 10.000 messages
> >
> > >
> >
> > > You could use the Slack search feature
> >
> > >
> >
> > >
> https://get.slack.help/hc/en-us/articles/202528808-Search-for-messages-and-files
> >
> > >
> >
> > > On Fri, 13 Jan 2017 at 08:40, Sven Van Caekenberghe <s...@stfx.eu>
> wrote:
> >
> > > and slack is closed, right ?
> >
> > >
> >
> > >
> >
> > >
> >
> > > > On 13 Jan 2017, at 01:36, Dimitris Chloupis <kilon.al...@gmail.com>
> wrote:
> >
> > >
> >
> > > >
> >
> > >
> >
> > > > Google already is capable on focusing on Pharo related websites.
> >
> > >
> >
> > > >
> >
> > >
> >
> > > > The core of our documentation is located on 3 websites
> >
> > >
> >
> > > >
> >
> > >
> >
> > > > World.st , this sites includes a forum website for all the Smalltalk
> related mailing lists
> >
> > >
> >
> > > > Stackoverflow, Pharo has its own tag and a ton of answered questions
> >
> > >
> >
> > > > Github.com, here are located all the Pharo books
> >
> > >
> >
> > > >
> >
> > >
> >
> > > > So to search all documentation about Spec on only these 3 websites
> you use the following search query
> >
> > >
> >
> > > >
> >
> > >
> >
> > > > pharo spec site:world.st OR site:stackoverflow.com OR site:
> github.com
> >
> > >
> >
> > > >
> >
> > >
> >
> > > > There are other ways to customize a google search query , please
> look at google search documentation
> >
> > >
> >
> > > > On Thu, 12 Jan 2017 at 11:38, Siemen Baader <siemenbaa...@gmail.com>
> wrote:
> >
> > >
> >
> > > > Has anybody looked into SEO'ing any of the great documentation and
> archived questions on the mailing list?
> >
> > >
> >
> > > >
> >
> > >
> >
> > > > It strikes me that I often can't find the answer to questions I have
> on Google, but they are often answered in material that I can find when I
> look manually for some time or am pointed at it by an experienced member of
> the community.
> >
> > >
> >
> > > >
> >
> > >
> >
> > > > I also  miss Pharo - content on Stackoverflow, it is a very
> efficient way to get past road blocks quickly.
> >
> > >
> >
> > > >
> >
> > >
> >
> > > > Any thoughts or history to bring me up to speed with?
> >
> > >
> >
> > > >
> >
> > >
> >
> > > > cheers,
> >
> > >
> >
> > > > Siemen
> >
> > >
> >
> > >
> >
> > >
> >
> > >
> >
> > >
> >
> >
> >
> >
> >
>
>
>

Reply via email to