Skip to content

Instantly share code, notes, and snippets.

@STRd6

STRd6/recursive-selection.md

Last active October 18, 2019 19:47
Download ZIP

Revisions

  1. STRd6 revised this gist Jun 22, 2014. 1 changed file with 6 additions and 0 deletions.
    6 changes: 6 additions & 0 deletions recursive-selection.md
    View file
    Original file line number Diff line number Diff line change
    @@ -0,0 +1,6 @@
    Recursive Selection
    ===================

    What would a recursive selection tool look like in a pixel editor?

    One should be able to draw fractals using it.
  2. STRd6 revised this gist Jun 19, 2014. 1 changed file with 12 additions and 12 deletions.
    24 changes: 12 additions & 12 deletions s3-cas-ecosystem.md
    View file
    Original file line number Diff line number Diff line change
    @@ -19,21 +19,21 @@ Structure
    Worker
    ------

    Needs credentials to bucket root
    receives url to user submitted resource + server metadata payload
    notifies server with metadata payload and exits if sha exists in root
    validates SHA
    copies to root
    optionally deletes from users/username/sha
    notifies server with metadata payload
    - Needs credentials to bucket root
    - receives url to user submitted resource + server metadata payload
    - notifies server with metadata payload and exits if sha exists in root
    - validates SHA
    - copies to root
    - optionally deletes from users/username/sha
    - notifies server with metadata payload

    Server
    ------
    Receives metadata payload + SHA from worker
    Creates DB entry referencing SHA and any metadata (creator, etc...)
    - Receives metadata payload + SHA from worker
    - Creates DB entry referencing SHA and any metadata (creator, etc...)

    Users
    -----
    Get namespaced credentials from server so they can upload directly to S3
    Compute SHA locally and upload to S3
    Ping worker queue when an upload is complete
    - Get namespaced credentials from server so they can upload directly to S3
    - Compute SHA locally and upload to S3
    - Ping worker queue when an upload is complete
  3. STRd6 revised this gist Jun 19, 2014. 1 changed file with 5 additions and 0 deletions.
    5 changes: 5 additions & 0 deletions s3-cas-ecosystem.md
    View file
    Original file line number Diff line number Diff line change
    @@ -32,3 +32,8 @@ Server
    Receives metadata payload + SHA from worker
    Creates DB entry referencing SHA and any metadata (creator, etc...)

    Users
    -----
    Get namespaced credentials from server so they can upload directly to S3
    Compute SHA locally and upload to S3
    Ping worker queue when an upload is complete
  4. STRd6 revised this gist Jun 19, 2014. 1 changed file with 6 additions and 6 deletions.
    12 changes: 6 additions & 6 deletions s3-cas-ecosystem.md
    View file
    Original file line number Diff line number Diff line change
    @@ -9,12 +9,12 @@ Append only so no difference between dev and production.
    Structure
    ---------

    bucket
    + root
    | | SHAs...
    + users
    \ + some_duder
    \ | SHAs...
    bucket
    + root
    | | SHAs...
    + users
    \ + some_duder
    \ | SHAs...

    Worker
    ------
  5. STRd6 created this gist Jun 19, 2014.
    34 changes: 34 additions & 0 deletions s3-cas-ecosystem.md
    View file
    Original file line number Diff line number Diff line change
    @@ -0,0 +1,34 @@
    S3 CAS Ecosystem
    ================

    A mircoservice would validate pings notifying it of data to ingest into the central CAS.
    Users get permission to upload to a namespace then ping the workers to validate and move the file over.

    Append only so no difference between dev and production.

    Structure
    ---------

    bucket
    + root
    | | SHAs...
    + users
    \ + some_duder
    \ | SHAs...

    Worker
    ------

    Needs credentials to bucket root
    receives url to user submitted resource + server metadata payload
    notifies server with metadata payload and exits if sha exists in root
    validates SHA
    copies to root
    optionally deletes from users/username/sha
    notifies server with metadata payload

    Server
    ------
    Receives metadata payload + SHA from worker
    Creates DB entry referencing SHA and any metadata (creator, etc...)

    6 changes: 6 additions & 0 deletions s3-repliwiki.md
    View file
    Original file line number Diff line number Diff line change
    @@ -0,0 +1,6 @@
    Self-replicating S3 Hosted Wiki
    ===============================

    - Credentials stored only client localStorage
    - Contains tools to build and post files to S3, edits itself.
    - Post everything to a new bucket to replicate.