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

[12]

Scammers Profile Link:https://cracked.io/SpaceService
Sales Thread: https://cracked.io/Thread-Looking-for-de...ok-scraper
Amount or Item(s) Scammed: 250$
Screenshots of Communication:https://i.imgur.com/jRnViM5.jpeg https://i.imgur.com/TzcM7lo.jpeg https://i.imgur.com/oxjcXXQ.jpeg 
Additional Information: I paid him 250 to make a facbook scraper however Facebook frequently changes its HTML and class names, making direct CSS selectors unreliable. So the script is unreliable. Instead of relying on[font] css selectors[/font] similar classes the script needs to be remade. Need to Identify elements using text, stable attributes (like

Code:

data-testid

), or DOM structure rather than class names. Use XPath or other heuristic methods that aren’t tied to volatile CSS classes. 
Crypto address for a refund: TYxsdWFVB836tukzQksMYh64hWdNY1TpQm

---

He needs to either remake the script with the above methods or give me a refund

[1]

System bot message: @SpaceService (SpaceService) has been notified about this dispute via private messages and has 24hours to reply in this thread

top [exp 15/01/24]

 

Taking care of cracked.io's leechers. Every day.
If you have a question regarding your leeching level, click here.

[367]

bro i didnt respond for 4hrs and you are opening dd against me??

---

1. Initial Agreement:
Let's get back to basics: we never agreed on "remaking the script" or constant updates. I delivered exactly what we agreed on—a working scraper. Anybody familiar with scraping knows that platforms like Facebook are constantly changing their HTML. That's just how scraping works.

And while I know that's too many updates to expect, I still went above and beyond and provided you with more than 3 updates even though I didn’t have to. I can still correct minor issues easily, but rewriting the entire script? That’s something we never agreed on, and I’m not doing free work because Facebook changed something.

2. Timeline and Math That Ain't Mathing:
Here's where it gets funny: I first messaged you on November 8th after seeing your thread. Today is December 17th—that's over a month. But now, magically, your account is only 8 days old? (Link) and you just created the sales thread for this dispute? (Link) The math ain't mathing here. Clear signs of multi-accounting because I found the request thread for the service from different account.

Let me repeat that for staff:

November 8th: I messaged the user.

Account created 8 days ago.

Sales thread created now on this dispute.

You don’t have to be Sherlock Holmes to see what’s going on here.

Proof of other accounts:
Link1 Link2 Link3 Link4 And many more.

3. Delay in Replying:
I didn’t respond for 4 hours because I had some personal issues. Four hours, my guy. That’s less time than it takes to binge a couple of Netflix episodes. Instead of waiting, you ran straight to the dispute section like it was an emergency hotline.

Let’s also not forget you made us wait 4 days to receive the payment after our work was done. A little patience wouldn’t hurt.

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.

 

[19.088]

@lntelHawks Provide the full chat logs from start to finish. Do so within 24 hours.

 

AD by  @GoodEatsB4U exp 8/12/2024

 

 

 

Ad by @Bears - expiring 04-01-2025



Ad by @80s - expiring 1/10/2025

[12]

https://i.imgur.com/QyHheaw.jpeg https://i.imgur.com/LuebZw6.jpeg https://i.imgur.com/KZtwlE5.jpeg https://i.imgur.com/jRZ6jjb.jpeg  https://i.imgur.com/xYAejoh.jpeg.


he told me it wouldnt happen often you can see it the messages. https://i.imgur.com/QyHheaw.jpeg he knew that facebook  actively changes the markup content, dynamically yet he still used hard coded css selectors. So esentially this script is useless.

---

The current code relies heavily on static CSS selectors and specific HTML structures that Facebook frequently alters. As a result, the current selectors (like

Code:

".xieb3on"

) will break whenever Facebook updates their classes or DOM layout. He needs to either Look for unique textual patterns or attributes that are more stable or instead use XPath selectors that rely on visible text or hierarchical structure rather than class names. perhaps you can also check Network tab to see if the data is being fetched as JSON from certain endpoints. maybe facebook has some kindn of private API like instagram i.e instagram api/v1/users/web_profile_info/ username= .  

you dont need to remake the entire script but you do need to significantly refactor how elements are located and extracted.

[367]

1. Facebook Markup Changes:
I never denied the fact that Facebook changes their HTML structure—I clearly mentioned it wouldn't happen much. This was discussed during our initial agreement. The user agreed to this understanding and proceeded with the deal knowing that dynamic platforms like Facebook often make changes.

The claim that the script is "useless" is overstated. The script worked fine as delivered unless Facebook decides to make some changes. That is just the nature of web scraping, which needs updates over time as the platform evolves. If that wasn't good enough, the user should not have agreed to the terms.

2. Using CSS Selectors:
The script was created with CSS selectors for the following reasons:

It's an efficient and standard method for scraping.

The user never specified any other preferred methods like XPath or attribute-based scraping during the initial agreement.


If they had requested alternative methods like XPath or API exploitation, I would have considered that during development. However, they didn't mention this until now, long after the delivery. Changing the approach to meet new demands now requires extra work, which wasn't part of our agreement.

3. Refactoring the Script:
Refactoring the script to use more stable methods like XPath or detecting JSON endpoints is a significant update. While I’m happy to make small fixes to ensure functionality, this level of refactoring is essentially a rewrite of the script.

The user claims this doesn’t require “remaking the entire script,” but in reality, it involves:

Changing how elements are located.

Identifying entirely new selectors or methods.

Testing and debugging to ensure reliability with Facebook’s ever-changing structure.


This goes far beyond a simple adjustment and isn’t something I can do for free. If they need this level of work, they better find someone else.

4. Current Script:
The script has been implemented with the agreed-upon methods and works under the conditions discussed during development. As per the claim, it isn't "useless." It worked as intended once delivered. The changes made by Facebook now are irrelevant to the fact that it was poorly designed; the nature of scraping is always dynamic, which the user was already aware of.

5. Current Situation and Updates:
I will inform the user that the developer working on this project currently has COVID and, due to this, is behind on responses. The user was informed about this situation before opening this dispute, so they knew beforehand.

That still doesn't stop us from working on updates, and we’re committed to providing those updates and minor fixes wherever possible. An update will be provided as soon as one is available.

---

The user cannot dictate how the script should be built after the project has been completed. If they had specific requirements or methods in mind, those should have been communicated during the initial agreement. We followed exactly what the user asked for and what they agreed upon during our discussions.

It’s important to note that Facebook posts don’t have textual elements or unique identifiers beyond the classes. These are dynamic, unique posts with no other reliable identifiers available. CSS classes were the appropriate method based on the structure of the content and the user’s requirements.

The suggestion to use “textual patterns” or “other methods” isn’t feasible in this case, as these simply don’t exist in the data being scraped. If the user wishes to explore alternative approaches, that would fall under a new scope of work, as these ideas were not part of the original agreement.

We are happy to make small adjustments within reason, but we cannot redesign the script based on new expectations that weren’t discussed or agreed upon initially.

 

[12]

Facebook often uses ARIA attributes (

Code:

aria-label

,

Code:

role

, etc.) that are more stable compared to dynamic class names. These can be used to identify elements based on their function rather than styling. Perhaps you can also Maintain a list of possible XPath selectors for critical elements. This allows your scraper to try alternative paths if the primary one fails due to changes. 

if all else fails , then integrating computer vision techniques to identify elements based on their visual properties rather than DOM attributes should work.  Basically  Use selenium, take screenshot of what you want and give it to chatGPT to analyse and extract the data you need

---

We are happy to make small adjustments within reason, but we cannot redesign the script based on new expectations that weren’t discussed or agreed upon initially. I need the script to work , I paid 250$ for a script that is broken.

[12]

Leveraging relative positioning and hierarchical relationships based on stable elements can also work.  In general, if there is an element you can securely pinpoint, for example, by not-dynamic id, class, title, or label, use that and then you can do up or down the dom to the element you need.
 Locate the user's name as an anchor and then find posts relative to it. For example : 

From the user's name element, traverse up the DOM (

Code:

../../

) and then find the following sibling div that contains the posts feed (

Code:

//div[@role='feed']

). 

or //div[contains(., "welcome”)]//..//div//a - it will find the div that contains the given word (including children), then will go up the tree looking for the closest div, then back down to the first link.

 Use xpath 

Code:

contains()

to partially match attribute values if they have predictable patterns.

I am esentially telling you how to do your job , which i shouldnt even be doing.  Litteraly , All you have to do is just implement ready logic. Its not hard.