jdev - 2022-08-10

Hey I'm currently on vacations. I have indeed worked on a pubsub based merge request mechanism (see https://www.goffi.org/mr).

It's for Mercurial but I have plans to add git and a gateway for gitlab or github.

Sorry I'm not much available these days to talk about it, I'll check messages later.

Hi goffi. Yes I recall that project. My goal is less ambitious and consists simply of handling `git format-patch` attachments sent to a JID and passing them on via appropriate HTTP API calls to associated GitLab / Gitea repos. The general idea is that this should work from a bog standard no frills client such as Conversations (if you're enough of a masochist to be writing patches on your mobile phone).

Sending patches via PubSub is a cool idea though as effectively that abstracts away the underlying repository host(s) and possibly technology (e.g., Git vs Hg).

speaking of, reviewing patches in email clients is no fun, it'll take a while until I can get around to do that

jonas’: Save the emails as *.eml in the repository's root directory, then `git am -i *.eml`.

that doesn't give me a nice UI where I can attach comments to things I (don't) like ;)

quoted in a reply with in-line comments?

👉 `git send-email`

Of course, you could always commit into a new branch, push that to your favourite forge and add comments in there. Then you get possibly some convenience at the expense of resilience.

How can i create a privat XMPP / Jabber Server?

I'm not an expert, but I guess all you have to do is either: 1) Close its traffic to your domain alome. 2) Set all group chats to private by default.

> How can i create a privat XMPP / Jabber Server? Since this is open for interpretation, please let me ask you what exactly do you mean by private?

I always thought that whitespace wasn't allowed except at the top level between stanzas. Is this true? Gajim appears to send stuff from the XML console with whitespace and I can't find anything that forbids it except a vague implication in https://www.rfc-editor.org/rfc/rfc6120#section-11.7

Sam, did you add the whitespace?

Where, exactly? Between elements in a stanza?

Yes. Eg I thought the XML stream had to look like <message></message> and all tabs and newlines in examples were just for readability

But if I paste an example in gajim I get it sent as is, eg. <message> Foo </message>

I believe it's inherited from the XML specification that whitespace is allowed but usually ignored.

Mostly Harmless :)

Sam, its a xml stream, you read it with an xml parser, which xml parser would fail with your example?

May someone help, blackjack24?

lovetox: it's not really an l stream though, we ignore lots of other things like proc insts. I thought whitespace not at the top level was one of those xmpp oddities

I was parsing stuff using a token stream and it broke because of this. My own fault if it's allowed, I just really thought it wasn't and was trying to figure out if I should "error, invalid whitespace" or just accept it

You've newer seen .. is it Psi and strophe.js that send stanzas with indentation included?

Guess that answers my question either way… have to do it for support regardless

Sam, just for info, the xml console sends everything directly to the stream without processing

you can send everything invalid

There's been the odd bug in a prosody plugin due to code accessing the n'th node instead of the n'th child tag which trips over unexpected text nodes, but that's been pretty rare and we have better APIs for finding the tags you want.

Hmmm, that sounds like potential fun with XEP-0198

hm or maybe im lying, and i parse whatever you put into the console

basically because Link Mauve complained that when he puts something into the xml console, stream management breaks because its not counted

So you already had that fun? :D

yes

i wonder if you can do memory corruption in a XMPP server

I faintly remember that yeah.

techmetx11: in what way? If you could that'd be a critical bug that'd need fixed right away

flow: There is something I don't understand concerning this https://github.com/xsf/xeps/issues/1173#issuecomment-1074060793 Isn't that what `make refs` does?