Top contributors to this page: DerekCaelin
To find an image, do a Google image search of the tool. Find an image about 600px wide, if possible. Copy the image URL and paste into the box below.
What is the name of the tool?
| Tool Class
To what "family" does the tool belong? Pick as many categories as are appropriate. EG: Data Collection, Security, etc. The wiki will automatically create a link to the relevant tool class.
Who made the tool? Sometimes the tool name and the developer name are the same, and sometimes, they are different.
| Date Created
What was the date when the tool was first launched?
| Still Maintained?
Do the developers of the tool continue to work on it, adding features and fixing problems?
| Open Source?
Is the tool's source code original source code freely available and may it be redistributed and modified? (This makes it possible for users to employ the tool for free, with some technical effort.)
Pick the platforms on which the user would primarily use the tool. Be as selective as possible. If a tool works mainly in the browser, select "Web". If the user can technically load the interface on a smartphone but have a very poor experience, do not select "Android" or "iOS". "Mac" and "PC" are for apps that must be installed to a machine in order to run, as opposed to running from a browser.
What is the main website where a user can learn more about the tool? (Remember to include "http://)."
| Payment Structure
How, if at all, does a user pay to use the tool. Select all that apply: "Free" if there are components of a service that can be used for free; "Paid" if payment is required (either one-time, or at a given rate upon use) for use of the tool's full functionality; "subscription" if a monthly payment is required.
| Languages Supported
What languages does the app's interface support? Note: some apps allow users to communicate in other languages but require the user to use an English language interface. In this case, the app is considered only to support "English".
| Skill Level Needed
LibraryBox is an Open Source File Sharing tool that allows people to share pictures, video, audio and text locally through the use of a wireless router. The tool comes in two versions - an open source software package that can be installed on certain routers (the TP-Link MR3040 is recommended) or users can purchase a pre-made Librarybox for $165 from the tool's website.
LibraryBox Runs on a Small Router (in this case, a TP-Link MR3040)
LibraryBox v 2.1 can be used accessed by both computers and mobile devices. On laptop and desktop machines, the user is prompted to log into a captive portal. On mobile devices the experience is complicated slightly. Users with iOS devices will receive no log-in prompt, whereas Android devices will be directed to log into a network from a captive portal browser and must select "Use Network As Is" from the menu option. For all devices, the user must go to an non-https website (like CNN.com) to be redirected to the LibraryBox page - otherwise the user will
What Makes This Tool Different from Others in its Class?
LibraryBox, and like the sister tool PirateBox, runs locally on a mobile router. When running, the service is not connected to the Internet and users are interfacing only with the website and files stored on the router. This can be useful in low-connectivity environments when access to the Internet is slow or expensive. The service also provides a measure of security for sharing files because it is more difficult to monitor. The tool requires some technical understanding in order to use, especially for those building the application from the open source files (use of a Linux terminal is required for some stages in the install process.)
The LibraryBox Operating System