Search Results for "app get"

IPFS Desktop bundles an IPFS node, file manager, peer manager, and content explorer into a single, easy-to-use application. Use IPFS Desktop to get acquainted with IPFS without needing to touch the terminal — or, if you're already experienced, use the powerful menubar/taskbar shortcuts alongside the command line to make your IPFS workflow faster. If you already have an IPFS node on your computer, IPFS Desktop will act as a control panel and file browser for that node. If you don't have a...

...Using any wifi enabled device with a browser (computer, phone, tablet) connect to the newly created Access Point. Because of the Captive Portal and the DNS server you will either get a 'Join to network' type of popup or get any domain you try to access redirected to the configuration portal. ESP will try to connect. If successful, it relinquishes control back to your app. If not, reconnect to AP and reconfigure.

LoopGate is a web app that allows creators to token-gate content based on Loopring Layer-2 NFTs. It uses the Loopring API alongside the Piñata Submarine API to unlock hidden content hosted on IPFS. LoopGate is a web application built using in TypeScript using NextJS and TailwindCSS. LoopGate implements external SDKs/APIs. Most importantly, Loopring API, Query the Loopring blockchain to get NFT ownership data.

Web4 is a new way to distribute decentralized apps. Deploy a single WASM smart contract to deploy the whole web app. You only need to deploy a single smart contract using WebAssembly to host your app's HTTP backend, static resources, and blockchain logic. There is an HTTP gateway to NEAR blockchain which allows smart contract to handle arbitrary GET requests. Every smart contract on NEAR also gets a corresponding API endpoint which can be accessed through regular HTTP requests. ...

...It provides the bare minimum functionality for any application to interact with the IPFS network (by getting and putting IPLD blocks) without having to deal with the complexities of operating a full IPFS node. It is an attempt to remake the core piece of the IPFS node reusable on it's own. Because 99% of the time, a browser or mobile (d)App only needs to be able to add and get small bits of data over the IPFS network. This library provides that, in a much smaller package (currently less than 1/2 the size of js-ipfs without much optimization -- we will continue to optimize further). It is also highly extensible, so developers need only include the features they need, keeping load times fast, and (d)Apps feeling snappy.