Skip to content

backend decentralisation #154

@armantorkzaban

Description

@armantorkzaban

Type of Issue

  • New Feature Implementation
  • Addition / Enhancement / Improvement

Type of Work

  • Backend Service
  • DevOps

Description
Instances of the backend can run in harmony in a chain or independently separately.
Joining the chain is accepted only if the networks share same core value, moderation principles, precision and speed.
Outdated or non-responding servers are balanced out.

As a service provider,
I want to be able to run an instance of fordem-backend for my community. Since they have unstable access to internet,
offer them periodic internet connectivity while they use the platform P2P the rest of time.
I share the values of the platform, use satellite internet from Starlink and run and carry the server in my car.
I am willing to participate in Location And Trajectories surveys and set the server available on certain trajectories
suggested by the forDem.


so that I can [achieve a goal].

Actionable Tasks

  • Implement a Cubit/BloC for [action] with states [...] and methods [...]
  • Implement Widget to trigger [action]
  • Implement Widget to display [result of the action]
  • ...

Acceptance criteria

  • Screen should render the initial UI properly
  • After [action is performed] state should change
  • New UI is properly rendered
  • ...

Metadata

Metadata

Assignees

Type

No type

Projects

Status

🆕 New

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions