There are players that mistakenly have the data center option checked when listing stuff that only applies to the server, but they're few and far between, are not all the same type of listing, don't require interested parties to contact them outside of the game and it's not the same people doing it. Also, they don't know to not advertise server-specific content across the data center, but they know to select duties such as Lak, Sus and Expert Roulette to maximize visibility? Of the people who mistakenly list hunts, treasure hunting, sales of crafts and the like, how many have you seen use the wrong duty? I can't recall any.
Read the thread, people. It's in the title and one of my responses on the first page: The advertising using the cross-server party finder, NOT the selling itself. Ain't nothing SE can do about sales, regardless of payment method used.
Across servers. That requires buyers to use real money or to buy gil and have it sent to that server.
https://giphy.com/gifs/3o6nV2JsWpUnl3ftvO
https://giphy.com/gifs/xUNd9zOyaVyCQSX3CU
https://giphy.com/gifs/l4EoSCItlaeHCTT1u
We don't know 100% that the player is botting, so it should be allowed and it shouldn't be reported? The majority of player botting is done as shown.
Spoilers: It's one of the so-called advertisers while their pf is up across the data center.
Pay real money to transfer servers after going through the hassle of having yourself meet the requirements, or use that money to buy gil and have it sent to the seller? Hmm.
Context for people not on Aether: At it's peak, there are 5+ advertisers in the cross-server pf at the same time. You'd be hard pressed to find 5 incorrect listings like you describe in total. It's the same people from the same servers.
I'll reiterate the ending of my OP: I'd love if they add filters to hide the listings, but look at the response they received in regards to housing in 4.1. They knew within a day or two and announced they have a fix in mind, but it'll be 3.5-4 months later. Fingers crossed the pf will get an update in 4.2.