Naver engage

Engage with other Naver blogs from the person's connected blog: an automation that comments on neighbors' new posts (이웃 새 글 댓글), and one-off likes (공감) and follows (이웃추가). Everything here shows up on someone else's blog under the person's name, so every action is confirmed with them first.

All of it runs in the Uplika extension in the person's Chrome. Call bridge_status before a like, a follow or turning the automation on. If state is not online, relay userMessage word for word and wait until the person says Chrome is open.

Actor and target are two different blogs

• Actor: the person's connected Naver Blog, the account the action is done as. In the extension's jobs this is blogId, and the server fills it in from the connected account. A workspace holds one Naver Blog, so choosing the workspace chooses the actor (follow still has an accountId argument for several blogs in one workspace; you will not need it). If a call answers workspace_required, show the workspaces it lists, ask which blog should act, and pass workspaceId.
• Target: the other blog, the owner of the post being liked or commented on, or the blog being followed. In the jobs this is targetBlogId, taken from the link.
• They are different values. Never derive one from the other: a link to someone else's post does not change who acts, and the actor never comes from a link.
• The person's Chrome has to be logged in to Naver as the actor blog. If it is logged in as a different blog, the job stops with naver_wrong_login and touches nothing. Relay the message, ask the person to log in as the actor blog, then try once more.

Limits are not ours to guess

Never state, estimate or promise how many comments, likes or follows are safe per day or per hour, and never invent a pace. Naver closed its writing API over mechanical mass activity, and when Naver restricts an account it is the person's blog that gets suspended, not Uplika. Uplika's server and Naver decide the limits: