Skip to content
View in the app

A better way to browse. Learn more.

ernestdefoe.online

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.
ernestdefoe.online

Extensions, themes & support for Flarum and Invision Community

Vibe coding for the community web. Report a bug, request a feature, or dig into the source — this is where the tools you use get built, in the open.

We do custom Bespoke Invision Community apps. If you have an idea for something you want then use the contact form to get in touch with us.
Knowledge base

Things that cost me a day, so they cost you none

Working notes from building Invision Community and Flarum applications. Mostly the failures that give no error at all — the ones where everything installs cleanly and quietly does the wrong thing.

92 articles

Invision Community 5

86 articles

Extensions and contracts

39

What each extension point is for, what it must declare, and what happens when it is wrong — which is usually nothing visible.

Languages and text

5

The string table, translation, and the places where text does not appear where you expected it to.

Theming, templates and forms

9

Theme hooks, CSS that survives both colour schemes, and building forms that do not throw on render.

Background work and scheduled tasks

5

The queue system, work that has to happen after the response, and jobs that finish without doing anything.

Data, settings and storage

11

The database layer, settings, tags, file storage, and backing up a live site.

AI features and expectations

5

What these features do, what they cost, and what buyers reasonably but wrongly assume they do.

Application structure and releases

11

The JSON files an application is made of, versioning and upgrade steps, and testing from the command line.

Realtime, chat and calls

1

WebSocket gateways, relays and the server-side pieces live features depend on — where "it works when I test it" and "it works for your members" are different claims.

Nothing matches that.

Your AI assistant is only as good as what you gave it to read

An AI support assistant on a forum does not know your community, and it does not go and look. It answers from whatever you have given it. Install one on a site with nothing to read and you get an assistant that is confident, general, and wrong about the specifics — while billing you for every answer.

This surprises people, because the same models answer general questions well. The difference is that your members are not asking general questions. They are asking about your settings, your policies and your add-ons.

What "no knowledge base" actually looks like

  • Plausible answers that are wrong for your site. Asked where a setting lives, it describes where that setting lives in a default install, or in a different version, or in software it has confused with yours.
  • Hedging. A well-behaved assistant that has nothing to go on says "check your AdminCP settings", which is not an answer and reads as evasive.
  • Credits spent on nothing. Every one of those non-answers costs the same as a good one.
It does not search the internet on your behalf. Retrieval means searching the documents you supplied and answering from those. No documents, no retrieval — just a general-purpose model guessing about a site it has never seen.

What to write, and it is less than you think

You do not need a manual. You need the answers you are already typing by hand. A useful starting set is:

  • Your ten most repeated support answers. Look at what you have actually replied to in the last month. That is the list.
  • Anything with a non-obvious cause. The problems where the symptom points at the wrong thing are exactly the ones an assistant saves you the most time on — and exactly the ones it cannot guess.
  • Your policies. Refunds, signatures, what gets a warning. These are pure site-specific fact and impossible to infer.
  • Version and setup specifics. Which add-ons you run, what you have deliberately turned off.

Write each one as the answer to a question somebody actually asked, in plain prose. Do not write it as a specification — an assistant retrieves prose far better than it retrieves a table of settings.

Why it is worth the afternoon

An assistant grounded in real answers resolves the repeat questions without you, at any hour, in the member's own words rather than yours. The unglamorous part — writing down what you already know — is the entire difference between an assistant that deflects support and one that generates it.

The test is simple: take the last five questions you answered by hand, and ask the assistant those. If it cannot answer them, it is not going to answer them for a member either.

Related

The same expectation gap applies to other AI features: see Your classifier does not learn, and everyone will assume it does. In both cases the software works exactly as intended, and the disappointment comes from a reasonable but wrong mental model of what it is doing.



User Feedback

Recommended Comments

There are no comments to display.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.