prosopo / captcha Goto Github PK

This second docker network allows external traffic to the server but does not contain the mongodb docker instance in the network, disallowing external traffic straight to the mongodb

could use google translate as only single words (atm!)

getStorage broken when it was removed from an API. Use runtime API instead.

We need to start various jobs when running a Provider and ensure that they are completed without errors.

• calculate solutions
• batch solutions
• ...

A job runner should be used for starting and reporting on jobs. It should be possible to

• start jobs
• stop jobs
• add new jobs to the queue
• change job priorities
• view job output

In-memory in node

In many places, string is used when AccountId or Hash should be used. These should be fixed.

https://gist.github.com/rupeshtiwari/e7235addd5f52dc3e449672c4d8b88d5#%F0%9F%8C%84creating-a-typescript-nodejs-project

Currently, we only have a mongo plugin for the database. We should add a decentralised storage option such as

• chia
• storj
• maidsafe
• crust

#21 should be completed first.

This sometimes fails, most likely due to a race condition in provider.

Currently there's a quiet error.

When building the app, ~20 errors come from substrate not being able to find files.

E.g.
WARNING in ../../node_modules/@substrate/connect-extension-protocol/dist/cjs/index.js Module Warning (from ../../node_modules/source-map-loader/dist/cjs.js): Failed to parse source map from '/home/geopro/bench/workspaces/node_modules/@substrate/connect-extension-protocol/src/index.ts' file: Error: ENOENT: no such file or directory, open '/home/geopro/bench/workspaces/node_modules/@substrate/connect-extension-protocol/src/index.ts'
Failed to parse source map from '/home/geopro/bench/workspaces/node_modules/@substrate/connect/src/index.ts' file: Error: ENOENT: no such file or directory, open '/home/geopro/bench/workspaces/node_modules/@substrate/connect/src/index.ts'

Tests need to be fixed now that we're in a monorepo.

E.g. we don't need to export the utils pkg, right?

We need to split components into separate files (or add separate files) to enable default exports and improve tree-shaking and therefore bundle size

This can wait until after we're live.

Currently, we only batch solutions on-chain based on a schedule. Solutions should be batched on-chain if a certain volume threshold is met.

Can we use letsencrypt for this?

Caddy2 does letsencrypt automatically (using only ip I believe).

Nginx is another option.

Can do it in nodejs manually, but scripting the ssl renewal might be reinventing the wheel. Perhaps there's an npm library for this?

If a provider is unresponsive in the frontend, a new provider should automatically be chosen so that the user does not have a bad experience.

Currently pops up with error but allows retry

The provider database is dynamically imported based on the db config. It is designed to allow different database engines as long as an interface is provided. This feature should be pulled into its own package.

A dataset may contain 1M captchas but only 1 solved captcha initially. The captchas may need to be served in batches so that captchas are solved in a short enough amount of time to ensure that the Provider quickly gains more than 1 solved captcha.

Client will make a request for random active provider, passing Dapp AccountId. If Dapp is Suspended or Deactivated no Provider will be received. How will this be handled in proCaptcha?

prosopo/protocol#38

Dapps should handle this use case in their frontend and in their contract.

Collisions of fingerprints can cause massive issues in web2 mode due to two users sharing the same ID. This may incorrectly permit a user by mistaking them for a verified user

Change the word commitment to solution everywhere

Mongo should not be accessible from outside but should be accessible from the server docker instance. The two should share a network which has no external inlet.

This is a task to create several high volume, high quality datasets.

Since there is no longer an on-chain commitment being made by the user, solutions is a more accurate word for the data the user is sending the Provider.