e-five

I agree with you that `type` should be pulled out because it's exclusive to `threads` so it being in the url for `microblogs` and not doing anything is confusing

Took this for a spin and it looks good to me, do you still have any outstanding work? I was going to say if the redirect stuff made things more...

One very minor thing, maybe not worth holding this up, but it looks like `?type=` is kept in the header nav bar when set and selecting microblog. For example on...

Not sure I agree with actually generating random images and storing them, that seems like a large cost for instances with tons of users where it already is prohibitively expensive...

Even if this was moved to comments vs likes I think we still don't need every single update always as the check is >24h, it seems like we shouldn't landrush...

When your queues fall behind and you try to catch up, _every single event_ locks the magazine row to update this. It most likely causes deadlocks as debounced has shown...

@BentiGorlich want to make sure this seems acceptable to you after the change

I'll work on making the changes suggested

definitely super look over me here as this is outside my wheelhouse, kind of guessing based on grabbing payloads from past logs shared in matrix, as obviously this is difficult...

I think I've handled the situations as described now where it will update the value when a create or an announced create after 3 hours