Contact

Danny Ayers — danny.ayers@gmail.com

Email is the reliable route and the right one for anything that matters. The rest are here because some people prefer them, not because they are watched as closely.

• GitHub: @danja — an issue on the repository is fine for anything about the software
• Homepage: danny.ayers.name
• Reddit: u/danja
• Twitter/X: @danja

What to say, and where it goes

Something in the catalogue is yours and should not be there. Say so and it will be dealt with rather than argued about — whether or not you contributed it, and whether or not the licence would technically permit it. This is the one that gets answered first.

Your account or your data. Withdrawal, removal, or a correction to what is recorded about you. Contributions are stored in a graph of their own per person, so erasing someone is a deletion of those graphs rather than a search through everything. The contributor terms set out what is kept.

The crawler. How it identifies itself, how fast it goes, and how to make it stop are on the crawler page, which is what its user agent points at. If it has been a nuisance, that is worth an email rather than a robots.txt rule — the rule will be honoured, but it will not tell us what went wrong.

A source that should be harvested, or should not. Adding one means reviewing its terms first, which is a real piece of work rather than a switch. Saying a source's terms have been misread is very welcome.

Access in a shape that is not offered. There are several ways in and none of them needs an account or a key. If none of them suits, ask — a bulk consumer paginating the SPARQL endpoint costs this server far more than answering the email would.

What this is not

There is no support contract and no response-time promise. This is one person and one small server. Anything about data removal or something being wrongly published gets looked at quickly; a feature request may sit for a while.