

AFAIK, there is no criminality (even in Russia) for homosexuality or religion.
You don’t know shit about fuck.


AFAIK, there is no criminality (even in Russia) for homosexuality or religion.
You don’t know shit about fuck.


Peter Thiel explicitly sided with Sauron in an interview, because “things work in Mordor, while outside Mordor it’s all wishy-washy and environmental”.
I mean, I still consider this page cool. It seems to have originated in 2016, and IMO it’s not quite the 90s ‘dancing baby’ design or Myspace, but instead has a definite whiff of Tumblr art circa early-mid 2010s. I liked psychedelic-ish Tumblr art, it gave a whimsical perspective on life.


It’s likely much faster to fetch the common feed from the database cache or prepared cache like Redis, and apply all this additional data in the app, than do uncached joins. So I’d hope that the apps do this. Especially since you say they use Redis, which of course doesn’t do joins and such, unless something changed in the past years.


To add to other answers, the result for the ‘all’ feed is likely to be cached, either explicitly by the server app or implicitly by the database. Personal feeds are less likely to be cached, since they’re only used by individual users.


Strictly speaking, the db might be looking in an index to choose rows by the communities — but using such a condition is pretty much guaranteed to be slower than not using it, anyway.
The actual answer depends on the actual database organization, of course. Ideally the whole database should be organized around frequent queries.
Merriweather is great for longer texts. I use it in all book reader apps.
Anonymous Pro is my coding font of choice.