Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Registration Functionality to Proto-Avatar #275

Closed
5 tasks
Tracked by #402
Mookse opened this issue Jul 16, 2024 · 0 comments · Fixed by #419
Closed
5 tasks
Tracked by #402

Registration Functionality to Proto-Avatar #275

Mookse opened this issue Jul 16, 2024 · 0 comments · Fixed by #419
Assignees
Labels
consent member-avatar MyLife-provided Core Member Intelligence refactor refactoring of current code register required functionality required for primary pre-alpha release to family and friends security system-avatar MyLife Core Intelligence

Comments

@Mookse
Copy link
Member

Mookse commented Jul 16, 2024

In order to not reveal private information to Q threads (i.e., never stored in metadata or reviewable kb) (still session-stovepiped, and 'chat' objects for Q have never been accessible for its own intelligence [Isis maybe, but...])

temp proto-avatar spawned to manage process, if baptized by validation (propose initiating memory-version with "confirm registration" - while I have no objection to expansion to act of registering so that Q threads have zero personal data other than by accident of input which we aim to minimize or eradicate, I don't want to store in database at moment, and don't see necessity (i.e., separate table, yada, all doable) immediately, so I'm focusing on usage specification:

  • "register me" = Q takes and write email and input name, writable by Q, not readable by Q
  • ?vld= = proto-avatar spawned with presumed member Data which can be constructed from reg data
  • proto-avatar manages confirmation and create account requests, if successful (no throw) proto-avatar has become a real boy!
  • Q request to add mbr_id to hosting, if successful
  • Member avatar conducts any further business
@Mookse Mookse added system-avatar MyLife Core Intelligence required functionality required for primary pre-alpha release to family and friends refactor refactoring of current code consent register security member-avatar MyLife-provided Core Member Intelligence labels Jul 16, 2024
@Mookse Mookse self-assigned this Jul 16, 2024
@Mookse Mookse moved this from Open to In Progress in MyLife Alpha-Talc Jul 16, 2024
@Mookse Mookse moved this from To triage to In progress in MyLife Alpha MVP Build Jul 16, 2024
@Mookse Mookse mentioned this issue Jul 16, 2024
15 tasks
@Mookse Mookse moved this from In Progress to Open in MyLife Alpha-Talc Jul 22, 2024
@Mookse Mookse mentioned this issue Jul 22, 2024
7 tasks
@Mookse Mookse moved this from In progress to Backlog in MyLife Alpha MVP Build Jul 29, 2024
@Mookse Mookse mentioned this issue Jul 29, 2024
17 tasks
@Mookse Mookse removed this from the MyLife Member Alpha Release 0.0.16 milestone Jul 30, 2024
@Mookse Mookse mentioned this issue Aug 19, 2024
8 tasks
@Mookse Mookse mentioned this issue Aug 27, 2024
4 tasks
This was referenced Sep 4, 2024
This was referenced Sep 17, 2024
@Mookse Mookse mentioned this issue Oct 1, 2024
3 tasks
@Mookse Mookse mentioned this issue Oct 8, 2024
25 tasks
This was referenced Oct 26, 2024
@github-project-automation github-project-automation bot moved this from Backlog to Done in MyLife Alpha MVP Build Oct 26, 2024
@github-project-automation github-project-automation bot moved this from Open to Done in MyLife Alpha-Talc Oct 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
consent member-avatar MyLife-provided Core Member Intelligence refactor refactoring of current code register required functionality required for primary pre-alpha release to family and friends security system-avatar MyLife Core Intelligence
Projects
Status: Done
Status: Done
Development

Successfully merging a pull request may close this issue.

1 participant