Search Results for "js library"

Summa is a full-text IPFS-friendly search engine that may be launched on both large servers and inside your browser. Thanks to the embedded IPFS daemon, your data can be replicated and published through P2P, allowing for a truly distributed and uncensorable search experience. And, thanks to compatibility with WASM, Summa can be launched entirely inside your browser, enabling you to search in network-published indices without ever having to execute search queries on remote servers.

Typescript/Javascript libs for interacting with Textile APIs. @textile/hub provides access to Textile APIs in apps based on Account Keys or User Group Keys. For details on getting keys, see textileio/textile and for the full Textile documentation. The Hub library contains three API clients: Users, Buckets, and Threads Client. You can use each of these to access the full set of APIs available on the Hub. To use any of them, you must first start by authenticating your app with the API....

...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.

...The reference implementation of Textile is written in Go, and can be compiled to various platforms, including mobile (Android/iOS) and desktop/server (OSX, Windows, Linux, etc). The library in this repo is designed to help support things like browser-based Textile apps, Node.js apps, and other use-cases.

An alternative client library for the IPFS HTTP API, aiming to be as lightweight as possible (<20KB) in the browser. To interact with the API, you need to have a local daemon running. It needs to be open on the right port. 5001 is the default and is used in the examples below, but it can be set to whatever you need. In a web browser IPFS HTTP client (either browserified or CDN-based) might encounter an error saying that the origin is not allowed. This would be a CORS ("Cross Origin Resource...

...Transfer data directly from/to storage without BASE64 bridging. File API supports regular files, Asset files, and CameraRoll files. Native-to-native file manipulation API, reduces JS bridging performance loss. File stream support for dealing with large file. Blob, File, XMLHttpRequest polyfills that make the browser-based library available in RN (experimental) It is committed to making file access and transfer easier and more efficient for React Native developers. We've implemented highly customizable filesystem and network module which plays well together.