GlancityBot
GlancityBot is the program Glancity uses to read public event listings, so the app can show what's on in each city. This page explains what it reads, how often, and how to stop it.
How to recognise it
Every request carries this user agent:
GlancityBot/1.0 (+https://glancity.com/bot; contato@glancity.com)The robots.txt token is GlancityBot. Requests come from Cloudflare's network, so there is no fixed list of IP addresses.
What it reads
- Event listings and event pages on the public websites of city halls, tourism offices and cultural organisations (for example Sesc and Mapas Culturais).
- Only public pages: it never logs in or fills in forms.
- Only cities that people open in Glancity.
- From each event it keeps what is needed to list it (name, date and time, place, image address) and the link to the original page, which the app shows as the source.
It also uses public services under their own usage rules, with the same user agent: Wikipedia and Wikidata, OpenStreetMap (Nominatim, Photon, Overpass) and MET Norway.
How it behaves
- It follows robots.txt (RFC 9309): the
GlancityBotgroup, otherwise the*group. - If a site has no robots.txt, it may read the site. If robots.txt can't be read (server error or timeout), it reads nothing there and tries again after 60 minutes.
- It reads robots.txt again at least every 24 hours.
- It honours Crawl-delay up to 10 seconds.
- One request at a time per site, at least 1 second apart.
- At most 5 redirects, checking the robots.txt of every new site.
How often
- A city's event sites are read once a day. The 5 most-opened cities (100 or more opens in a week) every 6 hours, the next 15 (20 or more opens) every 12 hours.
- Each visit makes at most 38 requests for all of that city's sites together, and reads at most 4 listing pages and 15 event pages per site.
- A city's official sites are looked for once every 30 days.
- When an event disappears from a listing, its page is checked again, at most every 12 hours.
- If a site fails, it tries again after 1 hour, then waits twice as long each time, never more often than the normal schedule.
How to stop it
Add this to your site's robots.txt:
User-agent: GlancityBot
Disallow: /GlancityBot stops within 24 hours, the next time it reads robots.txt. To limit it instead, disallow only some paths or set a Crawl-delay.
Removing an event or image
If you organise an event and want it, or only its image, removed from Glancity, email contato@glancity.com with the link. We remove it within 24 hours.
For anything else about GlancityBot, write to the same address.