<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Community Building on Arkadii Yakovets</title><link>https://arkid15r.dev/categories/community-building/</link><description>Recent content in Community Building on Arkadii Yakovets</description><language>en</language><copyright>© Arkadii Yakovets</copyright><lastBuildDate>Mon, 28 Sep 2026 13:15:00 -0700</lastBuildDate><atom:link href="https://arkid15r.dev/categories/community-building/index.xml" rel="self" type="application/rss+xml"/><item><title>Attention tax: your Slack habits are other people's unread count</title><link>https://arkid15r.dev/slack-community-etiquette/</link><pubDate>Thu, 17 Sep 2026 11:00:00 -0700</pubDate><guid>https://arkid15r.dev/slack-community-etiquette/</guid><description>Communities get the Slack they tolerate. Large communities drown less often in obvious scam posts or clear code of conduct violations than in everyday attention tax. Wrong channel posts, top-level replies that should have been threads, and the `Also send to #channel` checkbox quietly multiply unread counts for people who never asked for the ping. This post is a practitioner etiquette essay from Slack-lived experience: pick the right room, consolidate before you hit Enter, trim link previews, prefer reactions over thanks-noise, and remember that deleted messages still leave footprints. It ends with a short checklist you can pin.</description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://arkid15r.dev/slack-community-etiquette/feature.jpg"/></item></channel></rss>