21–30 of 70 posts
Earlier quoted context omitted.
Would not it be better, as an interim state, to freeze the current content and provide it as static pages, likely with minimal server load.
It's in the post: So why close? It gives me room to work. The continuous scraping bumps up against my web throttling making all other web services useless. Even shell is painfully slow.
Earlier quoted context omitted.
Read the article. Unfortunately the content is looked up in a tangle of different character encodings and Ward needs to do a lot of work to convert it all into UTF-8. When that is done, it will all come back, better than before.
Why does Ward need to do that before putting a tarball up somewhere? I've seen so many sites cease to exist after undertaking ambitious overhauls like this.
Earlier quoted context omitted.
It's in the post: So why close? It gives me room to work. The continuous scraping bumps up against my web throttling making all other web services useless. Even shell is painfully slow.
So, he's developing on the same server the c2 wiki runs on? One solution is to not do that.
I was afraid that they'd get taken in by this federated wiki nonsense; I fear we might have lost one of the greats to second system syndrome. Federated wiki is a cool idea and all, but I don't want to have to build my own wiki of everything, or decide what concepts should be included in my own wiki. The whole strength of wiki to me is that it massively multiplayer user curated content, where the whole state is determ…
I was afraid that they'd get taken in by this federated wiki nonsense; I fear we might have lost one of the greats to second system syndrome. Federated wiki is a cool idea and all, but I don't want to have to build my own wiki of everything, or decide what concepts should be included in my own wiki. The whole strength of wiki to me is that it massively multiplayer user curated content, where the whole state is determ…
Has federated anything every really caught on?
I was afraid that they'd get taken in by this federated wiki nonsense; I fear we might have lost one of the greats to second system syndrome. Federated wiki is a cool idea and all, but I don't want to have to build my own wiki of everything, or decide what concepts should be included in my own wiki. The whole strength of wiki to me is that it massively multiplayer user curated content, where the whole state is determ…
Has federated anything every really caught on?
The part I don't understand is why they would take down a working site. They should of waited until they were ready to switch over.
The part I don't understand is why they would take down a working site. They should of waited until they were ready to switch over.
The post explains this. Closing gives space. That could be technical, psychological, social. Shutting down what's there is cleaner. If you miss it, this would be a good chance to thank the people who kept it running all this time.
Earlier quoted context omitted.
Why? I don't see any problem, the message seems quite clear; wikis (similar to forums) are hard to maintain (spam, server load & costs); new inventions are hard to promote (federated wiki mentioned in the post); and maintenance work on hobby projects is gruesome and taxing (thus any chance at getting some leeway by any means available is invaluable).
Would not it be better, as an interim state, to freeze the current content and provide it as static pages, likely with minimal server load.
Edit: turns out this was already the case. What I really want to say is that we should respect Ward Cunningham's choices in maintaining the site how he wants, in whatever way works for him.