WEBVTT Kind: captions Language: en 1 00:00:00.260 --> 00:00:03.720 Hi, I'm Matt. And I'm Tom. And we're at Electromagnetic Field festival. 2 00:00:04.160 --> 00:00:07.660 That's the enormous hacker camp that's running all this weekend in the middle of the UK. 3 00:00:08.000 --> 00:00:14.200 This isn't a normal video. We did a half-hour talk today. About Emojli, our emoji-only messenger app. 4 00:00:14.200 --> 00:00:20.220 Yeah, you might remember the video of that from a few weeks ago but if that isn't your thing, there's some other videos around here you might be interested in. 5 00:00:22.420 --> 00:00:24.940 And if you're watching on mobile, they're in the description 6 00:00:25.040 --> 00:00:27.040 If that is your thing, then enjoy the talk 7 00:00:27.720 --> 00:00:31.140 So, we were in Westfield Stratford, 8 00:00:31.240 --> 00:00:35.320 in London, in the kind of hellhole of consumerism that is near the Olympic Park 9 00:00:35.960 --> 00:00:39.100 I can not remember why we were there Matt: I think we both had a long day 10 00:00:39.100 --> 00:00:42.080 and we were having a lovely sit down outside Jamie's Italian 11 00:00:42.440 --> 00:00:44.440 Not in Jamie's Italian, just outside 12 00:00:44.900 --> 00:00:47.800 Jamie's Italian is a restaurant, it's not just the person that Jamie Oliver knows 13 00:00:49.960 --> 00:00:51.960 You want to take a step in, I'm not sure the camera can see you there 14 00:00:54.600 --> 00:00:56.060 That might have been deliberate 15 00:00:57.280 --> 00:00:59.280 And he says to me, um 16 00:00:59.420 --> 00:01:01.380 You basically came up with the idea for an Emoji messenger 17 00:01:02.140 --> 00:01:04.880 And I said, "Well I've had that idea", which was actually true 18 00:01:05.060 --> 00:01:06.560 I had thought of that as well 19 00:01:06.560 --> 00:01:08.460 But it was weird, no one else seemed to have done it yet 20 00:01:09.080 --> 00:01:11.080 Everyone was talking about 21 00:01:11.440 --> 00:01:13.580 Emoji because Unicode had just released, 22 00:01:13.960 --> 00:01:16.560 Well just said they were releasing all these new Emoji coming out 23 00:01:16.580 --> 00:01:19.280 Tom: yeah, there will now be a Unicode Spock hand 24 00:01:20.020 --> 00:01:22.020 In the actual standard, which is wonderful 25 00:01:22.480 --> 00:01:24.980 There's also, Reversed Victory Sign 26 00:01:27.600 --> 00:01:29.600 That's in the speck now 27 00:01:30.220 --> 00:01:32.260 And with there being a social network for everything 28 00:01:32.260 --> 00:01:33.900 And everyone talking about Emoji 29 00:01:34.120 --> 00:01:36.100 Yeah, because Yo had just come out 30 00:01:37.060 --> 00:01:40.340 How that idea didn't collide in more people's head, we don't know 31 00:01:41.040 --> 00:01:43.940 it urns out it had collided in a few other people's heads 32 00:01:43.940 --> 00:01:46.100 And they might have got to market first, but I'll get to that in a minute 33 00:01:46.400 --> 00:01:47.940 The important thing is 34 00:01:48.200 --> 00:01:51.320 We got to reserving usernames first 35 00:01:54.100 --> 00:01:57.400 On the overground, on the way home from Westfield Stratford 36 00:01:57.400 --> 00:01:59.600 We came up with the name, I reserved the 37 00:01:59.920 --> 00:02:02.760 domain Emoj.li on my phone 38 00:02:03.040 --> 00:02:04.760 on the tube Wi-Fi Tom: Yeah 39 00:02:05.060 --> 00:02:06.700 Because you can do that now 40 00:02:07.280 --> 00:02:08.340 Welcome to 2014 41 00:02:09.300 --> 00:02:11.920 and we thought this was going to be a really easy build 42 00:02:12.060 --> 00:02:13.700 Its just an instant messenger 43 00:02:13.920 --> 00:02:16.420 There's not going to be much on the backend, there's not going to be much on the frontend 44 00:02:16.420 --> 00:02:18.720 We'll have it done in a week Matt: It can't be that hard 45 00:02:18.720 --> 00:02:19.660 (quiet laughter from crowd) 46 00:02:19.900 --> 00:02:22.760 Thank you! Bitter laughter from the front there 47 00:02:23.380 --> 00:02:25.540 There is someone who tried to do this before 48 00:02:26.660 --> 00:02:28.740 Yeah, um. So a week later we hadn't done it, 49 00:02:29.000 --> 00:02:32.820 So I quickly cobbled together a thing that would take an email address 50 00:02:33.340 --> 00:02:35.320 And a username, which of course had to be Emoji 51 00:02:36.220 --> 00:02:38.360 and just sort of reserve it and send you an email saying 52 00:02:38.360 --> 00:02:39.940 "Thanks we'll get to you soon" 53 00:02:40.960 --> 00:02:42.960 And we figured that's fine, no one is going to pay any attention 54 00:02:42.960 --> 00:02:45.240 And if know one pays any attention, which they won't 55 00:02:46.120 --> 00:02:48.880 We can just say that it was a joke, and we can forget about it 56 00:02:50.160 --> 00:02:52.160 And we put up a little video, just 57 00:02:52.400 --> 00:02:54.660 as Tom and I do every so often 58 00:02:55.280 --> 00:02:56.980 To explain what it was, and our idea 59 00:02:57.960 --> 00:02:59.960 And then a few people saw that Tom: yeah yeah 60 00:03:00.160 --> 00:03:00.900 Quite a few 61 00:03:02.140 --> 00:03:04.600 So we have 70,000 usernames reserved 62 00:03:05.420 --> 00:03:06.900 Matt: Within a couple of days 63 00:03:07.720 --> 00:03:09.180 Seventy thousand 64 00:03:09.540 --> 00:03:11.960 For a silly little idea we had on a bench at Westfield 65 00:03:12.020 --> 00:03:15.340 Alright and the lovely thing is no one was bitter that their actual username they use 66 00:03:15.560 --> 00:03:18.800 Because I'm "Tom Scotttt" on Instagram because I got there too late 67 00:03:19.660 --> 00:03:21.660 Five T's if you count the one at the start 68 00:03:23.700 --> 00:03:27.680 You can't do that, because if your username is Emoji you suddenly have the problem 69 00:03:28.400 --> 00:03:29.480 That you can't type your name 70 00:03:29.480 --> 00:03:30.480 Well, I- some people did 71 00:03:30.880 --> 00:03:32.820 We had some really creative ones, have you looked through the username list? 72 00:03:33.280 --> 00:03:35.280 I've seen a few, but i didn't see any actual people's names 73 00:03:36.160 --> 00:03:38.160 Someone called Adam got one, 74 00:03:38.220 --> 00:03:41.940 Because Emoji was based out of Japan 75 00:03:42.440 --> 00:03:44.440 It has symbols for blood types in there 76 00:03:44.620 --> 00:03:46.780 Which means you have A, B, and O in there 77 00:03:47.440 --> 00:03:50.740 There is a D, something that looks like a D, and a chart that looks like an M 78 00:03:51.260 --> 00:03:52.540 So you can get A, D, A, M 79 00:03:53.120 --> 00:03:55.120 You can also, if you include the dollar sign as an S 80 00:03:55.360 --> 00:03:57.120 get the word 'BOOB$' 81 00:03:59.020 --> 00:04:00.080 Several people did 82 00:04:00.260 --> 00:04:04.180 Yeah yeah, because there is also a little arrow with 'free' above it so... 83 00:04:05.280 --> 00:04:07.580 We had 'free boobs' we had 'cool boobs' 84 00:04:07.920 --> 00:04:09.060 We had, 85 00:04:09.280 --> 00:04:12.220 Well I don't think there is anything beginning with F in there 86 00:04:13.000 --> 00:04:15.540 Like there are some horoscope signs that kind of look a bit like, but no one managed to get 87 00:04:16.640 --> 00:04:19.160 Actual, proper off-comm banned words in there 88 00:04:19.880 --> 00:04:22.100 As far as I know, if you did don't take that as a challenge 89 00:04:24.960 --> 00:04:28.680 We basically did, an Emoji spelling competition by accident 90 00:04:30.440 --> 00:04:32.600 Yeah, and some people 91 00:04:33.740 --> 00:04:35.440 Didn't seem to understand, 92 00:04:35.440 --> 00:04:39.020 Like we thought we'd be nice and put an email address at the bottom if anyone had any questions about it 93 00:04:39.540 --> 00:04:40.880 Don't do that Matt: Don't 94 00:04:41.960 --> 00:04:43.280 No, no 95 00:04:43.920 --> 00:04:46.320 Hundreds and hundreds and hundreds of emails on the first day 96 00:04:46.400 --> 00:04:50.100 People saying, "I tried to register a smiley face and it's not working, why doesn't that work?" 97 00:04:50.600 --> 00:04:52.600 Because someone had got that one before you! 98 00:04:52.960 --> 00:04:54.780 There are only 500 odd Emoji 99 00:04:54.960 --> 00:04:56.660 You can use more than one 100 00:04:57.220 --> 00:04:58.400 We have sent Tom: Sorry 101 00:04:58.500 --> 00:05:00.580 We have sent literally hundreds of emails 102 00:05:00.940 --> 00:05:03.160 Saying, "You have to use more than one" 103 00:05:03.160 --> 00:05:04.900 Because that username will be taken 104 00:05:05.320 --> 00:05:07.320 We've sent dozens of emails saying 105 00:05:07.480 --> 00:05:09.480 "No, you can't have that because it's already taken" 106 00:05:10.020 --> 00:05:14.520 we've sent at least 5 emails saying, "No your username has to be an Emoji" 107 00:05:17.060 --> 00:05:18.560 I want to be careful, 108 00:05:18.980 --> 00:05:22.620 Not being too nasty about people here because there are folk out there who are using this 109 00:05:22.840 --> 00:05:24.840 English is not their first language 110 00:05:24.900 --> 00:05:26.440 There are people out there who 111 00:05:26.820 --> 00:05:29.400 Genuinely are not tech-savvy and still want part of this 112 00:05:29.840 --> 00:05:32.840 And that's absolutely fine, but if you are tech-savvy enough to send me an email complaining about 113 00:05:32.980 --> 00:05:36.020 The thing that is on the screen in front of you 114 00:05:37.380 --> 00:05:40.960 So by this point, which is a couple of days in, this silly little idea we had on a bench 115 00:05:41.040 --> 00:05:43.040 That we had no idea how we were actually going to make 116 00:05:43.600 --> 00:05:46.640 Had turned into a support job 117 00:05:47.500 --> 00:05:50.900 Technical support job, for one registration form 118 00:05:51.440 --> 00:05:53.440 That we were doing in our spare time 119 00:05:53.620 --> 00:05:55.400 Because we thought it was funny Tom: Thank you 120 00:05:55.760 --> 00:05:58.300 There's a smattering of applause I don't know if the microphone will have picked that up 121 00:05:59.720 --> 00:06:03.620 "Yeah, well done. Did you not see that coming? Really? Okay, good" 122 00:06:04.660 --> 00:06:05.880 Yeah, we didn't 123 00:06:09.000 --> 00:06:10.440 So then we had to build the thing 124 00:06:12.360 --> 00:06:16.580 Can anyone guess, because I'm a professional web developer I guess 125 00:06:16.680 --> 00:06:18.400 That's what i get paid for, I make 126 00:06:18.640 --> 00:06:20.640 Web toys for a site called 'Us vs Th3m' 127 00:06:21.920 --> 00:06:24.660 All the stuff I have to code for that is coded very quickly 128 00:06:25.280 --> 00:06:28.020 Very very fast, we aim to be responsive and topical. So, 129 00:06:28.860 --> 00:06:31.220 Using skills from that and you know, years of web development 130 00:06:31.880 --> 00:06:36.460 Several years, in the 2000s of web development 131 00:06:36.760 --> 00:06:40.260 Can anyone guess, what language the backend of Emojli is coded in 132 00:06:41.460 --> 00:06:44.200 JavaScript? Oh no, JS that is 133 00:06:44.880 --> 00:06:46.700 Matt: We'll get to that later Tom: That's way too modern 134 00:06:46.840 --> 00:06:48.420 There we go! PHP 135 00:06:50.620 --> 00:06:54.060 Matt: So we had split this up Tom: Boos, boos from the audience there 136 00:06:55.700 --> 00:06:58.080 We had split it up so Tom was doing the backend 137 00:06:58.740 --> 00:06:59.780 I was doing the frontend 138 00:07:00.540 --> 00:07:01.240 So, 139 00:07:01.520 --> 00:07:03.480 By day I'm a Broadcast Engineer 140 00:07:04.200 --> 00:07:05.320 I don't program 141 00:07:06.560 --> 00:07:08.260 I make little web things every so often 142 00:07:08.740 --> 00:07:10.120 That not many people use 143 00:07:10.340 --> 00:07:12.120 Guess what I made the app in? 144 00:07:12.880 --> 00:07:13.960 Audience Member: Objective-C? 566 00:07:13.960 --> 00:07:14.960 Both: No 146 00:07:14.960 --> 00:07:17.300 Objective-C was the guess from the audience there, no 147 00:07:18.840 --> 00:07:20.020 What was that? Audience Member: JS? 148 00:07:21.020 --> 00:07:23.020 No, JS. You got that half right 149 00:07:23.480 --> 00:07:24.560 The second half 150 00:07:26.500 --> 00:07:28.680 HTML, CSS and JavaScript 151 00:07:29.820 --> 00:07:30.800 I made an app 152 00:07:31.700 --> 00:07:35.000 Now you might ask, if we're doing that, why did we not make that as a web app? 153 00:07:35.560 --> 00:07:37.000 Given that's what it basically is 154 00:07:37.540 --> 00:07:39.220 There are many browsers out there Tom: Yes 155 00:07:39.220 --> 00:07:41.800 And none of them support Emoji Matt: At all 156 00:07:45.120 --> 00:07:49.840 Hands up if you've actually looked and know how well Emoji is supported 157 00:07:51.740 --> 00:07:56.160 Yeah I see Matt Sommerville there, who designed train times 158 00:07:59.840 --> 00:08:04.860 Glin here, Glin in the front row is a security expert who is going to be having a field day after he's heard all this 159 00:08:04.960 --> 00:08:05.780 By the way 160 00:08:06.720 --> 00:08:08.720 Thanks to knowing him and running through this 161 00:08:08.920 --> 00:08:11.080 Again, I don't want to issue this as an invitation 162 00:08:11.080 --> 00:08:12.920 But I say as someone who designed it 163 00:08:13.400 --> 00:08:16.080 I'm reasonably certain of the security of the stuff we are storing 164 00:08:17.120 --> 00:08:20.640 Like no, genuinely, because we have a privacy policy 165 00:08:21.120 --> 00:08:23.440 And I've had to register under the Data Protection Act 166 00:08:24.400 --> 00:08:27.860 For the silly little idea we had, on a bench outside Westfield 167 00:08:28.220 --> 00:08:30.220 Registering costs £35! 168 00:08:37.400 --> 00:08:39.400 So we have an HTML chat as front end 169 00:08:39.860 --> 00:08:41.860 Oh yeah, while I'm complaining about PHP 170 00:08:42.380 --> 00:08:44.400 So, Emoji support, um browsers don't support it 171 00:08:44.400 --> 00:08:46.180 iOS, because we are releasing for iPhone 172 00:08:46.180 --> 00:08:48.320 iOS does support it really well, to be fair 441 00:08:49.840 --> 00:08:51.380 You said we would come to that later Android 174 00:08:51.380 --> 00:08:52.920 Eighh Matt: Noo 175 00:08:53.420 --> 00:08:54.900 Windows Phone ha! 176 00:08:56.720 --> 00:08:58.720 Because Windows Phone runs Internet Explorer 177 00:08:59.340 --> 00:09:01.340 Matt: And that doesn't support 178 00:09:02.000 --> 00:09:05.260 Emoji and JavaScript are not handled properly 179 00:09:05.980 --> 00:09:08.260 They are treated as two characters and bundled together 180 00:09:11.600 --> 00:09:15.180 If I say the worlds MySQL and Unicode 181 00:09:15.440 --> 00:09:17.280 (collective uproar) 182 00:09:19.660 --> 00:09:21.660 Matt: They are feeling your pain Tom: Yeah, on the backend, 183 00:09:22.480 --> 00:09:26.360 How, I've made sure that the stuff that comes in 184 00:09:26.360 --> 00:09:28.360 Which does come in really well, from Matt's JavaScript 185 00:09:28.600 --> 00:09:31.320 The stuff that comes in, gets into the database and back out 186 00:09:31.760 --> 00:09:35.060 Without getting munged, bearing in mind I'm using PHP and MySQL 187 00:09:35.820 --> 00:09:36.500 Audience Member: Binary 188 00:09:36.500 --> 00:09:41.400 Binary? Oh, no because UTFMB4 can still mess that up sometimes 189 00:09:41.860 --> 00:09:42.700 Audience Member: Base 64 190 00:09:42.700 --> 00:09:45.300 Base 64! There we go 191 00:09:46.420 --> 00:09:50.160 Half of the crowd knows what I'm talking about and is going "Oh, did you really?" 192 00:09:50.240 --> 00:09:53.120 Half of the crowd is going "I have no idea what that is, but I'm going to laugh anyways" 193 00:09:55.060 --> 00:09:59.080 Put basically, we used what we knew to make something as quickly as possible Tom: Yup 194 00:09:59.280 --> 00:10:02.600 I'll be honest, we were not going for quality Tom: Yup 195 00:10:03.620 --> 00:10:04.960 It took us a month 196 00:10:05.180 --> 00:10:06.180 And a bit 197 00:10:07.020 --> 00:10:08.200 In our spare time 198 00:10:09.240 --> 00:10:13.140 And it's now launched, we launched it yesterday because that's when Apple approved it 199 00:10:13.600 --> 00:10:15.280 The first time Tom: Yeah 200 00:10:16.280 --> 00:10:17.780 First time I've ever made an app 201 00:10:18.380 --> 00:10:20.660 I didn't do it they way they wanted me to do it, and they approved it 202 00:10:21.220 --> 00:10:24.240 I'm not saying Apple's review process isn't thorough 203 00:10:25.840 --> 00:10:29.620 But it took them 11 minutes and they only looked at about a couple things in the app 204 00:10:31.880 --> 00:10:33.880 Ten to midnight we got an email saying 'In Review' 205 00:10:34.060 --> 00:10:36.060 (panicked noises) Panic! Panic! Pa- 206 00:10:36.520 --> 00:10:39.200 Midnight, we got an email saying 'Preparing for App Store' 207 00:10:43.940 --> 00:10:46.540 We submitted it a week beforehand, we had to wait for them to do that 208 00:10:47.420 --> 00:10:50.300 What I love is that they sent the email at 10 minutes before midnight 209 00:10:50.820 --> 00:10:54.300 Just before the date when we said we're going live with this thing 210 00:10:55.640 --> 00:10:59.100 I'm not saying it sat in a bin for 6 days until someone went, 211 00:10:59.760 --> 00:11:05.100 "Oh, oh they are meant to be launching that tomorrow. Guys, guy-" But I am saying that's what happened 212 00:11:06.480 --> 00:11:08.480 In the meantime some things happened 213 00:11:10.500 --> 00:11:12.500 People thought we were a startup 214 00:11:14.640 --> 00:11:18.380 Many. People. Journalists, from web publications, newspapers Tom: Yup 215 00:11:18.760 --> 00:11:20.420 I mean it used to be a big thing, like 216 00:11:20.560 --> 00:11:23.920 Ten years ago, you said, "We got coverage in Time Magazine" 217 00:11:24.180 --> 00:11:25.420 That would be really impressive 218 00:11:25.420 --> 00:11:28.440 Now a days Time Magazine is just Buzzfeed but they're not admitting it 219 00:11:30.820 --> 00:11:33.920 Like getting a review in Time Magazine requires sending it to them 220 00:11:33.920 --> 00:11:36.900 Because they'll go, "Oh my God that's content we can use it!" 221 00:11:40.540 --> 00:11:44.080 I don't understand how people think that two white middle class males 222 00:11:44.080 --> 00:11:46.800 Can't have an idea and it not being a startup 223 00:11:47.540 --> 00:11:49.060 We just made a silly thing 224 00:11:49.180 --> 00:11:52.720 We look like we're going to be Silicon Valley types 225 00:11:52.800 --> 00:11:54.480 Looking for enormous amounts of investment in this 226 00:11:54.640 --> 00:11:57.800 We look like we're going to be the two 227 00:11:59.520 --> 00:12:03.560 I'm going to use the phrase "Douchbag Tech Bros" if I can say it 228 00:12:03.800 --> 00:12:04.800 In t-shirts 229 00:12:05.080 --> 00:12:06.260 Yeah 230 00:12:06.640 --> 00:12:08.820 Launching an app because that's the way to make 231 00:12:09.000 --> 00:12:10.460 A lot of money 232 00:12:10.520 --> 00:12:12.120 No, we kind of just had a stupid idea 233 00:12:12.120 --> 00:12:13.240 Bring on the dollars 234 00:12:13.360 --> 00:12:19.220 Yeah, the tech press disagrees and at least one investment fund that has emailed us recently disagrees 235 00:12:20.080 --> 00:12:22.080 So we got a call with them at some point 236 00:12:24.380 --> 00:12:26.460 Now I'll be honest for this silly idea that we've had 237 00:12:27.760 --> 00:12:29.760 Which I may have mentioned this before 238 00:12:30.400 --> 00:12:32.400 We'd thought it would be quick Tom: No 239 00:12:34.960 --> 00:12:37.180 And we thought it would be over very quickly Tom: No 240 00:12:37.680 --> 00:12:39.560 Now we have no spare time to do Tom: Yup 241 00:12:39.800 --> 00:12:41.080 We have no, 242 00:12:41.100 --> 00:12:44.140 No one has payed us anything for it so we have spent some of our own money doing it 243 00:12:44.920 --> 00:12:49.560 You might guess at what our intentions of continuing to put a lot of effort into this might be at the moment 244 00:12:51.500 --> 00:12:52.380 It's not high 245 00:12:52.380 --> 00:12:53.780 And the thing is it works 246 00:12:54.220 --> 00:12:55.900 It works reliably, like we have 247 00:12:56.560 --> 00:12:58.380 Quite a lot of people using it now 248 00:12:58.440 --> 00:13:01.880 We sent 70,000 emails yesterday 249 00:13:02.400 --> 00:13:04.540 To people who had reserved and confirmed their usernames 250 00:13:04.620 --> 00:13:06.460 That was from here by the way 251 00:13:06.460 --> 00:13:07.680 Tom: Oh yeah, that was from the lounge Matt: We're here this weekend 252 00:13:07.880 --> 00:13:09.880 Partly in the lounge, partly in his tent 253 00:13:11.080 --> 00:13:13.080 I mean some of those emails like literally came from my phone 254 00:13:13.140 --> 00:13:15.140 Because that was where the app was running 255 00:13:18.260 --> 00:13:22.160 And the thing is if you send 70,000 emails to people and they are on twitter and they are saying, 256 00:13:22.320 --> 00:13:25.960 "Oh my username is Aubergine No Under 18s" 257 00:13:26.400 --> 00:13:28.400 Which is actually someone's username 258 00:13:28.720 --> 00:13:32.300 Shout out there to Aubergine No Under 18s 259 00:13:38.560 --> 00:13:41.280 We thought there was no way we would have to mark this as adult rated 260 00:13:41.280 --> 00:13:43.200 There's nothing you can do with Emoj- no. 261 00:13:47.740 --> 00:13:50.700 Because the thing is under the Data Protection Act 262 00:13:50.760 --> 00:13:53.060 You have to list on your Data Protection Act submission 263 00:13:53.700 --> 00:13:56.820 The possible things you might be storing about people, does it include sensitive data 264 00:13:57.760 --> 00:13:59.800 And they give an example of what sensitive data might include 265 00:13:59.800 --> 00:14:01.800 And it includes details about people's sexuality 266 00:14:02.480 --> 00:14:04.940 And I went, "Well no, obviously not, that's not, Emoji" 267 00:14:06.980 --> 00:14:09.460 "There's a two men holding hands Emoji that you could use" 268 00:14:09.860 --> 00:14:11.120 Oh for God's sake 269 00:14:13.440 --> 00:14:15.440 So I have to *laughs* Thank you Tom! 270 00:14:19.040 --> 00:14:20.120 What's your username Tom? 271 00:14:20.120 --> 00:14:22.120 Tom: Trademark Two Men Holding Hands 272 00:14:22.540 --> 00:14:24.540 "Trademark Two Men Holding Hands" 273 00:14:30.520 --> 00:14:32.960 I'm being really careful with password security on this thing 274 00:14:35.800 --> 00:14:37.120 The thing is 275 00:14:39.240 --> 00:14:42.020 People haven't used Emojli to converse yet 276 00:14:42.800 --> 00:14:44.800 Properly Tom: Yeah, wait no there's been a few 277 00:14:45.240 --> 00:14:47.460 I saw a friend of mine get, 'cup of tea?' 278 00:14:47.620 --> 00:14:50.220 And responded with a smiley face, so you know that's technically a conversation 279 00:14:50.460 --> 00:14:52.460 The basics, the basics are there 280 00:14:52.960 --> 00:14:55.700 But, as soon as you go out of your friendship circle 281 00:14:55.980 --> 00:14:58.900 Or your known interests or your commonalities 282 00:14:59.960 --> 00:15:03.180 The sort of understanding of what you might mean 283 00:15:03.180 --> 00:15:06.000 In these silly little pictures that don't actually mean anything 284 00:15:06.200 --> 00:15:09.060 That you are using to converse with, gets a bit skewed 285 00:15:10.020 --> 00:15:12.820 A few people tried to interview us by sending a load of 286 00:15:13.160 --> 00:15:15.860 Emojis, which we had no idea what they were on about 287 00:15:16.640 --> 00:15:19.620 So we guessed something and sent it back, and they had no idea what we meant 288 00:15:20.500 --> 00:15:22.800 But they published it Matt: Yup 289 00:15:27.720 --> 00:15:29.720 Ah, I haven't mentioned 290 00:15:30.160 --> 00:15:34.900 Thing where, I mean we took a month to go from here's your username to here's your app 291 00:15:35.540 --> 00:15:39.680 in that month, two other Emoji-only messengers launched 292 00:15:40.960 --> 00:15:43.840 Neither of which got any press because we kinda spoiled it for them 293 00:15:44.740 --> 00:15:46.740 One of which is called Emojli 294 00:15:46.980 --> 00:15:48.580 I wonder where they got that name from 295 00:15:49.160 --> 00:15:50.800 Now, to be fair, we emailed them 296 00:15:51.040 --> 00:15:53.360 And we said, "uh, guys you, um..." 297 00:15:53.740 --> 00:15:56.920 Well, guy it was one name on the thing, 298 00:15:57.560 --> 00:15:59.460 "You're using the same name as us" 299 00:15:59.720 --> 00:16:03.500 "You registered your domain 3 weeks after we launched" 300 00:16:04.240 --> 00:16:09.180 "And you've registered your Twitter, which is our name with a couple of letters on the end of it" 301 00:16:09.780 --> 00:16:11.780 "several weeks after we launched" 302 00:16:12.020 --> 00:16:13.500 "Did you not notice?" 303 00:16:14.620 --> 00:16:19.980 If you were starting something, you'd google the name you came up with first to see if anyone else was there Tom: Yeah, that's a thing you would do 304 00:16:21.340 --> 00:16:23.340 And they said, "No, no we've been planing this for a while" 305 00:16:24.020 --> 00:16:25.400 Oh really? 306 00:16:26.320 --> 00:16:29.320 21 5-star reviews on their app 307 00:16:29.860 --> 00:16:33.160 All in slightly one sentence pigeon english 308 00:16:34.180 --> 00:16:37.020 They've all vanished now, I can't imagine why. There's no reviews for it anymore 309 00:16:37.420 --> 00:16:39.840 Still slightly ahead of us on the app store which is really annoying 310 00:16:41.980 --> 00:16:44.540 You know why? Because we are getting tech support requests for there app! 311 00:16:47.760 --> 00:16:51.140 "I can't find where to unlock my username" Yeah, wrong app 312 00:16:51.920 --> 00:16:53.920 "I can't talk to my frie-" Wrong app 313 00:16:56.240 --> 00:16:57.600 Yes.... 314 00:16:59.040 --> 00:17:01.420 Don't build an app Tom: Yeah that's basically what we are saying because 315 00:17:03.280 --> 00:17:06.300 The economics doesn't make sense, no one will make money off this 316 00:17:07.360 --> 00:17:09.360 The support time doesn't make sense 317 00:17:09.820 --> 00:17:13.360 You have to think about you're own personal knowledge and skills 318 00:17:13.360 --> 00:17:16.960 If they involve, making apps Tom: Yeah 319 00:17:17.000 --> 00:17:19.000 Then you might have a chance 320 00:17:20.640 --> 00:17:24.520 Thing is we now have to update this for our site, because it doesn't work on our site 321 00:17:24.980 --> 00:17:28.560 And we've had a few emails saying, "Why doesn't it work on iOS 6" 322 00:17:29.040 --> 00:17:31.000 Never mind Android, we'll get to that later 323 00:17:31.260 --> 00:17:33.260 Why doesn't work on iOS 6? 324 00:17:33.560 --> 00:17:37.140 And the real answer for that is: I tried running it on iOS 6, and it didn't work 325 00:17:37.700 --> 00:17:39.700 It works on iOS 7 326 00:17:39.740 --> 00:17:41.740 So, tick the box: "Not on iOS 6" 327 00:17:41.980 --> 00:17:43.980 Because I had spent a month on this bloody thing 328 00:17:45.380 --> 00:17:48.920 Which I thought was going to be a quick thing Tom: I don't want to come across as ungrateful 329 00:17:49.280 --> 00:17:52.420 Because we've got 70,000 usernames on this thing 330 00:17:52.880 --> 00:17:54.380 And that's really cool 331 00:17:54.520 --> 00:17:56.000 Like, we've made a thing 332 00:17:57.100 --> 00:17:59.880 And it's great, unfortunately we've now made a millstone that is around our neck 333 00:18:00.560 --> 00:18:02.940 So, that's not good 334 00:18:03.020 --> 00:18:06.440 I think I've dealt with 100 tech support requests this morning 335 00:18:07.040 --> 00:18:11.520 90% of which were actually dealt with by the automatic vacation response 336 00:18:11.940 --> 00:18:14.880 That I put on the GMail thing saying "We're a bit busy this will probably solve it" 337 00:18:17.480 --> 00:18:19.480 So let's open the floor to questions! 338 00:18:19.560 --> 00:18:23.860 Let's, yeah guy over there in the really cool skeleton hoodie 339 00:18:24.120 --> 00:18:26.720 If you could yell really loud then we'll repeat your question so other people can hear 340 00:18:26.960 --> 00:18:30.340 Audience Member: Have you tried selling the app to the other person who wants to copy you? 341 00:18:30.800 --> 00:18:34.660 Have we tried selling the app to the other person that has the app? 342 00:18:36.400 --> 00:18:40.300 No, what I think we actually did was file a request with Apple 343 00:18:40.300 --> 00:18:42.400 Saying "They kind of nicked our name" 344 00:18:42.900 --> 00:18:46.740 And as you might expect Apple's response to that was nothing, absolutely nothing Matt: They didn't reply 345 00:18:48.700 --> 00:18:51.120 I'm going to take Glyn, your hand was up first 346 00:18:52.020 --> 00:18:53.340 Glyn: Dear Emojli's Tom Scott 347 00:18:53.540 --> 00:18:54.140 Oh dear 348 00:18:55.700 --> 00:18:57.980 Glyn: When are you going to go public with your first round of shares? 349 00:18:58.100 --> 00:19:00.520 When are we going to go public with out first round of shares 350 00:19:03.560 --> 00:19:08.200 Now the thing is, I don't want to be too cynical here because we do have, 351 00:19:09.000 --> 00:19:12.180 70,000 usernames there, like some of them haven't been pulled out yet 352 00:19:12.220 --> 00:19:14.220 Because they are waiting for an Android release 353 00:19:14.500 --> 00:19:19.560 If someone were to come along and say, "Yeah, we actually want to take this off your hands, because this is a thing that would start" 354 00:19:20.480 --> 00:19:24.540 Yeah, okay. They're welcome to it, but we're not start up people, we're not business people 355 00:19:24.740 --> 00:19:25.960 We're not businessmen 356 00:19:26.520 --> 00:19:28.520 We really don't want to run a start up 357 00:19:29.260 --> 00:19:33.980 And the thing is we may have sounded bitter at it, that's mainly because we had spent a month of all of our spare time 358 00:19:33.980 --> 00:19:35.260 We both have full time jobs 359 00:19:35.500 --> 00:19:37.560 Which can be reasonably demanding 360 00:19:37.560 --> 00:19:40.520 And we are spending every waking moment trying to make this thing 361 00:19:40.820 --> 00:19:42.820 So we might be sounding a bit more Both: Bitter 362 00:19:42.820 --> 00:19:44.280 Then we could be otherwise 363 00:19:44.640 --> 00:19:49.220 But I'm certainly very proud of the fact that we know bugger-all about making apps 364 00:19:49.220 --> 00:19:52.660 And we seemed to have made one and launched one and got 70,000 registrations on it 365 00:19:53.000 --> 00:19:55.520 So if it turns out that some investor wants it, then lovely 366 00:19:55.520 --> 00:19:57.400 But I suggest that they find the tech team 367 00:19:57.740 --> 00:19:59.960 And you put it into something they already have 368 00:20:00.740 --> 00:20:03.880 Rather than trying to give us vague incompetence money to do it 369 00:20:04.140 --> 00:20:06.000 We don't want it to die 370 00:20:06.000 --> 00:20:07.820 Yeah, but we don't really want it to live either 371 00:20:08.000 --> 00:20:11.000 We, we don't have the time to keep it alive 372 00:20:12.460 --> 00:20:14.460 Guy in the green top there 373 00:20:17.200 --> 00:20:20.800 Audience Member: When did you realize that internet start up culture had gone beyond parody 374 00:20:21.380 --> 00:20:24.300 When did we realize that internet start up culture had gone beyond parody 375 00:20:24.880 --> 00:20:25.920 Matt: Yo? Tom: Yo. 376 00:20:25.920 --> 00:20:26.800 Both: Yo 377 00:20:28.880 --> 00:20:31.720 Not, Yo; when Yo got investment 378 00:20:32.040 --> 00:20:34.840 Matt: Yes Tom: When Yo got more then $1,000,000 from an investment fund 379 00:20:35.040 --> 00:20:37.360 That is the point, they've pivoted now by the way 380 00:20:37.600 --> 00:20:41.620 Pivot means, "Oh dear that idea didn't work start everything over fresh again" 381 00:20:42.020 --> 00:20:46.200 They are now a proper notification service because that, that's good 382 00:20:47.020 --> 00:20:47.940 That'll work 383 00:20:47.940 --> 00:20:50.940 In fact, while I'm thinking of this, my favourite quote from the review of us 384 00:20:51.400 --> 00:20:52.900 Oh yeah! We got reviews 385 00:20:55.020 --> 00:20:57.620 My favourite was, I can't remember the exact wording, something along the lines of 386 00:20:57.740 --> 00:21:00.180 "Finally, we found something worse than Yo" 387 00:21:01.480 --> 00:21:05.220 (Crowd cheers) 388 00:21:06.680 --> 00:21:09.500 And so I thought, well we need something in our app store description 389 00:21:09.500 --> 00:21:11.480 So I put two good quotes and that on the bottom 390 00:21:13.700 --> 00:21:15.700 I'm not going to say they're wrong 391 00:21:17.600 --> 00:21:18.940 Uh, yup, just there 392 00:21:19.540 --> 00:21:23.600 Audience Member: Have you tried replacing UTF-8 sequences with actual images? 393 00:21:23.960 --> 00:21:27.180 Yes, have we tried replacing UTF-8 sequences with images 394 00:21:27.780 --> 00:21:29.880 Yes, there is 395 00:21:30.580 --> 00:21:32.460 There's a library for doing that in JavaScript 396 00:21:32.800 --> 00:21:36.460 What I basically do for the website, because there is only a couple places you need it on the web 397 00:21:37.000 --> 00:21:41.320 In most cases people were looking at through a phone's browser that would automatically do the replacement anyway 398 00:21:42.620 --> 00:21:44.620 What I'm actually using is a font stack 399 00:21:46.160 --> 00:21:49.340 On Apple you can use, obviously the Emoji font, Android has an Emoji font 400 00:21:49.720 --> 00:21:52.260 On Windows there's actually a font on Windows 7 and later 401 00:21:52.260 --> 00:21:54.200 Called Segoe UI Symbol 402 00:21:54.440 --> 00:21:56.740 Which includes full list of Emojis 403 00:21:56.960 --> 00:21:59.740 With pictograms for all of them 404 00:22:00.140 --> 00:22:02.140 So in most cases it's use that 405 00:22:02.320 --> 00:22:08.820 The trouble is that there are no copyright-free or creative commons or easily licensed sets of Emoji right now 406 00:22:09.460 --> 00:22:11.360 That's one of the big problems we have 407 00:22:11.420 --> 00:22:15.860 Is that we either have to get someone to draw every Emoji for us 408 00:22:19.200 --> 00:22:21.200 Yeah, "Use the investment money for that", he says 409 00:22:22.940 --> 00:22:24.060 Audience Member: Put it on Kickstarter 410 00:22:24.620 --> 00:22:29.700 Someone did! No, someone said, "Put it on Kickstarter", and there was a Kickstarter for open Emojis 411 00:22:30.080 --> 00:22:31.760 And it got an enormous amount of money 412 00:22:32.380 --> 00:22:35.220 And then it got about 10% of the way through and they said nope 413 00:22:35.500 --> 00:22:35.500 Tom: No! Matt: Nope 414 00:22:35.500 --> 00:22:37.180 Matt: Nope Tom: It's not finished 415 00:22:37.220 --> 00:22:41.520 Github I think is basically just using Apple's 416 00:22:41.880 --> 00:22:43.740 And converting them into images 417 00:22:44.020 --> 00:22:46.840 And because Githib are really cool no one really minds 418 00:22:46.840 --> 00:22:48.500 I don't think Apple would really mind 419 00:22:48.780 --> 00:22:52.620 Quite a few places have been using their images and using them.... 420 00:22:53.280 --> 00:22:55.660 There is a question about whether you can copyright a font 421 00:22:55.920 --> 00:22:58.900 What is a font, what is a series of images 422 00:22:59.320 --> 00:23:02.740 If they package up a series of images as a font does that make it copyrightable 423 00:23:03.100 --> 00:23:06.600 We don't want to get involved in that which is one of the reasons we are just using the native UI 424 00:23:06.660 --> 00:23:10.500 Matt looks like he has something to add 425 00:23:10.800 --> 00:23:12.560 Matt (Audience): Ask the users to draw their usernames 426 00:23:12.900 --> 00:23:13.980 Ask the user to what? 427 00:23:14.420 --> 00:23:15.460 To draw their username 428 00:23:15.660 --> 00:23:17.540 Matt: I don't know how to do that, sorry Tom: No, do you know what that's going to get us 429 00:23:17.720 --> 00:23:20.960 That is going to get us, drawing of a cock, drawing of a cock, drawing of a cock 430 00:23:23.880 --> 00:23:27.060 I am not moderating 10,000 pictures like that 431 00:23:27.060 --> 00:23:30.220 Just to try and get a list I would rather pay to have someone draw them 432 00:23:30.220 --> 00:23:32.300 Then have to go through and Matt: What cocks? 433 00:23:34.240 --> 00:23:35.420 That's a job I could take 434 00:23:36.940 --> 00:23:39.460 I'm going to stop this before it goes beyond the code of conduct here 435 00:23:39.680 --> 00:23:41.240 In all seriousness 436 00:23:42.240 --> 00:23:44.240 Anyone else from the floor with a question that will not go 437 00:23:44.620 --> 00:23:47.000 And I'll not be dragged down in an incredibly terrible alley 438 00:23:47.380 --> 00:23:49.100 Yeah, okay guy on the left 439 00:23:49.800 --> 00:23:50.440 Right 440 00:23:51.600 --> 00:08:49.840 Audience Member: It's not been asked. You've been avoiding, 441 00:08:49.840 --> 00:08:51.380 You said we would come to that later Android 442 00:23:58.620 --> 00:24:00.620 Tom: Android, Yes Matt: Okay, so 443 00:24:01.020 --> 00:24:03.020 The backend will support it 444 00:24:03.100 --> 00:24:04.340 Yeah, No worries 445 00:24:04.640 --> 00:24:08.000 I'll give you a bit more background on how the app has been developed 446 00:24:08.180 --> 00:24:11.820 Tom: All yours Matt: I've used Cordova or PhoneGap 447 00:24:11.820 --> 00:24:14.180 It seems to have two names I don't quite understand why 448 00:24:14.500 --> 00:24:17.380 Which is a way of packaging a website into an app 449 00:24:17.800 --> 00:24:19.800 And that's vaguely cross-platform 450 00:24:20.900 --> 00:24:21.780 Tom: Vaguely 451 00:24:22.940 --> 00:24:27.400 But, for you to be able to test things reasonably well you need to have the devices 452 00:24:27.440 --> 00:24:29.440 I have an iPhone, I have an iPad 453 00:24:29.960 --> 00:24:33.000 So that's why I've gone with iOS is because I can test it 454 00:24:33.200 --> 00:24:35.580 Okay, it might not be the best app in the world currently 455 00:24:35.760 --> 00:24:38.320 But I have some standards 456 00:24:38.320 --> 00:24:40.660 And that app the is currently out has passed those standards 457 00:24:40.660 --> 00:24:42.420 Because I've been able to test them 458 00:24:42.920 --> 00:24:44.880 I don't have an Android device 459 00:24:45.380 --> 00:24:48.540 We've already put quite a bit of money into this to get it going, I don't want to, 460 00:24:48.760 --> 00:24:50.420 Buy one, the amount of time taken 461 00:24:50.840 --> 00:24:52.840 The code isn't going to be, you know, directly portable 462 00:24:53.120 --> 00:24:56.060 Also, that means on the backend there are Android push notifications 463 00:24:56.060 --> 00:24:59.740 Which are even more interesting the Apple's push notifications 464 00:24:59.740 --> 00:25:01.460 I forgot about the push notifications 465 00:25:02.620 --> 00:25:05.760 Yeah, right, okay here's the problem 466 00:25:06.040 --> 00:25:08.120 I mentioned the PHP, I mentioned the JavaScript 467 00:25:08.600 --> 00:25:11.600 Push notifications, I'm using a library. Because of course you use a library 468 00:25:11.680 --> 00:25:13.860 That makes, a lot of sense 469 00:25:14.060 --> 00:25:15.720 Push notification attempt #1 470 00:25:16.260 --> 00:25:18.260 "? has sent you ?" 471 00:25:19.660 --> 00:25:23.260 #2 "/? has sent you /?" no 472 00:25:24.040 --> 00:25:27.700 Attempt #3 "///? has se-" no 473 00:25:28.800 --> 00:25:32.000 Attempt #4 "/x21-" 474 00:25:33.160 --> 00:25:34.700 I caught many different places at this point 475 00:25:34.760 --> 00:25:38.100 What Tom hasn't mentioned is, for push notifications to work 476 00:25:38.280 --> 00:25:41.460 And basically for anything Apple to work you have to generate certificates 477 00:25:41.920 --> 00:25:46.080 You have to have a server certificate You have to have a user certificate You have to have an app certificate 478 00:25:46.480 --> 00:25:51.000 And a developer certificate, and then also for the push notifications you have to have a sandbox certificate 479 00:25:52.220 --> 00:25:53.800 That only works on his phone 480 00:25:54.800 --> 00:25:56.280 And we weren't in the same place 481 00:25:56.580 --> 00:25:59.680 And because we had all the certificates on my laptop 482 00:25:59.840 --> 00:26:03.340 I would need his phone in my room to be able to put it so 483 00:26:03.720 --> 00:26:06.360 So each one of those wasn't just me going *taptaptap* "oh that didn't work" 484 00:26:06.360 --> 00:26:10.380 It was *taptaptapTAP* Matt: And then I get a push notification with a load of gobbledygook 485 00:26:10.420 --> 00:26:12.720 Which I would screenshot and iMessage back to him 486 00:26:14.640 --> 00:26:18.820 And then he would send back to me some swear words, or things along that line 487 00:26:18.820 --> 00:26:19.880 Reversed Victory Hand 488 00:26:23.660 --> 00:26:24.820 Both: Yeah... 489 00:26:26.520 --> 00:26:28.520 That answers the Android question more or less 490 00:26:28.720 --> 00:26:30.180 I think we have about 5 to 10 minutes left 491 00:26:30.180 --> 00:26:31.920 Matt: Yeah about 5 minutes Tom: Anyone else? 492 00:26:33.160 --> 00:26:35.680 Oh, blimey alright let's go right to left 493 00:26:35.680 --> 00:26:37.220 Guy in the blue, oh hi Alex! 494 00:26:38.140 --> 00:26:40.140 Alex: Why not take the money? 495 00:26:40.560 --> 00:26:41.920 Why not take the money? 496 00:26:42.480 --> 00:26:43.720 Okay, 497 00:26:45.860 --> 00:26:49.060 We really don't want to quit our jobs to do this 498 00:26:49.600 --> 00:26:51.860 We both have jobs we enjoy 499 00:26:54.560 --> 00:26:58.200 In its current timescale, as of finishing yesterday when we launched it 500 00:26:58.820 --> 00:27:00.360 Still classes as fun 501 00:27:00.520 --> 00:27:03.300 We're not app developers we don't want this as our job 502 00:27:03.920 --> 00:27:09.000 Like we would happily take the money and give it to someone else 503 00:27:09.240 --> 00:27:11.840 And I'm sure at some point, we have a price 504 00:27:13.580 --> 00:27:16.740 And we're willing to discuss that if anyone wants to take it and make it 505 00:27:17.300 --> 00:27:22.860 But we don't want to spend the next year of our lives being acqui-hired by some big corporation 506 00:27:22.860 --> 00:27:25.080 And doing something we don't enjoy 507 00:27:25.660 --> 00:27:29.280 We've already got our careers which we're set in and we like doing 508 00:27:30.120 --> 00:27:32.300 Why would we leave that for something that isn't fun 509 00:27:32.300 --> 00:27:35.100 And isn't going to last because it's an app in an app bubble 510 00:27:35.100 --> 00:27:39.240 And let's be honest, when we said Yo got $1.2 Million in funding 511 00:27:39.880 --> 00:27:43.780 That doesn't mean that they are walking out with $600k- well no there's four of them 512 00:27:43.780 --> 00:27:45.740 So they aren't walking out with $300k each 513 00:27:45.940 --> 00:27:49.440 Matt: That comes with conditions Tom: That comes with them working there for a year 514 00:27:49.440 --> 00:27:51.460 And hiring other people to make it work 515 00:27:53.000 --> 00:27:55.480 I can't see, well we're in an app bubble now 516 00:27:55.600 --> 00:27:57.000 That's fairly obvious I think 517 00:27:57.500 --> 00:28:02.000 We're in the same kind of bubble as the Dot Com bubble before it 518 00:28:03.780 --> 00:28:08.180 They will walk out of that probably with a decent salary for the time they spent on it 519 00:28:09.620 --> 00:28:12.600 We got that, on things we actually enjoy 520 00:28:12.760 --> 00:28:14.940 I'm getting payed to work at 'Us vs Th3m' three days a week 521 00:28:15.120 --> 00:28:18.180 And the rest of the time I'm making videos for YouTube and looking at TV stuff 522 00:28:18.180 --> 00:28:19.400 That's what I want to do 523 00:28:20.040 --> 00:28:22.780 Yeah, I'm a Broadcast Engineer I like doing that 524 00:28:22.780 --> 00:28:24.940 I'm having great fun doing that; I'm going to keep doing that 525 00:28:25.560 --> 00:28:28.620 If they keep employing me Tom: So if someone wants to take 526 00:28:29.280 --> 00:28:31.420 Wants to, buy out the thing 527 00:28:31.420 --> 00:28:35.700 And take it and run with it and give it to a team who can actually make something good with it 528 00:28:36.240 --> 00:28:38.240 hello@emoj.li Tom: Yeah 529 00:28:40.680 --> 00:28:43.220 But there's not much, and there's not much we can usefully do 530 00:28:44.980 --> 00:28:47.920 There are ways, I'm assuming you can monetize it? Tom: Yeah 531 00:28:49.020 --> 00:28:53.200 One of many suggestions we've had, but we don't have the skill, we don't have the time, we don't have the, will 532 00:28:54.000 --> 00:28:55.880 So, that's why, to answer that question 533 00:28:56.200 --> 00:28:57.960 So we've got, one minute left I think 534 00:28:57.960 --> 00:29:00.620 Matt: And then we need to leave the stage Tom: Let's take the last couple, well, how are we doing? 535 00:29:00.780 --> 00:29:02.780 I think we're alright, let's take one or two more 536 00:29:03.480 --> 00:29:05.920 Ha! Okay. Very quickly, there were two hands up there 537 00:29:05.920 --> 00:29:07.720 Is anyone else going to take that question, who was it 538 00:29:08.200 --> 00:29:09.100 Audience Member: Do you have a trademark yet? 539 00:29:09.520 --> 00:29:11.280 Do we have a trademark? Both: Nope! 540 00:29:11.280 --> 00:29:13.280 You know why? Trademarks cost money 541 00:29:13.280 --> 00:29:15.280 You know what we are not spending any more on this? 542 00:29:15.280 --> 00:29:16.260 No more money 543 00:29:17.340 --> 00:29:19.640 Because the Apple developer set thing cost money 544 00:29:19.900 --> 00:29:23.320 And the SSL certificate, because we are running fully SSL, cost money 545 00:29:23.560 --> 00:29:25.060 The hosting! I need to mention the hosting Matt: Oh yes 546 00:29:25.060 --> 00:29:28.300 Bytemark. Bytemark are also sponsoring the hosting for EMF Camp 547 00:29:28.440 --> 00:29:30.400 Which is where we are for those watching this online 548 00:29:30.760 --> 00:29:35.440 Matt: They very very generously offered to host Tom: Yes, seriously I just 549 00:29:35.440 --> 00:29:37.360 They said, "I can we host?" 550 00:29:37.640 --> 00:29:40.260 And I said, "Yeah, we need an SSL server and it will need to handle this load" 551 00:29:41.020 --> 00:29:45.360 And it just stayed up overnight with 70,000 emails being sent out and it has worked 552 00:29:45.480 --> 00:29:46.780 They are good at what they do 553 00:29:46.840 --> 00:29:49.680 They also host 'Us vs Th3m', where I work, although that gets paid for 554 00:29:50.340 --> 00:29:52.760 I can't stress how good they are enough, actually 555 00:29:54.520 --> 00:29:57.740 So there's one more, please make this a good question to close on 556 00:29:58.320 --> 00:30:00.320 The pressure is on you, this is the last question 557 00:30:00.640 --> 00:30:04.420 I'm not saying this has to be a good question to end it with, but Matt: *Ascending groan* 558 00:30:05.180 --> 00:30:09.660 Audience Member: What are you going to do with all of the conversation data and are you going to use it for natural language processing? 559 00:30:09.940 --> 00:30:15.180 Alright, so are we going to do anything with the conversation data, and are we going to do natural language processing on it 560 00:30:19.000 --> 00:30:22.280 We're not Facebook, we're not OkCupid, we're not going to run experiments on our users 561 00:30:22.900 --> 00:30:27.860 While technically our privacy policy says that we can use it for internal record keeping and things like that 562 00:30:28.160 --> 00:30:29.000 We're not 563 00:30:29.800 --> 00:30:30.880 It's not 564 00:30:30.980 --> 00:30:33.720 No! Matt: In fact, I can modify the question slightly: 565 00:30:33.980 --> 00:07:13.960 "Are we going to do anything?" 566 00:07:13.960 --> 00:07:14.960 Both: No 567 00:30:38.920 --> 00:30:41.820 Tom: That's Matt Gray! Matt: And he's Tom Scott 568 00:30:41.900 --> 00:30:42.520 Thank you 569 00:30:44.160 --> 00:30:46.160 [Translating these subtitles? Add your name here!]