A key feature of Lifeboat should be that it works well even without access to the capital-i Internet. Internet access is unlikely to be reliable in a disaster, for example, but also vulnerable to censorship and/or eavesdropping during protests or even targeted attacks (see Stingrays, for example).
One promising workaround is mesh networking, the ability to create a network in a peer-to-peer fashion using traditional internet technologies. Free software such as Serval exists on all major platforms for this purpose.
Lifeboat should be able to utilize this form of ad-hoc connectivity in addition to traditionally centralized Internet backbone architecture to receive and send alerts.
A farther-future version of Lifeboat could bundle a slimmed-down WordPress plus HTTP daemon and carry along its own Buoy "server," not just a client. This would effectively make each Lifeboat user their own Buoy as well, enabling their device to serve as a Buoy in a disaster situation where there is no Internet access for anyone at all, effectively creating an ad-hoc Buoy server for the survivors of a disaster or who have been kettled by cops and are forcibly disconnected from the canonical Internet.
This scenario depends on first accomplishing betterangels/buoy#17 and switching to OpenStreetMaps away from Google Maps, since the former allows offline caching of map tiles. (And also fuck Google.)
A key feature of Lifeboat should be that it works well even without access to the capital-i Internet. Internet access is unlikely to be reliable in a disaster, for example, but also vulnerable to censorship and/or eavesdropping during protests or even targeted attacks (see Stingrays, for example).
One promising workaround is mesh networking, the ability to create a network in a peer-to-peer fashion using traditional internet technologies. Free software such as Serval exists on all major platforms for this purpose.
Lifeboat should be able to utilize this form of ad-hoc connectivity in addition to traditionally centralized Internet backbone architecture to receive and send alerts.
A farther-future version of Lifeboat could bundle a slimmed-down WordPress plus HTTP daemon and carry along its own Buoy "server," not just a client. This would effectively make each Lifeboat user their own Buoy as well, enabling their device to serve as a Buoy in a disaster situation where there is no Internet access for anyone at all, effectively creating an ad-hoc Buoy server for the survivors of a disaster or who have been kettled by cops and are forcibly disconnected from the canonical Internet.
This scenario depends on first accomplishing betterangels/buoy#17 and switching to OpenStreetMaps away from Google Maps, since the former allows offline caching of map tiles. (And also fuck Google.)