URL semantics
Opened this issue · 2 comments
I want to be able to refactor different wikis aside by pasting a URL after the other
http://change.lab/view/welcome-visitors/http://jon.patterns.wiki.transformap.co/view/welcome-visitors
into the URL bar, like I am doing it at times, usually including the neccessary adaptations, when I don't want to leave traces of drags and drops.
If we understand "crude and unappealing" (tm) interfaces as unwelcoming human interaction choices, probably also reading all these /view fragments may not be needed at all one day? Yet I understand their existence is implied if we want to be able to distinguish between a remote and the current location.
Now I am asking myself why I am avoiding the drag and the drop at all.
We will have to come up with something else for touch interfaces so might as well make that work on the desktop.
These kinds of URLs occur in other places, such as hypothesis/via#158
We use different URL patterns for addressing wiki pages, lists of pages or lineups:
- http://fed.wiki/welcome-visitors.html
- http://fed.wiki/welcome-visitors.json
- http://fed.wiki/system/sitemap.json
- http://fed.wiki/view/welcome-visitors/view/how-to-wiki/fed.wiki.org/how-to-wiki/fed.wiki.org/field-guide-to-the-federation/hello.ward.bay.wiki.org/featured-sites/hello.ward.bay.wiki.org/featured-documentation/view/how-to-wiki/view/search-for-lineup/ward.bay.wiki.org/temporary-transclusion/view/lineup-diagram/future.fedwiki.org/fedwiki-card-lineup/future.fedwiki.org/lineup-links/future.fedwiki.org/lineup-viewer/ward.fed.wiki.org/lineup-url
- http://read.wiki.org/#fed.wiki/welcome-visitors/fed.wiki/how-to-wiki/fed.wiki.org/how-to-wiki/fed.wiki.org/field-guide-to-the-federation/hello.ward.bay.wiki.org/featured-sites/hello.ward.bay.wiki.org/featured-documentation/fed.wiki/how-to-wiki/fed.wiki/search-for-lineup/ward.bay.wiki.org/temporary-transclusion/fed.wiki/lineup-diagram/future.fedwiki.org/fedwiki-card-lineup/future.fedwiki.org/lineup-links/future.fedwiki.org/lineup-viewer/ward.fed.wiki.org/lineup-url
Optionally preserving the scheme in these URL lineups, we could possibly also transcend into other transports to widen the federation. Thinking of dat://, ssb:// or imaginable ones like ipfs:// or matrix://.
This correlates with WardCunningham/Smallest-Federated-Wiki#411 (comment) and recent experiments with http://found.ward.bay.wiki.org/view/wikis-robot-scouts/view/async-polymorphic-fetch