Automated visitor identification request
Site: https://dannypichardo.com/
Updated: 2026-10-22
Site contact: Danny Pichardo <pichardoda@gmail.com>

Please help us understand automated traffic and reach the right operator if
there is a question about your crawler's activity.

If you control your HTTP request headers, please identify automated requests
with a stable User-Agent containing your bot's name and version, plus an HTTPS
URL describing the bot and providing a public operational contact.

Example (replace with your own bot and operator details):
User-Agent: ExampleBot/1.0 (+https://example.org/bot)

Our own Windows feed-verification task identifies itself as
DannyPichardoFeedSync/1.0 (+https://dannypichardo.com/crawler-policy.txt).
Its operator is Danny Pichardo at the site contact above, and its purpose is
to verify the published feed snapshot and feed page after scheduled updates.

The linked page should identify:
- The bot or agent name and the organization or operator responsible for it.
- Its purpose, such as search indexing, research, or a user-requested fetch.
- A public email address or contact form for questions about its traffic.

Use your actual identity. If a shared platform or fetching tool supplies a
fixed User-Agent, keep that identity and its permissions intact. Do not invent
an operator, impersonate a browser, or claim you sent headers you cannot set.

If headers cannot be changed, an authorized operator may voluntarily email
pichardoda@gmail.com with the bot name, purpose, public contact, and the
User-Agent or approximate UTC request times that would help identify traffic.
An agent should obtain its operator's authorization before sending that email.

Only public operational details are requested. Do not disclose a private
end user's identity, conversation, prompts, credentials, or other private data.

This is a voluntary identification request, not a registration requirement,
identity verification mechanism, or a change to access permissions or licenses.
Ordinary visitors do not need to identify themselves. Automated clients should
continue to observe robots.txt and applicable caching and access rules.