Eggyhead@kbin.social to /kbin meta@kbin.social · 1 year agoIs there a way to deal with crap like this yet?media.kbin.socialimagemessage-square26fedilinkarrow-up10arrow-down10
arrow-up10arrow-down1imageIs there a way to deal with crap like this yet?media.kbin.socialEggyhead@kbin.social to /kbin meta@kbin.social · 1 year agomessage-square26fedilink
minus-squarePabloDiscobar@kbin.sociallinkfedilinkarrow-up1·edit-21 year agoIf you are subscribed to the same mag 3 times, well it’s on you. You want volume you have it. What is possible is to filter through a script and only show the local one.
minus-squareplantstho@kbin.sociallinkfedilinkarrow-up1·edit-21 year agoA possibly nice UX could be clients grouping all crossposts from the same author together in a little stack, but showing the local or oldest version “on top”
minus-squarephoenixdigita1@kbin.sociallinkfedilinkarrow-up1·edit-21 year agoInitially I thought you were saying they subscribed to a single magazine from the same instance three times and was thinking “Is that even possible?”. Then I had a closer look and realised they were 3x different magazines on different instances but all with the same name. Makes sense that it would appear 3x times.
If you are subscribed to the same mag 3 times, well it’s on you. You want volume you have it.
What is possible is to filter through a script and only show the local one.
A possibly nice UX could be clients grouping all crossposts from the same author together in a little stack, but showing the local or oldest version “on top”
Initially I thought you were saying they subscribed to a single magazine from the same instance three times and was thinking “Is that even possible?”.
Then I had a closer look and realised they were 3x different magazines on different instances but all with the same name.
Makes sense that it would appear 3x times.