Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Francis Brunelle
    @frabrunelle
    I love Gitter! <3 Thank you for adding this chat room :+1:
    David Irvine
    @dirvine
    The tap is certainly on :-) Hope this allows more general comments on RFCs
    Your welcome @frabrunelle
    Peter Jankuliak
    @inetic
    @dirvine, I'm rereading the https://github.com/maidsafe/rfcs/pull/11/files PR, I think there is a lot of missing context there, which makes it very hard to understand at least for me.
    David Irvine
    @dirvine
    I am probably very close to it, in what way do you mean. This is to really have a types of StructuredData in routing that everyone can use, but they need to identify their type. So StructuredData is data that retains it's position in the network and can be referenced from other data elements, even when it updates.
    Peter Jankuliak
    @inetic
    E.g. in the summary paragraph, you start with giving a name for two new data structures and stating that they will contain a type_tag, this is a really generic idea and could apply to about any problem, so I think it should first be specified what the problem is and what are the current approaches of dealing with it.
    David Irvine
    @dirvine
    I see, our problem is that we define exactly each structured data in types and pass back to routing traits. This is confining and not extensible without us coding each new type. App devs then have little or no chance to create their own types, where we can guarantee security
    We are all really used to the terms in house which probably makes it confusing though.
    Peter Jankuliak
    @inetic
    Yes, e.g. I, myself wasn't in any of the discussions about maidsafe_types, so such context would be essential.
    David Irvine
    @dirvine
    Yes we need to ensure system docs are clear and perhaps link to there for current scheme, otherwise the RFC would get too big perhaps? We do want community members to be able to get that info fast as well.
    Peter Jankuliak
    @inetic
    Links should be fine, but being redundant is also helpful sometimes. In general, I think stating clearly what the problem is should always be somewhere at the beginning.
    David Irvine
    @dirvine
    Yes, I am trying to follow Rusts examples here though and provide a single para summary, so it's hard to fit everything in there. (we take ages and pages to explain these types and why they are like they are)
    Peter Jankuliak
    @inetic
    Another, minor, thing I wanted to ask is whether we need Option<Vec<...>> in two occasions: previous_owner_keys and signature. The answer to that question lays in answer whether e.g. None and Some(empty_vector) have different meaning.
    David Irvine
    @dirvine
    No I think None is fine there, I am not 100% sure difference between an empty vector and None, perhaps None is smaller? It feels easier to use in this case, but I am certainly not fixed on it.
    Peter Jankuliak
    @inetic
    Sorry, what I'm trying to say is that in most cases we don't really need the type Option<Vec<T>> because Vec<T> is powerful enough.
    David Irvine
    @dirvine
    Ah yes I get your point, as it's a container Empty is a special case without needing a new type. That makes sense. If you comment on the RFC there I will get it updated and update the doc to comply. Makes perfect sense
    Peter Jankuliak
    @inetic
    :)
    David Irvine
    @dirvine
    :+1:
    Pretty good for a fella with a fever :D
    Peter Jankuliak
    @inetic
    :) I'm looking at the Rust RFCs, they are indeed quite smaller than RFCs I'm used to.
    Zac Stewart
    @zacstewart
    Hi all
    Vinícius dos Santos Oliveira
    @vinipsmaker
    hello @zacstewart
    Zac Stewart
    @zacstewart
    I'm looking for an entry point to this project. I'm a decent rust hacker and I'm looking for a project to focus on
    Is there room for contributors right now, and if so, which area needs help the most?
    Vinícius dos Santos Oliveira
    @vinipsmaker
    by room, you mean a room on gitter?
    Benjamin Bollen
    @benjaminbollen
    routing! :) - this is not a bias point of view at all
    Zac Stewart
    @zacstewart
    @vinipsmaker: by room I mean space :)
    er, capacity
    But any such room on gitter would also be cool
    Vinícius dos Santos Oliveira
    @vinipsmaker
    oh, sorry
    Zac Stewart
    @zacstewart
    @benjaminbollen: do you have a schpeel? What could I do to help?
    Network programming is definitely something I'm interested in learning more about.
    I wrote this tiny DNS proxy hack to learn to use Rust's socket stdlib: https://github.com/zacstewart/fasterdns
    Benjamin Bollen
    @benjaminbollen
    if network programming is your interest either CRUST or routing can be a good call
    we're currently planning out tasks in both libraries, and there are already open issues (at least in routing)
    Zac Stewart
    @zacstewart
    Cool. I'll check it out.
    Benjamin Bollen
    @benjaminbollen
    thanks @vinipsmaker !
    the ones with a 'ready' label should be good to pick up, but feel free to comment on them asking questions, ping me (if for routing)
    Prakash
    @chandraprakash
    @zacstewart we are currently in planning and will be scoping up multiple new tasks in all libraries.
    As @vinipsmaker already mentioned the links, a good starting point will be to fix ready issues.
    Also get familiar with the libraries and help us in the upcoming sprint.
    Feel free to clarify any doubts :-)
    And yes Welcome to the project !
    Zac Stewart
    @zacstewart
    Thank you all!
    Zac Stewart
    @zacstewart
    Is anyone planning to go to RustCamp in August?
    I just got my ticket this weekend
    Benjamin Bollen
    @benjaminbollen
    as far as I am aware, from the local Scotland office no-one is. Maybe some US based collaborators might go
    Vinícius dos Santos Oliveira
    @vinipsmaker
    I shouldn't plan trips for awhile, but maybe next year I'll go =P
    Grizmoblust
    @Grizmoblust
    I want help you guys testing crust/routing, where can I start?
    David Irvine
    @dirvine
    @Grizmoblust At the moment as much testing in Crust is great, we are currently integrating utp and also udp hole punching. We cannot test it enough so please look at the tests and see what you can do there.
    Routing is pulled apart in refactor right now and will likely over next few days, so right now crust is great and we will let you know when routing is OK again. I use libraries.io to watch for crate updates, if you sign up there you will see us pushing the new routing create (soon I hope).
    @zacstewart Did you get anywhere? Things will be much simpler after this week, so please lets us know if we can help you get comfortable.