A few points 1. Yes you can look at my transports2 branch on my repository or chetan-transports on freenet's. 2. This needs to be merged before you start working. I think you should not start till this is done. This is not easy and needs testing and will take time. 3. I have not been able to implement a sample plugin because there are a few hacks in my code. This is because I could not completely refactor everything in freenet. It will take time. 4. Yup. You can run two or three nodes and test. 5. You can get a cloak in free node. You can ask your previous organization or wait to become a developer at freenet or get an unaffiliated one(anyone can get this). 6. If the above is resolved you can come on IRC. I would prefer that. I don't run sone all the time. 7. Implementing the architecture for streams will need to completed before the plugin. Lot of work there :)
And do send me an email when you are on IRC. We can discuss more. And yes we can wait one more day for the results. Thanks Chetan On Apr 7, 2013 7:41 PM, <[email protected]> wrote: > Hey Toad and Chetan, > > Matthew Toseland <[email protected]> writes: > > Implementing a simple stego'ed UDP transport might be an idea? > > (E.g. with a custom header) I suspect even this will require a lot of > > fixes to the transports branch though, since it only has the basic UDP > > transport working at the moment ... > I like this idea as it force me to delve into chetan's code. I had a little > peek into the last summer commits and the code. So I need to inherit > my new transport from PacketTransportPlugin and implement > startPlugin/stopPlugin/resumePlugin/pausePlugin and toPluginAddress, > isn't that correct? > > Unlike StreamTransportPlugin that has more function than its parent > (connect and listen) PacketTransportPlugin seems to be identical. Maybe > It is for consistency and readability. > > 1) Is there any other sample HelloWorld packet transport plugin that is > implemented? > > 2) If I implement a plugin how can I test it? I should make a darknet > of two nodes of mine? then I need to run two instance of freenet on my > computer on different ports. Is that possible? > > > We use irc.freenode.net. We (devs) don't use a tor hidden service. A > > few people use FLIP, but it's slow. For talking to the wider anonymous > > community FMS and Sone are the best options. > > If I don't use Tor my IP will be easily discoverable on IRC. oftc.net > and srh.org are easily allow me to connect to IRC without tor, freenet > only > allows one hidden server to connect to it and (I guess) because of that, > it is always busy and I can't connect to freenode.net most of the time. > > Can I talk to devs (Toad and Chetan at least) using Sone or any other > freenet service (so I can keep my IP to myself)? > > If it is too much of hassle I can get a public VPS and run my IRC client > on it to protect my IP. > > > You'd need to work quite closely with Chetan; there's plenty of room > > to expand the proposal, once you get streams working you can > > e.g. write more stream transports, and no doubt there are complicated > > issues in the core code related to e.g. bandwidth limiting. However, > > *if* Chetan has the time to mentor (at least several hours per week > > IMHO, especially in core code which can be quite complex to > > understand), this seems like a good idea. > > That seems to be a good proposal plan. Which stream transport is more > desirable something like HTTP or something that encrypt everything so > the traffic doesn't look like anything special? > > Once I get familiar with Chetan's design and the related core code, I > should be able to work more independently. I hope freenet get > selected. Does freenet, has a pre-defined format for GSoC proposals? > > Thanks for your helps, > Vmon > _______________________________________________ > Devl mailing list > [email protected] > https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl >
_______________________________________________ Devl mailing list [email protected] https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
