Capmonster.cloud support

[telugu-boy]

Since a recent Discord update, joining any guild might require the token to complete an hcaptcha. We can use some captcha solver service like capmonster.cloud to solve these though. How feasible is it to add support for this? Maybe I can make a PR over the weekend.

[TheOnlyWayUp]

Interesting, I believe this library uses parts from captcha harvester, I doubt it supports hCaptcha though. I don't believe using capmonster would be feasible as it looks like a paid service. I'll see if there are free alternatives, if we find one, feel free to make a PR. (I doubt a PR that adds support for a paid service would be accepted, hence, let's try using a free alternative)

[dolfies]

I have support to create your own captcha solvers locally, but it might take a while to push because it's integrated with auth.

I can definitely have some example solvers that use 2Captcha-like APIs.

[TheOnlyWayUp]

@TheOnlyWayUp Why does an optional service need to be free? I mean, it's not only capmonster that would be supported if this was added, it's any service that supports a popular captcha API (see: 2captcha)

When something is made FOSS, what's the point of having components that you need to pay to use directly in the code? Instead, I believe dolfies's current implementation of being able to subclass is better suited.

[telugu-boy]

@TheOnlyWayUp Why does an optional service need to be free? I mean, it's not only capmonster that would be supported if this was added, it's any service that supports a popular captcha API (see: 2captcha)

When something is made FOSS, what's the point of having components that you need to pay to use directly in the code? Instead, I believe dolfies's current implementation of being able to subclass is better suited.

It doesn't have to be directly in the code, though, and even if it was, it would still be a completely optional component. It doesn't affect the philosophy of FOSS at all

[TheOnlyWayUp]

@TheOnlyWayUp Why does an optional service need to be free? I mean, it's not only capmonster that would be supported if this was added, it's any service that supports a popular captcha API (see: 2captcha)

When something is made FOSS, what's the point of having components that you need to pay to use directly in the code? Instead, I believe dolfies's current implementation of being able to subclass is better suited.

It doesn't have to be directly in the code, though, and even if it was, it would still be a completely optional component. It doesn't affect the philosophy of FOSS at all

In that case isn't everything optional? When everything is free, and you aren't locked to just one service (capmonster.cloud in this case), it's much easier to work with and extend. Dolfies's implementation of subclassing is more appropriate in my opinion.

[telugu-boy]

Yeah, capmonster.cloud was the just first thing that came to mind. In reality, most captcha services support other captcha services' APIs (like 2captcha or DBC). And I did point this out as well

some captcha solver service like capmonster.cloud to solve these though.

I don't know what exactly subclassing has to do with this issue. It's one solution, that's for sure

[TheOnlyWayUp]

I don't know what exactly subclassing has to do with this issue. It's one solution, that's for sure

It allows you to add support for whatever captcha service you want, instead of adding and maintaining support for one or more captcha services (I believe maintaining them wouldn't be too hard, but it's unneeded work when), allowing the user to do so if they need it is much more effective, and easier too I would guess