User:NeoAmsterdam/Notes to Self: Difference between revisions

From OLPC
Jump to navigation Jump to search
(Sugar on a G5 Quad (or as close as I'll get to it))
No edit summary
Line 3: Line 3:
* Radio streaming? (transmitting from "[http://www.thevoiceofpeace.co.il/gallery2/showphoto.php?photo=439_e3a0a0732ff8dc75d7dd77d26e72d22e.jpg ...somewhere in the mesh]"?)
* Radio streaming? (transmitting from "[http://www.thevoiceofpeace.co.il/gallery2/showphoto.php?photo=439_e3a0a0732ff8dc75d7dd77d26e72d22e.jpg ...somewhere in the mesh]"?)
* Rebuild [[Mini vMac]] (multiple drives, 576x448 or 1184x900 screen, max speed by default; X11 v. GTK builds)
* 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)
* <del>Write a "hack ~/.sugar/default/config" note (builds before 852; after ~/.gconf/desktop.sugar/user/%gconf.xml)</del> fairly self-explanatory.
* Extracting XO splash sound (possibly replace) from w/in OFW
* Extracting XO splash sound (possibly replace) from w/in OFW
* SOS/Post-catastrophe app (how to fit a collaborative documentation effort into ≤512MB? or make it decentralized?)
* SOS/Post-catastrophe app (how to fit a collaborative documentation effort into ≤512MB? or make it decentralized?)
Line 13: Line 13:
*# 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.
* Running <tt>sugar-emulator</tt> on F12/PPC64<br />(<tt>/usr/share/sugar/activites</tt>??)
* <del>Running <tt>sugar-emulator</tt> on F12/PPC64<br />(<tt>/usr/share/sugar/activites</tt>??)</del> Horrible. Just plain horrible. Shame on Fedora.
* Build KDE 3 from scratch (because KDE4 is almost Java-like in resource hogging).

Revision as of 19:27, 12 February 2011

  • 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) fairly self-explanatory.
  • Extracting XO splash sound (possibly replace) from w/in OFW
  • 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.
  • Running sugar-emulator on F12/PPC64
    (/usr/share/sugar/activites??)
    Horrible. Just plain horrible. Shame on Fedora.
  • Build KDE 3 from scratch (because KDE4 is almost Java-like in resource hogging).