Fork me on GitHub
#community-development
<
2018-02-12
>
gonewest81806:02:57

by the way, looks like Clojurians hit the free plan’s upload limit again: “Your file was uploaded — it’s safe and sound in Slack. Unfortunately your workspace doesn’t have any storage space left. To get more space, you can upgrade to a paid account or delete some of your older files.”

martinklepsch14:02:25

@gonewest818 thanks for the heads up, I’ll try to clear up space again soon

arrdem16:02:48

@martinklepsch does slack still expose a deletes API? On one of the first slacks I ran we had a script to download archive and delete all the files routinely. I remember Slack changed their API at some point, don't remember details.

martinklepsch16:02:45

Yeah, also have a script slack-prune.rb seems to work still. @seancorfield should we give people another heads up or should I just run it now?

arrdem16:02:09

I'd support going to a general mere days retention policy on files given that we rarely have more than 3d of logs visible. Slack is a transient chat tool not a knowledge base etc

seancorfield18:02:28

@martinklepsch I'd vote for just running it from time to time -- everyone attempting to upload images knows we're "over limit" (although, confusingly, Slack still actually uploads and displays the images -- despite the message!).

martinklepsch18:02:00

got it + seems appropriate to me too

gonewest81819:02:50

does the pruning script know about pinned items?

seancorfield19:02:03

@gonewest818 Unlikely. But the script is pruning files, not messages, and most (nearly all?) pinned items will be messages I think...

seancorfield19:02:32

If you know of any pinned files that you want to keep, go download them and perhaps post them up on ClojureVerse as a permanent home?

gonewest81819:02:59

none for me, just curious.