User:NeoAmsterdam/Notes to Self: Difference between revisions

From OLPC
Jump to navigation Jump to search
No edit summary
m (More brainstorming)
Line 11: Line 11:
*# Each XO gathers info, establishes pt-2-pt comm links with nearest 2 neighbors (min. for msg. relay)
*# Each XO gathers info, establishes pt-2-pt comm links with nearest 2 neighbors (min. for msg. relay)
*#* Is there a way to make long-distance multi-node pt-2-pt contact?
*#* Is there a way to make long-distance multi-node pt-2-pt contact?
*# As users enter information, suggestions could be given to the user (how much water x number of people need, how to recognize possible water-borne diseases, triage how-to)
*# Once a relief center shows up (w/ hard drives), acts as XS/server - XOs spot it in the mesh (?) or by mesh-relay and U/L upon discovery (deltas thereafter)
*# Once a relief center shows up (w/ hard drives), acts as XS/server…<br /><small>or a real one - it would make sense that schools would become impromptu first-aid and triage stations</small><br />…XOs spot it in the mesh (?) or by mesh-relay and U/L upon discovery (deltas thereafter)
*#* But how long until relief shows up? How much data captured in that time?
*#* But how long until relief shows up? How much data captured in that time? What data would be the most urgent?
*# Comms are transient (vid/pic/voice), but written info (chat/DIY wiki) would need context awareness - geo/GPS, people/relations, needed items, status (Injured/killed/infirm)
*# Comms are transient (vid/pic/voice), but written info (chat/DIY wiki) would need context awareness - geo/GPS, people/relations, needed items, status (Injured/killed/infirm)
**Caveat emptor: Batteries might drain before relief arrives, and there might not be any power source.
**Caveat emptor: Batteries might drain before relief arrives, and there might not be any power source.

Revision as of 23:30, 6 September 2010

  • A temping recipe for booting Plan 9 (and the evidence to prove it's possible)
  • Radio streaming? (transmitting from "...somewhere in the mesh"?)
  • Rebuild Mini vMac (multiple drives, 576x448 or 1184x900 screen, max speed by default; X11 v. GTK builds)
  • Write a "hack ~/.sugar/default/config" note (builds before 852; after ~/.gconf/desktop.sugar/user/%gconf.xml)
  • Extracting XO splash sound (possibly replace) from w/in OFW
  • Write the "Add a drop of Wine/Who'd-a-thunk-it?" (or "How to shut up the bad-mouthing and make them take the XO seriously") note
  • Screenshots gallery ("Drop of Wine", activity "oops"s, )
    • yum gnome-utils, but it doesn't work with certain apps running.
  • SOS/Post-catastrophe app (how to fit a collaborative documentation effort into ≤512MB? or make it decentralized?)
    1. Each XO gathers info, establishes pt-2-pt comm links with nearest 2 neighbors (min. for msg. relay)
      • Is there a way to make long-distance multi-node pt-2-pt contact?
    2. As users enter information, suggestions could be given to the user (how much water x number of people need, how to recognize possible water-borne diseases, triage how-to)
    3. Once a relief center shows up (w/ hard drives), acts as XS/server…
      or a real one - it would make sense that schools would become impromptu first-aid and triage stations
      …XOs spot it in the mesh (?) or by mesh-relay and U/L upon discovery (deltas thereafter)
      • But how long until relief shows up? How much data captured in that time? What data would be the most urgent?
    4. Comms are transient (vid/pic/voice), but written info (chat/DIY wiki) would need context awareness - geo/GPS, people/relations, needed items, status (Injured/killed/infirm)
    • Caveat emptor: Batteries might drain before relief arrives, and there might not be any power source.