The painting in real size :
👉 
The painting right now (big size)
Download the painting (reale tiny size)
Participate : 1000000000.art
Art01 is a painting, Its size will be 40,000 px wide by 25,000 pixel high. That is a 1 000 000 000 pixels.
This painting requires a billion participants to be completed.
Every pixel is added by one person, you for example. When you first signs in and visualizes the artwork, a colored dot corresponding to your IP address is added. It's your pixel.
For example : your IP is 78.234.74.82
Your RGB color is rgb(78,234,74)
Red : 78
Green : 234
Blue : 74
And your opacity is between 0 (0) and 1 (255).
Opacity for 82 => 0.32
Final RGB color with opacity : rgba(78,234,74,0.32) :
This rectangular painting is only an example of representation. The artwork is made up of data provided by people over time, not its appearance.
Did you say "participatory Art" ? 👉 https://en.wikipedia.org/wiki/Participatory_art
For the moment (January 10, 2021 ), 706 people have participated to this project since its beginning, 5 months ago. 0.0000706% of the painting is complete
At this rate, 1000000000.art be finished in 1 102 261 years.
I use a Ulam spiral to add each pixels, the first one the first being in the center :
I use eventsourcing pattern. Take a look : eventstore
Number of pixels : https://api.1000000000.art/api/pixels/count
All Painters and their pixels (json) : https://api.1000000000.art/api/users/
Last painter (json) https://api.1000000000.art/api/pixels/last
In the project directory, you can run:
Runs the front react app in the development mode.
Open http://localhost:3000 to view it in the browser.
The page will reload if you make edits.
You will also see any lint errors in the console.
Launches the test runner in the interactive watch mode.
See the section about running tests for more information.
Builds the app for production to the build folder.
It correctly bundles React in production mode and optimizes the build for the best performance.
The build is minified and the filenames include the hashes.
Your app is ready to be deployed!
See the section about deployment for more information.
Note: this is a one-way operation. Once you eject, you can’t go back!
If you aren’t satisfied with the build tool and configuration choices, you can eject at any time. This command will remove the single build dependency from your project.
Instead, it will copy all the configuration files and the transitive dependencies (Webpack, Babel, ESLint, etc) right into your project so you have full control over them. All of the commands except eject will still work, but they will point to the copied scripts so you can tweak them. At this point you’re on your own.
You don’t have to ever use eject. The curated feature set is suitable for small and middle deployments, and you shouldn’t feel obligated to use this feature. However we understand that this tool wouldn’t be useful if you couldn’t customize it when you are ready for it.
cd /api nodemon
See it at http://localhost:3001/