Yes mumble audio is way superior, then more interactive if others join in. We can easily record that and we can add to the vid easily.
1 Like
The guys got the message about audio quality early on in that room and went to headsetsā¦didnāt seem to work out ā¦had a chuckle at viv trying to wrestle with them.
Just saying that, if sessions are going to continue to be recorded out of that roomā¦the issue remains. Diffusing is the way this problem is solved in the audio world. A local contractor can do this work very quickly with no time suck on developer timeā¦just a suggestion from an audio guy.
The question I have right now, not being a developer but understanding how network stuff interacts: Is my xyz service, suitable to build on SAFE?
RESTful API? Javascript based apps? ā¦just the very bones of what would be dead easy, not so easy, hard, forget it. Maybe a Maidsafe blog post to that effect, where developers could be pointed for a quick lowdown.
Iād like to sniff out the coolest stuff and turn them on to SAFE and have them ask questionsā¦but who to approach?
1 Like
I thought the headsets were being used for the Google hangout session, not on mumble. Iāll check mumble and see if the audio quality has the same issue with the echo. If anyone in Troon is still awake give me a shout in the conference room. Iām logging in right now.
EDIT: I just had a quick chat with @dirvine on mumble, at his home. The audio was very clear. So we are going to try mumble again at the MaidSafe office in about 10hrs from now, that is 6am for me, Iāll try to get up early and see how bad the echo is from the office location. You guys/gals are welcome to jump in the Conference Room on Mumble. Weāll find a solution. 
Regarding using mumble, please use āPush to Talkā to avoid cross noise when on the party line. Thanks.
Ah yes, Iām talking about room echo when they use the table microphone , not transmission/network echoes.
Sorry for the confusion thereā¦
10 hours from 19:00?
If so, thatās 5:00 for meā¦ and Iāll pass on waking that early. 
Mumble is definitely a good idea for improving audio qualityā¦ just canāt forget to record so we can cut it in post hangout.
Iāll work on cutting up this one to see how long it takesā¦ if it seems to be taking too long, Iāll just mark down the timestamps for various topics.
Iām in the Mumble conference room, but it looks like MaidSafe Team is a little busy right now. They are working on some updates to the code base, which is a good thing. Iāll go ahead and start the AMA TestNet1 thread and leave the conference date as TBA (To Be Announced).
The general rule of thumb for this is if itās suitable for Google App Engine, itāll probably be suitable for SAFE.
Thatās a conservative view of course, but it wonāt lead to any disappointment later.
Niall
1 Like
Thanks Ned, so accordingly that would include
Python, Java, PHP, Go and Cloud SQL
If itās suitable for Google App Engine, itāll probably be suitable for SAFE
easy 
1 Like
It should include at least this set, think itās fair to say with c and c++ interfaces then we should handle pretty much any language or binding. We have no corporate business model to protect or business reason to restrict developers. Should be quite a ride. I agree though we need a tough roadmap, we do hope the community provide many of the language bindings as we move on.
2 Likes
Ooo, not quite what I meant.
I more meant that if a web application works well on Google App Engine i.e. has been designed to do so, it has a strong chance of working well on SAFE.
Just to quickly expand, persisting storage durably on a LAMP server takes milliseconds, whereas on App Engine it takes seconds, and on SAFE I expect it will also take seconds. Similarly, your code will have to accept running in a very tightly defined sandbox with restrictions similar - or even more so - to Google App Engine. Most web applications donāt run well on App Engine as they make hard assumptions about their freedom to do insecure things.
Niall