Zack Puhl

> It would also be beneficial to include options to block certain bridges. This feature would help those hosting public instances by allowing them to control which bridges are accessible,...

@Dinth The branch from the PR above (#4171) will most likely get you what you're looking for out-of-the-box. Give it a read and see if that's what you'd like to...

> @NotsoanoNimus what happened with the PR? I was just about to clone your repository :( Howdy, sorry about the confusion. If you're looking for this feature, you can pull...

> Actually it would be better to cache the `fetchArticleContent` for more than 1 hour, no idea how to do that. If I'm not mistaken, you should just be able...

@BWindey Thanks for the feedback, and makes sense about the parentheses. ```c macro @echo($message) { $echo $message, "$echo: "; } // ... @echo(@sprintf("Test message on line %s", $$LINE)); ``` ```...

> An alternative is to make it configurable as a build parameter: `--echo-prefix myecho` I think that's a great idea. Would this still work if someone wanted to use a...

> It could I guess, although that is more work. I suppose the original proposal is perhaps a more flexible option (whatever that gains C3). But I'm willing to help...

> I added a simple --echo-prefix build option now. It can definitely be improved on. Currently it supports {FILE} and {LINE} Nice! We can close this in favor of your...

I was of the opinion that it _should not_ be an error, and that the 0-length slice is fine. I will attach our last conversation about this.

I think that's entirely sensible, given the extra complexities that compile-time evaluation can introduce as well as the added sluggishness to `c3c`, which I understand is important to limit carefully....