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

[512]

1. Unrealistic Suggestions:
Let me address this directly—what exactly do you mean by "integrating computer vision techniques to identify elements based on their visual properties rather than DOM attributes"? You’re suggesting taking screenshots, using Selenium, and analyzing them with ChatGPT to extract data.

This approach would require an entirely new system, including integrating advanced AI and computer vision techniques. Not only is this far beyond the scope of the original agreement, but it’s also an impractical and convoluted solution. Let’s not forget that ChatGPT and similar tools face Cloudflare protection, which many developers struggle to bypass. Suggesting this method is simply unrealistic and doesn’t align with the initial project expectations.

2. Constantly Adding New Terms:
It’s also worth noting that you’re introducing new requirements day by day—features and approaches that were never part of our initial agreement. The script was delivered to you approximately a month ago and met the specifications we agreed upon. Suddenly demanding complex AI integration or XPath-based dynamic scraping is like changing the rules after the game has ended.

If these advanced techniques were so important to you, they should have been discussed and agreed upon before the project began, not after delivery.

3. Dynamic Nature of Scraping and Updates:
As explained before, scraping platforms like Facebook comes with its own challenges. The delivered script worked perfectly at the time of delivery, using methods that you approved during the development process. Changes made by Facebook since then are beyond anyone’s control and are a known risk with scraping.

That said, as I’ve mentioned previously, we will be updating the script for you this time only, despite our initial agreement not including after-sales support. We have already provided updates in the past out of goodwill, and this update will be done to ensure the script works as expected. However, no baseless arguments or new requests—such as using ChatGPT or implementing AI-based scraping—will be entertained. These demands are simply unreasonable and impractical.

Once this update is provided, it will conclude our commitment to this project.

4. Conclusion:
Let’s be clear:

The script was delivered as agreed and worked as intended.

We have already provided updates out of goodwill, and we will ensure it’s updated again for you this one last time.

Your new demands for AI, computer vision, and advanced scraping techniques are entirely outside the original agreement.


We are happy to assist with this update to ensure the script works for you, but no further after-sales support will be provided, as it was never part of the original terms. Let’s stay focused on resolving the issue rather than introducing brainless arguments that deviate from the scope of our agreement.

[25]

if you will just modify the script with new css slectors it will be competly useless and break again. Dont even waste your time on that.

 You’re suggesting taking screenshots, using Selenium, and analyzing them with ChatGPT to extract data.

You can use OpenAI API for this , its not that difficult.  

2. Constantly Adding New Terms: Yes , because i want the script to ACTUALLY work and NOT break in a day or so when facebook updates its html layout. I gave u multiple suggestions how to do it and make it work properly.

I am expecting a working script that doesnt rely on changing css slectors. If you dont want to use my methods thats completly fine but simply changing the selectors again is not going to cut it.

---

It’s also worth noting that you’re introducing new requirements day by day—features and approaches that were never part of our initial agreement.

Are you serious now? our intial agreement was a WORKING facebook scraper. Your scraper does not work. It worked like a few times and thats it then it broke.

[25]

any update on this ? @SpaceService @Liars

[25]

@Liars he hasnt responded to me or provided me with any updated script its already been a week

[2.806]

Hello, I am not supposed to reply here but I will give additional context.
@SpaceService seem to be in the wrong here.
If you are aware that a script might not work after a short period of time and purposely make a understatement of the troubles that can arise from your program, you are in the wrong.
Facebook HTML Dom attributes will change VERY regularly, because they are most likely re-compiled but cached to optimize performances.

@SpaceService, would you sell a car if you knew it would break down regularly because of you do your weldings poorly ?
Then why would you not do the same when coding a script for someone ?

To come back on your claim:

Code:

4. Previous Scamming Behavior:
On top of all this, you have scammed my friend before and then conveniently deleted the chats to hide it. I don’t have proof of that incident, but it’s enough to show a pattern of shady behavior. Adding that with your multiple accounts, it’s pretty clear what’s going on here.

If that is the case why would you deal with him if the first place if you "knew" he was a scammer, and why would you not take payment prior knowing he "could scam you".
 

Code:

3. Refactoring the Script:
Refactoring the script to use more stable methods like XPath or detecting JSON endpoints is a significant update

That is factually false, using XPaths is virtually the same as using CSS Selectors, maybe using different functions to call it is the same.

Here are the recommended solutions for you to fix the program easily without having to do much re-implementation:
1. Use WAI-ARIA Attributes like IntelHawks mentioned if they exists, theses attributs are used by assistive technologies to give meaningful informations to people with disabilities, and they are unlikely to change from my knowedge.
2. Use XPATHS 
3. Using a recursive function to traverse all nodes in the document, apply a list of if rules to verify if a specific node matches for example: Regex Pattern, selectorElement.style, CSS Format, dq
4. One other solution if the key element does not move inside the document, obtain the exact ellement coordinates and obtain the node via theses coordinates.

Overall this seem to be an issue regarding the quality of the code and the User deserve a fixed version of his code.

[512]

1. Acknowledgment of Input: @IgniteHost, I appreciate you taking the time to weigh in on this situation. Your comments were… colorful, to say the least. However, this is a discussion between myself and the user, and while your input has added some spice to the pot, I think we’ve got all the seasoning we need. There’s no need for further replies—we’re all topped up, thanks!


2. Misguided Car Analogy: Your analogy about selling a car with poor weldings gave me a chuckle, but let’s shift gears for a second. Scraping isn’t quite like manufacturing cars; it’s more like selling a train ticket for a track that might occasionally get rerouted. The destination is the same, but there might be a detour. Blaming me for Facebook’s frequent changes is like blaming the train company for unexpected construction work on the tracks.


3. Clarification of Agreement: The project was delivered as per the original agreement, and the user was informed of the dynamic nature of web scraping. Updates due to Facebook’s changes were not part of the deal. While your suggestions are interesting, they don’t change the scope of the original agreement.


4. On Suggested Solutions: I’ve noted your ideas about ARIA attributes, XPath, and recursive DOM traversal. While they’re valid techniques, they require significant restructuring, which is outside the original scope of the project. Also, let’s not pretend that even these methods are immune to platform updates—they’re just another flavor of the same dynamic challenges.


5. Holiday Season: Also, let’s remember it’s the holiday season! Developers, like everyone else, deserve a break during this time. If we weren’t busy handling disputes like this, we’d probably be sipping eggnog and debugging our own lives instead of scripts.


6. Closing Thoughts (with a bit Humor): I appreciate the effort you’ve put into this, @IgniteHost, but we’re not trying to build a community garden here. One person planting tomatoes is enough—we don’t need the whole block pitching in. Your contribution has been noted, and you can now rest easy knowing you’ve done your good deed for the day. No further replies are needed—you’ve done more than enough, my friend!

---

i sent more updates to @IntelHawks because some people like to poke into others matter (no offense)

[512]

Hello, I am not supposed to reply here but I will give additional context.
@SpaceService seem to be in the wrong here.
If you are aware that a script might not work after a short period of time and purposely make a understatement of the troubles that can arise from your program, you are in the wrong.
Facebook HTML Dom attributes will change VERY regularly, because they are most likely re-compiled but cached to optimize performances.

@SpaceService, would you sell a car if you knew it would break down regularly because of you do your weldings poorly ?
Then why would you not do the same when coding a script for someone ?

To come back on your claim:

Code:

4. Previous Scamming Behavior:
On top of all this, you have scammed my friend before and then conveniently deleted the chats to hide it. I don’t have proof of that incident, but it’s enough to show a pattern of shady behavior. Adding that with your multiple accounts, it’s pretty clear what’s going on here.

If that is the case why would you deal with him if the first place if you "knew" he was a scammer, and why would you not take payment prior knowing he "could scam you".
 

Code:

3. Refactoring the Script:
Refactoring the script to use more stable methods like XPath or detecting JSON endpoints is a significant update

That is factually false, using XPaths is virtually the same as using CSS Selectors, maybe using different functions to call it is the same.

Here are the recommended solutions for you to fix the program easily without having to do much re-implementation:
1. Use WAI-ARIA Attributes like IntelHawks mentioned if they exists, theses attributs are used by assistive technologies to give meaningful informations to people with disabilities, and they are unlikely to change from my knowedge.
2. Use XPATHS 
3. Using a recursive function to traverse all nodes in the document, apply a list of if rules to verify if a specific node matches for example: Regex Pattern, selectorElement.style, CSS Format, dq
4. One other solution if the key element does not move inside the document, obtain the exact ellement coordinates and obtain the node via theses coordinates.

Overall this seem to be an issue regarding the quality of the code and the User deserve a fixed version of his code.

also I just remembered delete his msg @Liars @Darkness he can't get involved in a dd which he isn't a part of

---

This entire dispute was absolute bullshit. The script works perfectly, and we just ran it to confirm (Link). The only adjustments needed were tiny—changing name and loginbutton. That’s it. This was never about the script being broken, and the only reason this dragged on was because my dev had COVID and couldn’t check sooner. Otherwise, this waste of time could’ve been avoided entirely.

@Liars @Darkness, ban this clown already. I’ve shown proof of his multi-account abuse, and now it’s clear this was nothing but an attempt to scam and waste my time. He’s not here for legitimate work, and his claims have no basis.

And @IgniteHost, stay the fuck out of disputes that don’t concern you. Nobody asked for your useless analogies or half-baked input. You’re not the savior of disputes, so keep your opinions to yourself.

This is done. Script works. Claims were baseless. Action needs to be taken against this guy now.

[25]

He didnt set up the script on my rdp and didnt provide me with a wokring account which was part of our deal. He just recoreded a video and I am sure he just manually changed the selectors again , I would like to test the script for a few days to make sure it doesnt break.