4 ms·
I'll mention Amaya here. https://www.w3.org/Amaya/ https://www.w3.org/Amaya/ The original vision for the web was that editing/creation had the same status as
by femto 8y ago
I'll mention Amaya here.
https://www.w3.org/Amaya/ https://www.w3.org/Amaya/
The original vision for the web was that editing/creation had the same status as viewing/consumption, and that websites were writable as well as readable. This is what Amaya implemented. It never gained wide adoption, but is served as a reference implementation of the W3C's vision of the web. (In my experience Amays is not particularly usable because it regularly crashes, but that could be fixed.)
Is Beaker similar to Amaya extended to use transport layers beyond http, such as ipfs?
- nine_k 8y agoI'd hazard to say that the concept of "wiki" is what successfully implemented that early vision of editable WWW. Wiki markup is different from HTML markup, but it represents many of the same (early) text-formatting and resource-linking concepts, while limiting the excessively powerful features of arbitrary layout, scripting, etc.
- edwintorok 8y agoHave a look at the federated wiki [0], it allows someone to easily fork someone else's page, edit it, and host it. History is tracked at the paragraph level. [0] http://fedwiki.org/view/welcome-visitors http://fedwiki.org/view/welcome-visitors
- kickscondor 8y agoI can't really answer this yet, because I've never heard of Amaya and I don't want to answer based on a cursory glance - but I really appreciate this link, as I love bits of Web history and I am going to do some homework on this. So, thankyou, femto!