Hello, 4clojure problem solvers. You've probably noticed SSL errors on
over the last week. The old decrepit system 4clojure runs on has finally gotten out of date enough that I can't even figure out how to get it recent enough that SSL certs will auto-renew anymore.
In principle I could start from scratch on a new server and move 4clojure over, but I won't. 4clojure has been piggybacking along on a server that I use for personal reasons, and over the years I have less and less reason to keep paying for that server - it's now pretty much just 4clojure costing me an embarrassing amount of money every month because I haven't wanted to disappoint the community by shutting it down. This SSL thing is just what made me finally pull the trigger.
I don't have a specific EOL date in mind, but sometime near the end of the month, since that's the billing cycle. Until that time, 4clojure still works, as long as you don't mind clicking through the security warnings - it really is still me hosting the site, and since the connection is still HTTPS (albeit with an invalid cert) I think that means your data is still safe. If you have solutions to problems you're proud of, you've still got some time to print them out and put them up on your refrigerator.
I'm not seeking new maintainers. I'd feel uncomfortable handing over a database with so many email addresses and password hashes in it to anyone. The service has had a good run - just over a decade since the
first release. I hope you enjoyed it during that time.