Ben Pate

Yes. This is the best way to handle this. **It should be a custom conversion.**

Try `_hyperscript.processNode(theNewElement)` -- it's a part of the public API, but it's not conveniently documented. That should let hyperscript know about your new elements

This would be helpful, but it also starts down the road of replicating a lot of what htmx already does. This might be a good thing, but it would also...

It's *super* easy to make your own conversions. [Here's an example](https://github.com/whisperverse/whisperverse/blob/master/_static/extensions.js) that I made for another project. You might just make it and then publish it. We're still talking about...

Absolutely. And, sorry I haven't been able to make much headway on this recently. The short answer is that it's probably something with the headers being sent -- the extension...

Thanks for this report. Long-term, I think we'll need another way of handling preloads. For now, does the `Vary` header work for you?

Sorry you're having trouble, @onemoreahmad. Can you provide more information? Have you tried working with the `Vary` header?

Hey.. sorry I couldn't dig into this until now. It's hard to see all the header information on your screenshot, but if your responses have `Vary:Accept-Encoding` then it's worth it...

Hey @yokomizor - I'm sorry you're having trouble with the extension. I don't have much experience using `hx-boost` but it looks like there's an `HX-Boosted` request header that is also...

I've gotten htmx to work for for a chat app, but it takes some extra tinkering. The easiest thing for me to do is was to use the SSE as...