Here is a list of links that return 404

https://apility.io/apidocs/
http://developer.linkedin.com/docs/rest-api
https://sentim-api.herokuapp.com/ works
https://quarantine.country/coronavirus/api/ works

https://blog.mugenmonkey.com/2017/09/10/ds3-api.html
https://developer.walmartlabs.com/docs
https://taylor.rest

Please feel free to add more broken links when you find t

Enhancement proposal

Currently, Dot3D uses the default Sphere resolution of (12, 24). Running a scene with lots of Dot3Ds, like a scene with polyhedra, takes incredibly long because of the high resolution. I think a resolution of (8, 8) is a good balance between speed and visual looks. After changing the resolution, the control data for some tests have to be regenerated.

Addition

Description of GITHUB_ENV is inconsistent regarding if set envs are available across the workflow or only within a job.

What article on docs.github.com is affected?

https://docs.github.com/en/actions/reference/environment-variables#about-environment-variables
https://docs.github.com/en/actions/reference/workflow-commands-for-github-actions#setting-an-environment-variable

What par

What would you like to happen?
The sections 4.7.11.1 Testing for Local File Inclusion & 4.7.11.2 Testing for Remote File Inclusion address two attack vectors that are very similar one to the other. Given this situation and the few documentation on the Remote injection one, my proposal would be to merge both in a single section called Testing for File Injection.

🎉 Description

The ECDSA contract has a function toEthSignedMessage(bytes32), but we should have a function that works for any length of a bytes array:

function toEthSignedMessage(bytes s) pure internal returns (bytes32) {
  return keccak256(
    "\x19Ethereum Signed Message:\n",
    uintToBytes(s.length),
    s);
}

Where uintToBytes is implemented from an ideally