|
Size: 667
Comment:
|
Size: 1054
Comment: adding a link to the current splash page content that goes on new nodes
|
| 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 * 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 |
|
| Line 12: | Line 17: |
|
* authorization persistence across reboot * pitch * state is maintained in perl data structure |
|
| Line 19: | Line 21: |
|
* recognition of donors * thanks from the PT team to our sponsors |
|
| Line 23: | Line 27: |
| * the splash page content is [[http://git.personaltelco.net/?p=files-master;a=tree;f=www;hb=master|here]]. |
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.
the splash page content is here.