|
← Revision 6 as of 2013-04-17 19:11:03
Size: 778
Comment:
|
← Revision 7 as of 2013-04-17 21:32:53 →
Size: 945
Comment: a couple more mechanics things
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 11: | Line 11: |
| * state is maintained in perl data structure |
* allow administrative redirections for misbehavior to explanations * state is currently maintained in perl data structure, maintain state in a file system (or similar) instead so that it can survive restarts |
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
- allow administrative redirections for misbehavior to explanations
- state is currently maintained in perl data structure, maintain state in a file system (or similar) instead so that it can survive restarts
- 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.