lastmjs / browser-based-super-grid Goto Github PK

• UI
• Retrieve code
• Display code?
• Execute code

• Can we increase by 2 every time? 2 is also a prime number, so we aren't handling that case
• Why are m and n different in the success function
• Why are we initializing the variables at the top to randomish numbers?

Choose an algorithm and figure out how to parallelize it across multiple peers.

If we want this project to ever continue, we must make the README amazing:

• Describe the goals of the project
• Link to all past research and current projects (including that one business)
• Very nice installation explanation for development
• Detail how to make algorithms parallelizable in our system. It would be nice to ensure that our system can arbitrarily parallelize programs...but of course that might be extremely difficult

Because we aren't distributing this as of yet, and because everything is open sourced and the openpgp license is "dynamically" linked through an npm install, I think we're fine. But before offering this to the public at large by hosting it as a web app, we should look into this.

With the new polyfills, Polymer 2 should work even with transpilation to ES5, as long as you include the custom elements adapter. Make sure to thank the guy who told you about the adapter here: microsoft/TypeScript#12949 (comment)

Create the WebRTC component with its corresponding event handlers and actions for generating events.

• Figure out signaling. We do not want to have to create a signaling server...each peer should be able to physically look at another peer to find out the information it needs. The problem is, what is that information?
• Create an SDP offer. It looks like there is also an answer. The peers offer and answer. All you need is to get that text and use it appropriately...the signaling server with web sockets might be the best way to do this actually, and it won't be that complicated.

Ideas for what we should include:

• Timer to show how long the job is taking
• Current startIdex, stopIndex, and product
• Source peer with identifier
• Worker peers with identifier
• Maybe pause and start the loaded job...or just start and stop

Other things.

Right now we explain to the users that they must use the following command to generate their signature:

gpg --armor --clearsign --output [script name].sig --sign [script name]

They might not need both the --armor and --clearsign options. Also, we might want to look into the merits of using a detached signature.

• Find commands to create signatures of script files, put them in the README
• Implement PGPService.loadPublicKey
• Restructure the verification. Just load the signature file and verify it all at once. Extract the source code from the signature...this simplifies things a bit, and ensures that the source code is taken from a verified source. I was having troubles verifying the message and the signature independently.
• Implement PGPService.verifySignature
• Figure out how the verification will occur (signature...or something else? Maybe look at what Arch Linux does when you download from them)
• Should the verification occur automatically?
• UI for choosing the public key...or maybe the public key will be automatically retrieved from GitHub, or at least the URL to the public key which is hosted on MIT PGP Key Server