Peace and blessings, everyone! This post is to aggregate client-side freedom cells "proposals", God willing.

A common theme in this application is segregating client generated data from curated "back-end" data. Client data could be a number of things: signing up, posting, and creating cells. All of which is done using their account.

On the other hand, the application needs to be able to pull data reliably to present to the user. In order to avoid processing multiple times on the client, the application/main account can poll the data submitted by clients and verify/curate it.

This process sits squarely in between the client and the application. You could look at it as post-processing the client submitted data or pre-processing the application data before being used by the application.

When this pre/post processing is finished, we can signal the data is good by following a user, upvoting a post, or commenting on the post, or a number of things (like reference the post using a permlink on another thread).

Like I mentioned, this is already done a few times in the freedom cells application.

User signs up (update account with appropriate metadata, follow main freedom-cells account)
- main account polls for new followers, verifying metadata to be sure they signed up for the account (could use a special follow 'what' parameter?)
  - main account then follows back if verified, thus the application can get all signed up users by grabbing this one accounts followers.
User posts using the application (includes freedom-cells tag)
- main account polls for new posts with this tag, verifies user is followed by main account
  - main account then upvotes this post or references the permlink in a geohash location data structure thread so application can get all posts in one tree.
User creates freedom-cells using the application...
- main account polls...
  - main account then votes, or references...

So this clearly seems like a general pattern. In this case, creating freedom cells could be done with it's own dedicated post by the user, or posted as a comment to a main thread like this one, or even be a dedicated account similar to one being built for this application :) And this isn't even an exhaustive list... very interesting to say the least!

I'm going with the posts as comments to the main thread to avoid polling for a specific tag, like standalone posts. But the accounts similar to the main account would be interesting since it is mutable and could add some features regarding handling of the account (perhaps this account could be automated to run by consensus of the members of the freedom cell? God willing.)

Well, that's the run down. Back to the adventures of decentralized application architecture and development.

Kind Regards!

Topics