TimWolla

12 ms·

1. 151.▲
   by TimWolla 7y ago

   The 'Y' is mentioned in this blog post: https://lars.ingebrigtsen.no/2016/09/06/gmane-alive/
2. 152.▲
   Haproxy-2.1.0(mail-archive.com)

   37 points by TimWolla 7y ago|6 comments
3. 153.▲
   by TimWolla 7y ago

   I can second Hetzner. In my case with their dedicated offering, though. Been running mail servers there since at least 2013 with next to no problems. Google sometimes put mails into the spam folder, though not in recent times. Microsoft ten
4. 154.▲
   by TimWolla 7y ago

   > I believe most clients renew certs ~10 days in advance. The recommendation and the time certbot uses is 30 days.
5. 155.▲
   Docker 19.03.0(docs.docker.com)

   3 points by TimWolla 7y ago|0 comments
6. 156.▲
   by TimWolla 7y ago

   Yes, exactly. Here's an example for a repository hosted on my server and in Keybase Git. Pulls / Fetches will use the repository on my server. Pushes go to both. [timwolla@/s/xxx (master)]g remote show origin *
7. 157.▲
   by TimWolla 7y ago

   Tags are going to be ugly, but branches can simply be merged like any other. Alternatively you decide the one of the repositories is the primary one, set up a remote called `mirror` and set-up a `post-receive` hook to: git push --mirr
8. 158.▲
   by TimWolla 7y ago

   You mean like? git remote set-url --add --push origin git@github.com:Foo/bar.git git remote set-url --add --push origin git@gitlab.com:Foo/bar.git :-) see: https://git-scm.com/docs/git-remote#Docu
9. 159.▲
   by TimWolla 7y ago

   I already noticed that after the workspace selector looked different Slack was no longer being regularly killed by the OOM killer. Finally.
10. 160.▲
    by TimWolla 7y ago

    see: https://news.ycombinator.com/item?id=20499070 and https://news.ycombinator.com/item?id=20498983
11. 161.▲
    by TimWolla 7y ago

    see also: https://news.ycombinator.com/item?id=20498983
12. 162.▲
    by TimWolla 7y ago

    see: https://news.ycombinator.com/item?id=20499070 and https://news.ycombinator.com/item?id=20498983
13. 163.▲
    by TimWolla 7y ago

    Or the status is automatically being updated once a certain percentage of requests fail in e.g. the last 5 minutes, thus introducing a bit of delay.
14. 164.▲
    by TimWolla 7y ago

    Not all repositories / profiles are affected for me. And for repositories not all pages are affected. e.g. https://github.com/typeorm/typeorm/ is accessible, but the commit list at https://github.c
15. 165.▲
    by TimWolla 7y ago

    GitHub is sending 500's on repositories and user profiles as well: https://github.com/DefinitelyTyped/DefinitelyTyped / https://github.com/TimWolla
16. 166.▲
    by TimWolla 7y ago

    > in which case is there your own registry where you maintain docker images ? Please note that I'm a community contributor. I am not employed by HAProxy Technologies and I cannot speak for the open source project in any official ca
17. 167.▲
    by TimWolla 7y ago

    You probably remember the nbproc [1] setting which indeed is multiple, unrelated processes. There's proper threading now (since 1.8). [1] http://cbonte.github.io/haproxy-dconv/2.0/configuration.html...
18. 168.▲
    by TimWolla 7y ago

    > As of RIGHT NOW, haproxy has not updated it's official docker image and has 6 day old docker images which docker hub flags as having vulnerabilities (screenshot at https://imgur.com/a/SiYoZzc ). So I'm a
19. 169.▲
    by TimWolla 7y ago

    Apart from a few new warnings for long-deprecated options it is compatible. HAProxy 2.0 is not a major version. Willy apparently just dislikes two-digit versions in the second place.
20. 170.▲
    by TimWolla 7y ago

    For me it's the superior HTTP / header rewriting capabilities. With nginx you are more or less restricted to just adding headers the last time I looked into it. Disclosure: I'm a community contributor to HAProxy and I help
21. 171.▲
    CVE-2019-10149 Exim 4.87 to 4.91(exim.org)

    2 points by TimWolla 7y ago|1 comments
22. 172.▲
    by TimWolla 7y ago

    It does not only scan 3000. From the source code: const portsToTry = [ 80, 81, 88, 3000, 3001, 3030, 3031, 3333, 4000, 4001, 4040, 4041, 4444, 5000, 5001, 5050, 5051, 5555, 6000, 6001, 6060, 6
23. 173.▲
    Nginx-1.16.0 stable version has been released(nginx.org)

    3 points by TimWolla 7y ago|0 comments
24. 174.▲
    The text of Article 13 and the EU Copyright Directive has been finalised(juliareda.eu)

    354 points by TimWolla 8y ago|215 comments
25. 175.▲
    About Git tags (2017)(stefanchrist.eu)

    2 points by TimWolla 8y ago|0 comments
26. 176.▲
    Updated Debian 9: 9.7 released(debian.org)

    56 points by TimWolla 8y ago|30 comments
27. 177.▲
    by TimWolla 8y ago

    systemd is not a syslog daemon either. systemd-journald is.
28. 178.▲
    Haproxy-1.8.17 – Fixing CVE-2018-20615(mail-archive.com)

    2 points by TimWolla 8y ago|0 comments
29. 179.▲
    by TimWolla 8y ago

    I believe this is going to be fixed with Threema Safe: https://threema.ch/en/blog/posts/threema-safe-en . It is already rolled out for Android and iOS should be soon according to the blog.
30. 180.▲
    by TimWolla 8y ago

    Google for "Telegram Security" or "Telegram Moxie" to see why Telegram / mtproto might not be the best choice. This is repeatedly the topic on Hacker News as well.