[dexen]

The C2 wiki was re-written and re-implemented as single page app, currently at http://fed.wiki.org/

It is an interesting change, to a more federated style.

I ended up doing a small project inspired by this change, at https://github.com/dexen/tlb

[ricardobeat]

Complete with unnecessary page transitions, cascading loaders and a ton of layout shifting. Classic SPA success story.

[bongobingo1]

I don't 100% disagree with the sentiment, but I think in this case the push-in style transitions fit well with a knowledge base wiki in which you (or at least, I) often drill down and pop out of topics.

Though... that particular implementation seems to not handle unwinding the stack very well. And as the classic web2 adage goes, if you think your animation is "just right", knock another 3rd off it at least.

[mananaysiempre]

IMO TiddlyWiki[1] is a much better implementation of this UI idea of bite-sized, heavily linked text (card catalog?) with multiple simultaneously visible entries. (No federation and a bizarre storage approach though.)

[1] https://tiddlywiki.com/ (haven’t looked at the homepage in years, the current one seems kind of awful and not really bite-sized unfortunately).

[fsckboy]

> It is an interesting change, to a more federated style.

what does "federated" mean in this context? do you mean decentralized segmented "peer to peer" storage, or something?

unfederated wikipedia is not helpful in defining federated:

Federated content is digital media content that is designed to be self-managing to support reporting and rights management in a peer-to-peer (P2P) network. Ex: Audio stored in a digital rights management (DRM) file format. https://en.wikipedia.org/wiki/Federated_content

[mananaysiempre]

That’s certainly.... a definition of a thing. That I haven’t seen once in my life. In any case, the relevant page is https://en.wikipedia.org/wiki/Federation_(information_techno... .

The idea is essentially to follow the way email (and partly the Web) works: users aren’t tied to one server (centralized), but neither are they required to each run their own one (peer-to-peer), instead there’s a narrower group of server operators who host users, but those users can cause the server software to connect to a server it doesn’t know about if they mention it explicitly.

Of course, if the protocol is too weak in allowing the operator to control those connections (in either direction), it will evolve informal means for that which will make all but the largest servers extremely unreliable, much as email did. On the other hand, the experience of Mastodon shows the dangers of operators exercising too much control (where e.g. Mozilla seems eager to defederate with any server that has anyone post anything even slightly offensive or objectionable to anybody whose opinion Mozilla considers valid).

The federated wiki idea as promoted by Ward seems to be to have the federation (network of servers) be able to browse each other’s pages—so far so Web—but then to allow each user to clone and edit any page anywhere, storing the clone on their own server. The original page isn’t affected, except I think there’s a provision for some sort of backlinking (referral spam? what’s that?). It doesn’t sound unreasonable, but I’m not sure it can support anything interesting either—for a large pool of collaborators you’d need a Torvalds-like full-time merge BDFL, and I haven’t even seen a discussion of pull requests or anything similar.

[manojlds]

Works bad on mobile with some weird transitions. Can't believe C2 is fallen to this trap as well.

[gtirloni]

> The C2 wiki was re-written and re-implemented as single page app, currently at http://fed.wiki.org/

It seems empty. Or am I not grasping what this is?

[jacobsenscott]

I don't believe C2 was moved here. The Federated wiki seems to be Ward Cunningham's experiment - an answer to centralized wikis - also invited by Ward. It is interesting, but as far as I can tell not some kind of mirror of the content on C2. If you click "recent changes" a lot of stuff comes up, mostly about federated wiki.

[imachine1980_]

holly cow this redisign is awfull, im not against federated content, but this inst a wiki at all

[WesolyKubeczek]

But all the old content seems to be gone (or all links to it are broken)

[insulanus]

Sadly, I've had bad experiences with some Single Page Apps. Here are some problems I've had:

Linking to a specific topic.

Archiving the site.

[SpaghettiCthulu]

Also routing breaking if you trigger back/forward too fast (looking at you, GitHub)

[Zanfa]

This is completely broken and unusable on latest iOS Safari.

[forgetfreeman]

If you find inspiration in converting a raft of long-term usable URLs into a single page usability clusterfuck one questions your motives and your craft.

[jimbosis]

Is there any way to see a running demo of tlb (or a real-life website)?

[ilyt]

...that is fucking terrible.

Do they not know back button and tabs exist in browsers ?