Long-term: What *can* we do re dynamic/semidynamic HTML content? Different models of updating. Searching, of course (with published indexes initially). Simplest thing would be the ability to toggle different categories on and off, like in a categorized blog feed. Could e.g. tweak your own new/updated page on the indexes... or even TFE. Best way to do this would be to support some of the nice stuff you can do with XML... but would need some other stuff too... Message board sites - possible? Surely... For both of these, we don't actually need a full scripting language. We can do a lot with fairly simple query and transformation languages. Hence: - Underlying XML: list of sites, their alinks, etc. - Style sheet transforms this into TFE. - User can change a parameter of the style sheet by clicking a link. This requires minimal serverside support (normally one would use javascript). - If style sheet is clever enough, can select or deselect sub-parts by arbitrary criteria, then re-order the whole document. Can current standards do this? Are they implemented, or would we need to pull it in on serverside? - Next stage is to query the node for a range of documents. E.g. we might have each category in a different file, and want to combine them. Or we might want to pull in every message posted to a board. We can do *a lot* with this. - What about wiki? Challenges: -- Word highlighting. Easy; we know when a word is a WikiWord, and we know when it has an explicit link... what slows things down is looking up whether they are defined or not, so don't bother. -- Authoritative latest version. This is rather harder. It may be possible to provide an authoritative latest version via a central, but anonymized, server; this has some major issues however (intersection attacks, bandwidth abuse of the sort of messaging/streams that would be needed, etc). Also login. This gets into the whole anonymous collaborative authoring thing, which is an interesting problem to tackle later. Maybe can approach it like distributed RCS?? Would require additional support anyway.
Hopefully if we can separate fproxy into a separate module with clean interfaces to the node and a stub that lets you debug it without having to look at node code, and if we rewrite it to be less horrible, non-core people will look into these sorts of things... -- Matthew J Toseland - toad at amphibian.dyndns.org Freenet Project Official Codemonkey - http://freenetproject.org/ ICTHUS - Nothing is impossible. Our Boss says so. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: Digital signature URL: <https://emu.freenetproject.org/pipermail/tech/attachments/20051117/46e3de19/attachment.pgp>
