(#s4btqiq) @xuu Ah! I never did something with SIGQUIT.

(#3syipzq) @xuu Cool! I particularly like the idea of converting it into a `grep`-able version, that's very neat. Interesting choice of aligning the colons at the values and not the keys, I think I never came across this.

(#zwpd7hq) Yeah, the lack of comments makes regular JSON not a good configuration format in my view. Also, putting all keys in quotes and the use of commas is annoying. The big upside is that's in lots of standard libraries. I think the appeal with YAML is that is has comments, is kind of easy to write and read and also provides unlimited nesting levels. But it has all its drawbacks, no question. Forbidding tabs, thousands of different string flavors, having so many boolean options (poor Norwegians) etc. I use it, but I don't particularly enjoy it. Among simple key value pairs, I like INI files, but with `#` for comments, not `;`. I never used TOML, read up on it yesteray before writing this question, but it looks a bit weird and has some strange rules. I guess I have to give it a try one day. And yes, as mentioned by several of you, it always depends on the complexity of the configuration at hand. I'm developing something for the scouts at the moment with rather simple requirements on the config. Currently, there are just four settings. Even INI would be overkill with its section. I selected JSON for now, because that's readily available with Go's std lib. But I do not like it. Btw. what's your own config format, @xuu?

(#yl2illa) @xuu You are absolutely right, that would be terrible. The whole point of Nostr is to own your identity. I don't know what I was thinking.

(#jq2xtea) @xuu I would say yes. Maybe caching related?

(#r4vadlq) @xuu wow, I can tell I am older than you (I already knew this, but still). It was nothing but Pascal for me.

(#3c2i2ia) @xuu These are indeed iterators. Very weird syntax, though.

(#3c2i2ia) @xuu Oh, I wasn't aware of this! Thanks for bringing it to my attention. I do like that they move away from one shared variable per loop to an own one per iteration. That makes sooo much more sense. I don't hit that often, but it happened a few times in the past and getting this figured out is not the easiest thing in the world. I have to read up on the yield functions. From your examples I fear iterators would have been more useful. Let's see.

(#mnpnvda) @xuu This is already supported by Yarn. Perhaps we just need to formalise l it? 🤔

(#mnpnvda) @xuu That's an interesting idea. Twt hashes still need a canonical URL to work, though.