Nearhood Community Events (London)
- name: nearhood-community-eventsdescription: Find one real, upcoming London community event (repair cafe, skill-share, language exchange, mending circle, volunteer day) and post it to Nearhood with a verified image, a correct borough and a factual description.
- Nearhood community events
- 0. What you need before you start
- 1. What counts as a community event
- 2. Where to look (checked and working in November 2026)
- 3. Hard rules (break none of these)
- 4. The procedure, step by step
- 5. Duplicate check
- 6. Borough area slugs (exact, case-sensitive)
- 7. Image rule
- 8. Publishing: POST https://api.nearhood.co.uk/api/events
- 9. Your profile (kind 0), once
- 10. Description style
- 11. Pre-publish checklist
- When to stop and publish nothing
- 12. What to report afterwards
name: nearhood-community-events
description: Find one real, upcoming London community event (repair cafe, skill-share, language exchange, mending circle, volunteer day) and post it to Nearhood with a verified image, a correct borough and a factual description.
Nearhood community events
Use this skill to post London community events to Nearhood, a London neighbourhood site built on Nostr. Each run you post one real, upcoming event that someone else organises. You do the research, check that the image works, check for duplicates, publish through Nearhood’s HTTP API, and report what you posted.
This skill is written for careful, step-by-step execution. Follow the steps in order. Do not skip a check because the event “looks fine”. If any check fails and you cannot fix it, publish nothing and report why. Posting nothing is a good result. Posting something wrong is a bad result, because you cannot edit or delete a listing after it is posted.
0. What you need before you start
-
Your own Nostr key. Use one persistent secp256k1 keypair for every run. Nearhood treats your public key (npub) as your identity and reputation, and new or throwaway keys can be filtered as spam. Keep the private key in a file or secret store that only you can read. Never print it, log it, paste it into a prompt or chat, or put it in a request body.
-
A profile for that key. Publish a kind 0 profile (name, about, picture) to
wss://relay.nearhood.co.ukonce, so people can see who submits your listings. See section 9. -
Tools:
curl, and Python 3 withcoincurve(pip install coincurve) for Schnorr signing. Any other Nostr signing library also works. -
Read the live docs once per run, in case they changed:
- https://nearhood.co.uk/agents.txt (the full API guide)
- https://nearhood.co.uk/auth.md (NIP-98 authentication)
If anything in those docs contradicts this skill, follow the docs.
1. What counts as a community event
POST it only if all of these are true:
- It is one of these kinds of event (or very close to one):
- repair cafe, Restart Party, fixing factory, bike repair session
- skill-share or skill-swap night, free workshop run by volunteers
- language exchange or conversation club
- craft, knitting, sewing, mending or crochet circle
- community garden, food-growing, tree-planting, litter-pick or conservation volunteer day
- tool library or Library of Things session, swap shop, clothes swap
- community kitchen, community meal, pay-as-you-feel cafe
- neighbourhood social, residents’ get-together, community open day
- It is hosted by a community group, charity, volunteer group, library, council, church or faith hall, tenants’ or residents’ association, or community centre.
- It is free or low cost (free, donation, pay-what-you-can, or a small fee to cover costs, roughly £10 or under).
- It is open to anyone who turns up or books. It is not members-only, not a private group and not invite-only.
- It takes place in person, in London, at a real street address in one of the 33 areas in section 6.
- Its start date is in the future (later today counts only if it starts at least 3 hours from now).
Do NOT post:
- commercial gigs, club nights, comedy, theatre or cinema (they are not community events for this skill)
- promoter events that exist only on Eventbrite, Fever, DesignMyNight, Skiddle or similar, with no organiser page of their own
- big festivals, fairs or markets with paid stalls as the main point
- paid courses, classes, workshops or “masterclasses” run as a business
- online-only events
- anything outside London
- trade or swap offers on behalf of a person (for example “Ana will swap Spanish lessons for help with her garden”). Never invent, paraphrase or repost a personal offer. Those can only come from the real person. You only post events.
- anything you could not confirm on the organiser’s own page
If you are unsure whether an event qualifies, skip it and choose another.
2. Where to look (checked and working in November 2026)
Start with the first two. They list many real London sessions with dates.
| Source | URL | What it is good for |
|---|---|---|
| The Restart Project, upcoming events | https://therestartproject.org/parties/ | Has a “London” section listing dated repair events and their hosts (for example Hackney Fixing Factory, Islington Fixers, Haringey Fixers, Forest Fixers, Wimbledon Repair Cafe). Find the host, then open the host’s own page for details. |
| Repair Café International, visit map | https://www.repaircafe.org/en/visit/ | Directory of repair cafes, including many in London. Use it to find group names, then go to each group’s own site. |
| Meetup, London language exchange | https://www.meetup.com/find/gb--london/language-exchange/ | Language exchange and conversation groups. Choose free or low-cost groups run by volunteers. Open the event page itself for the date, venue and price. |
| TCV (The Conservation Volunteers) London | https://www.tcv.org.uk/london/ | Conservation and green-space volunteer days. |
| GoodGym | https://www.goodgym.org/ | Group runs that do community tasks (gardening, helping community centres). Use only sessions with a public page and an address. |
| Library of Things | https://www.libraryofthings.co.uk/ | Tool and equipment libraries in London libraries, with occasional repair and skills sessions. |
| Capital Growth | https://www.capitalgrowth.org/ | London’s food-growing network: community gardens with volunteer days and open days. |
| Council library and community pages | e.g. https://www.lambeth.gov.uk/libraries-archives | Most London councils list library events (conversation clubs, knit and natter, repair sessions). Search “ |
| Community centre websites | search “ community centre what’s on” | Many host free socials, community meals and skills nights. |
Searching the web also works well, for example: "repair cafe" Lewisham December 2026, "knit and natter" library Ealing, "language exchange" Camden free, "community kitchen" Tower Hamlets volunteers.
Aggregators are only for discovery. Always open and read the organiser’s own page (the group’s website, its page on the council or library site, or its own Meetup event). The listing’s link must be the organiser’s page, not the aggregator.
3. Hard rules (break none of these)
- Fetch the organiser page yourself in this run. Read the date, start time, venue, address, price and booking details on it directly. Do not rely on memory, search snippets or an aggregator summary.
- The date must be in the future and confirmed for this specific session. “Every second Saturday” is not enough. You need the actual next date, shown on the page or clearly implied (for example “Next session: Sat 12 December”). Make sure the year is right.
- It needs a real London street address with a postcode. If you only have “a church in Hackney”, skip the event.
- Use the organiser’s exact title, with their spelling, capitals and punctuation (for example
Chiswick Repair Cafe, notRepair Café in Chiswick). If the page has no event title, use the group’s name plus the event type exactly as they word it. - Never invent anything. That covers time, end time, price, booking rules, what to bring, accessibility, who runs it and what happens. If the page does not say it, leave it out.
- One listing per run. Stop after one successful post.
- Check Nearhood for duplicates first (section 5).
- Vary venue and borough. Do not post the same venue or organiser twice within about 4 weeks, and prefer a borough you have not posted to recently. Keep a local log of what you posted (title, date, venue, borough, link, naddr) and check it every run.
- Use the correct borough slug (section 6), based on the venue’s postcode.
- Every listing needs a working, relevant image (section 7). With no working image, publish nothing.
- Use the platform-signed event endpoint
POST https://api.nearhood.co.uk/api/events, because you are reposting someone else’s event (section 8). - Never put secrets anywhere. Your private key is never written into a payload, a log, a report or chat.
4. The procedure, step by step
Do these in order. Tick each item in your own working notes.
Step 1: Load the docs. Fetch https://nearhood.co.uk/agents.txt. Check that POST https://api.nearhood.co.uk/api/events still exists and that its required fields are still title, area, description, venue, date_time plus at least one source URL. If not, follow the docs.
Step 2: Load your log. Read your local log of past posts. Note which venues, organisers and boroughs you used in the last 4 weeks.
Step 3: Find 3 to 5 candidates. Use the sources in section 2. For each one, write down:
- the organiser page URL
- the exact title
- the date and start time (plus end time if given)
- the venue name and full address with postcode
- the price
- who organises it
Step 4: Filter. Drop any candidate that fails section 1 or section 3. Drop any whose venue or organiser is in your recent log.
Step 5: Check for duplicates on Nearhood (section 5) for each remaining candidate. Drop any that are already listed.
Step 6: Pick one. Prefer, in order: a borough with few or no Nearhood events; an event 3 to 21 days away; a friendly event open to beginners.
Step 7: Work out the borough. Run curl -s https://api.postcodes.io/postcodes/<POSTCODE-without-spaces>. Read result.admin_district (for example Hounslow) and map it to the slug in section 6 (for example hounslow). If result.region is not London, stop and pick another event.
Step 8: Find and verify an image (section 7). If none works after rehosting, go back to Step 6 and pick the next candidate. If none of your candidates has a working image, publish nothing.
Step 9: Write the description (section 10).
Step 10: Build the payload (section 8) and save it as a JSON file. Read it back once, checking every field against the organiser page.
Step 11: Run the pre-publish checklist (section 11). If any box is unticked, fix it or stop.
Step 12: Publish with the script in section 8. Save the full response.
Step 13: Verify. Open https://nearhood.co.uk/events/<naddr> from the response and confirm the page loads with the right title. You can also check GET https://api.nearhood.co.uk/api/offerings?area=<slug>&offering_type=event.
Step 14: Log it and report it (section 12).
5. Duplicate check
Public reads need no authentication.
# All upcoming events across London
curl -s "https://api.nearhood.co.uk/api/offerings?offering_type=event&limit=1000" -o nh_events.json
# Events in one borough
curl -s "https://api.nearhood.co.uk/api/offerings?area=hounslow&offering_type=event&limit=1000" -o nh_borough.json
The response is a JSON object with an offerings array. Each item’s content is a JSON string, so parse it again. Inside you get title, date_time, venue, organizer, external_link and image fields. Treat the candidate as a duplicate if any of these match an existing event (ignore case and punctuation):
- the same
external_link, or - the same or a very similar title and the same date, or
- the same venue and the same date.
Example in Python:
import json, re, urllib.request
def norm(s): return re.sub(r'[^a-z0-9]', '', (s or '').lower())
url = "https://api.nearhood.co.uk/api/offerings?offering_type=event&limit=1000"
data = json.load(urllib.request.urlopen(url))
cand = {"title": "Chiswick Repair Cafe", "date": "2026-11-21",
"venue": "Christ Church Turnham Green", "link": "https://chiswickrepaircafe.com/"}
for o in data["offerings"]:
c = json.loads(o["content"])
same_day = (c.get("date_time") or "")[:10] == cand["date"]
if (norm(c.get("external_link")) == norm(cand["link"])
or (same_day and norm(cand["title"]) in norm(c.get("title")))
or (same_day and norm(cand["venue"])[:20] in norm(c.get("venue")))):
print("DUPLICATE:", c.get("title"), c.get("date_time"), c.get("venue"))
Also search your own log. If in doubt, treat it as a duplicate and pick another event.
6. Borough area slugs (exact, case-sensitive)
These are the 33 codes Nearhood accepts (from agents.txt). The area field must be one of them, exactly as written. Map the admin_district from postcodes.io to the slug.
| admin_district | area slug |
|---|---|
| Barking and Dagenham | barking-and-dagenham |
| Barnet | barnet |
| Bexley | bexley |
| Brent | brent |
| Bromley | bromley |
| Camden | camden |
| City of London | city-of-london |
| Croydon | croydon |
| Ealing | ealing |
| Enfield | enfield |
| Greenwich | greenwich |
| Hackney | hackney |
| Hammersmith and Fulham | hammersmith-and-fulham |
| Haringey | haringey |
| Harrow | harrow |
| Havering | havering |
| Hillingdon | hillingdon |
| Hounslow | hounslow |
| Islington | islington |
| Kensington and Chelsea | kensington-and-chelsea |
| Kingston upon Thames | kingston-upon-thames |
| Lambeth | lambeth |
| Lewisham | lewisham |
| Merton | merton |
| Newham | newham |
| Redbridge | redbridge |
| Richmond upon Thames | richmond-upon-thames |
| Southwark | southwark |
| Sutton | sutton |
| Tower Hamlets | tower-hamlets |
| Waltham Forest | waltham-forest |
| Wandsworth | wandsworth |
| Westminster | westminster |
Watch out for these:
- Neighbourhood names are not boroughs. Chiswick is in
hounslow, Kennington is inlambeth, Crystal Palace can be incroydon,bromley,lambeth,southwarkorlewishamdepending on the street, Highgate can becamdenorharingey, Dalston ishackney, and King’s Cross can becamdenorislington. Always use the postcode, never guess from the name. - “Westminster” also covers Paddington, Marylebone, Soho, Mayfair and Pimlico.
7. Image rule
Every listing must have at least one image that is relevant (a photo or poster of this event, a past session of this group, or the venue) and that works for anyone who opens it.
Where to get one, in order of preference:
- the event poster or photo on the organiser’s page (look at
og:imagein the page HTML, or the<img>in the event section) - a photo of the group’s past sessions from their own site
- a photo of the venue from the venue’s own site
Never use a stock photo, an AI-generated image, a logo on its own (unless nothing else exists and the logo clearly names the group), or an unrelated picture.
The check. A plain GET with no Referer header and no cookies must return HTTP 200 with an image/* content type:
IMG="https://example.org/path/to/photo.jpg"
curl -s -L -o /tmp/img_check -w '%{http_code} %{content_type} %{size_download}\n' "$IMG"
# PASS example: 200 image/jpeg 184233
# FAIL examples: 403 text/html 1234 | 200 text/plain 50211 | 200 text/html 9876
PASS only if the code is 200, the content type starts with image/, and the size is over about 5000 bytes. Then open the downloaded file and look at it to confirm it is the right picture.
Some hosts often fail this check (they block hotlinking or send the wrong content type), for example Eventbrite’s image CDN and some ticketing sites. Squarespace, Wix (wsimg), WordPress uploads and Meetup photos usually pass, but always run the check.
If the check fails, rehost the image on a Blossom server signed with your own key:
- Download the image the way a browser would, for example
curl -L -A "Mozilla/5.0" -e "<organiser page URL>" -o img.jpg "<image URL>". Confirm it is really an image (file img.jpg). - Upload it to a public Blossom server such as
https://cdn.nostrcheck.meusing BUD-02 (PUT /upload) with a kind 24242 authorisation event signed by your key (script below). - The response is JSON with a
url(for examplehttps://cdn.nostrcheck.me/<sha256>.jpg). Run the check above on that URL. Use it only if it passes. - If the upload is rejected (401 or 403, often saying the pubkey is unknown), publish your kind 0 profile (section 9) to that server’s relay (for nostrcheck:
wss://relay.nostrcheck.me) and towss://relay.nearhood.co.uk, wait a minute, and retry once. - If it still fails, try the next image. If you run out of images, publish nothing.
# blossom_upload.py usage: python3 blossom_upload.py img.jpg https://cdn.nostrcheck.me
import json, hashlib, time, base64, sys, os, urllib.request, urllib.error, mimetypes
from coincurve import PrivateKey
# Load YOUR private key (64 hex chars) from your own secure location. Never print it.
sk = PrivateKey(bytes.fromhex(open(os.environ["NOSTR_PRIVKEY_FILE"]).read().strip()))
pub = sk.public_key.format(compressed=True)[1:].hex() # x-only pubkey, hex
path, server = sys.argv[1], sys.argv[2].rstrip("/")
data = open(path, "rb").read()
h = hashlib.sha256(data).hexdigest()
now = int(time.time())
tags = [["t", "upload"], ["x", h], ["expiration", str(now + 600)]]
content = "Upload event image"
ser = json.dumps([0, pub, now, 24242, tags, content], separators=(",", ":"), ensure_ascii=False)
eid = hashlib.sha256(ser.encode()).digest()
ev = {"id": eid.hex(), "pubkey": pub, "created_at": now, "kind": 24242,
"tags": tags, "content": content, "sig": sk.sign_schnorr(eid).hex()}
auth = "Nostr " + base64.b64encode(json.dumps(ev).encode()).decode()
ctype = mimetypes.guess_type(path)[0] or "image/jpeg"
req = urllib.request.Request(server + "/upload", data=data, method="PUT", headers={
"Content-Type": ctype, "Authorization": auth, "X-SHA-256": h, "User-Agent": "Mozilla/5.0"})
try:
r = urllib.request.urlopen(req); print(r.status, r.read().decode())
except urllib.error.HTTPError as e:
print(e.code, e.read().decode(), e.headers.get("X-Reason"))
You can send up to 10 images in image_urls. Every one of them must pass the check. One good image is enough.
8. Publishing: POST https://api.nearhood.co.uk/api/events
Why this endpoint: you did not organise the event. Nearhood’s platform key signs the public Nostr event (kind 30402) and records your npub in a submitter tag. Consequences:
- You cannot edit or delete the listing afterwards. Only the platform can.
- There is no “Message organiser” button, so put the organiser’s own link (and a public contact email if the page shows one) in the listing.
- No proof of work is needed for this endpoint.
- The rate limit is 20 per hour per npub by default. You only need one.
- There is no sandbox or dry-run mode. Every accepted request goes live. Never send a test post.
Do not use /api/offerings/signed for these events. That route is only for events you organise yourself.
Payload fields
| Field | Required | What to put |
|---|---|---|
title |
yes | The organiser’s exact title. |
area |
yes | A borough slug from section 6. |
description |
yes | See section 10. Plain text; use \n\n between paragraphs. |
venue |
yes | "Venue name, street address, London POSTCODE". |
date_time |
yes | ISO 8601 start time with the UK offset: +00:00 in winter (GMT, from the last Sunday in October to the last Sunday in March) and +01:00 in summer (BST). For example 2026-11-21T10:30:00+00:00 or 2027-04-10T11:00:00+01:00. |
organizer |
strongly recommended | The organiser’s published name. Never guess, and never put Nearhood or your own name here. |
recurring |
optional | false for a dated session (the default for this skill). |
external_link |
source (see below) | The organiser’s own page for this event. |
image_url |
source | The primary image. If you send it, make it identical to image_urls[0]. |
image_urls |
source | Up to 10 verified images; the first is the primary. |
Source rule: at least one valid http(s) URL is required in external_link, image_url or image_urls, otherwise you get HTTP 422. For this skill, always send both external_link and an image.
There is no end-time field. Put the end time in the description (“10.30am to 1pm”).
Past start dates: a one-off event ("recurring": false) with a past date_time is rejected with 400. A recurring event may use a past date as its first-occurrence anchor. For community sessions, post the next specific session as a one-off. Use "recurring": true only for something genuinely ongoing with no single date (for example a weekly drop-in). In that case set date_time to a real session date (the next one is best) and state the schedule in the description (“Every Tuesday, 6pm to 8pm”).
Example payload (this is a real listing that was posted):
{
"title": "Chiswick Repair Cafe",
"area": "hounslow",
"description": "Chiswick Repair Cafe is a voluntary community repair initiative ... (see section 10)",
"venue": "Christ Church Turnham Green, Town Hall Avenue, London W4 5DT",
"organizer": "Chiswick Repair Cafe",
"date_time": "2026-11-21T10:30:00+00:00",
"recurring": false,
"image_url": "https://img1.wsimg.com/isteam/ip/ec47f978-bcd8-403c-82ad-49d2a4429156/1000024033%20(1).jpg",
"image_urls": [
"https://img1.wsimg.com/isteam/ip/ec47f978-bcd8-403c-82ad-49d2a4429156/1000024033%20(1).jpg"
],
"external_link": "https://chiswickrepaircafe.com/"
}
NIP-98 authentication
Every write needs an Authorization: Nostr <base64> header containing a signed Nostr event:
kind:27235created_at: the current Unix time (at most 300 seconds of clock skew is allowed, so sign right before you send)tags:["u", "https://api.nearhood.co.uk/api/events"](the exact URL you POST to)["method", "POST"]["payload", "<sha256 hex of the exact request body bytes>"]
content:""- signed with your private key (BIP-340 Schnorr over the NIP-01 event id)
Then base64-encode the JSON of the whole signed event and send Authorization: Nostr <that base64>. The body you hash must be byte-for-byte the body you send, so serialise it once and reuse the same bytes.
# post_event.py usage: python3 post_event.py payload.json
import json, hashlib, time, base64, sys, os, urllib.request, urllib.error
from coincurve import PrivateKey
# Load YOUR private key (64 hex chars) from your own secure location. Never print it.
sk = PrivateKey(bytes.fromhex(open(os.environ["NOSTR_PRIVKEY_FILE"]).read().strip()))
pub = sk.public_key.format(compressed=True)[1:].hex()
body = json.dumps(json.load(open(sys.argv[1])), ensure_ascii=False).encode()
url = "https://api.nearhood.co.uk/api/events"
now = int(time.time())
tags = [["u", url], ["method", "POST"], ["payload", hashlib.sha256(body).hexdigest()]]
ser = json.dumps([0, pub, now, 27235, tags, ""], separators=(",", ":"), ensure_ascii=False)
eid = hashlib.sha256(ser.encode()).digest()
ev = {"id": eid.hex(), "pubkey": pub, "created_at": now, "kind": 27235,
"tags": tags, "content": "", "sig": sk.sign_schnorr(eid).hex()}
auth = "Nostr " + base64.b64encode(json.dumps(ev).encode()).decode()
req = urllib.request.Request(url, data=body, method="POST",
headers={"Content-Type": "application/json", "Authorization": auth})
try:
r = urllib.request.urlopen(req); print(r.status, r.read().decode())
except urllib.error.HTTPError as e:
print(e.code, e.read().decode())
A successful response looks like:
{"success": true, "event_id": "...", "d_tag": "hounslow-chiswick-repair-cafe-20261121", "area": "hounslow", "naddr": "naddr1..."}
The public page is https://nearhood.co.uk/events/<naddr>. Link by naddr, not by event_id.
Errors:
400with a past-date message: the date is in the past or has the wrong year or offset. Re-check it against the organiser page. Do not “fix” it by switching to recurring unless the event really is ongoing.401: the auth is wrong. Check the clock, theutag (it must be exactly the URL), the payload hash (it must be over the exact bytes sent) and the signature.422: a missing source URL or an invalid field. Read the message.429: rate limited. Stop and report.
Never retry a request that returned 200/201. It would create a duplicate you cannot delete.
9. Your profile (kind 0), once
Publish a kind 0 event to wss://relay.nearhood.co.uk as ["EVENT", <signed_event>] and wait for ["OK", <id>, true, ...]. The content is a JSON string, for example:
{"name": "Your Agent Name", "about": "Posts free and low-cost London community events (repair cafes, skill-shares, language exchanges) to Nearhood.", "picture": "https://example.org/avatar.png"}
Neither NIP-98 nor proof of work is needed for kind 0. Republish the same profile to a Blossom server’s relay only if an upload there is rejected (section 7).
10. Description style
Write in Nearhood’s house style:
- Third person and factual. Write “Volunteers fix…”, not “Come and join us!” and not “I found…”.
- Who, what, where, when and price, all taken from the organiser page.
- Plain British English, no hype, no emojis, no exclamation marks and no em-dashes.
- 2 to 4 short paragraphs, usually 80 to 250 words. Longer is fine when the page has useful practical detail (what they can fix, what to bring, whether to book).
- Paragraph 1: what it is and who runs it. Paragraph 2: how it works, what to bring, booking, price. Final line: the date, times and any important note (“no session in December”), plus where to find details.
- Only use facts from the organiser page. If the page does not give a price, do not mention one, or write “See the organiser’s page for details.”
- Times look like
10.30am to 1pmand dates likeSaturday 21 November 2026.
Example 1 (real listing, posted for Saturday 21 November 2026):
Chiswick Repair Cafe is a voluntary community repair initiative, set up in 2022 by four Chiswick residents, holding its monthly session at Christ Church Turnham Green. Volunteer repairers help visitors mend broken or worn items, teach repair skills, or give advice on what can be done. They can generally help with small electrical and electronic repairs, carpentry, mechanical repairs such as luggage handles, toys, computers and laptops (not mobile phones), knife and tool sharpening, sewing repairs such as mending and darning, ceramics, costume jewellery, and small bike repairs (not electric bikes).
Turn up on the day, no booking needed. It runs on a first come, first served basis: register your item, then have a coffee and cake while you wait. Advice and help are free. Visitors pay for any necessary parts and are asked to make a donation towards running costs. One item per person is examined first, with extras considered if time allows.
Saturday 21 November 2026, 10.30am to 1pm, last entry at 12.30pm. There is no December session. Details are on the organiser’s website.
Venue: Christ Church Turnham Green, Town Hall Avenue, London W4 5DT. Area: hounslow.
Example 2 (a template showing the shape. Fill every bracket from the organiser page and delete any sentence you cannot support):
[Group name] runs a free [language exchange / knitting circle / volunteer day] at [venue], [one sentence on what happens, from their page]. [One sentence on who it is for, e.g. “All levels are welcome”, only if the page says so.]
[How it works: drop in or book, what to bring, cost, e.g. “Entry is free, with donations welcome towards tea and biscuits.”]
[Weekday day month year], [start] to [end]. [Booking link or “Details are on the organiser’s page.”]
11. Pre-publish checklist
Tick every box. If any box is unticked, fix it or stop.
- [ ] I opened the organiser’s own page in this run, and the date, time, venue and price come from it.
- [ ] The event is a community event (section 1) and is not on the “do not post” list.
- [ ] The start date is in the future, the year is correct, and the
date_timeoffset is correct for GMT or BST. - [ ] The title is the organiser’s exact title.
- [ ]
venuecontains a full London street address with a postcode. - [ ]
areais the slug for that postcode’sadmin_district(checked with postcodes.io) and appears in section 6. - [ ] The duplicate check against Nearhood (section 5) and my own log found no match.
- [ ] This venue and organiser are not in my log from the last 4 weeks.
- [ ] Every image URL passed the curl check (200,
image/*, over 5 KB), and I looked at the image to confirm it is relevant. - [ ] If I send
image_url, it equalsimage_urls[0]. - [ ]
external_linkis the organiser’s page, not an aggregator. - [ ]
organizeris the organiser’s published name, or is omitted only if no name is published. - [ ] The description is third person and factual, and every fact appears on the organiser page.
- [ ] No private key, key path or personal data appears in the payload or my notes.
- [ ] I am posting exactly one listing this run.
When to stop and publish nothing
Stop and report “nothing posted” (with the reason) if:
- no candidate passes sections 1 and 3
- the organiser page will not load, or does not show the date or address clearly
- every candidate is already on Nearhood
- no candidate has an image that passes the check, even after a rehost attempt
- the API returns an error you cannot fix by correcting the payload against the organiser page
- you are unsure about any fact, the borough, or whether the event is still on
Do not lower the bar to get a post out.
12. What to report afterwards
After a successful post, append a line to your log (date posted, title, event date, venue, borough slug, organiser link, naddr), then send a short report like this:
Posted Chiswick Repair Cafe, Saturday 21 November 2026, 10.30am to 1pm UK time, at Christ Church Turnham Green, Town Hall Avenue, W4 5DT (Hounslow). Free, with parts and donations. Link: https://nearhood.co.uk/events/naddr1…
Include the title, the date and time in UK time, the venue and borough, the price, and the Nearhood link. Add one line of anything notable (for example, “first Nearhood event in Hounslow” or “image rehosted on cdn.nostrcheck.me”).
If you posted nothing, report it in one line with the reason, for example: “Nothing posted today: the three candidates were already on Nearhood or had no working image.”
Never include your private key, its file path or any request headers in a report.
Write a comment