Case study
Facebook Marketplace poster
Posts listings to Facebook Marketplace on a schedule from a config file rather than by hand. Public, and the most starred and most forked repository on my account.
Overview
Listing items by hand does not scale past a handful, and listings go stale and need reposting. This drives the whole flow from a configuration file: the items, their details, their images and when they go up.
It is public, and it is the most starred and most forked repository I have. Forks matter more than stars here, because a fork means somebody took the code and built on it.
Complexities tackled
Automating a flow that is actively defended. Marketplace listing is a multi-step form that changes, and the automation has to survive both the changes and the platform’s interest in not being automated. Pacing, ordering and waiting for the right state rather than a fixed delay is most of what keeps it working.
Written to be forked. Because it is public, the config file is the interface and the code is not meant to be edited to use it. That is a different design goal from a private script, and it is the reason the forks exist.
Stack
Python with Selenium, configuration driven.
Working on something similar?
Tell me what you are building and what is in the way. I will tell you honestly whether I am the right person for it.