Matthias Endler
Matthias Endler
twitter recently announced "Practical and robust anomaly detection in a time series" (see blog post here: https://blog.twitter.com/2015/introducing-practical-and-robust-anomaly-detection-in-a-time-series) The code is on GitHub: https://github.com/twitter/AnomalyDetection It is written in R, so it's...
In https://github.com/lycheeverse/lychee/issues/733 we've been discussing whether `reqwest-impersonate` could be a solution to getting blocked by various websites. After some testing we found that indeed we would be able to circumvent...
## Summary This adds support for formatting responses in different ways. For now the options are * `plain`: No color, basic formatting * `color`: Color, indented formatting (default) * `emoji`:...
I found it hard to understand whether the train was on time or not, just by taking a quick glance at the program output. The red color would make me...
The sample responses from the official Slack documentation are often invalid JSON. For example, check [files.upload](https://api.slack.com/methods/files.upload) (because of '...') or [im.history](https://api.slack.com/methods/im.history) (because of a trailing comma in the second message)....
Async/await has landed. And with it, there were quite a few changes on the Rust ecosystem. Our lovely dependabot [wanted to update futures to 0.3](https://github.com/hello-rust/hello/pull/20), but it's not that easy....
Right now, only error messages get printed. Would be nice to have a clickable link to a post after a sucessful submission.
I've noticed that some sample responses from the API are invalid JSON. For example, check [files.upload](https://api.slack.com/methods/files.upload) (invalid because of '...') or [im.history](https://api.slack.com/methods/files.upload) (invalid because of a trailing comma in the...
For testing an API client which uses ease, I'd like to mock a server response with some predefined JSON data. For example, each request to http://example.com/endpoint would return ``` json...