|
← Revision 1 as of 2013-04-17 18:08:04 →
Size: 126
Comment: initial features that would be desirable in a new captive portal/splash page system
|
Size: 667
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 4: | Line 4: |
|
* 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 |
|
| Line 8: | Line 11: |
| * |
* news from pt * authorization persistence across reboot * pitch * state is maintained in perl data structure * 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. |
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
- Splash page:
- opportunity to pitch people on creating new nodes
- news from pt
- authorization persistence across reboot
- pitch
- state is maintained in perl data structure
- 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.