@ -26,13 +28,16 @@ Place a `config.json` file in the same directory that looks like this: (below ar
],
"blacklist": [
"youtube.com"
]
],
"whitelist": []
}
```
- baseURL, with trailing slash: base access point, used in approval/admin panel
- adminEmail, the e-mail address to send notificaions to. If absent, will not send out mails. **uses 127.0.0.1:25 postfix** at the moment.
- port, host: http server params
- token, allowedWebmentionSources: see below, used for authentication
- blacklist: blacklist domains from which we do NOT send to or accept mentions from.
- blacklist/whitelist: domains from which we do (NOT) send to or accept mentions from.
- utcOffset: offset in minutes for date processing, starting from UTC time.
If a config file is missing, or required keys are missing, a warning will be generated and default values will be used instead. See `common/config.go`.
@ -126,7 +126,7 @@ It will attempt to auto-discover them with a HEAD call, in the following order:
3. `/feed`
4. `/feed/index.xml`
If none provied a status of 200 with content-type `application/xml`, it will abort and log an error.
If none provied a status of 200 with a Content-Type that contains `xml`, it will abort and log an error.
Note that this _requires your site to be on HTTPS_!!
@ -188,7 +188,21 @@ Database migrations are run using the `-migrate` flag.
Since Go-jamming still supports Pingbacks, spam could be an issue. However, if the URL doesn't contain a genuine link, the mention will be immediately dropped.
Still, spammers always find a way and sometimes even create fake blog posts with real links to your blog. In that case, simply add the domain to the `blacklist` in `config.json`.
Still, spammers always find a way and sometimes even create fake blog posts with real links to your blog.
### Mentions _in moderation_
Go-Jamming employs a `whitelist` and `blacklist` system. By default, all mentions end up in a moderation queue, another database that will not pollute the mention db.
Each mention has to be manually approved. An e-mail to `localhost:25` (a local Postfix) will be sent out with approve/reject links, if configured. Otherwise, the endpoint `/admin/{token}` is the dashboard where you can approve/reject from time to time: