how the fuck do fedi people work with this shit dude. every single frontend out there is just Fundamentally Fucked in so many ways that make it impossible to understand the context of any conversation. this is not conducive to Reading Posts at all. is this why the fediverse is so dysfunctional? i'd believe it

@ruby it's SO BAD, this is exactly the sort of shitty ux that got me to leave twitter lmao

@ruby im biased because ive been there so long but like... im gaining a new appreciation for the mastodon/glitch-soc frontend right now lolsob

@ruby i’m always sad that opentween never ended up supporting mastodon. just want my client to look like a fuckin’ mail/NNTP client from 1996

@nora if you have particular thoughts, i'd love to hear them. i imagine a large part of what i'm experiencing is culture shock, coming from someone who never used twitter or fedi, but spent the past almost 2 years on cohost

@nora @ruby …wait, out of band tags are in the spec? I somehow did not know that, and now I’m wondering if we could do something with that (though it probably would require some integration effort)

@nora

• yeah, the lack of boosting here is a little odd. certainly was not an issue on cohost. i suspect with how young the network is, we’re all in the bootstrapping phase of discovery, and hence we aren’t coming across a lot of things to boost. bit of a chicken and egg problem, that one. maybe relays will help
• interesting on the cw/subject distinction. cohost had both of these implemented as first class citizens on a post - you could add content warnings to a post, and all posts had an (optional) title, which i imagine maps neatly onto the subject usecase. unfortunate that we don’t have 2 distinct places for both of those here
• i did not know that out-of-band tags were even in the AP spec. that may be useful if we can get existing software to make use of those, chucking tags in the middle of a post is a little jarring for readability imo, and putting them at the end of the post feels like a workaround in some ways

@nora @ruby that actually makes sense. I’d still check if the instance software doesn’t do additional Weird Things with the text tho

@elena @ruby the more i poke around at anything that isn’t cohost the more i think you’re right. we should just go back to nntp. it’s peak communication ux.

@exerian @ruby this is what peak performance truly looks like