From 3c4d9e1cac2f3a6dde24d8940cd5983648b89d5a Mon Sep 17 00:00:00 2001 From: grunfink Date: Fri, 10 Apr 2026 17:14:29 +0200 Subject: Updated RELEASE_NOTES. --- RELEASE_NOTES.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) (limited to 'RELEASE_NOTES.md') diff --git a/RELEASE_NOTES.md b/RELEASE_NOTES.md index 6c10908..a413ce7 100644 --- a/RELEASE_NOTES.md +++ b/RELEASE_NOTES.md @@ -4,7 +4,9 @@ Changed default: for newly created instances, `disable_inbox_collection` is set to `true` (see `snac(8)` for more information). The reason is because it seems to be used for harrasing people. -Changed default: for newly created instances, `disable_history` is set to `true` (see `snac(8)` for more information). The reason is because archived history files don't change when posts are deleted or modified, and they always have been an ugly kludge. +Changed default: for newly created instances, `disable_history` is set to `true` (see `snac(8)` for more information). The reason is because archived history files don't reflect reality after posts are deleted or modified (they always have been an ugly kludge). + +Changed default: in previous versions, posts with a scope of `unlisted` were shown in public pages and RSS feeds. Now, they are no longer shown. If you want to get back to previous behaviour, use a new toggle in the User Settings section (see `snac(1)` for more information). New admin configuration option: if the `purge_static` value is set to `true` in `server.json`, each user's static directory is explored and those files there that are no longer attached to any post or referenced anywhere are deleted. See `snac(8)` for more information about those cases where you may not want to enable this option. -- cgit