Backlinking and Invites System

[Arlodotexe]

The Concept

The concept of backlinking is vital to the SDK. If someone adds your user to their project, you must add their project to your user for the link to be valid.

This concept applies to all entities in the SDK, spanning Users, Publishers and Projects.

Discord Bot Considerations

However, for the purposes of a Discord bot, backlinking presents a challenge and an opportunity:

Challenge

When interacting with their own data, backlinking should happen automatically.

Opportunity

When interacting with data that belongs to someone else, the data is not valid until the other person has completed the backlink. This gives form to an invitation system that we can facilitate through Discord.

The long-term plan

On the invites system, this is our long-term (non-MVP) solution which may also work fully p2p, not just via the Discord bot.

For initial MVP/Appathon, we don't need to do all of this upfront. To prepare for it later, we need only model the end UX needed on the Discord side. If we have this, we can swap out the implementation for the p2p-friendly version later-- but it must be conceptually compatible (e.g. we can directly re-implement or create adapter classes as needed).

MVP Implementation Notes

We'll look at fleshing out and adding both of these, once we've laid the basic groundwork for SDK-in-bot.

[Arlodotexe]

On the invites system, this is our long-term (non-MVP) solution which may also work fully p2p, not just via the Discord bot.

For initial MVP/Appathon, we don't need to do all of this upfront. To prepare for it later, we need only model the end UX needed on the Discord side. If we have this, we can swap out the implementation for the p2p-friendly version later.