|
Size: 667
Comment:
|
Size: 778
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
|
This is brainstorming of possible requirements |
|
| Line 8: | Line 10: |
|
* authorization persistence across reboot * state is maintained in perl data structure |
|
| Line 12: | Line 16: |
|
* authorization persistence across reboot * pitch * state is maintained in perl data structure |
|
| Line 19: | Line 20: |
|
* recognition of donors * thanks from the PT team to our sponsors |
This is brainstorming of possible requirements
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
- recognition of donors
- thanks from the PT team to our sponsors
The Splash Page is rendered during the node configuration process.
The current thought is to put the splash page up on github someplace.