~emersion

France

https://emersion.fr

I'm Simon Ser, I write open-source software.

Trackers

~emersion/goguma

Last active a day ago

~emersion/tlstunnel

Last active 3 days ago

~emersion/soju

Last active 3 days ago

~emersion/hottub

Last active 4 days ago

~emersion/kanshi

Last active 6 days ago

~emersion/sinwon

Last active 7 days ago

~emersion/hut

Last active 7 days ago

~emersion/grim

Last active 11 days ago

~emersion/pyonji

Last active a month ago

~emersion/sr.ht-container-compose

Last active a month ago
View more

#146 iOS: Scrolling in the buffer should folder keyboard a day ago

Comment by ~emersion on ~emersion/goguma

Also as another data point none of the other IM apps seem to have this behavior (at least on Android).

#146 iOS: Scrolling in the buffer should folder keyboard a day ago

Comment by ~emersion on ~emersion/goguma

I have a patch for this (https://paste.sr.ht/~emersion/93954fdacd553cbf98082e74eb1b3b8f830bf35c) however I'm having second thoughts about doing this when the composer text field is not empty. Hiding the keyboard can be undesirable when in the middle of writing a message and peeking at a partially obscured message.

#27 failed to start listener: listen tcp :443: bind: address already in use 3 days ago

bug added by ~emersion on ~emersion/tlstunnel

#27 failed to start listener: listen tcp :443: bind: address already in use 3 days ago

Ticket created by ~emersion on ~emersion/tlstunnel

Seems like certmagic might be starting a TLS listener behind our back…?

Mar 01 12:00:37 sheeta tlstunnel[368]: 2024/03/01 12:00:37 failed to start listener: listen tcp :443: bind: address already in use
Mar 01 12:00:37 sheeta tlstunnel[368]: 2024/03/01 12:00:37 [ERROR] TLS-ALPN challenge server: handshake: tls: client requested unsupported application protocols ([http/1.1])
Mar 01 12:00:37 sheeta tlstunnel[368]: 2024/03/01 12:00:37 [ERROR] TLS-ALPN challenge server: handshake: tls: client requested unsupported application protocols ([http/1.1])
Mar 01 12:00:37 sheeta tlstunnel[368]: 2024/03/01 12:00:37 [ERROR] TLS-ALPN challenge server: handshake: tls: client requested unsupported application protocols ([http/1.1])
Mar 01 12:00:37 sheeta tlstunnel[368]: 2024/03/01 12:00:37 [ERROR] TLS-ALPN challenge server: handshake: tls: client requested unsupported application protocols ([http/1.1])
Mar 01 12:00:36 sheeta tlstunnel[368]: 2024/03/01 12:00:36 [ERROR] TLS-ALPN challenge server: handshake: tls: client requested unsupported application protocols ([http/1.1])
Mar 01 12:00:36 sheeta tlstunnel[368]: 2024-03-01T12:00:36.781+0100        INFO        acme_client        trying to solve challenge        {"identifier": "[...]", "challenge_type": "tls-alpn-01", "ca": "https://acme>
Mar 01 12:00:36 sheeta tlstunnel[368]: 2024-03-01T12:00:36.766+0100        INFO        acme_client        trying to solve challenge        {"identifier": "[...]", "challenge_type": "tls-alpn-01", "ca": "https://acme-v02.api.letsencrypt.o>
Mar 01 12:00:35 sheeta tlstunnel[368]: 2024-03-01T12:00:35.856+0100        INFO        done waiting on internal rate limiter        {"identifiers": ["[...]"], "ca": "https://acme-v02.api.letsencrypt.org/directory", "account": ""}
Mar 01 12:00:35 sheeta tlstunnel[368]: 2024-03-01T12:00:35.856+0100        INFO        waiting on internal rate limiter        {"identifiers": ["[...]"], "ca": "https://acme-v02.api.letsencrypt.org/directory", "account": ""}
Mar 01 12:00:35 sheeta tlstunnel[368]: 2024-03-01T12:00:35.855+0100        INFO        renew        renewing certificate        {"identifier": "[...]", "remaining": "-1034h54m38.855349326s"}
Mar 01 12:00:35 sheeta tlstunnel[368]: 2024-03-01T12:00:35.854+0100        INFO        renew        lock acquired        {"identifier": "[...]"}
Mar 01 12:00:35 sheeta tlstunnel[368]: 2024/03/01 12:00:35 [INFO][FileStorage:/var/lib/tlstunnel] Lock for 'issue_cert_[...]' is stale (created: 2024-02-24 12:51:53.205836 +0100 CET, last update: 2024-03-01 12:00:19.654157444 +0100 CET);>
Mar 01 12:00:35 sheeta tlstunnel[368]: 2024-03-01T12:00:35.853+0100        INFO        renew        acquiring lock        {"identifier": "[...]"}
Mar 01 12:00:35 sheeta tlstunnel[368]: 2024-03-01T12:00:35.852+0100        WARN        stapling OCSP        {"error": "no OCSP stapling for [[...]]: parsing OCSP response: ocsp: error from server: unauthorized", "identifiers": ["[...]">
Mar 01 12:00:35 sheeta tlstunnel[368]: 2024-03-01T12:00:35.695+0100        INFO        done waiting on internal rate limiter        {"identifiers": ["[...]"], "ca": "https://acme-v02.api.letsencrypt.org/directory", >
Mar 01 12:00:35 sheeta tlstunnel[368]: 2024-03-01T12:00:35.695+0100        INFO        waiting on internal rate limiter        {"identifiers": ["[...]"], "ca": "https://acme-v02.api.letsencrypt.org/directory", "acco>
Mar 01 12:00:35 sheeta tlstunnel[368]: 2024-03-01T12:00:35.694+0100        INFO        renew        renewing certificate        {"identifier": "[...]", "remaining": "-1055h4m36.694470626s"}
Mar 01 12:00:35 sheeta tlstunnel[368]: 2024-03-01T12:00:35.694+0100        INFO        renew        lock acquired        {"identifier": "[...]"}
Mar 01 12:00:35 sheeta tlstunnel[368]: 2024/03/01 12:00:35 [INFO][FileStorage:/var/lib/tlstunnel] Lock for 'issue_cert_[...]' is stale (created: 2024-02-24 12:51:53.205849916 +0100 CET, last update: 2024-03-01 12:00>
Mar 01 12:00:35 sheeta tlstunnel[368]: 2024-03-01T12:00:35.692+0100        INFO        renew        acquiring lock        {"identifier": "[...]"}
Mar 01 12:00:35 sheeta tlstunnel[368]: 2024-03-01T12:00:35.690+0100        WARN        stapling OCSP        {"error": "no OCSP stapling for [[...]]: parsing OCSP response: ocsp: error from server: unauthorized", "id>
Mar 01 12:00:34 sheeta tlstunnel[368]: 1.7092908349255881e+09        info        maintenance        started background certificate maintenance        {"cache": "0xc00007e000"}
Mar 01 12:00:34 sheeta systemd[1]: Started tlstunnel reverse proxy.

#228 fileupload: redact uploader username from public URL 3 days ago

enhancement added by ~emersion on ~emersion/soju

#228 fileupload: redact uploader username from public URL 3 days ago

Ticket created by ~emersion on ~emersion/soju

Don't include the soju username in file upload URLs. Use a different, opaque user identifier instead.

#8 Wrong redirection for GH repos belonging to organisation 4 days ago

Comment by ~emersion on ~emersion/hottub

Duplicate of #4.

REPORTED RESOLVED DUPLICATE

#4 GitHub installation settings link gives 404 for orgs 4 days ago

Comment by ~emersion on ~emersion/hottub

Seems like this doesn't work as expected.

RESOLVED CLOSED REPORTED

#107 Random Crashes 6 days ago

Comment by ~emersion on ~emersion/kanshi

Can you share a WAYLAND_DEBUG=1 log of kanshi?

#24 Add options for customization 7 days ago

Comment by ~emersion on ~emersion/sinwon

Simon Ser referenced this ticket in commit 3118ac0.