Anyone can answer this guy here? i mean, he want to help and he seems
he can. So don't let him go on another open source project.<br>
<br>
Alexis<br><br><div><span class="gmail_quote">On 7/19/06, <b class="gmail_sendername">Sam Leathers</b> <<a href="mailto:disasm@gentux.org">disasm@gentux.org</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I'm interested in helping with the project. I have a few good ideas of<br>changes to enhance it.<br><br>First, to give you a little background:<br><br>I live in Central PA, and am looking at marketing free wireless setups
<br>to restaurants, bed & breakfasts, etc... in the area here. I have a<br>working test setup currently at <a href="http://wifidog.gentux.org">wifidog.gentux.org</a>.<br><br>Some ideas I have:<br><br>1) enhancements to the hotspot map. Integrations with google local, so
<br>if the business address matches google local, a search could be done of<br>restaurants, and it would return all restaurants on the wireless hotspot<br>map, same with inns/hotels, etc...<br>2) localities, I'm not sure if this is what networks could be used for,
<br>but it seemed the network list showed up for all networks at every<br>hotspot, let me know if I'm wrong with this. By localities, I mean<br><a href="http://city1.domain.com">city1.domain.com</a> and <a href="http://city2.domain.com">
city2.domain.com</a>, where the hotspot map for city1<br>would zoom around city1, and city2 would zoom around city2, then<br><a href="http://domain.com">domain.com</a> hotspot map would zoom out to show all localities. Then the
<br>default splash for all nodes with city1 would tailor to the city (ie. A<br>victorian historic district would have images of historic buildings on<br>the login and splash page, and a football town, would have logos for the
<br>team)<br>3) Locality administrators. This would require a database change I<br>think. Basically a username would need to have an array of localities it<br>administers, so it could change things for that given locality.
<br>4) Node user management. This is a little more tricky. This way, if John<br>Smith is abusing node_1, the manager of the node could block him from<br>node_1, but he'd still be able to access other nodes.<br>5) mac address blocking from auth server. This way a known abuser can't
<br>create a new user. maybe timed, so an abuse expires after a month.<br><br>These are the main ideas I have now. I have other ideas, but they aren't<br>quite as major. So what do I need to do to get involved in the project
<br>and submit changes to the base code? I know I can modify the php and<br>database myself, but I'm not looking customize the project for myself,<br>but to help make these changes so anyone can take advantage of them.<br>
Also, in regard to these ideas, do you think they'd be better as part of<br>the base of it, or modular where they can be enabled or disabled by the<br>user?<br><br>Sam<br><br>--<br>in life, direction is everything, distance is secondary--so keep your bearings!
<br><br>[KJV] Luke 5:16 And he withdrew himself into the wilderness, and prayed.<br><br>Get Firefox!!!<br><a href="http://www.spreadfirefox.com/?q=affiliates&amp;id=13731&amp;t=1">http://www.spreadfirefox.com/?q=affiliates&amp;id=13731&amp;t=1
</a><br><br>Exodus 6<br><br>_______________________________________________<br>WiFiDog mailing list<br><a href="mailto:WiFiDog@listes.ilesansfil.org">WiFiDog@listes.ilesansfil.org</a><br><a href="http://listes.ilesansfil.org/cgi-bin/mailman/listinfo/wifidog">
http://listes.ilesansfil.org/cgi-bin/mailman/listinfo/wifidog</a><br></blockquote></div><br><br clear="all"><br>-- <br>Alexis Cornellier<br>327 53eme Avenue<br>Pointe-Calumet, Québec<br>J0N 1G4<br>(450) 623-8454