I read you migrated to an S3-based git backend — would love to hear more about that story and how you managed the migration. Did you migrate all repos at once or on demand?
Also chapeau for the quick turnaround, I logged into lovable and saw the incident and you didn't let GitHub slow you down :-)
The Feature Macros proposal is only adding macros and vars to Clojure---the reader isn't modified at all. Since all of the things you mentioned are reader macros (as you pointed out), Feature Macros never even see them, so they won't be affected in any way. (Reader macros are expanded before regular macros are, so regular macros don't see things like `#(...)`, they see `(fn [] ...)`.)
The great point made in the README is that we can't generate feature expressions. With feature macros we can have macros that generate cross-platform code. That's big in my mind.
That hasn't been a problem with reader macros in the past since you don't need to generate `#(...)` if you have `(fn [] ...)`.
I don't understand when I would ever want to generate a feature expression. The goal is to generate platform-specialized code. You never have to generate code that generates platform-specialized code!
HN does "voting ring detection" IIRC and penalizes heavily news which are upvoted by many people in a short time. There is some logic to differentiate between voting rings and genuinely very interesting articles, but I don't know any specifics. Anyway, posting a link to HN submission anywhere else than HN has a good chance of making this submission dead.
I would implement cassowary (the constraint solving algorithm) in Clojure/Clojurescript. And then I would try to find a good way to make it usable for layouting in React-based environments. I think it could be done in a shorter timespan.
Also chapeau for the quick turnaround, I logged into lovable and saw the incident and you didn't let GitHub slow you down :-)