dragongirlsnout

in reply to @minecraft's post:

ProtoDot@ProtoDot3 mins ago

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.

I forgot the characters in the SVG extension icon were actual glyphs until I tried to install it on my work PC that only has Firefox ESR and it used a fallback serif font instead of Atkinson Hyperlegible.

I haven't been listening to it nearly as much as I should be but damn is the SLARPG soundtrack good. The opening/title sequences nearly beat out SPM and the original TTYD for my favourite title screen of all time.

That's definitely possible, and I could probably also wrap it together with options to hide shares and duplicates. That sort of thing is very easy to implement since I have a mutation setup to run a callback for each new post added to the page, and I can make use of React props to skip even touching the API. Glad you like using it!

I knew I was forgetting a feature I meant to add, I swear I remembered writing the module for this but I think it was just the own post checker function for shareTree (RIP). Still, that's literally 99% of the work for hiding your own posts done, so glad I at least got something out of that.