 So basically, Meteor doesn't provide a 3D0 package, which is the client-side package. There is some server-side package from 3D0, but nobody created this client-side package. So from server-side, you can do server calling or whatever, but now we want to do the client-side calling from browser itself, which can be used in mobile, basically. So here, I'm working with a client, which is the user. And then we have another one, it's called Interbrator. So it's a project between user and interpreter. So I'm logged in as a user. Okay, so user can search for interpreter. So we have some interpreter here. Now I can log in as an interpreter, which is another browser. Okay, so I'm an interpreter now. This is me. But I can call this guy. So it's calling now. It's established. So the interpreter, well, whether you want to accept the call or not, if you do, then do a call. So you can try to talk. Hello, hello. Hello, hello. Okay, so this is basically the communication between user and interpreter. The communication is pretty well at this station right now. The DDD connection is pretty good. So there's that. Right now you have two browsers running in one computer. I have to stop because I'm paying for this. Okay, so basically this is the project. Okay, thank you. Sir, what is your... 2-0. 2-0. 2-0. Yeah, it's a service that allows you to call the RESTful API form for allowing you to do contacts form, call, basically. So do you have to write a code to use the... 2-0. 2-0 specifically for Meteor. So interesting is that 2-0... I mean, Meteor doesn't have this package for 2-0 from client side. What I mean client side is that you have to either write a package or actually if you do a call from asynchronously like inject into the header, this JavaScript that provided by 2-0, it will not work. I don't know why. What happens is I assume that you call this JavaScript and this JavaScript is calling another file. So if you download this file from 2-0 and then you put into your Meteor anywhere, it doesn't work. You just break. So you have to create a package, injecting asynchronously, then it will work. Sir, did you build the package? I built the package. So is it open source? No, no. So this is the package, which is the client. So we have a client inject and then we have some server calling functions. Is that the code by them or...? No, by me. So it's not that much. It's just your injection of head to the head. Say you're making a phone call which will cost you a lot of web service from this to your record and send the voice, then the guy will play a record back and send it to you. We want live, so we don't want a record thing. We should consider web RTC. Yeah, it is using. So the interesting part is if you don't have web RTC, they'll fall back to flash. So that's quite powerful. I don't think we want to check the place. Websites get a room I.O. That's not meant as a suggestion to be a road company. Which is actually a local Singapore company. They got the web RTC stuff sorted out. So the complete codes will get up and so forth. For our next meetup, you will see the same version of this one using get a room I.O. Okay, okay, so that's good. So they have a backend code, which basically the backend is only there to make the initial connection once the web RTC is there and you have to know how to get it here. And it's I4C. Okay. Okay, very cool. Using Temasis. Temasis will use it. Temasis. The thing is, this provider, they doesn't come with a lot of countries. So 3DO is very interesting because they provide any country access. So you can call from any countries wherever and it's cheap. So I think it's great. And I don't know, right now I'm seeing a few options that I have, but 3DO is definitely the best choice right now. Okay, thanks.