eBrainPool is a software technology enabling people to work together, play together and learn from each other.
You do this by sharing the modern day equivalent of tools such as their pen, lawn mower or car jack - share your software and computing resources.
"...What if I could simply use any software regardless of whether it is installed on my device or even designed to run on my device? "
Developer Code Released, Get it and Join us
We, over here at eBrain have always been GNU|FREE children.
Developer? Designer? Documenter? User?
We definitely need you :)
Come share and play in our pool.
As I look to embark on a trip to the sands of Phuket, Thailand in the next 3 hours, I'm pleased to announce that code to implement sandboxing is now up in it's own branch in the git repo.
This is a Followup Post to eBrainPool Messaging System.
What follows is my current understanding of how thrift works. I am still not competely sure that I have it right, and as I learn, I will append / change this post accordingly.
Getting back to what is the kind of communication happening between two eBrainPool clients. When they discover each other, and know the route to connect to each other, how do they exchange information? Background Reading: Our Earlier post, Workflow Sketch, how it fits together (the exact workflow is now updated), and Under the Hood we now have an updated architecture, but they should be a good starting point if you need a refresher
Hello everyone.....yes we haven't been able to ask someone to RTFM so far since hmm well there has been no manual ;).....well all of that is a step closer to being changed thankfully :)
As of last night I've completed documenting the code in the current master. I've formatted the code documentation in Doxygen style and the code documentation in HTML / Latex has been pushed onto the repo.
Hopefully this makes understanding the code a lot easier. It also brings to light TODO's in the code and pitfalls we need to fix.
Having put in code to handle Avahi discovery in what has now been labeled as the 0.3 release, I have been focusing on having an integrated libssh based server.
Thought I'd close this year with a 0.3.0 release of eBrainPool. Code now put up on git.
This release is quite a milestone since it follows what the community has been advising us and moves away from the olsrd binding we had for discovery via our custom olsr plugin. Therefore, discovery is handled by Avahi now and eBrainPool works with any network which works with Avahi/mDNS.
As we had reported here, we came to the realization that the eBrainPool client needed to be ported away from Nbtk/Clutter which is now depracated and the devel libraries are no longer available on Debian testing onwards.
The eBrainPool client was built on Nbtk/Clutter primarily for Moblin which required this. Since it ran on other linux distros too (and because we are short handed - HELP ;) ) we kept it as is even though this has been gnawing away at us.
You know what the die-hards say "command line is the only way".. Ashamedly, I will have to admit that it is one of my favourite fall-backs too. There is however nothing wrong with making our lives a little simpler.
Well guys, I thought that while I work with the libssh guys and we figure out what is causing the strange behaviour I have been seeing with my ssh server, I'll go through the eBrainPool client code and see where we need to strengthen it - fix any potential memory leaks, run it through Valgrind, that kind of thing.
Browse Code
View our code tree here. This is the publicly vieweable browser of the source tree, containing the main client code and our supporting projects,