Lady @Lady@cat.family

@coriander okay but you feed it a sub sandwich and it goes “Gomp”

@Taweret@octodon.social @coriander we didn't get all of this stuff implemented into glitchsoc because of time+energy constraints but i feel like filtering was one of the few areas where we actually had very clear user stories about what things were needed and why

but upstream mastodon has never heard of the concept of a "user story" so i guess it's not surprising to see things backslide there

@Taweret@octodon.social @coriander i very specifically remember very specific conversations in 2017 regarding how filtering functionality needed to work, like

• it's good to know that things are being filtered so you don't think federation is broken, although you might want to hide these indicators (for example if you only have one or two filters and it's obvious what everyone is talking about, maybe you don't want the constant reminder that everyone is talking about it)

• sometimes it's good to be able to click through and see why something was filtered, but it shouldn't be blasted on the main timeline for a lot of topics

• sometimes it's good to be able to reveal the thing which was filtered, but some people have CW clickthrough syndrome and would really rather not have that ability for some topics

anyway i guess eugen wasn't paying attention or else forgot. whoops 🤷🏻‍♀️

@djsundog @kemonine i know locally we're planning on patching at least some of the antifeatures (still working on the list…) before we make the jump, but some stuff like the removal of remote actions or defaulting to /explore instead of /about unfortunately mostly affects OTHER instances, so

@aescling on the other hand this could be accomplished with an RSS feed

@coriander @FloatingGhost@ihatebeinga.live it's true