The new Mutual Following feature was written in less than 100 LoC total for both the backend and mobile app.

Here's how we did it:
1) API invokes a new FollowerService method which is a redis zinterstore set of account ids that are hydrated on the controller and returned as an array of Account objects (max 24)

2) The mobile app uses the simple Fisher-Yates algorithm to shuffle and return 3 accounts which are displayed on profiles

Less than 1 hour of work for an exceptional feature, not bad 😎

@TuxOnBike Yes, we agree, and are working on a solution to improve this!

We will be consulting the community before we proceed as we want to get this right the first time.

Thanks for the awesome feedback and kickstarting the discussion around this improvement, we will be reaching out to you to get your opinion on our proposed solution before we announce it publicly.

We're shipping a new related hashtag feature to our mobile app!

Related hashtags are shown on the hashtag feed screens and are manually curated by admins!

PR: https://github.com/pixelfed/pixelfed/pull/4777

#pixelfedEngineering

We're back 😎

Check out our blog if you haven't already!

https://pixelfed.blog

@jk Hi, we just tested account following from pixelfed.social <-> lain.com and it works as expected.

Are you running the latest pixelfed commits that disable COSTARS? That might have caused the issue.