Yes, they should make it clear that xCurl has nothing to do with real curl.
But if it intends to implement the same interface, I don't see any problem with saying look at the curl docs for what its supposed to do. I don't see how that would be much different then if you implemented your own web browser and was like, look at MDN for how its supposed to work.
<2 pages of back-and-forth posts later>
"Oh you're using xCurl, yeah you need to talk to Microsoft."
It probably depends on the reach this has within the intended audience (people wanting to deploy libcurl on Xbox?) as to how much of a support burden it will end up, but I suspect more than Mozilla has to deal with from similar situations.
But we’re talking about curl here. MS could have an intern copy paste the curl document, delete the stuff that doesn’t apply to XCurl, and host it on a shared OneDrive Word document all within a day, and it would be orders of magnitude a significantly better experience.
Instead curl maintainers will end up spending man years supporting XCurl issues instead.
I get the feeling people think MS is different now it has embraced open source.