WikiWikiWeb is back online
wiki.c2.com
wiki.c2.com
I thought for sure they did a PJAX [1] like design when I saw the spinner to keep asset loading minimal (why c2 would need that is beyond me).
But it is even worse. A full page reload on each click and then an XMLHTTPRequest call is made for some JSON.
I wonder who is running and why they picked such an awful design. Do people just not know how to write old web 1.0 apps?
For now I will play devils advocate and just assume perhaps they are offering JSON like API so that someone else can maybe write a better skin. If some one does hopefully they will use push state.
EDIT
I clicked around to see what Ward has been up to and now I can sort of see why c2 is the way it is. Basically Ward is working on Federated Wiki. I think the idea is sort of cool as it is yet another attempt to continue to decentralize the web.
I believe it is going to be based on some JSON protocol but it would be interesting and perhaps have greater consumption if it was in Google AMP format or supported that format or converted or whatever (not c2 but the federated wiki stuff).
See also: https://github.com/WardCunningham/remodeling/issues/2 http://wardcunningham.github.io/
Then again I probably don't fully understand all of the problems.
it took some digging but I managed to grab a dump of every page in JSON. he hid it well but I scraped everything and put it up for people to see (it's in its original markup form, and I'm working on converting it to HTML again.)
the wiki's been locked for quite a while. why not keep it that way. the existing commentary is at least more valuable than the ability to edit it.
provide a static mirror, ward, and I won't have to mirror your "database" of json! ;)
That's not particularly helpful for people crawling and not keeping state between page hits, but it should make a difference for end users if done right.
https://imode.gitlab.io/projects/c2/index.html
if someone wants me to, I can archive it up.
I'm not concerned.
> None of the “sha256” hashes in the integrity attribute match the content of the subresource.
The basic concept behind federated wiki is interesting, but it still needs to be simple, clean, and usable. As it is, the most basic things like selecting text or navigation do not work or work in totally unexpected ways. It shouldn't actually need instructions for basic things like How to Follow Links and How to View Changes ("you can view the changed page on that site by clicking on the flag of that page. Don't expect the link to find the remote site because it will likely be hidden behind the original page on your site." What?)
Just trying to find the list of sites, I have no idea what's going on here: http://c2.fed.wiki.org/view/welcome-visitors/view/federated-...
I'm not a fan. I worry for the other rabbit holes of the internet that are still smart and able to be searched, mined, and mirrored easily.