SQLalchemy does that. One advantage of the Django syntax is that it can be (pretty much) directly dropped into a query string on any admin page or DRF query and filter the results. E.g. the admin page for all the events after noon today:
admin/event/?end__gt=2026-07-26T12:00:00
Being able to do ad-hoc queries using the same paradigm your app queries are written in, and then pass urls around with those queries included (e.g., quick one-off reports or answers to client questions) is so helpful.
IME crosswords traditionally say "Word before...". Also thanks for the game, I love it and was excited you used one of my submitted clues a few months ago.
Can you please make it (and keep it) so that friendships are symmetrical? I.e., "friend" rather than "follow". IMO that's the enshittification inflection point of Facebook.
Not email; social networking. Symmetrical just means the relationship is the same from both sides. Imagine a two-way "friendship" relationship (old-school Facebook) vs. a one-way "following" relationship (more recent Facebook, Insta, Twitter, etc.).
I'm surprised there's not more discussion here and in general about symmetric- vs. asymmetric-relationship networks. Facebook worked in the beginning because relationships were symmetric and there was no concept of getting "follows" -- friendships are modeled after real life ones, where the friendship is between two people.
I can see why the big networks moved away from that: pushing "content" has a lot more friction when relationships are symmetrical. What I don't understand is why there is no upstart trying to bring that back.
I'm working on a self-hostable replacement for Google Timeline, which is being discontinued. It includes a web app to view my timeline and an Android app to send tracking pings to the server. It also includes an import function for exports of your Google Timeline data so that your historical data from that can be integrated as well. I'm planning on open-sourcing both the web app and the POC Android app early next month.
Knowing the rules and 'seeing' the ways that pieces can move are different things. I could see this being helpful to someone who has a working knowledge of the ways pieces can move, but hasn't yet built their skill of visualization thereof.
Why call it "name and shame" and not just "name"? Be honest about the behavior and let people judge for themselves whether the behavior is shameful. If an action is above-board, the actor should not mind being named.
Require that a person besides the author has to review code changes before they are allowed into a code base. Do it under the guise of 'transparency' or 'being on the same page'. Don't let him see your post.
Being able to do ad-hoc queries using the same paradigm your app queries are written in, and then pass urls around with those queries included (e.g., quick one-off reports or answers to client questions) is so helpful.