by LINE Engineer on 2016.11.30
Hi, my name is Hasebe. I’m in charge of the development of LINE Notify.
In a previous post, we introduced how you can use LINE Notify to send messages to LINE from the command-line. Today, I’m going to introduce two features newly implemented in the LINE Notify API. One is sending stickers and the other is uploading images.
The use case demonstrated in the previous post was sending a build result from Jenkins to LINE by using LINE Notify. In that use case, an image of Moon laughing was used to show how it can notify us of a build failure. It was during that time that we came to wonder, “why not make LINE Notify send stickers as well as images?”
We thought that sending stickers would make LINE Notify more “LINE-ish.” That’s why we decided to develop this feature.
Sending stickers from the command-line
Let’s try sending a sticker by using the curl command.
$ curl -X POST https://notify-api.line.me/api/notify -H 'Authorization: Bearer YOUR_PERSONAL_ACCESS_TOKEN' -F 'message=test' -F 'stickerPackageId=1' -F 'stickerId=113'
You can now send stickers in this way.
by LINE Engineer on 2016.11.24
This post introduces how to run tests with the ad client module provided for the LINE Platform. The LINE ad client module runs on both mobile and the web. This post will focus on testing with a mobile client.
LINE Ads Platform overview
The structure of the LINE Platform is quite simple as shown below. Various types of protocols can be used for server-client communications. This post will focus on testing with the HTTP protocol.
by LINE Engineer on 2016.11.14
In this blog post, I’d like to explain how the LINE TODAY service was developed using the Agile development method. LINE TODAY is a mobile news service that was released in Taiwan, Thailand, Indonesia, Myanmar, and the United States in early 2016. As of July 30, 2016, the service recorded nearly 30M daily PV (page views). In Japan, a service similar to LINE TODAY is available under the name of LINE NEWS.
The LINE TODAY development project is a transnational project with users, customers, developers and planners from various countries. Plenty of members participated in the project including developers, planners, QA engineers, UIT (User Interface Technology) engineers, designers, and business owners located across Taiwan, Dalian, and Korea. Moreover, it was a newly created team starting everything from scratch. Most of the developers were rookies unfamiliar to the LINE development environments and skills. No one had the experience of handling a new development project and no one knew the overall process of building a global product.
The LINE TODAY service was planned from the beginning to be released in several countries such as Taiwan, Thailand, and Indonesia. Various requirements had to be taken into account. For example, we had to consider that the content providers (CP) might prefer different types of content feeding mechanisms; Taiwan CPs preferred FTP whereas Thailand and Indonesia CPs preferred RSS.
LINE TODAY was a project with very tight development schedules. The LINE TODAY service was released twice as a FastTrack version and RegularTrack version. The FastTrack version was a proof of concept for evaluating business potential, which was then leveraged to the RegularTrack version aimed at providing the service in the long term. The FastTrack version had to be designed, developed, tested and released in 6 weeks and the RegularTrack version within 3 months after the FastTrack version was released.
by LINE Engineer on 2016.11.9
Hello, my name is Inami (@inamiy), a member of the LINE development team. In this post, I’ll be sharing my experience from being a part of the panel discussion at GitHub Universe 2016.
About GitHub Universe 2016
GitHub Universe 2016 took place during September 13-15 at Pier 70 in San Francisco.
Inside the refurbished warehouse, now conference hall, gathered over 1500 developers, technology and business leaders. Beginning with a keynote presentation from GitHub cofounder and CEO Chris Wanstrath, over 40 speakers from all over the globe gave talks on various open source projects and business activities.
I was invited as the sole Japanese member at the panel discussion.
by LINE Engineer on 2016.11.1
Hi, my name is Watanabe and I’m in charge of the development of LINE Notify. In this post, I’d like to share how developers can use LINE Notify to send messages to LINE straight from the command-line.
Up until now sending system messages to LINE either required a Bot API Trial or Business Connect account. While both are improved by Messaging API and provide many great features, they require a high level of implementation.
LINE Notify is an API that has a limited set of features, streamlining the whole process of sending messages to LINE.
Sending messages using cURL
By generating your own “personal access token” through LINE Notify, you can send messages by sending an HTTP POST request to the API endpoint. Any method can be used as long as it uses an HTTP request. In this post, let’s go over how you can use the HTTP client cURL.
Generating personal access tokens
You can generate your own personal tokens by navigating to My page (LINE account required).
When you click the “Generate token” button, you will see a screen where you can name your token and select a target that you will send messages to when the token is used.
Use an easily recognizable name for your token. When selecting message targets, selecting “1-on-1 chat with LINE Notify” will make the LINE Notify official account send a message to you. Selecting a group will make the LINE Notify official account send a message to the selected group.
You can change message targets on each token. To send messages to separate chats, you can generate individual tokens for each chat.
Your generated access token will not be shown to you again. You will need to keep the token written down, or else you will need to delete the token and generate a new one. More »
by LINE Engineer on 2016.10.26
This is Oklahomer from LINE Corp. In this post, I’d like to explain the architecture behind the chatting function of LINE LIVE, a video streaming service.
LINE LIVE for iOS and Android has a chat feature that lets its users send comments in real-time while they are watching a live-streaming video. This not only lets users (or viewers in this case) communicate with each other, but it also lets the streamers connect with their viewers. Streamers can chat with their viewers back and forth, and sometimes plan their videos according to what the viewers say in the chat. This is why the chat is an integral part of the streaming experience.
As you can probably imagine, celebrity live streams attract a large number of viewers, and along with them a torrent of comments. Comments sent to the stream must be simultaneously broadcast to every other viewer, and effectively distributing the load has always been one of our top-priority tasks. There are sometimes 10,000 comments sent per minute on just one stream alone.
We took the possibility of large amounts of comments into consideration when we were developing LINE LIVE and presently have over 100 server instances in operation for the chat feature.
More on the server architecture below.
Overall server architecture
Below is the overall architecture of the server.
by LINE Engineer on 2016.9.29
Hello, this is Momoki from the LINE Developer Day preparation committee.
LINE Developer Day has always been a gathering place for sharing various technological experiences and global challenges and trends, and LINE Developer Day 2016 has just successfully come to a close.
You’ve shown us a great amount of support by registering for the event, so much so that we could only invite a few that were selected from a draw.
We regret that we could only invite about 1000 of you to the event but we thank you all for showing tremendous support all the same!
At LINE Developer Day 2016, our engineers talked about our chatbot tactics, along with the announcement of the LINE BOT AWARDS. There were also live coding sessions, sessions about the structure of our message encryption method called “Letter Sealing,” sessions on how we handle large amounts of data transfers for LINE LIVE and LINE group calls, and sessions on how we handled large scale service outages. There were a total of 17 sessions at the conference, introducing our technologies and talking about other topics.
The slides are available through the links below.