gMail. Please could you "invite" me you use GMail, becouse it is not able to register mayself witout it. my alternative mail is email@example.com for invite sending, please... P.S. (mail name withiut"-" - it is just for protection)
No worries, DONE! ENJOY! -7cows
Wikimedia already seems to have some sort of mirror for sites, however if we could just put a link to that page on EVERY page, we'd be good. I like the idea, it just doesn't seem like something that needs to be a seperate project. Thunderhead 17:39, 14 January 2007 (UTC)
Interesting suggestion, how would that work if a mobile phone is accessing the site, they would have to view the whole site and scroll down to find the link to reach the mobile version. Unless there was some script to detect if their HTTP Header was a mobile and re-direct them to the Mobile link (I don't think scripts are allowed on Wiki).
Alternativley you can have the link as you suggested (or little WikiMobile Icon) that points to a WAP site version of Wikipedia. For argument sake lets call it for now WAPwiki.mobi (.mobi is mobile URL's). The front page of WAPwiki.mobi will be the search page that will just provide mobile info sites available. You can also register each individual page with Google mobile which will bring them up on mobile searches. I think it would take of very qucikly (depending on how popular Mobile Browsing becomes).
The only real labour here is going through all the pages and manually compiling a summary or synopsis for the mobile version. This then has to be tested or done in a way that would be generic enough to display properly for most mobile wap browsers. Unless someone out there can put together a script or WikiSpider crawler that can automatically crawl through all Wikipages automatically generating a .mobi version of the site and pasting an Mobile Icon on main page (if this is allowed?). Then we just need people verifying the pages which can save a lot of time.
What are your thoughts? Suggestions?
- A simple (and maybe to crude) solution would be to have a proxy process the query.
7cows 10:17, 26 January 2007 (AUS)
- "Unless someone out there can put together a script or WikiSpider crawler that can automatically crawl through all Wikipages automatically generating a .mobi version of the site and pasting an Mobile Icon on main page " This is definitely possible, but obviously it's better to have humans look over the output. You might also want to look at the way w:HawHaw works, w:tikiwiki supports it, so mediawiki should as well.
- You might want to look at the way other wikis condense complex information for presentation on mobile devices; Among other advantages, the people trained in those practices could do a lot of other tasks. If you want an active discussion about mobility and wiki, you'll have to think harder also about verb/noun/type presentation. The old GUI interface of mediawiki won't work.
Hello!-- I've been thinking a little on the model developed by the simple Wikipedia, and it seems to me that the "simple" wikipedia would be better if it was a concise wikipedia: smaller, written in a simpler language. In a way, your MobileWiki proposal runs in the same direction: the contents should be shorter, to allow people to find the relevant information even on ther mobile devices (PDA, smartphone, whatever). If you allow me the comparison, this "mobile" wikipedia would be the Columbia Encyclopaedia, while the "full" wikipedia could be compared to the Britannica.--- Lwyx 19:33, 28 November 2007 (UTC)
- Let me rephrase my comments after a little more thought overnight.
- I fear that setting up a different domain for a "wikimobile" wikipedia would produce an unwittingly duplication of efforts. We're talking here of a series of projects (wikipedia, wiktionary, etc.) in several languages; if we set up a different "concise" wikipedia, wiktionary, etc. for each language, we'll have twice as many wikiprojects!
- Now: considering that most articles include basically a main summary, sections, and cross references ("see also" and "external links"), a workable solution without duplication could be the following: let the wikimedia software figure out that you're accessing from some mobile device (the HTTP header request or a suitable cookie in the desktop browser, for instance); then the server could return ONLY the text from the introduction and the cross references sections, ignoring pictures (displayed as links, accesible on request) and templates. This way, those interested in accessing/editing the "concise" wikipedia from mobile (or even "static") equipment could concentrate in these sections, leaving the rest of the contents untouched...
- My two penny thoughts.--- Lwyx 17:46, 29 November 2007 (UTC)