-
-
Notifications
You must be signed in to change notification settings - Fork 102
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
slackarchive.io isn't up to date #312
Comments
I've pinged their support as I've forgotten where to go to fix this. |
I've added the slackarchive bot to #general so hopefully when @karianna gets it back up and running we should start getting an archive of #general. |
Apparently @gdams support is more responsive than the official one, I've pinged them again |
@karianna Any progress on this? Still no archiving of the |
Yeah I've pinged them again, annoyingly no response and they've taken another year's payment! |
They're dropping the service - we may have to host our own based off https://github.com/AdoptOpenJDK/slackarchive |
From slackarchive: Hi, What will be the easiest is to work with the SlackArchive Importer to import an exported archive from Slack. Remco |
I'm not sure if hosting this ourselves is a good idea... I imagine that we are going to require a huge amount of disk space to store the full archive |
It's text, I suspect it'll be tiny.
Cheers,
Martijn
…On 3 May 2018 at 12:37, George Adams ***@***.***> wrote:
I'm not sure if hosting this ourselves is a good idea... I imagine that we
are going to require a huge amount of disk space to store the full archive
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#312 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AALCaD7mBOSqRIVlN4aLqvJ1Tmc0j-gKks5tuuwIgaJpZM4StyOR>
.
|
We've got a paid slack instance now so have the history back - closing |
It looks like it stopped working on the 11th January. It also doesn't appear to have been tracking #general and really needs to now that we shut down #getopenjdk earlier this week.
The text was updated successfully, but these errors were encountered: