[freenet-dev] Berlin or close resident needed, Fundraising opportunity on May 2-5

[xor]

Hey folks,

I recently attended a local Internet politics meetup to speak about Freenet, 
at the hope of getting ideas for fundraising.
We turned out to chat about it for 4 hours, and one of the politicians there 
likes Freenet and is indeed interested in helping us with acquiring donations!
His plan is to speak to higher level members of the green party about this.

He will be at the re:publica "Web 2.0" conference in Berlin, May 2-4.
On Thursday May 5, he'll also attend the screening of a movie from a 
politician who he suspects to be able to help.

I cannot be there myself unfortunately.
So if one of you folks can be in Berlin on May 2-4, and/or ideally on May 5, 
it would be nice if you could accompany the guy so he has a Freenet expert at 
hand.

If you are interested, please quickly send me a mail about how you're easy to 
be contacted, for example your phone number, as this is next week already.

Thanks & Greetings

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

Re: [freenet-dev] Possibly obsolete code in AnnounceSender and reordering problem during opennet announcements

[Martin Byrenheid]

On Sunday, April 17, 2016 06:51:25 PM Matthew Toseland wrote:
> On 01/03/16 13:52, Martin Byrenheid wrote:
> > On Wednesday, February 24, 2016 05:38:09 PM Matthew Toseland wrote:
>  The message should have been matched anyway: Unmatched messages (in
>  MessageCore are added to a data structure and we check before timing
>  out
>  the waitFor()). Possibly a concurrency issue, I thought I'd debugged
>  all
>  such problems ages ago. :(
> >> 
> >> It seems unlikely that a race condition like that would happen reliably,
> >> so I don't know what is happening here.
> > 
> > I looked at the log output again and found that the problem might be that
> > an unmatched message from a source that is not routable gets still marked
> > as matched.  In my case, it's the FNPBulkPacketSend-message that gets fed
> > to the NodeDispatcher before the actual noderef-receiver thread starts.
> > And since it gets marked as matched, it won't be passed to the receiver
> > thread later on. This behavior was introduced near the end of last year
> > [1]. However, I'm not sure if the problem lies in the fact that the
> > message gets marked as matched although it actually doesn't seem to be or
> > if the source (in my case, it is a SeedServerPeerNode) should normally be
> > considered as routable. What do you think? In my case, reverting the
> > commit mentioned above solved the problem.
> Yes, we fixed this in the most recent build. Please confirm.

Yes, bootstrapping via seed nodes works fine now. Thank you!

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