Difference between revisions of "Mesh/MeshApps"

From Sudo Room
Jump to navigation Jump to search
(changed layout again)
(Refactoring MeshApps page)
 
(19 intermediate revisions by 4 users not shown)
Line 1: Line 1:
What sort of services would we like to integrate with the network? See also about [[Mesh/Local_servers|local server]] choices.
What should live on the network?


=Services=
=Server Setup and Configuration=
The network ''should'' provide secure communication services (email, contacts, calendar, phone) to create more incentive to be on the network. The services can be integrated into a user account distributed database with master-master replication and low latency (ex. [http://www.datastax.com/resources/whitepapers/benchmarking-top-nosql-databases Cassandra]). These services will use existing open source projects.
[[Mesh/Local_servers|local server]]
 
==Storage / File Systems==
 
There are several options for a distributed file system and each have there advantages and disadvantages. The distributed file system can be used to offer file storage or reduce latency across the network.
 
* [http://opensfs.org/lustre/ Lustre] - Used by sixty percent of the top 100 websites.
*: Performance: Amazingly fast! I can assert that Lustre can serve a lot of streams and that encoding speed is not affected by accessing files via Lustre.
*: POXIS compatibility: Very good!. No need to modify applications to use luster.
*: Replication, Load Balancing and Fail Over: Very bad!. For replication load balancing we and fail over we need to rely on other software such as virtual IPs and DRDB.
*: Installation: The worst!. Impossible to install by mere mortals. Requires a very specific combination of kernel, lustre patches and tweaks to get it working. And current luster patches usually work with old kernels that are incompatible with new hardware/software.
 
* [https://code.google.com/p/mogilefs/ MogileFS]
*: Performance: Good for small files but not usable for medium to large files. This is mostly due to HTTP overhead since all files are send/receive via HTTP requests that encode all data in base64 adding a 33% overhead to each file.
*: POXIX compatibility is non existent. All applications require to be modified to use mogilefs that renders it useless for streaming/encoding since most streaming servers and encoding tools do not understand MogileFS protocol.
*: Replication and failover out of the box and load balancing can be implemented in the application by accessing more than one tracker at a time.
*: Installation: Relatively easy and ready to use packages exist in most distributions. The only difficulty I found was setting the database master-slave to eliminate the single point of failure.
 
* [http://www.gluster.org/ GlusterFS]
*: Performance: Very bad for streaming. I cannot reach more than a few Mbps in a 10Gbps network. Clients and Server CPU skyrockets on heavy writes. For encoding works because the CPU is saturated before the network and I/O.
*: POXIS: Almost compatible. The tools I use can access gluster mounts as normal folders in disk but in some edge cases things start causing problems. Check gluster mailing lists and you will see there are a lot of problems.
*: Replication, Failover and Load balancing: The best! if they actually worked. Gluster is very new and it has a lot of bugs and performance problems.
*: Installation is too easy. The management command line is amazing and setting replicated, striped and distributed volumes among several servers can not be any easier.
 
([http://stackoverflow.com/questions/916902/lustre-gluster-or-mogilefs-for-video-storage-encoding-and-streaming source of above information])
 
[http://www.xtreemfs.org/ XtreemFS] - needs more research.
 
==Databases and Servers==
 
* [https://cassandra.apache.org/ Cassandra] - a decentralized database that has benchmarked with the lowest latencies and has master-master replication.
* [https://couchdb.apache.org/ CouchDB] - I can tell you that it quickly becomes complicated to write multi-user app with CouchDB. Decent access control means that you need a database per user and likely a few extra databases. You then have to set all of these databases up to synchronize between each other which is further complicated by the limitations on what information is available by the limitations on how synchronization rules and filters can be written. There seem to be no good tools for managing/visualizing these complex relationships so you end up having to roll your own.
* [http://pouchdb.com/ PouchDB] - a javascript based couchDB.
* [https://github.com/dominictarr/scuttlebutt Scuttlebutt] - a data synchronization protocol, or a peer-to-peer replicatable data structure.
* [https://tahoe-lafs.org/trac/tahoe-lafs TahoeLAFS] - a decentralized database.
* [http://code.google.com/p/leveldb/ LevelDB] - a fast and lightweight key/value database library.
* [http://www.mongodb.org/ MongoDB] - an open-source document database, a NoSQL database. Written in C++.
* [http://nodejs.org/ Node.js] - an HTTP server written in javascript.
 
==Communications==
 
*[http://radicale.org/ Radicale] - a CalDAV (calendar) and CardDAV (contacts) server.
*[http://villagetelco.org Village Telco] - is an initiative to build low-cost community telephone network hardware and software that can be set up in minutes anywhere in the world.  No mobile phone towers or land lines are required.
*[http://maidsafe.net/ MaidSafe] - a secure communications platform (charges money)
*[http://www.openmama.org/what-is-openmama OpenMAMA] - a high performance middleware agnostic messaging API that interfaces with a variety of message oriented middleware systems
*an encrypted asynchronous messaging system to replace email
*a module to have collaborative documents, voting, and groups (or sub-groups)
*a module for peer to peer file sharing.
*a module for object-orientated tagging, shareable feeds.
*a module for feeds and posts, such as [http://www.trsst.com/ Trsst].
 
==Utilities and Misc.==
*Bulletin Board / Hyperlocal Craigslist
**Community Asset Mapping (eg; [http://thepyre.org/wiki/Mycelia Mycelia])
*Local Wiki (eg; http://oaklandwiki.org)
*Communication (eg; chat room, decentralized Twitter)
*Sensor Data (eg; Temperature, Seismic activity, air pollution)
*Location-aware social network (eg; http://dev.wlan-si.net/wiki/PiplMesh)
*Neocities for free user sites (eg; https://github.com/kyledrake/neocities-web)
* Use avahi to broadcast member-run local services, such as on a home laptop server.
** Turns out that Avahi works with windows: https://github.com/Byzantium/Byzantium/blob/master/porteus/avahi/etc/avahi/avahi-daemon.conf
* [http://crabgrass.riseuplabs.org/ Crabgrass] - a project out of riseup labs, a ruby rails application for community organizing. It's not the easiest to run your own instance, but very easy to sign up to their server ([https://we.riseup.net/ we.riseup.net])
** Anarchist Redmine
* Groundstation - twitter clone for n3rdz
** Git base
* QwebIRC is the webclient used by freenode
* How about [http://www.frontlinesms.com/ Frontline SMS]!
* [https://www.docker.io/ Docker] - an open-source project to easily create lightweight, portable, self-sufficient containers from any application.
 
==Mapping==
 
* [http://villagetelco.org/2011/06/spud-simple-unified-dashboard-for-mesh-networks/  Simple Unified Dashboard (SPUD) for mesh networks]
* [http://nodewatcher.readthedocs.org/en/latest/installation.html NodeWatcher] -
* [http://wiki.ninux.org/InstallNodeshot NodeShot] -
* [https://github.com/freifunk/openwifimap-html5  OpenWiFiMap] -
* [https://github.com/libremap  LibreMap] -  a scalable, global and decentralized router database and map visualization for community networks, such as guifi, ninux, etc.
* [http://tidepools.co Tidepools] - collaborative local mapping software
* [http://ediblecities.org/ Edible Cities] - a food mapping project


=Distributed Services=
[[Mesh/Distributed_Services|Distributed Services]].


=Use Cases=
=Use Cases=
==Leisure, Treasure Hunt, Animal Spotting, History / Science Plotting , Art/Design/Drawing, Mapping Secret/Weird stuff, Expression, Emotion==
[[Mesh/MeshApps/UseCases|UseCases]]
*Jordan is a 36-year old scientist and queer activist. Occasionally, he travels north to a 'radical fairy' retreat center on over 80 acres of land. He's undertaking a project to map out the diverse and undocumented biology and wildlife in this sacred area. For this, he would like a tool that would enable him to automatically map the coordinates, attach a picture, and include a comment about what it is, as well as the ability to add to social media (Facebook & Twitter).
 
==Bulletin Board / Local Information sharing (jobs, events, etc) (people to people)==
*Martin is a 35-year old Latino man who runs a website for displaying new job postings and opportunities for diverse, underserved populations in Oakland (eg; youth, veterans, and formerly incarcerated). Martin would like to easily transpose this data onto a searchable map that he could populate daily with new opportunities and programs.
 
==Sensors: hardware-based [inputs & outputs]==
*Naomi is a Midweatern 30-year old environmental activist concerned about the impact of fracking on the quality of water in her county. She's organizing a campaign to encourage fellow concerned homeowners to monitor changes and contaminants in air and water quality, seismic activity, radiation, and other potential environmental impacts of fracking.
 
==Evidence Based Citizenship (crowdsourced data/reporting for an institution to solve, neighborhood to be aware of) (people to institutions)==
*Alyssa is a 35-year old African-American woman working for the city government. Passionate about diversifying and expanding civic participation, she's been participating with Open Oakland to make civic data more accessible. She's working on an educational campaign for creating short videos explaining civic issues and how local government works.
 
==Political Crisis Readiness (people to people, against institutions)==
 
=Contexts=
==Community Asset Mapping / Archiving==
*Kiara is a 34-year-old African-American community organizer and activist interested in mapping the various organizations addressing digital divide issues, as well as available resources such as public computers, free training and education, and free wifi spots.
*Molly is a 26 year old community organizer working on Oakland Wiki, a website editable by anyone and dedicated to everything Oakland. She recently announced the launch of an oral history project, the end product of which would ideally be mapped onto specific areas and landmarks.
 
==Community Hub (communications / sensors / input + output APIs )==
*Ali is a 28-year old Iraqi-American and works to catalyze community organizations in the Middle East. He is currently collecting stories from hackerspaces in the form of comics, as well as a 'Sister Spaces' project to partner hackerspaces for sharing insights and infrastructure challenges.
*Luke is a 33-year-old Australian data and open government geek. Among the mappable projects he's working on with Open Oakland are storm drains (the Adopt-A-Drain project), crime data, vacant and blighted properties, and organizations and resources addressing the digital divide.
 
==Organizing Tool (activists, security matters)==
*Mateo is a 32-year old Latino father living in the San Antonio neighborhood in Oakland, CA. He is interested in the capabilities of a mesh network for streaming Creative Commons-licensed content to his neighbors (possibly using an Asterisk server) and providing a means for connecting the community both digitally and physically through an online neighborhood bulletin board. He has a strong interest in reaching out to local businesses with an 'everybody wins' model of free wifi through a mesh, with a map-based splash page for communicating with others in the network.
 
==Crisis Readiness==
*Jen is a 30-year-old Asian-American technologist and community organizer in East Oakland. Passionate about DIY education and grassroots community-building, she's interested in mapping DIY communities as well as available resources for crisis readiness (such as relief centers, tools, food, water and shelter).
*Alexis is a 29-year old African-American technologist interested in the potential for mesh networking to expand internet access in underserved areas and creating a resilient communications network for crisis readiness. She is especially passionate about issues surrounding access to technology, and would like to see underserved communities participating in putting themselves on the map.

Latest revision as of 22:16, 21 July 2015

What should live on the network?

Server Setup and Configuration

local server

Distributed Services

Distributed Services.

Use Cases

UseCases

Retrieved from "https://sudoroom.org/mediawiki/index.php?title=Mesh/MeshApps&oldid=9531"