Re: [freenet-dev] What blocks Freenet adoption?

2016-01-06 Thread hyazinthe
I second Steve's statement. We've done enough 'looking what all is bad' stuff 
in recent past, people already know what's wrong, that's enough.
Keep doing it - even when done in a very friendly and nice tone - just 
demotivates and that highens unproductivity.


Greetings,
Tobias Lechner

--- Ursprüngliche Nachricht ---
Von: Arne Babenhauserheide 
Datum: 04.01.2016 02:26:28
An: Discussion of development issues 
Betreff: [freenet-dev] What blocks Freenet adoption?

> I asked myself that question. These are my answers. Please add yours!
>
> Note: This is just for listing. Please don’t discuss these before January
> 16th.
>
> What blocks Freenet adoption?
>
> - Our themes look clunky and our web-interface is slow. Why is access
>   to bookmarked activelinks slow? Why isn’t 404 sent instantly (for
>   bookmarked activelinks) -> remove the checkbox “has an activelink?”,
>
>   just check instead. Prefetch activelinks at random intervals.
>   -> FreeStyle announced in FLIP to be working on new themes.
>
> - Hackers in-the-know reject Darknet due to the non-implemented fix
>   for the Pitch Black Attack. It’s been simulated several years ago
>   and just needs implementation.
>
> - Our installers often fail -> Work is already being done for Windows
>
>   and OSX (short of being deployed) and for Debian packages. Gentoo
>   mostly works (except for a hard-to-trace compression bug).
>
> - No working Darknet invites. We say “use darknet”, but advise
>   against that (“only connect to …”) and don’t make it easy and
>   useful. And new Darknet users get horrible performance. I invited
>   about 5-7 people over the past years, and at least 3 left again
>   because Darknet with a single friend is slow. For the others I
>   moderated the noderef exchange with my existing friends by manually
>   sending them each others references. To get adoption via Darknet,
>   this has to be fast on the initial connection without additional
>   manual interaction ← requirement.
>
> - WoT consumes too many resources (build 18 is faster, but my node
>   OOMs now, also without Sone).
>
> - New users don’t see what they can do with Freenet. We don’t fix
>   that, because starting to use WoT takes over an hour, so most of our
>   services can’t be shown to new users. -> Sharesite should improve
>   that (publish easily: due to Tor inproxies “Freenet is the easiest
>   way to publish a site in Tor”) -> recover Freemail v1 or recover
>   LCWoT and LCIntro and activate them by default (switching to
>   regular WoT once it works well enough will be easiy thanks to
>   having the same FCP interface). -> recover flircp and add it as
>   official plugin, active by default with random name per startup
>   to avoid timing attacks. Autoconnect to #public or such.
>
> - Does not work on mobile phones -> now that db4o is gone, it could be
>
>   worthwhile to change that. Using only while connected to power and
>   wifi should give 8-16 hours uptime (given that people plug in their
>   phones at night, at work and in trains), which is more than what
>   half the nodes in Freenet have. Freenet can cope with 30% backoff,
>   so being offline 30% of the time should work.
>
> - Opennet starts slowly. Our seednodes are overloaded. -> announce
>   through previous peers.
>
> - Our website looks much better now, but it still needs serious design
>   work to get on par with modern sites. It’s at a point where I’m
>   happy to show it, but not yet at a point where someone who randomly
>   hits the site instantly feels a desire to try Freenet.
>
> As you see, most of these can be fixed.
>
> Please add what I missed.
>
> Best wishes,
> Arne
> --
>   Writing about Freenet
> http://draketo.de/stichwort/freenet
>
>
> ___
> Devl mailing list
> Devl@freenetproject.org
> https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
___
Devl mailing list
Devl@freenetproject.org
https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl

Re: [freenet-dev] Freenet 0.7.5 1471-pre3

2016-01-06 Thread Steve Dougherty
On 01/03/2016 10:17 AM, Steve Dougherty wrote:
...
> - Due to node reference changes packets for setting up connections to
>   opennet seednodes are now larger. If you have low MTU (lower than
>   the typical 1500 bytes) this may prevent you from connecting to seed
>   nodes.

My mistake - Freenet has an MTU setting that defaults to 1280 bytes,
which should be the one mentioned here. 1500 bytes is for Ethernet.



signature.asc
Description: OpenPGP digital signature
___
Devl mailing list
Devl@freenetproject.org
https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl

Re: [freenet-dev] What blocks Freenet adoption?

2016-01-06 Thread Ian
On Wed, Jan 6, 2016 at 4:28 AM,  wrote:

> I second Steve's statement. We've done enough 'looking what all is bad'
> stuff in recent past, people already know what's wrong, that's enough.
> Keep doing it - even when done in a very friendly and nice tone - just
> demotivates and that highens unproductivity.
>

I've never heard of a project that didn't try to maintain a clear idea of
what the project's priorities should be.  Are you saying that we already
have a comprehensive list of the issues in priority order?

If not, and it really doesn't sound like we do, then any discussion that
leads to one is entirely appropriate in any project, and there is no reason
anyone should be demotivated by it.

Ian.
___
Devl mailing list
Devl@freenetproject.org
https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl

Re: [freenet-dev] What blocks Freenet adoption?

2016-01-06 Thread hyazinthe
All I'm saying is:
1. One has good things to look at, neutral things to look at, and bad things to 
look at.
2. One should look at all, but it's important to have a balance between all. 
Only focussing on bad things drags you down.

Greetings,
Tobias Lechner

--- Ursprüngliche Nachricht ---
Von: Ian 
Datum: 06.01.2016 16:12:48
An: hyazin...@emailn.de,Discussion of development issues 

Betreff: Re: [freenet-dev] What blocks Freenet adoption?

On Wed, Jan 6, 2016 at 4:28 AM,   wrote:
I second Steve's statement. We've done enough 'looking what all is bad' stuff 
in recent past, people already know what's wrong, that's enough.
Keep doing it - even when done in a very friendly and nice tone - just 
demotivates and that highens unproductivity.


I've never heard of a project that didn't try to maintain a clear idea of what 
the project's priorities should be. Are you saying that we already have a 
comprehensive list of the issues in priority order?


If not, and it really doesn't sound like we do, then any discussion that leads 
to one is entirely appropriate in any project, and there is no reason anyone 
should be demotivated by it.


Ian.
___
Devl mailing list
Devl@freenetproject.org
https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl

Re: [freenet-dev] What blocks Freenet adoption?

2016-01-06 Thread Arne Babenhauserheide
Am Mittwoch, 6. Januar 2016, 11:28:46 schrieb hyazin...@emailn.de:
> I second Steve's statement. We've done enough 'looking what all is
> bad' stuff in recent past, people already know what's wrong, that's
> enough.  Keep doing it - even when done in a very friendly and nice
> tone - just demotivates and that highens unproductivity.

What we did not do is gather the stuff to ensure that we don’t miss
something which is easy to fix.

I’d like to give the background on how I got to think about this:

When I sent the proposal to the open tech fund, they answered, among
others, “it isn’t clear that users will adopt this”. So for the next
proposal (which I sent just before new year), I collected the things
we know which are blocking adoption.

It was then that I realized that we had not done such a list. As in
not ever. We had lots of bugs to fix and lots of longterm plans, but
no clear list which said “this costs us users who might otherwise use
Freenet mostly as it is right now”.

And I don’t think that I see the whole picture all by myself.

That’s why I created this list and sent it here.

Best wishes,
Arne
-- 
1w6 sie zu achten,
sie alle zu finden,
in Spiele zu leiten
und sacht zu verbinden.
→ http://1w6.org



signature.asc
Description: This is a digitally signed message part.
___
Devl mailing list
Devl@freenetproject.org
https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl

[freenet-dev] Applying for pro UX help for free

2016-01-06 Thread charles
So I just found this program for free software projects that support
free expression online to apply to to get help with UX.[1] I think it
would be really useful for us to apply for this. There are so many
places we could try and improve UX. I don't think they would necessarily
help with the development side of things, but it would still be really
valuable to get input and data from pro UX people. They could also help
run usability studies and such.

-Charles

[1]  https://simplysecure.org/blog/apply-for-help/




signature.asc
Description: OpenPGP digital signature
___
Devl mailing list
Devl@freenetproject.org
https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl

Re: [freenet-dev] Applying for pro UX help for free

2016-01-06 Thread Ian Clarke
That would be great Charles, would you be able to submit an application?
If you need any help just let me know.

On Wed, Jan 6, 2016 at 2:25 PM, charles  wrote:

> So I just found this program for free software projects that support
> free expression online to apply to to get help with UX.[1] I think it
> would be really useful for us to apply for this. There are so many
> places we could try and improve UX. I don't think they would necessarily
> help with the development side of things, but it would still be really
> valuable to get input and data from pro UX people. They could also help
> run usability studies and such.
>
> -Charles
>
> [1]  https://simplysecure.org/blog/apply-for-help/
>
>
>
> ___
> Devl mailing list
> Devl@freenetproject.org
> https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
>



-- 
Ian Clarke
Blog: http://blog.locut.us/
___
Devl mailing list
Devl@freenetproject.org
https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl