@coffeegeek Could @Gargron implement/reccommend a solution for your issue Coffeegeek? Is it a known issue with the mastodon development team?