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

[Operation]: Archival Daemon & Source Attribution #26

Closed
ks0m1c opened this issue Jan 22, 2024 · 0 comments · Fixed by #24
Closed

[Operation]: Archival Daemon & Source Attribution #26

ks0m1c opened this issue Jan 22, 2024 · 0 comments · Fixed by #24

Comments

@ks0m1c
Copy link
Contributor

ks0m1c commented Jan 22, 2024

Present Context

Helping words...

Where we collectively investigate and interrogate the problem space and iteratively scope our approach.

Breakdown to landmarks that communicate shared context we are working towards through 2-tiered task list, CRUD list elements as development unfolds.

Strike the scope of code that reveals the most about the problem/solution FIRST not necessarily the easiest or hardest parts

- [ ] Parent Task
    - [ ]  Child Task
    - [ ]  Child Task
  
- [ ] Parent Task
    - [ ]  Child Task
    - [ ]  Child Task


We currently depend, curate and serve as a window to a richer internet milieu in terms of foundational data
We can begin with Wayback fallbacks for sources of translations/commentaries and progress to a system of preemptive archival that preserves the form/content as the author wished to present it with a hashed timestamp. This ensures a copy will be available indefinitely from one of these fallbacks regardless of the process of linkrot

Groundwork

Helping words...

Introduce us to the problem space. Write out what you already know about the terrain you are the recce commander enriching us with details beyond the fog of war.

Where have you tried applying and encountered difficulties?

How have others attempted to scale or explore these challenges?

(Embed internal & external links to related or possible paths of exploration, stackoverflow, documentation, github etc)

Who should be notified?

Emphasis on previous or current practice to discover what is ugly, missing, or unnecessary.

INPUT UR ANSWER HERE

Reflection

Helping words... Where the eternal wheel returns back to practice and what we finally implemented is to be outlined. You are the historian or archivist bringing clarity to future-yous and us about your foray.

Emphasis on approaching timeless solutions for well-defined problem space through distillation by decanting that which is un-needed and abstracting that which is essential to approaching the problem space.

Add any reflections and internal links to future potential and blindsides.

INPUT UR ANSWER HERE
@ks0m1c ks0m1c linked a pull request Jan 27, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant