|
← Revision 4 as of 2013-04-17 18:32:46
Size: 667
Comment:
|
← Revision 5 as of 2013-04-17 18:34:53 →
Size: 656
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 8: | Line 8: |
|
* authorization persistence across reboot * state is maintained in perl data structure |
|
| Line 12: | Line 14: |
|
* authorization persistence across reboot * pitch * state is maintained in perl data structure |
Two parts:
- Captive portal mechanics:
- use something other than perl (too big a foot print)
- use iptables rules to track inbound/outbound traffic volumes (currently outbound only?)
- eliminate redundant crap
- make user experience smoother
- authorization persistence across reboot
- state is maintained in perl data structure
- Splash page:
- opportunity to pitch people on creating new nodes
- news from pt
- mobile version
- logo(s)
- terms of service
The Splash Page is rendered during the node configuration process.
The current thought is to put the splash page up on github someplace.