Add an option to open Twitter links using a user specified nitter instance instead

Allow users to set their profile description, display name, header image, profile picture, default post visibility and if new followers must request the follow

Display notes on profiles and allow editing them

Enable users to log in with multiple accounts, browse their timelines and interact with posts

Show, accept and reject follow requests

Provide a setting to hide replies from the timeline

Add capability to create media posts, only allow sending with an image description by default

Allow users to specify a list of CWs that they want to expand automatically

• Find out which backend an account is on
• Add an HOC for components that are only available in specific backends
• Only render features a user can actually use
• (Add option to show all features in case a backend has a feature added but I'm too slow to update the app to show it to their users)

Let people decide if they want to hide whole conversations if they include people they've blocked.

Useful if you want to avoid seeing someone you've blocked mentioned, or to avoid partial conversations popping up on the tl

Make sure the app looks good on tablets

Let users log out of their account

Boosts and favourites for posts

It is possible to upload animated profile pictures and emojos. Other than many clients, FediSqueak actually does support those animations.
That is cool for many people, but may cause discomfort or even seizures for others. We should therefore add an option to disable the display of animated things app wide.

Currently, due to a mismatch in peer dependencies, you need --force to run npm install.
That is not really acceptable and should be fixed.

Currently trying to log into a mastodon instance causes the app to crash.
That should probably not happen.

Allow users to post new posts and replies

When the user leaves the app or switches between views/ timelines their scroll position should be remembered. This is extremely difficult to pull off because we do not know in advance what any given post's height is.

Here's an idea for how it could be implemented:

• Add a height field to posts, it is undefined be default
• When the post is rendered, check if it already has a height field
• If not, get the rendered post's height and store it. This will cause a rerender :(
• Add the prop that allows the Timeline view to figure out how heigh a post is. Check the data index and return the height if given, return 500px otherwise (this is going to be the longest height before a post is cut off)
• Add a scroll listener to the timeline and store the current scroll position
• Add the initialOffset prop to the view with the last value stored by the scroll listener

Implement the local instance timeline

Allow users to schedule posts.
This should be easy to implement as its already supported in the mastodon API.

TODO: check if GoToSocial also has this feature already and if not maybe send them a PR?

Allow users to automatically add a CN to posts that contain specific words or match a regex

Currently the cache is very "greedy", only removing posts when the user clicks the clear cache button in settings. This will lead to caches that become extremely large and slow to load and render.

TODO:

• Figure out a good algorithm to decide which posts to delete from cache
• Check if it makes sense to replace @react-native-async-storage/async-storage with something more performant

The React Native FlatList is not really intended for what we're doing with it (very large lists with entries that do not have uniform height)

Instead of spending tons of development time on working around that limitation, a new implementation would probably be a better idea

Currently the different variables that store weather a user has favorited or boosted a post are pretty buggy. This is due to a combination of API bugs, the way boosts are implemented and the fact that we cache a ton of stuff.

We should consider adding a global deduplicated object that contains post interactions (possibly including weather or not CNs are expanded and more) and read that info from there.

The main issue with this idea is that users might use other clients to interact with posts. In this case we could get the info about those interactions from the API but we don't really know if that info is to be trusted.
Maybe this isn't as big of an issue in reality because people don't actually care that much about what color the favorite Star underneath a post has?

Add a project Code of conduct

Add a CN expanded field to cached post data, so that expanded posts stay expanded even if the user leaves the app or view.

Bonus points for deduplication, meaning if a user has expanded a CN in a notification, all other notifications for that post will also have their CN expanded.

Show incoming notifications

Sometimes half the fediverse likes boosting the same post. That can get annoying.

Add an option to hide specific posts from the user's tl.

Allow users to have a timeline that does not contain any boosts

Allow users to click posts to expand them and show replies as well as the full thread if the post is a reply itself

Currently the timeline is rendered simply by going through all cached posts and rendering an element for it in a large ScrollView. As the app gets more and more features, this will definitely lead to performance issues.

Figure out a good way to only render posts that are actually being shown while still allowing "endless scrolling"

Add a feature to automatically add a CN to all posts that are made by accounts marked as bots

Add themes:

• dark
• light
• Auto default from OS preferences
• cybre (similar to the cybre.space custom css, replaces posts with pings, favs with florps and boosts with relays)

Implement the federated timeline

Allow searching for accounts

Every time the user navigates away from a timeline screen, move a certain amount of posts into cold storage and delete them from hot storage to reduce the size of the FlatList of posts that is rendered.

If if is possible to remove data from the FlatList without loosing scroll position, this could be done regularly in the background.

If the user refreshes or loads more, at first there is a cold storage lookup to get newer/ older posts back into hot storage and if there are none, the posts are fetched from the API.

Allow users to specify how many posts they want to load in a single request

This is going to get me a lot of hate, but I want to stop people from logging into the worst instances on the fediverse using my app

Allow users to create client side regex filters to hide certain posts

Implement the home timeline

Find a way to store the current scroll position and maybe cache rendered entities to avoid rerendering time

Add features to administer a GoToSocial instance:

• Manage emojos
• Manage domain blocks
• Set the instance description
• Clean up old media
• Maybe more?

The app needs an icon.
The icon should be cute.

Localize strings that are shown to the user

Allow users to follow, unfollow and block other accounts

Add a settings menu allowing users to:

• Manage accounts
• Allow posting images without a description
• Maybe more?

Maybe add the possibility to follow RSS feeds and have them show up in the home timeline

Allow users to display their and other people's accounts

Get the base font size from the device configuration and scale everything according to that