Ian Clarke
Ian Clarke
* Peers track CPU and bandwidth usage, attributing it either to the peer's user, or to other peers * eg. Peer A sends request to peer B, peer B keeps...
* Greedy routing will always pick the closest peer to the desired location. * But optimal strategy is to pick the peer that will complete the request fastest * Use...
* Inboxes stored in a secure decentralized way in the network * Support PGP transparently to the user, consider: https://sequoia-pgp.org/ * Gateway to normal Internet email through freenet.org, potentially allocating...
I think we need to rethink the DSL to support this kind of usage: ```kotlin doc.body { section { classes("section") h1 { classes("title") text("What would you like to know?") }...
related: #68 In the event of a websocket connection failure, Kweb should exponentially back-off in the event that it is unable to establish a websocket connection - and display a...
Samples aren't showing up in Kdocs, seems to be a regression of some kind in Dokka. I asked on Reddit about it [here](https://www.reddit.com/r/Kotlin/comments/oqryy1/is_there_a_current_explanation_for_how_to_use/).
Should be easy enough using [JSoup](https://jsoup.org/cookbook/input/parse-body-fragment). Ideally it could be made available online, similar to https://jsonformatter.curiousconcept.com/.
Currently routing doesn't fully support browser history functionality, like handling the back button. See [routing.kt](https://github.com/kwebio/core/blob/master/src/main/kotlin/io/kweb/routing/routing.kt).
Looks like a good candidate for a Kweb plugin, CSS only: https://bulma.io/