This is brainstorming of possible requirements
- 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
- 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.
KeeganQuinn now has a mirror in GitHub; he will accept pull requests and merge into the main PTP repository and vice versa. This may make it easier for people to contribute? https://github.com/keeganquinn/ptp-files-master
Please bear in mind that the main PTP repository is the production version, please use a separate branch for any development versions, thanks! --RussellSenior