![](https://subsubd.com/pictrs/image/36f365cd-a56a-4120-b2ba-945370fcfe4b.png)
this is a new comment to an old comment
this is a new comment to an old comment
this is a new comment
that’s fixed… now are comment reply avatars still yuge?
avatars still yuge?
bells and whistles
cool post, bro
This is absolutely amazing!
deleted by creator
I’m writing a frontend in flask right now and something like this would be a godsend. Trying to dig not just the endpoints out of the lemmy/lemmy-ui/lemmy-js-client but also figuring out responses forenough variations has been like pulling teeth. Only thing more helpful would be an openapi spec.
another test post
now close this one afterwards
and close it directly afterwards
new top level comment insert after maybe?
deleted by creator
new top level comment worky?
I’ll be in the cold, cold ground before I recognize Missourah!
admin and mod tags now maybe?
yeah, I just spent the last hour writing some python to grab all the mappings via the pict-rs api. Didn’t help that the env var for the pictrs api token was named incorrectly (I should probably make a PR to the Lemmy ansible repo). EDIT: Nevermind, seems there is one already! https://github.com/LemmyNet/lemmy-ansible/pull/153