Test failed.

Test failed

Test failed

Maybe you could edit this diary entry to actually have some meaningful content so people stop reporting it as spam?

Yes and that is exactly the problem - people expect us to provide the same sort of advertising style business listings as Google but that is not something we have any intention of offering.

Mostly it’s not actually the business owners, it’s whatever bargain basement SEO shop they’re using this week that submit the information - the real problems start when the next SEO consultant comes along and starts complaining about the “business listing” the previous one created (which usually turns out to be a note) but of course they don’t have the details of the account the first consultant created.

Because draft changesets that can be approved aren’t a thing and because we’re a map data provider not a business listings service…

Anything like this will just encourage SEO spammers (as ONOSM already does) as well as causing much subsequent confusion and support load from people enquiring about their “business listing” which I then have to spend my time explaining is not something we offer.

It’s almost certainly not a problem with OSM at all, rather the problem is the IP geolocation database Facebook/Instagram are using.

Sadly as they make themselves impossible to contact their users see our names on the map and flood our support channels with their complaint instead.

Test failed

The reason docker fails is that there is no init at all when using kitchen-docket so chef (having found there is no systemd running) assumes upstart is the init and then fails to find /sbin/status and errors.

As I explained on the github ticket, this is why we use vagrant, so that we have full VMs with a running init where we can manage services.

I am working on trying to use containers, but with a running init, and I have many of our tests working now, though with podman and I haven’t tried with real docker yet.

Please accept my apologies for my total incompetence.

I have immediately pushed an urgent update to re-enable indexing of diary entries and I beg that will accept my most grovelling apology.

Wasn’t it you that suggested blocking indexing of the diary pages as a temporary measure? Certainly it’s something we can revisit now.

As to why we don’t allow the geodata to be indexed it’s because of the load hundreds of searching engines crawling billions of objects puts on our servers.

Please contact [email protected]

Nobody has refused to remove anything - the report was still in the queue for review.

It has now been dealt with.

See https://github.com/gravitystorm/blogs.osm.org/issues/17 but the short version is that there’s no real way to do it because RSS doesn’t have a way to publish a removal request and the aggregator only looks for new posts and takes existing posts from it’s cache.

The only way to do it would be to remove the aggregator’s cache before every run and rebuild everything completely from scratch which would mean it would not keep any history.

I’ll tell you how not to do it - by posting spam on third party sites!

No OSM sysadmin is going to assist a random user with access to potentially personal data like IP addresses.

If there is a problem then report it to DWG and they will be able to make whatever enquiries are necessary and to seek assistance of the admins where necessary.

It is completely untrue that Nominatim doesn’t search relations - the first result for https://nominatim.openstreetmap.org/search.php?q=Broxbourne is https://nominatim.openstreetmap.org/details.php?place_id=198582074 which is, as the page clearly says, a result for relation/2677978.

The problem is that you want us to presume guilt on the basis of no evidence other than your hunch and I say we will only act where there is reasonable evidence.

Let me be clear - we will not be closing accounts just because you think they might spam at some point in the future, and posting a diary entry that is simply “odd” or “not useful” does not constitute spam under any sane definition that I am aware of.

By your own logic (of not being relevant to OSM) this diary entry is, in fact, spam.