We already have most of the code needed to make a httprequest version of the api. Though sub optimal it will be easy to implement.

Story

User 1: wants to connect with another ODESI user. They Search for a user, selects the user, and then sends a request

User 2: sees a pending request in their list of users and wants to find out who this user is and decide on how to proceed.

Tasks

• Add any missing functions in OpenSeed-Godot.
• Create search window / dialog

• • List users noting user
• • List groups noting group (only open groups)
• • Select user and view profile
• • Send Request

• Create Connection Dialog

• • Give basic information about user that wants to connect with User 2
• • Add ability to look at full profile
• • Add ability to Accept / Deny connection

The ability to share to IPFS is already added to OpenSeeds api, but not all clients or users will want or have access to install IPFS. So for all files great and small we should be able to move them.

Downloads via the http interface is simple enough. However, there seems to be no documentation on uploading through that same interface. One could argue that uploading images and files via the game engine isn't a good use of the engine, but if we are to have a complete solution It is my opinion that this needs to be solved.

This would also make projects like Thicket shine as for the moment we are asking users to install IPFS on their system and while that is fine for Thicket it doesn't make sense for many applications.

Story

User wants to look at another users profile, what games they are playing, what groups they are a part of, what posts they have made, etc.

Tasks

• Create Dialog

• • Pull in OpenSeed profile
• • close button

With all the news around the websocket support that Mozilla has funded we should offer that as a possible way to create godot webgames.

Story

User needs to create a group in his Godot based ODESI powered game or application.

Tasks

• Group functions need to be added to OpenSeed-Godot
• Dialog box to create Group

• • Group Title
• • Add users within connections list
• • Accept or cancel buttons

• Add groups in connections lists.

#Story
User wants to use OpenSeed in a secure manor for obvious reasons. Right now everything comes back unintelligible.

Tasks

• Using current OpenSeed code to rework algorithm.
• Test with chat
• Test with general app data

Story

User has over 20 people in the group, he/she wants to give several users the right to add and remove users or mute certain posts.

Task

• Add ODESI Role management functions to OpenSeed-Godot
• Add Dialog

• • List users in group and view current role
• • Select user and set Role

As a part of our larger plans everything should be encrypted. Chat is now in a state where we can focus on other aspects of the project. So we should remove the ability to send un-encrypted messages.

Story

Now that the user has a group they need to be able to add and remove connections from the list.

Tasks

• Add Group editing features to OpenSeed-Godot
• Add Dialog for Group editing

• • Add user
• • Delete user

Rework network code for better developer control and clearer logic.

#Story
Developer wants to use OpenSeed-Godot but doesn't have the intimate knowledge that the developers to do access these functions.

Task

Each section needs to be completed to close this ticket

• Account
• Chat
• Music
• Images
• Save / Load Data
• Highscore adding and retrieval.

OpenSeed's Godot plugin is being developed in Tandom with Thicket a Media delivery platform for the distributed and decentralized age. The chat dialog is self contained and can be moved to the OpenSeed-godot plugin folder for drop in chat for clients.

Leader board code is seperated from the rest of the application code in OpenSeed. This is pointless as leaderboards are just historical data that can be pulled using the history functions.
The functions will still be
get_leaderboard
update_leaderboard

but they will function more like alias than real functions.

TCP traffic can sometimes be less than reliable when dealing with larger data transfers. The addition of an intelligent data management pattern would decrease the data retrieval failures. This could be in the form of data streams or a reduce and resize mechanic where each chuck sent could dynamically change size to decrease resends.

The TCP socket connection works well enough but I believe it would be better served if we can some how use the multiplayer abstraction layer to offer better overall preformance.

Save Games is a seperate function within OpenSeed and could be moved to the appdata section of the program. The functions would remain
save_game
update_save
get_save

but will be aliased to their app equivalent.