Ruben Taelman

Ok, that's great! There may also be a difference in browser performance, do you have insights on that?

> So I had some variables wrong in the above experiment, turns out ActorHttpFetch is about 2x faster on node on average That's really good to hear! > Trying to...

> It should be feasible to exclude. Let's exclude it then. > That said, I'm not sure I see the benefit of keeping it given that actor-http-native is not used...

Thanks for reporting!

Could you raise this question in our discord channel (see the repo README badge)? It might just be a limitation wrt to how these time crystals works (I don't know...

Can't you just use the `ArrayIterator` constructor directly?

This may be fixed already in eb73ae2aa6f1477b3b11bb681484eff43f5a6302 (v5.0.0), to be tested.

A bounty has been placed on this issue via the Comunica Association (see original post).

Besides the Server header, do you see any other information in the responses that could help identifying it as a SPARQL endpoint?

Hi @milafrerichs, just checking in to see how this bounty is progressing on your end?