Scam report against https://cracked.sh/SpaceService

[25]

It doesnt work. I am getting bunch of errors again. @Liars or anyone can test the script and see for themselves that its not working. The script is cooked. I would like to get a full refund at this point since this has been going on and off for over a month now.

[512]

LMAO WHAT

---

bro get your own account im not sharing it

[512]

i gave you a account you rape it by logging in them by logging in while using vpns
dont play fucking games with me I got video recording of it working when the account was working before you raped it don't play games here

---

in this dispute he made us change code on 3 different rdps even today, we fix it he makes us wait again for a week even after showing us proof of it working he doesn't have a account then that's not on us

[512]

https://imgur.com/a/VIEDA8N
https://imgur.com/a/BHJFOUC
https://imgur.com/a/qZZ0W00
https://we.tl/t-ryie0zHEln

All proofs of it working and this is past 2 days with my account, the account got flagged because the user logged into it with vpn i have mail notification from 4 different locations.

He can go use his own account im not giving my account again

---

he buys the script 2months ago uses it foor one and half month that also to note with the accounts we gave to him, Haas some problem and directly creats a dd we resolve the issue approx 10 days after the dd was opened it was a minor fix and he hasn't checked it since that day??? if you don't think that's time wasting then what it is. just ridiculous

[512]

My Final Response

First off, let’s set the record straight: the script is fully functional, and we’ve proven it repeatedly. Below is a breakdown of everything that’s happened, showing exactly why this user is in the wrong, why they have been wasting everyone’s time, and why their refund demands are baseless.

1. The Script Does Work

• We gave them multiple screenshots, logs, and even video recordings showing that the scraper works perfectly on our end.
  
• We set it up on not one, not two, but three separate RDPs at the user's request—each time proving that the only minor fixes were simple selectors or login button changes.
  
• The user still keeps dragging this on, claiming "it doesn't work" without ever showing actual, concrete errors that we haven't already addressed.
  

Translation: The script is good. They used it for over a month but as soon as they come to the conclusion that "they want something new", they claim it is faulty and start threatening refund demands. This is pure opportunism.

2. They admitted to using the wrong endpoint and port.

• The user literally used the endpoint "/start-scrapping" (with double "p" in scrapping instead of single "p" in scraping) on port 80, even though we told them the script runs on port 5000 and the endpoint is "/start-scraping".
  
• That alone shows they're not even following basic instructions and are just flinging accusations around when the real problem is their own misuse.
  

Translation: They are complaining of a "broken script" when they don't even use the right endpoint. That is 100% user error, not the fault of the script.

3. Endless Demands, Zero Cooperation

• We explicitly stated that account credentials were never part of the original deal. Yet the user demanded we provide our personal testing account. Out of goodwill, we loaned them an account anyway, and they promptly got it flagged by logging in from random VPNs and suspicious locations, effectively killing that account.
  
• They also asked us to do a full setup on their RDP, yet they made us wait hours to get credentials and then ghosted us for days or even weeks at a time. Meanwhile, each minor fix we offered took us a fraction of that time.
  
• They keep introducing "new requirements" like AI-based screenshot analysis or advanced XPath structures—a complete scope change from the original deal. Then they blame us for not implementing their far-fetched methods.
  

Translation: We bent over backwards to accommodate them—upgrading code, offering to set up on RDPs, even giving them our own account for a short time—yet they still play victim. They're either deliberately stalling to justify a refund or just entirely clueless.

4. They used the script for over a month, now they want a refund?

• The user had the script for well over a month-long period of time, sufficient to do whatever they needed to do with it.
  
• Only after fully using the script did they run to open a dispute, demanding a complete refund, alleging it's "broken."
  
• We have proven that it works perfectly, so the only conclusion is that they are trying to game the system.
  

Translation: They basically want a free ride after benefiting from the script. That is the classic pattern: use the product as much as you want, then yell "refund!" the moment you're done with it or you want more advanced features for free.

5. The "Bad Evil Man" Wasting Everyone's Time

• They have been slow from day one, uncooperative, and consistently change the goalposts.
  
• Every time we fix a minor detail, they disappear, then reappear later with new random complaints.
  
• Now they are going as low as personal attacks, brand-new demands, and refusing direct evidence that the script works.
  

Translation: This is a time-wasting strategy, plain and simple. They're not really after a working scraper (they did have one!). They're looking for an out of paying for professional development or a way to extract free updates beyond our agreement.

6. Conclusion & Request for Staff

• We have delivered exactly what was agreed upon: a working Facebook scraper.
  
• We have spent too much time on free updates, RDP setups, and troubleshooting, even for user errors.
  
• We provided evidence of successful runs, but the user either refuses to accept reality or simply wants to exploit the dispute system for a refund.
  

At this point, we ask that this nonsense be closed immediately. The user has no case for a refund, and we have shown that we did our part of the bargain—and then some.
Staff, please take action: This user has wasted enough time, opened a frivolous dispute based on incorrect usage and false claims, and keeps shifting blame instead of cooperating. They are clearly not here in good faith.
 

Final Words

The script works. Their usage of the wrong endpoint, repeated requests for freebies well outside the agreed scope, and blatant time-wasting tactics reveal their true intentions: getting a free product or a last-minute refund they do not deserve. We’ve done everything in our power to assist, and the user has done everything possible to avoid a straightforward resolution.

We stand by our work and ask the staff to see through these baseless refund demands. We are done playing circus here.

Thank You,
@SpaceService

[25]

It doesnt work. I tried with a new account. Getting the same exact errors as before. He refused to admit the script is cooked. The video he uploaded is likely due the code being hard coded with the new elements. Now its not working. @Liars or anyone else can check the script and test the endpoint. Its not working.

---

@Liars @Darkness  can we please get an update on this?

[512]

send me the account

---

HE IS USING MY ACCOUNT STILL

[512]

so in the image he sent about the error: https://imgur.com/a/Cb2x1LL
The blue circle should be the username they wanna scrape but they put a mail there idk why
the red circle is the mail and pass he put me mail and there own password again idk why.

I think they got confused here and did it wrong. AND the audacity of this guy to say that I'm faking the videos?? thats why I started the script from start and it's recorded from mobile phone you can't even edit that it's from starting where we send request to the endpoint till the end.

Idk what he is trying to do, sending wrong requests again and again it's just user error all the time because of his low iq or him just acting to get a refund

---

Im so done with this guy i swear