@feld It's not really a problem. More of a trade-off. I'm considering copying Pleroma's way of not caring. It's about emoji react counts. To update the count, we SELECT the object, modify, then UPDATE. But if two processes SELECT at the same time, the later one will overwrite the prior one. The solution is to lock it, or something? Doesn't seem worth the added complexity. Or use Redis, which actually supports Sets, which really doesn't seem worth it. So what it's doing is actually fine. Unlike when Pleroma got Webfingered yesterday. 😂
@alex no need to lock it; just use an Agent. If we ran an Agent for this and had all operations push a change into its inbox you avoid the entire issue
Had a dream I ate a piece of steak at a venue. I literally couldn't stop myself. Then I saw the entire carcass fit on my plate. Then some guy got up and started shouting, "it's veal! these are baby cows! This is highly unethical!" And I started shouting back, "what is the difference between a baby cow and an adult cow?! Huh?! Huh?!"