It’s been some time since my last update. We’ve just been dealing with some life issues that have impacted development. This isn’t ideal but we use three times as learning opportunities. We’ve been working closely with the development team of ActivityPods and attending weekly meetings with them. We feel it’s important to be on the same page and have open dialogue. ActivityPods 2.0 should be here soon!

#Memory# We have started working on the client this week. The goals are to have native clients for Android and iOS. This also includes their respective devices such as iPadOS, macOS, watchOS and visionOS. The clients will be compatible with the ActivityPub specs and mastoapi. This will allow access to various fedi platforms and users. We do intend to have web app but that is for later down the road. We plan to do a slow rollout to get user feedback by having a closed beta and then an open beta.

#Platform#

This will answer is taking more work and time. What we have decided to do is fork Mastopod and spin up a Mastodon instance. This will provide the team and users with an open simulation of what it will be like on Memory platform. As we are taking a different approach than what has been done on fedi we want to get this right and provide the best experience possible.

Features in the wild## Some of the features that we have planned are currently available on Fediverse client Sora. A couple such features are Transformer Language Model thread summarisation. This is helpful for context and assists instead of reading a really long thread or it may create an interest in diving into the thread. The other feature is P2P video calling which allows users using the Sora app to make encrypted video calls.

Updates##

Going forward we will start providing weekly updates Thursdays or Fridays