Paul d'Aoust

I was thinking about what @WebDevTmas said and, while I was initially resistant to the idea, it's slowly growing on me. On the one hand, adding container query syntax to...

@aFarkas oh, good point; that totally didn't occur to me. So I wonder how this should be resolved... it'd sure be nice to have the browser select the correct image...

@aFarkas yeah, I realised that it's not really specific to container queries after thinking through the issue; hence my previous comment re: wishing we didn't need sizes and wanting something...

@ausi > A qualified element has to match certain characteristics, e.g. it must have a width which doesn’t depend on the size of its child elements. If the browser finds...

Okay, just checking, cuz I'm pretty ignorant of all this stuff :-) I do like the idea of container queries just not working if the container (whether explicit/particular or implicit/nearest)...

Sure @c12i . Are there any fixes that haven't already been made? Should I do a new PR with those?

Great to see this conversation being started. I agree that this is the way that validation should go -- for 90% of devs\*. The awkward thing about our SDK is...

> In a sharded network the agent activity is the most relevant regarding performance and data storage. Huh, well that makes sense to me. Every other context is roughly equivalent...

If there's concern about us having to throw everything away once we nail down a sensible op model, maybe that's an argument in favour of implementing `Op::to_record_to_validate` and using it...

just want to mention that rate limiting via `validate` callback alone isn't sufficient to prevent DHT spamming in an adversarial -- it assumes that bad guys won't try to fork...