Rustam

Thanks for the update, @csaket - did you use the "standard" format or "mattermost" with the slack_viewer?

@OevreFlataeker thanks for the feedback, I'll see what I can do. I just want to mention that export files are already FULL, if you enable file download, all files are...

Hey @yoshimotomasahir thanks for the feedback :) It looks like yet another edge case when API returns something that is not expected by slack library. I have prepared the tool...

@yoshimotomasahir Thanks for the file that you shared. I got some good news! I was able to reproduce the issue, will bee looking into fixing it.

The issue is with this block: ``` { "type": "date", "timestamp": 1636961629, "format": "{date_long} {time_secs}" }, ``` ~Block type "date" is not currently supported by upstream library. These are the...

@yoshimotomasahir It's quite possible that the bot that sent that message with the invalid type of the timestamp is serialising the timestamp incorrectly as an integer. I have raised the...

Hey @jagarop, I'm trying to reproduce this, as my test workspace is on free account, I'm not able to invite guests, but I have one workspace where I have a...

So I investigated quite a bit on this - the Slack Client calls a set of undocumented Slack edge APIs in order to retrieve the names of the users. I'm...

Possibly `JSONTime` will do the trick? (an additional branch for when input is a number would be needed)

Hey team, any chance this can be looked at?