Some good suggestions. On the UI, this would require a rewrite so may not be the direction we want to go, but I've been thinking about how to build good web-based UIs for apps for a long time now, in some regards Freenet was an early pioneer here, but unfortunately there has never really been a great option that met our needs.
I kept running into the same problems and so created something to try to solve the problem, it's called http://kweb.io/. The idea is that it makes it super-easy to create rich interactive web interfaces, and yet you never need to get your fingers dirty with javascript, it's all handled transparently. Kweb is written in Kotlin rather than Java, but Kotlin is fully interoperable and anyone familiar with Java should be able to get comfortable with Kotlin very easily. On the negative side, Kweb is still at the working prototype stage, but I've been tinkering with it for over 18 months at this point. If we wanted to take a fresh stab at the web UI, it would be worth at least considering Kweb. On Thu, May 24, 2018 at 12:59 PM, Arne Babenhauserheide <[email protected]> wrote: > Hi, > > This is a high-level roadmap. > > We had several roadmaps in the past. They focussed on releases and on > "when are we done". This one is different. It focusses on visions to > find a stronger audience. It does not shun controversial topics and it > is not a request for input. > > > These are the powerful visions I see, ordered alphabetically: > > > - Beautiful Freenet: Winterfacey by default, clean up UI warts > (i.e. first time wizard). Get rid of those UX hurdles which are likely > to cost us the most users. > > - Hosted Freenet: provide images (i.e. docker) to make it easy to run a > Freenet node for all the transparent freenet stuff which does not need > highest security but should be available to people who need highest > security. > > - Icicle Freenet: a crystal seed for darknet via mobile. Try the icicle > app. Improve it. Show it. It’s how we devs should be able to ping > other devs on their mobiles. > > - Mobile Freenet: transient nodes without storage which only connect > while on wifi and external power (~40% of the time) — and while the > user browses. Announcement is fast enough for that nowadays, and > median uptime of desktop nodes is lower (only two to four hours). > > - Multimedia Freenet: add more content filters and media tools. I want > to stream songs over Freenet with <2 minutes delay => m3u + opus + > tools to make that easy. Streaming video works well if > pre-recorded. Must avoid recently failed. > > - Stronger Freenet: Increase security against attackers, i.e. with > simple channels. > > - Transparent Freenet: backend to other apps, installed and started > on-demand. Makes Freenet available from any technology stack. Get > Freenet into all major distributions, so programs can use it there, > and provide a freenet-browser script and a run-with-freenet script > which does all the steps needed to start Freenet and connect the > browser or app securely (i.e. to Freenet with random IP and Port). > > - Unblocked Freenet: fix the pitch black attack and scale WoT. Makes > Freenet interesting to tech-savvy folks with >10 years of experience. > > > Best wishes, > Arne > -- > Unpolitisch sein > heißt politisch sein > ohne es zu merken > -- Ian Clarke Founder, The Freenet Project Email: [email protected]
