Slack Green 블로그

We created a channel canvas with the Slack API, wrote markdown into it, found sections and edited them, then read it back. The free-plan errors, the markdown that rendered and the mention syntax that did not.

We called reactions.add with standard, aliased, skin-tone and custom emoji names in a test workspace, then kept adding reactions until Slack refused. Every response, the reaction_added payload, and the per-user limit we hit.

Slack verifies an Events API Request URL by POSTing a url_verification challenge. We ran a 16-line Flask handler behind a tunnel and recorded the request, the Verified tick, and the exact error Slack shows for a wrong body, an HTTP error and a slow reply.

We built a Slack App Home tab with views.publish in a test workspace and recorded the app_home_opened payload, every error a bad view returned, and what users see when the Messages tab is off or read-only.

We added localhost, 127.0.0.1, https, custom-scheme and tunnel redirect URLs to a Slack app on 1 October 2026, then ran the OAuth flow against a local server. What was accepted, how Slack matches the URL, and the PKCE rules.

A Slack app manifest we used to create a working app on 1 October 2026, in YAML and JSON, plus the validation errors from broken versions and real output from apps.manifest.validate, export, create and update.

chat.delete removes a message by channel and ts. We deleted bot messages, a person's messages, a thread parent and an already deleted message with bot and user tokens, and list every response, including cant_delete_message and the tombstone a thread parent leaves.

We opened a Slack modal with views.open after delays from 0 to 5 seconds, 28 times, on 1 October 2026. The success rate per delay, the exact errors, and the Bolt code that avoids expired_trigger_id.

users.lookupByEmail turns an email address into a Slack user ID. It needs the users:read.email scope. We ran it with the right and wrong emails, upper case, spaces and a token without the scope, in curl and Python, and list every response.

We sent Block Kit messages just under and just over each limit through chat.postMessage and an incoming webhook on 1 October 2026. The last value that worked, the first that failed, and the exact error text for each.

We called auth.test with no token, a broken token, a revoked token and tokens from an uninstalled and a deleted app, and wrote down every response. invalid_auth, not_authed, account_inactive and token_revoked each point to a different fix.

search.messages works only with a user token that has search:read. We ran it against our own test workspace: the response shape, the bot token error, 10 search modifiers with their counts, paging limits that fail silently, how long new messages take to show up, and the newer assistant.search.context.

To reply in a Slack thread, pass the parent message's ts as thread_ts. We tested it with a bot token, a webhook and Socket Mode events on 1 October 2026, including the values that silently post to the channel instead.

We sent ephemeral messages with chat.postEphemeral, in a channel and in a thread, then tried chat.update and chat.delete on them, replaced and deleted them through response_url, and checked what was left after a reload. Every response is from the real run.

We called chat.update with a bot token and a user token on 1 October 2026: the response, every error we hit, the 4,000-character cap, and what an edit shows and notifies in Slack.

A 13-line Bolt for Python app that answers in Slack over Socket Mode, run against a real workspace, plus the exact errors from the wrong token, a missing connections:write scope, and two copies running at once.

게스트는 내 Slack 워크스페이스에 들어오고, 다중 채널 게스트의 비용은 내 회사가 냅니다. Slack Connect는 두 워크스페이스를 연결하고, 각 회사가 자기 인원만큼 냅니다. 비용, 제한, 권한, 무엇을 고를지.

LinkedIn에서 사진에 붙는 꽉 찬 초록 점은 지금 LinkedIn에서 활동 중이라는 뜻입니다. 속이 빈 초록 원은 지금은 없지만 모바일 앱으로 바로 알림이 간다는 뜻입니다. 설정 및 개인정보, 공개 범위, Manage active status에서 끌 수 있지만, No one으로 하면 다른 사람 상태도 안 보입니다.

Slack에 Google 캘린더 앱을 설치하고 기본 캘린더를 연결해 상태 동기화를 켜면, 다른 참석자가 있는 수락한 일정에서 "회의 중", OOO나 PTO 일정에서 "부재중"이 붙습니다. 방법, 규칙, Outlook, 동기화가 안 되는 이유.

Outlook에서 초록은 대화 가능, 빨강은 다른 용무 중, 모임 중, 방해 금지, 노랑은 자리 비움, 회색은 오프라인이나 상태 알 수 없음, 보라는 부재중입니다. 점은 Outlook이 아니라 Microsoft Teams 상태에서 옵니다. 색을 정하는 것, 회색이 되는 이유, 숨길 수 있는지, 일정 표시 방법 색과의 차이.

Windows용 Caffeine은 59초마다 F15 키 이벤트를 보내 컴퓨터를 깨워 두는 Zhorn Software의 무료 트레이 앱입니다. 2026년 10월 3일 caffeine.zip을 내려받아 exe 두 개의 크기, SHA-256, 서명, VirusTotal 결과, 트레이 아이콘을 확인했습니다. 쓸 만한 스위치와 PowerToys Awake 비교도 정리했습니다.

Mac에서 Slack 알림이 멈추는 원인은 대개 macOS 쪽에 있습니다. Slack 알림 권한, 집중 모드나 그 일정, 화면을 공유하는 동안 모든 배너를 숨기는 설정입니다. Mac에서 확인할 순서와 Slack 설정, 소리, 초기화 방법을 정리했습니다.

We called chat.scheduleMessage with a bot token for times from 10 seconds to 121 days ahead, listed and deleted the results, and watched which messages still arrived. The limits, the exact errors, and a delete that returned ok but did not stop the post.

Slack invite links expire after 30 days and have no longer option. We made links in a test workspace, deactivated them, and found a signed-out check that tells a live link from a dead one.

Slack's Set up mobile overrides checkbox lets your phone get a different notification level than your computer. We ticked it in every combination and read back the saved settings after each click.

Slack has no superscript format. We sent ^2^, ², x^2 and Unicode characters from the message box, the API and a Block Kit markdown block: only Unicode rendered raised. Copy-ready characters, and how Slack search treats them.

Slack에 커스텀 이모지를 추가하려면 입력창의 스마일 아이콘에서 "이모지 추가"를 열고, 이미지를 올리고 이름을 붙여 저장합니다. 저희 테스트에서는 정지 이미지는 모두 128 x 128로 줄어든 뒤 받아들여졌고, 거부된 것은 큰 GIF뿐이었습니다.

Call conversations.history, follow next_cursor, then fetch each thread with conversations.replies. We read 40 seeded messages and 6 replies from a test channel and show the script, its output, and what limit, oldest and latest did.

Discord 방해 금지는 상태를 빨간색으로 바꾸고, 멘션, DM, 통화 벨소리를 포함한 데스크톱 팝업과 소리를 끕니다. 메시지와 통화는 계속 오고, 읽지 않음 배지도 계속 쌓입니다. Discord에 따르면 모바일 푸시 알림도 옵니다. 타이머로 켜는 법, 오프라인 표시·자리 비움과의 차이, 저절로 켜지는 이유를 정리했습니다.

Three short Python scripts that post to Slack, run against a real workspace with their output: an incoming webhook with requests, chat_postMessage with a bot token, and a thread reply. Plus the errors we triggered and what an 80-message burst did.