Conversation

Notices

1. Embed this notice
   Fedilab Apps (apps@toot.fedilab.app)'s status on Friday, 10-Feb-2023 06:33:10 JST Fedilab Apps

   in reply to

   • EricCarroll
   • Wes George

   @EricCarroll @wesgeorge
   Filters have been fully reworked on Mastodon 4.0.2
   Afaik Tusky will bring these changes soon.

   • Embed this notice
     EricCarroll (ericcarroll@toad.social)'s status on Friday, 10-Feb-2023 06:33:15 JST EricCarroll

     in reply to

     • Wes George

     @wesgeorge @apps Fedilab android app definitely handles filters & shares them with the web UI, which says filters are at least stored server side.

     I have Tusky too, and it does not show filters. So I assume the client side has to pull the filters from the server & implement the filter in the client layer.

   • Embed this notice
     Wes George (wesgeorge@mstdn.social)'s status on Friday, 10-Feb-2023 06:33:22 JST Wes George

     in reply to

     • EricCarroll

     @EricCarroll confirmed, I am able to make it work on the advanced webUI, but it doesn't appear to exist in Tusky, for example, so it's definitely happening client-side.

   • Embed this notice
     EricCarroll (ericcarroll@toad.social)'s status on Friday, 10-Feb-2023 06:33:23 JST EricCarroll

     in reply to

     • Wes George

     @wesgeorge
     For me I have keywords applied and have the choice of compelely ignore or hide it with an expandable warning. I used the advanced web UI to set them up on instances with recent versions.

     Just looked, android fedilab supports filters too.

   • Embed this notice
     EricCarroll (ericcarroll@toad.social)'s status on Friday, 10-Feb-2023 06:33:24 JST EricCarroll

     in reply to

     • Wes George

     @wesgeorge
     It doesn't? I have keywords filtered on several of my accounts. Is it version dependant?

   • Embed this notice
     Wes George (wesgeorge@mstdn.social)'s status on Friday, 10-Feb-2023 06:33:24 JST Wes George

     in reply to

     • EricCarroll

     @EricCarroll hmm, that'd be great! I thought since they didn't index the full text of posts there'd be no way for keyword mute to work, so I assumed it didn't. Maybe it's being applied directly to the user's stream as it goes past sorta client-side? Like you get the post but your client throws it on the floor so the actual overhead of looking at all text is not on the server?

   • Embed this notice
     Wes George (wesgeorge@mstdn.social)'s status on Friday, 10-Feb-2023 06:33:25 JST Wes George

     So good news/bad news with the impending birdsite API shutdown -
     Bad news- large number of people that are pushing updates from there to here are probably not going to realize that has stopped working and a bunch of accounts are going to go dormant, at least temporarily.
     Good news- we'll stop getting retweets and user mentions from those crossposts that we can't filter because Mastodon doesn't support filtering keywords.