On Wednesday, January 25th, 2023 at 14:59, Stephen Castro-Starkey <stephen@calmabiding.me> wrote:

> Ok, so here’s the build I’m talking about: https://builds.sr.ht/~coreagile/job/928373
> 
> It appears as if the user that runs the build doesn’t have permissions to change the configuration file. It’s likely owned by root.

You'll need to use sudo to write to that file.

Pushed, thanks!

On Monday, January 23rd, 2023 at 21:47, novenary <streetwalkermc@gmail.com> wrote:

> I wonder if the square brackets notation [::1] would make sense here?

No, this would confuse clients which parse the IP and don't expect
square brackets. See:
https://modern.ircdocs.horse/#rplwhoisuser-311

Edited to not mutate the field. Pushed, thanks!

Hi,

On Monday, January 23rd, 2023 at 05:45, Patrick Staight <pstaight@gmail.com> wrote:

> I wanted to inquire about your bandwidth for answering questions
> before I invest a bit of time diving into your code.

Yes, feel free to post questions to this mailing list. I will try to
find time to reply.

For more general IRC-related questions, the #ircdocs and #ircv3 channels
are good places to discuss too.

Simon

Would you be willing to send a patch? e.g. by adding a semicolon after
the case's colon, before the variable declaration.

(Yes, that's an annoying C quirk. Thankfully C23 fixes this.)

Do not commit the surface with the new scale and the old buffer.
Leave it to the next rendering pass to commit the surface.

Fixes the following protocol error:

    wl_surface@10: error 2: Buffer size (717x795) is not divisible by scale (2)

Closes: https://todo.sr.ht/~exec64/imv/20
---
 src/wl_window.c | 2 --
 1 file changed, 2 deletions(-)

diff --git a/src/wl_window.c b/src/wl_window.c
index 5efa42f7d062..0c2221a9b9be 100644
[message trimmed]

On Tuesday, January 17th, 2023 at 04:15, jgart <jgart@dismail.de> wrote:

> Here's a patch for chathistorysync adding info for the user letting them
> know that they have to register for a token with meta.sr.ht scope access.

Thanks for the patch, but I'd rather not add this. The tool has nothing
specific to chat.sr.ht, it's a generic tool which can be used with other
IRC servers.

> Do you happen to know the minimum amount of access granting for meta.sr.ht
> that can be used with chathistorysync?

The docs at [1] have a link with the minimal grants.

Some servers don't comply with RFC 2812 and don't send RPL_ISUPPORT.
Use a legacy default for CHANTYPES in this case.

Modern servers can advertise "CHANTYPES=" (empty value) to indicate
that they don't support channels.
---

I'll wait before applying this patch because:

- It would be nice to get modern-irc updated accordingly.
- soju only sends an empty CHANTYPES since today.

 lib/irc.dart | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
[message trimmed]

On Monday, January 16th, 2023 at 11:54, Lauri Tirkkonen <lauri@hacktheplanet.fi> wrote:

> Out of curiosity, is the current behavior not problematic for
> chat.sr.ht? I would imagine larger deployments would generally not want
> to restart the bouncer :)

chat.sr.ht does not rely on sojuctl to add new users to the bouncer.
This issue only happens when sojuctl is used.

(The plan to fix this mess is to make sojuctl talk to soju instead of
mutating the DB.)