From IndieWeb

Joy Division album cover style chart of 90 days of IRC activity Join #indieweb discussions via Discord, Slack, web chat, or IRC, now with additional focused channels for developers, WordPress, and meta topics!

All are welcome to participate in chat and meet other members of the IndieWeb community, discuss personal websites and IndieWeb projects, ask for help with technical issues, and more.

First time here? Want a quick reminder of which channel to use for what topics?

For technical information about how our chat and related services function, see discuss infrastructure.

  • FYI: Matrix used to be supported until the bridge hosted by element.io was disabled, and there is no known effort to restore it.

Read Discussions

Discussions about the IndieWeb take place primarily in our chat channels which are archived:

Join Discussions

Join the discussions! The IndieWeb chat is bridged equivalently across four different chat services so that users can use their preferred chat client!

Join via Discord

Discord invitation link: https://discord.gg/dqmFnvmN7N. Join individual channels:

Join via Slack

Slack sign up link: https://chat.indieweb.org/slack. (Re)join the IndieWeb instance: https://indiewebcamp.slack.com/ or join individual channels:

Join via web chat


  • When using the online chat, you can change your username by sending /nick <new username> into the chat.

Join via IRC


Having trouble connecting? Refer to Libera’s Connection Guide

Join via Matrix

2023-11-28: The Matrix bridge hosted by element.io has been disabled for good.

Add your icon

To have your icon or avatar show up on some of the platforms you'll need to add yourself to the list of chat-names (even if you're not using IRC). Due to some restrictions, avatars may not necessarily bridge across all platforms.

Chat Channels Purposes

Each of our chat channels has a specific purpose documented below.

Channel purpose mini-FAQ:

  • Not sure which channel to use?
  • Not sure if something belongs in #indieweb or #dev?
  • WordPress topic/example that seems more broadly IndieWeb related?


#indieweb channel
Welcome to the indieweb! How to get on the indieweb, get started, how to post, what to post, indieweb events to join the community in-person, why indieweb (including applying principles directly to pragmatic personal site goals & improvements), what software / services are ready for users to use without dealing with coding or command lines.

Keep it user-centric please!

Not sure if you should ask a technical question here? Ask yourself:

  • Could someone who has never built a website understand what you’re about to say/ask?
    • If not, please ask in the indieweb-dev channel instead!
    • Everyone’s skill level and experience is different. Avoid words like “simple”, “just”, “obviously”, “easy” when explaining things. Such words may cause shame when people run into difficulty. Further reading is available in a blog post written by Chris Coyier on words to avoid in educational reading.
  • Is someone using jargon, code, or dev talk?

Politely request such conversations move to the indieweb-dev channel (see below). We encourage the whole community to help with this, to keep the main chat friendly for newcomers and folks that want to focus on using the indieweb! And it helps avoid encounters like:

For topics about the community, reasons/thinking behind (or evolving) the principles that are not otherwise directly tied to specific personal site improvements, please take those discussions to the indieweb-meta channel.

Lastly if you’re not sure where you should ask about a topic, you can ask that question in indieweb-meta.


#indieweb-dev channel (#dev in Slack)
Development tools, services (like Bridgy), issues, APIs, creating anything besides content, and any kind of jargon. E.g. creating design, UX, implementation details, protocols (like HTTP, Webmention, Micropub, IndieAuth), formats (like HTML, CSS, microformats2, h-entry, h-card, h-event), frameworks, coding languages (like JS, PHP, Python, Ruby), server configuration (Apache, nginx, HTTPS), and other plumbing.


#indieweb-wordpress channel (#wordpress in Slack)
WordPress-specific topics: Getting Started with WordPress, IndieWeb WordPress plugins, WordPress themes, general WordPress development. If a discussion becomes more generally applicable beyond WordPress, consider taking it to the #dev channel.


#indieweb-meta channel (#meta in Slack)
Anything about the IndieWeb community, our principles, events both IndieWeb-focused and open/interesting to IndieWeb participants (coding, social web, personal data etc.), organizing & planning events, wikifying & wiki gardening, indieweb.org infrastructure like our MediaWiki & Meetable (https://events.indieweb.org) & chat channels/bridges/bots, and any issues or feature requests for any of the above.


#indieweb-stream channel (#stream in Slack)
Loqi reports posts that mention IndieWeb keywords in this channel. Mastodon tag feeds for the keyword "#indieweb" from mastodon.social and indieweb.social are included. There are also a number of individual blogs followed with a filter for indieweb-related keywords. You can also read the combined feed of posts at https://stream.indieweb.org


#indieweb-chat channel (#chat in Slack)
Off-topic channel for discussing anything, and is not publicly logged. Even though Slack has some number of lines of scrollback, this channel is considered off the record. It is the expectation of community members that this channel remains off the record. Explicit quoting or even summarizing someone should only occur after getting explicit permission.

Related Chat Channels

Related channels often used by the community:

microformats channel

#microformats (#microformats in Slack)
Ask about microformats in general, or the process of developing a new one or new features by researching, documenting examples, brainstorming, etc.

known channel

#indieweb-known (#known in Slack)
Similar to the wordpress channel, the Known channel is for Known-specific topics (plugins, evolution, troubleshooting etc.)

Slack Users

  1. Join the IndieWeb Slack Community!
  2. Join additional channels!
    • From the desktop: click the Channels heading in the sidebar to view the other channels. Click a channel, i.e. #dev, it will show you a preview of that channel with a Join Channel button.


The chat rooms (except for #indieweb-chat) can be searched at

People on IRC

Main article: chat-names

See our list of chat regulars sorted by nickname, with their website and usual timezone(s).

The channel has regular administrators, who are also wiki administrators. If you want to get their attention, just say "adminhelp".


Anecdotally the channel seems quite active:

  • 08:00-10:00 Pacific Time (-0800/-0700)
  • 16:00-18:00 UK Time (+0000/+0100)
  • 17:00-19:00 EU Time (+0100/+0200)

Differences between chat services

Each of these four options is roughly equivalent from a text perspective, though each may have features, configurations, or other niceties that differentiate them somewhat from each other.

Depending on your chat client, users from Matrix may show up with a [m] on their usernames, Discord users will have a [d] following their names, or users from Slack appear with their username in brackets. Some usernames may have the word "app" after them to indicate their content is originating from another platform. For cross-platform notifications to work on the receiving platform, one may need to include the [d] on screen names from Discord.

Some platforms, like Slack, will unfurl URLs or provide a link-preview into the chat while others will allow wiki page names pre-pended with a slash to autolink to the exact wiki webpage (eg: "/principles" in some chat platforms will link to the principles wiki page). Slack emoji responses aren't bridged to other platforms, so giving a heart or thumbs up to someone's post won't be seen unless they're also on Slack. Slack threads are also platform specific, so any threaded messages will appear without context on other platforms.


People frequently in chat might like to be aware that many chat clients provide the ability to allow their users to be given real-time notifications when either their username or other specified keywords are used in individual channels. (Check the documentation of your chat client(s) for details.) This can be useful if one wants to engage in conversations around particular topics in chat.

Many organizers and project developers will have turned on notifications for keywords related to projects they're actively working on or which they support. Other community members or volunteers may have notifications for particular topics/keywords on which they're an expert and are willing to provide pointers or support. Keep in mind and be respectful of the fact that almost everyone in chat is an unpaid volunteer and we're all on different work and personal schedules as well as in different timezones. Depending on how often people are in chat and whether or not they read all the logs, Loqi can be helpful for communicating across time and space.

Using an IRC client

  1. If you're already an IRC user, setup your client with:
    • Server: irc.libera.chat
    • Port: 6697 (usually default)
  2. Join the channels above (by clicking on the chat links)

See the libera.chat connect guide if you’re having trouble connecting.


There is no mailing list! 🎉

This is a deliberate decision. We encourage focusing on short discussions in chat and capturing incremental agreements/disagreements on the wiki. This also discourages long essays and repetition of arguments that can take place on email threads.

For more see:


If you prefer an email-like experience reading things in the past, see the current logs!

The source data of the logs served at chat.indieweb.org is available on GitHub.

Logs on Your iPhone Home Screen

To add the IRC logs to your iPhone home screen, visit the page below on your phone:


Follow the link on that page. Then, from Safari, add that page to your home screen.


We have the most awesome IRC logs on the web. That doesn't mean they can't be even more awesome. Got an idea, suggestion, or issue to report about the logs? Create or comment on a GitHub issue:

Why is there no channel for X

Historically the number of channels in the IndieWeb community chat has grown organically, after documented use-cases, time for discussion, and rough consensus on new names.

From time to time we do add new channels, generally when there is a consistent level of discussion and conversation that either makes it overwhelming or potentially unwelcoming to carry on discussions related to specific topics. This is balanced against the possibility that a new chat channel would be either so quiet or infrequently used that asking questions or attempting to have a conversation there wouldn't be conducive or would result in people repeating the same question in multiple channels.

There is usually an annual conversation about adding new channels at the organizers' meeting at the IndieWeb Summit, though other conversations do happen throughout the year or can be brought up in the #indieweb-meta channel.

Discord issues

The Discord bridge is using the go-discord-irc daemon; if you encounter issues with the bridging itself, please ping Peter Molnar or Aaron Parecki

There are some ongoing issues with the Discord bridge: messages from Discord to IRC may get lost in the wire. Please report any problems you experience.


events meetups channel

There is a desire for a new channel, for simplicity by default like nearly all other new channels, logged, indexed, with web access, for use by folks before or at events or meetups, in-person or virtual, for potentially real-time and/or rapid chat about an event or related socializing & logistics.

Discussion: this has come up most recently on 2024-03-08 and has come up a few times in chat in the past (citations would help!).


  • A dedicated place to see event start and end notifications
    • 10 minutes before scheduled zoom meeting
    • a notification when the actual zoom call ends
  • A clear place to chat instead of Zoom during virtual or hybrid events!
    • We turn off Zoom chat in the IndieWeb Zooms, so it would be great if there was a singular clear chat channel to use specifically during such events that we could link to, and direct people to in Zooms.
    • The name of the channel should be easily speakable/hearable, so folks can find/join with minimal effort
  • ... extract more from meta chat logs 2024-03-08


  • separate out the discussion that happens during a zoom or in-person event
    • online discussions can continue without worrying about stepping on the toes of in-person/zoom discussions
    • a place to share links during a zoom meeting where it's ok that there's no context in chat (e.g. multiple instances of a link being dropped in the chat that appears as a sequitur because there was no prior discussion in chat because the discussion was on zoom)
  • when you're in person, you often want a high signal channel to get updates on scheduling or where the group is heading after the main event, etc


  • one more place to catch up on scrollback. (which is also a pro: easy to skim and ignore all scrollback if you aren't interested)

Prior art (other communities' channel names/purposes for events and meetups)

  • #meetup in Discord in the EH community for planning IRL meetups and coordinating when in the same town - Tantek Çelik
  • #live-stream-chat in Discord in the EH community for backchannel chat during a shared live video stream. - Tantek Çelik (more)
  • #voice-text-chat gRegor Morrill: "A Discord I'm in has a channel #voice-text-chat for when people are hanging out in the voice channel for an event. It works pretty well for dropping links, gif reactions, side-chat, and allows non-verbal people to participate." [1]
  • ...

Proposed names: (all names would have the "indieweb-" prefix in IRC and Discord, and no prefix in Slack,

web making channel

There is a growing broad spectrum of participants in the dev channel, including lots more beginner web developers who really want to learn a bit more about HTML+CSS (many recent questions) and may be (or are?) intimidated by the sometimes very deep and complex dev plumbing conversations.

Should we create a new channel that is focused primarily on (entry-level?) web makers for the curious and tinkerers who may be comfortable editing and uploading static HTML+CSS files, and maybe even using GitHub static pages to publish them, but are not interested in deep discussions of specifications, protocols, plumbing, server configuration etc.? Idea by capjamesg, roughly reworded by Tantek Çelik.

Examples of other communities that appeal to HTML+CSS web designers/developers (may be useful sources for naming considerations)

Ideas for names of such a channel?

  • #indieweb-maker
    • +1 capjamesg - Sounds approachable and empowering.
    • 0 Murray - I like it, but would expect it to be more about content creation/artistic outputs e.g. writing, filming, photography etc.
    • +1 João Pesce - Sounds fun and not too technical, but I tend to associate maker with maker culture (i.e. physical things). Maybe #web-maker? might also address Murray's concerns.
    • 0 Aaron Parecki - I think this is too associated with maker culture as mentioned above
    • +0 Tantek Çelik agree with James, this is approachable and inviting and I think some overlap with maker culture is ok
    • -1 Al Abut I love the intention of this but “maker” is one of those vague overarching words that strikes me the same way that “creator” does. I’m constantly having to decode it to depending on the context of the platform or user type. It can mean filmmaker, writer, full-time marketer of their own personal brand, etc. And none of those necessarily imply the newbie-friendliness or focus on frontend tech that I think can be so valuable.
    • +1/0/-1 Add yourself here… (see this for more details)
  • #indieweb-beginner
    • -1 capjamesg - This should be a channel to discuss your personal website and making it. "beginner" implies this channel isn't for people who are more advanced and have questions about HTML/CSS, etc (a category in which I certainly fall :D).
    • -1 Murray - I feel like this is what the #indieweb channel should strive to be, otherwise this feels like the first channel to go to if you're new.
    • -1 João Pesce - Not narrow enough. I think beginners should be able to participate on the indie web without being concerned about HTML/CSS, like using a platform + pre-built theme.
    • -1 Aaron Parecki - agreed with the above comments
    • -1 Tantek Çelik - it's not beginner, and we should always work to make main (#indieweb) beginner friendly
    • +1/0/-1 Add yourself here… (see this for more details)
  • #indieweb-html-css-js
    • 0 capjamesg - NB: There are other topics that are not HTML/CSS/JS that someone may want to discuss (my DNS isn't working / my site isn't loading properly, choosing colour schemes for one's website, layout principles like spacing, etc.).
    • 0 Murray - Feels too technical of a name, but I do think the simplicity has merit. I also think anything CSS automatically covers things like spacing, layout, colour schemes, but agree that this may not be clear.
    • -1 João Pesce - Might discourage people to ask some topics that are not HTML/CSS/JS related, but should be discussed.
    • 0 Aaron Parecki - Seems too specific
    • -1 Tantek Çelik - similar criticisms, too long, could/should also include ARIA, mf2, SVG
    • +1/0/-1 Add yourself here… (see this for more details)
  • #indieweb-web-dev
    • +1 Murray - I like that this keeps things broad enough but also uses a term many people are familiar with. Doesn't require technical knowledge/terms. Bonus that it mirrors the existing #dev channel, but perhaps too closely. Could be #web-development
    • 0 João Pesce - Sounds a little bit too technical to me. "dev" feels like a job. Making personal web sites should feel more like painting to me.
    • -1 Aaron Parecki - This is just going to be confusing, since in IRC it would be "#indieweb-web-dev" vs "#indieweb-dev", and then in Slack/Discord it would be "#web-dev" vs "#dev" and that doesn't really tell me what the difference is
    • -1 Tantek Çelik also confusing, web-dev is vague and means different things to different people
    • +1/0/-1 Add yourself here… (see this for more details)
  • #indieweb-frontend
    • +1 Tantek Çelik I like this overall, and definitely like it better than a bunch of of the other longer/wordier options like "-html-css-js" or "-web-dev", certainly better than "-beginner". Convinced of this instead of "-maker".
      • Description should include HTML+ARIA+mf2+CSS+SVG at least, with JS for progressive enhancement perhaps
    • +1 Al Abut I particularly love the word “frontend”. It’s sort of implicitly newbie-friendly by focusing on the best entry path to making websites (plain html is such a refreshingly “back to basics” type of tech) yet it also leaves a lot of head room to grow from that foundation. In fact I think the word “frontend” is strong enough to stand on its own as a channel name, without a prefix that muddies the waters like “indieweb-“ or “dev-“.
    • +1 Joe Crawford I think the indieweb-prefix sets the stage that the things intended are with an indieweb focus, and I think "frontend" is encompassing enough to address more than "html" and "CSS" which after all are incredibly rich technologies which pull in images, video, scripting, mobile, accessibility, and all the rest.
    • +1/0/-1 Add yourself here… (see this for more details)
  • #frontend
    • +1 Al Abut I’d vote for either “indieweb-frontend” or the more streamlined “frontend” compared to the options above.
    • -0 Tantek Çelik There are other resources (Slacks etc.) for generic frontend web discussions, and a global channel named "frontend" would imply that it is aiming for all of that, which either loses or dilutes the IndieWeb focus.
    • +1/0/-1 Add yourself here… (see this for more details)
  • ...

other new channels

Other new channel proposals, some as alternatives to each other or above proposals.

protocols split from dev

Alternate proposal: move all protocol chat to a new channel called #indieweb-protocols and use #indieweb-dev for developer chat.

  • #indieweb-protocols
    • capjamesg +1
    • [qubyte] in Slack: "Sounds like a good idea!"
    • Aaron Parecki +1
    • Paul Robert Lloyd +1
    • -1 Tantek Çelik too much community labor to actually get indieweb-dev folks to move to indieweb-protocols, as evidence by existing folks, some here on the page, themselves having difficulty moving from #indieweb to #indieweb-dev. More here: https://chat.indieweb.org/meta/2024-03-30#t1711813588098200. Also "protocols" is too narrow, it does not include all building blocks standards, we also have "formats", we have discovery algorithms, etc. This is poor framing and doesn't actually address a real problem / cluster of conversations that needs a separate channel. It's already hard enough for folks to know when they should use #indieweb-dev vs #microformats and that's an existing similar split.
    • -0.5 gRegor Morrill I've not found the discussions in dev overwhelming/distracting enough to split off personally. Also concerned about the extra cognitive load tantek mentioned "where does this go?"
    • +1/0/-1 Add yourself here… (see this for more details)
  • ...


  • How would we differentiate this from the current #indieweb-dev channel?
  • Should we split Category:jargon into beginner/advanced jargon to have Loqi nudge people to the appropriate channel?

server split from dev

Alternate proposal: move all server-related chat to a new channel called #indiweb-server and use #indieweb-dev for typical/default client-side developer chat.

  • #indieweb-server
    • -0 Tantek Çelik: I like this much better than "-protocols" because I think it gets more to the heart of what are differences of what people (not) want to talk about in -dev, however I would still prefer to try starting with -frontend first (see above) which be enough for -dev to default to server related talk. and it will be much easier to have new HTML+ARIA+mf2+CSS+SVG folks join a -frontend channel than it will be to nudge server conversations out of -dev and into -server (same burden as -protocol noted above)
      • I would also be OK with a different label like "-sysadmin", or anything that indicates that the topic is more centered on server-side or administrative topics, rather than the development of sites
      • Does this run the risk of becoming an admin tax channel? 😉
    • -0.5 gRegor Morrill I've not found the discussions in dev overwhelming/distracting enough to split off personally. Also concerned about the extra cognitive load tantek mentioned "where does this go?"
    • +1/0/-1 Add yourself here… (see this for more details)


  • Does -server imply -sysadmin?


Why use Slack?

Q: Why do you use Slack? Isn't that not "indie"?

A: Slack is one way to join the chat. The canonical chat logs are at https://chat.indieweb.org Slack provides several features that some people prefer over other chat clients, so bridging to Slack lets people join and communicate using their preferred chat client.

Why use Discord?

Q: Why do you use Discord? Isn't that not "indie"?

A: Discord is one way to join the chat. The canonical chat logs are at https://chat.indieweb.org Discord provides several features that some people prefer over other chat clients, so bridging to Discord lets people join and communicate using their preferred chat client.

See Also