Development resources at your finger tips
Build with the coolest Web3 projects
Recurring funding for Open Source
Ethical ads to power Open Source
Learn about Web3 & earn rewards
Show appreciation for each other
Meet fellow developers, designers, futurists and more. Collaborate and BUIDL awesome projects together.
Follow the orgs you like more with tribes and build relationships and meaningful projects.
Meet the top hunters and contributors from our community.
Most people working with Ethereum have questions about ETH2.0. Kevin Owocki hosted some developers working on the project for a recent episode of the…
Sia recently ran the Skynet Hackathon with Gitcoin for Skynet’s launch, leading to over 40 project submissions in a 2 week period. This piece, …
Gitcoin is GDPR complaint. Learn more in
Gitcoin's Terms & Conditions.
Check out the Issue Explorer
Looking to fund some work? You can submit a new Funded Issue here.
At www.dizmo.com, we're developing an interface (of things), and decided to go for VNC and noVNC to enable browser support for our software, which relies as well on multi-touch support. However, noVNC does not seem to have such a feature enabled.
Hence, would it be possible to have multi-touch integrated? We would be willing to also pay the developer who integrates this feature.
> I've issued a bounty of **240 DAI** (a stable-coin corresponding to **240 USD**) to have this issue *not* solved, but *fully* specified. Please have a look at: https://gitcoin.co/issue/novnc/noVNC/944/1047
> My goal with this bounty would be to have exhaustive specification, which would allow me to open a follow-up of issue where then the actual *multi-touch* support is implemented. To claim the bounty, please provide a pull request with a corresponding Markdown document containing the specification.
> Please see also our video gallery at https://www.dizmo.com/video-gallery/, where we display some of our use cases and where we plan to use multi-touch. In our case noVNC is running within a **Docker** container, hence the specification should be compatible with such a context.
> **NOTE:** The bounty is structured as a **contest** with an **expiration date** of **two weeks**.