Name: ダイヤルアップを復活させる：SMSを使ったインターネット by Alexandra Sunderland｜JSConf EU 2019 (Bringing back dial-up: the internet over SMS by Alexandra Sunderland | JSConf EU 2019)
Uploaded: 2021-01-14T10:25:48.000Z
Duration: 20 min 51 s
Description: VoiceTubeの動画で発音を聞きながら英語表現を覚えよう！学べる英語：

現在進行形

I'm a software engineer at Bella, we're making a product that acts as copilot for a manager,

And what I was to talk about today is something completely different in my spare time.

It's transferring all the data you need other SMS.

Why would I build something like this when we have data on Wi Fi connections all over

I come from a country where a data plan for 2 gigabytes a month costs 55 Euros and only

Three quarters of a million people are using dialup Internet in their homes.

So, the Internet is so, so expensive just when I'm at home, that when I'm traveling

somewhere, to come to Berlin, the prices are out my price range.

When I travel, I love to visit Paris and the streets look like this.

I get lost really easily in a grid like structure.

When I'm over here, I need data to get around.

And I could technically download a map offline and use that.

But that doesn't give me transit directions which is something I really need when I walk

When I was trying to come up with a solution for this problem, I noticed like I can't afford

But SMS without a data plan costs about 15 cents per message.

When I was starting a solution to this problem, chatbots were the big thing at the time.

I set up this problem, setting up a Python server with SMS and grabbing it from the Internet

and grabbing the directions and text it back to me.

I could do something simple, how do I get from point A to B and get the Google Map directions

I could do this for 30 cents per direction.

Which is pretty good compared to what I would be paying for data otherwise.

And this really worked, and I used it lot when I was traveling.

But the issue is when you get a little bit of access to the Internet, you start to crave

So, I was building these one off integrations to figure out ratings for a restaurant I wanted

to see or a translated word I didn't know and do all this stuff.

And building out all these integrations as a one off took up a lot of time.

And that's what I'm gonna show you today.

So, your two main components to the project I did.

There's the Android app on one side and the server in NodeJS on the other.

The app I made in Android because I was it just for me.

And I'm using Java instead of Kotlin because there was a lot more on StackOverflow on SMS.

That was a good solution for me, I'm not an app developer.

And NodeJS, I thought it would be fun you to use JavaScript on a browser where it doesn't

belong to make this JavaScript less browser.

And Twilio does a lot of things, I bought a phone number from it and it let me set up

I can send a text message to my Twilio phone number and it will forward all those messages

So, before I jump into the project, just to set up like a limitation I had to deal with,

SMS can only handle 160 characters at a time.

If I want to create a browser, I'm going to have to transmit this data less than one Tweet

Like this Google web page looks very, very small.

It's just a text box and the logo and a button.

But the thing is, if you actually look at the page source, not including any CSS, not

including the images or any sources being loaded in, this web page is a quarter of a

If you were to transmit this entire thing, 1300 SMS, not including the ones dropped along

In Twilio fees alone, I would have been paying $10 to transmit this Google page.

It defeats the purpose of being a cheap solution.

So, we have to do a lot on this page to get it to work.

But if we were to imagine what this Google page look would like building it up from scratch,

we wouldn't imagine all the CSS to make it load.

We would imagine this little bit of HTML that sets up the form and the text box which is

This is how we envision a lot of the web pages to make this project work.

So, we're going to walk through the life cycle of a request and that's starting on the Android

Right off the bat we get into this huge limitation with systems because the URL spec says that

a URL can be 2,000 characters longitudinal.

So, that could take up 13 SMS which is a lot more than we want to deal with.

The first thing on the app side, and the app looks like this, a text box and a go button.

We're going to start off by chopping off everything that we don't really need.

So, the browser is going to be a very text based browser.

We're not going to allow any kind of cool single page applications.

We can chop off anything that has a pound symbol, page, whatever.

We don't want any tracking IDs or query parameters.

Everything in black after the URL there we can get rid of.

And same with the HTTPS, www, at the start of the URL because it's assumed that all websites

So, the part in yellow is what we're going to be sending over as an SMS.

And that's gonna look something like this.

I'm not going to cover the Android side of things too much.

But make sure we have send, receive and write permissions on Android and use their simple

SMS manager API which lets you just specify the destination phone number which in this

Specify the text that you want to send and then it just gets sent off.

So, then Twilio picks up on message and converts it into a format that the server will read.

ダイヤルアップを復活させる：SMSを使ったインターネット by Alexandra Sunderland｜JSConf EU 2019 (Bringing back dial-up: the internet over SMS by Alexandra Sunderland | JSConf EU 2019)

字幕リスト動画再生

ダイヤルアップを復活させる：SMSを使ったインターネット by Alexandra Sunderland｜JSConf EU 2019 (Bringing back dial-up: the internet over SMS by Alexandra Sunderland | JSConf EU 2019)

specific

entire

grab

guarantee