minecraft

dragongirl funky fresh

april et al, several flavors of therian (plural edition)
engineer in training by day, furry artist and "web developer" also by day
adult, occasionally nsfw on main
💜@dragongirlcloaca💜
💜@8akesale💜
avatar by karvakera

last.fm recent played


find me elsewhere
floofy.tech/@starlight

minecraft
@minecraft

in reply to @minecraft's post:

ProtoDot

Hate hate hate hate HATE ASC's stance on this. This idea that you shouldn't be social on a social media site is just so stupid to me. If I'm not doing that, then what the hell am I doing here?

Yeah, it's been said to death at this point, but there's a point where it definitely crosses from "We didn't include these features because they encourage a toxic social media environment" to "We didn't include these features out of personal dislike or didn't want to implement them before going public and we're making it a feature and not a bug".

The whole argument for a lot of the shuttered-off approach to social media design in the name of nebulously "discouraging harassment" or "preventing toxicity" sort of just...falls apart once you realize that most of the excluded features are really non-issues when it comes to harassment. I can excuse not having direct messaging on launch, but it's definitely not a primary vector for harassment when you could just...send logged out anon asks with embedded media up until recently, and block avoiding is practically an intended feature (don't take that at face value, the idea that blocking can't be account-scoped in order to prevent "identifying people's side pages" is just stupid). None of the real issues this site has actually experienced were solved by any of these exclusions of content, so why not just fix what's broken and add what isn't?

And going back to the original topic of anti-social design, yeah, it's exactly what it says on the tin. There aren't really any problems being solved by not having private follower counts or not showing all of the shares or comments on a post. The latter one could maybe be excused on launch as a technically-complex feature, but if I could replicate it completely client-side than it can't be that hard.

And don't get me wrong, I still use cohost first and foremost as just a place to mess around with friends, but there's no proper excuse for why the UX shouldn't be better.


You must log in to comment.

in reply to @minecraft's post:

If this is true, that they broke it and semingly intentionally (?), doesn’t this also go against the “have fun modding the fuck out of the site you technically skilled mfers” stance? Or is that not the point of the “Third-Party Tools” official webpage?

It was removed completely from the API. I guess it's sort of understandable since there were apparently server-side performance issues, but it was my attempt at a solution to a problem that was created because of the lack of any better way to see shares. Still get the feeling that they're not exactly my biggest fans, though (I applied for chutils to be added to the third-party tools page ages ago and never heard back).