Dmitry Verkhoturov

Now it's up to @akellbl4 (or someone else familiar with the frontend) to implement the frontend part of the Telegram notifications.

@umputun I wonder how the problem statement looks at this moment and what is left to be done then? Quite a lot of things changed since that issue was created.

I thought one should use [mattn/goveralls](https://github.com/mattn/goveralls) in order to upload Go coverage data. [Here](https://github.com/umputun/remark/blob/master/.github/workflows/ci-build.yml#L52-L64) is an example of how to do that within GitHub actions.

The project would benefit greatly from an examples folder with different scenarios like big file upload or [examples per package](https://blog.golang.org/examples) to be available in the module [documentation](https://pkg.go.dev/github.com/gotd/td/telegram/uploader).

If someone figures out how to properly request currently working Twitter auth, please update https://github.com/go-pkgz/auth#twitter-auth-provider and https://github.com/umputun/remark42/blob/master/site/src/docs/configuration/authorization/index.md#twitter

Same for me, Nginx with `proxy_pass` proxies requests to backend: ``` $ fgrep stats_json /var/log/apache2/ -r | tail -1 /var/log/apache2/error.log:2020/09/14 19:41:00 [error] 28066#28066: *9111 open() "/etc/nginx/html/ngx_pagespeed_global_statistics/stats_json" failed (2: No such...

That's a shallow workaround IMHO. I think, the proper solution is following: ``` # to prevent pagespeed from rewriting https to http pagespeed MapRewriteDomain https://example.com http://example.com; pagespeed MapOriginDomain https://example.com http://example.com;...

Seems like everyone affected by it, it's kind of annoying.

I've checked, problem still present in latest ios app update.

It's counter-intuitive, makes simple timer too smart in my opinion.