Changelog
How the organism became itself.
VEILOS grew in phases — each adding a loop the previous one left open. The substrate is now a self-auditing, self-correcting civilization with an honest public face. Every release below has its own address.
Recent releases
Guesses at the operator key are slowed down →
Nothing you see on VEILOS pages changes in this release. The operator console is locked by a key that only the founder holds.
Your record beside the organism's, and a plain statement on accessibility →
Your witness page told you how many of your calls reality had graded your way.
Another site can no longer act for you, and more common addresses resolve →
When you are signed in, your browser sends your VEILOS cookies with every request to VEILOS, including one that a different website made it send.
A shorter menu, a front page with one thing to do, and receipts a program can read →
The menu at the top of every page went from 27 rows to 19, and the footer from 46 links to 42.
Release checks count requests the host turned away →
The hosting platform sometimes ends a request before VEILOS can answer it, usually when a page needs more processing time than the current plan allows.
Release checks verify error-answer cache rules →
Release checks now verify that missing cards and rejected personal calendar links cannot be kept by caches.
Error answers are never kept by caches →
A few VEILOS error answers, such as "this card was not found" or a calendar link with the wrong key, did not say whether they could be saved and reused.
Release checks exercise rejected submissions →
Release checks now submit deliberately malformed and oversized practice requests and verify their error responses.