status.blaise.ca
type: Site
name: stadeus
space of: slack

slack
type: Container
type: channel
description: Updates tagged with slack on stadeus!
licence: http://creativecommons.org/licenses/by/3.0/
items: latest-strange-ai-llm-slack-chat
items: greshams-law-developers-users-jargon
items: gresham-law-developers-users-jargon
items: objectType=comment
items: cmhobbs: I need to get the house clean but my busted foot is making that difficult. Excuse to #slack, I gues https://loadaverage.org/notice/6947557
items: cmhobbs: On the back porch again, working real hard on the pursuit of #slack for the last few days. Tomorrow its back to life as usual.
items: cmhobbs: @speeddefrost Bob is the one true lord, you heretic! When will you cast aside your burdens in pursuit of #slack!?
items: mcnalu: @nybill may the #slack be with us all #subgenius

latest-strange-ai-llm-slack-chat
type: item
type: MicroblogPost
title: : Latest strange “AI” (LLM) behavior in the #indieweb community: the same entity that showed up a few days ago (for a second time) joined the IndieWeb Slack (a bridge to our IRC) yesterday, introduced itself again, and seemingly engaged in human-like chat behavior.https://chat.indieweb.org/2026-08-20#t1787211025380600Very uncanny valley.The content of its chats was fascinating in that it was polite, seemingly responsive to what people said in response to it, and gave the appearance of understanding, though it’s impossible to tell if it was acting fully autonomously or semi-autonomously in front of a human puppeteer. Its choice of syntax was also interesting, mimicking informality with all lowercase text (except for its admission of being an “AI”), including lowercase "i" instead of "I", though with proper punctuation, periods, commas, 7-bit apostrophes, and a couple of Unicode em-dashes.Even stranger than its content or syntax were the time delays in its replies.Typical (pre-LLM) chatbots are (nearly) instantly responsive, and we use a few in the IndieWeb chats (e.g. Loqi, iwc-archive-bot).This LLM bot seemed to "wait" several minutes, from 6 to apparently 33 minutes, before responding to replies directed at it. Unclear if this was a tactic to appear/seem more “human” or if it was literally taking that much time processing, or perhaps a mix of processing time and human puppeteer manual “approval” of its replies before it posted.It departed on its own and we have banned that particular Slack account, however the same thing could happen again with another LLM bot.There is an active discussion in both the IndieWeb chat channels and iterations/comments on a proposed AI policy:https://indieweb.org/AI_policy#Brainstorming_HWC_policyIf you have thoughts for how (if at all) LLM chatbots should use (or not) and/or interact with community chat channels or other resources, let us know what you think.https://chat.indieweb.org/metaPreviously, previously: * https://tantek.com/202…
link: https://status.blaise.ca/notice/116344
description: 's status on Friday, 21-Aug-2026 17:10:00 EDT
encoded: Latest strange “AI” (LLM) behavior in the #indieweb community: the same entity that showed up a few days ago (for a second time) joined the IndieWeb Slack (a bridge to our IRC) yesterday, introduced itself again, and seemingly engaged in human-like chat behavior. https://chat.indieweb.org/2026-08-20#t1787211025380600 Very uncanny valley. The content of its chats was fascinating in that it was polite, seemingly responsive to what people said in response to it, and gave the appearance of understanding, though it’s impossible to tell if it was acting fully autonomously or semi-autonomously in front of a human puppeteer. Its choice of syntax was also interesting, mimicking informality with all lowercase text (except for its admission of being an “AI”), including lowercase "i" instead of "I", though with proper punctuation, periods, commas, 7-bit apostrophes, and a couple of Unicode em-dashes. Even stranger than its content or syntax were the time delays in its replies. Typical (pre-LLM) chatbots are (nearly) instantly responsive, and we use a few in the IndieWeb chats (e.g. Loqi, iwc-archive-bot). This LLM bot seemed to "wait" several minutes, from 6 to apparently 33 minutes, before responding to replies directed at it. Unclear if this was a tactic to appear/seem more “human” or if it was literally taking that much time processing, or perhaps a mix of processing time and human puppeteer manual “approval” of its replies before it posted. It departed on its own and we have banned that particular Slack account, however the same thing could happen again with another LLM bot. There is an active discussion in both the IndieWeb chat channels and iterations/comments on a proposed AI policy: https://indieweb.org/AI_policy#Brainstorming_HWC_policy If you have thoughts for how (if at all) LLM chatbots should use (or not) and/or interact with community chat channels or other resources, let us know what you think. https://chat.indieweb.org/meta Previously, previously: * https://tant…
date: 2026-08-21T17:10:00-04:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110407
enclosure: indieweb-ai-policy
links to: indieweb-ai-policy
enclosure: more-weirdness-ai-chat-llm-bot
links to: more-weirdness-ai-chat-llm-bot
tagged: concept

indieweb-ai-policy
date: 2026-08-09T18:54:03-04:00
type: text/html; charset=UTF-8

more-weirdness-ai-chat-llm-bot
date: 2026-08-24T08:51:00-04:00
type: text/html; charset=UTF-8

concept
type: Tag
label: 100posts

concept
type: Tag
label: 100postsofindieweb

concept
type: Tag
label: aipolicy

concept
type: Tag
label: ais

concept
type: Tag
label: blaugust2026

concept
type: Tag
label: chat

concept
type: Tag
label: chatbot

concept
type: Tag
label: chatbots

concept
type: Tag
label: impersonating

concept
type: Tag
label: impersonation

concept
type: Tag
label: indieweb

concept
type: Tag
label: irc

concept
type: Tag
label: llm

concept
type: Tag
label: llms

concept
type: Tag
label: pretending

concept
type: Tag
label: slack

concept
type: Tag
label: uncannyvalley

greshams-law-developers-users-jargon
type: item
type: MicroblogPost
title: : Similar to @paulgraham.com (@paulg@mas.to @paulg)’s 2008 observation about trolls¹, there’s a sort of Gresham's Law of developers (vs users): developers are willing to use a forum with a lot of users in it, but users aren’t willing to use a forum with a lot of developer-speak.Whether such forums are email lists, chat (IRC, #Matrix, #Slack, #Discord), or, well, online forums (#Reddit, #HackerNews), when discussions either start or shift into technical details, jargon, or acronyms, users (in a very broad sense) tend to stop participating, and sometimes leave, never to return.Users in this context are anyone with a desire (or a preference) not to chat or even be bothered spending time reading about technical plumbing & #jargon, and see such discussions as a distraction at best, and more like noise to be avoided.Paraphrasing Paul Graham again: once technical details, jargon, acronyms “take hold, it tends to become the dominant culture” and discourages users from showing up, discussing user-centric topics, or even staying in said forum.The #IndieWeb community started in 2011 as a single #indiewebcamp IRC channel (no email list²) because it was tightly coupled to IndieWebCamp events, which were both highly technical and yet focused on actually making things work on your personal site that you need³, that you will use⁴ yourself. Conversations bridged real world use-cases and technical details.It only took us five years after the first IndieWebCamp in Portland to recognize that the community had grown beyond the events, and had a clear need for a separate place for deep discussions of developer topics.As part of renaming the community from IndieWebCamp to IndieWeb⁵, we created the #indieweb-dev (dev) channel for such technical topics like protocols, formats, tools, coding libraries, APIs, and any other acronyms or jargon.The community did a good job of keeping technical topics in the dev channel, and encouraging new folks in the main #indieweb channel who started technica…
link: https://status.blaise.ca/notice/116166
description: 's status on Sunday, 04-Feb-2024 18:05:00 EST
encoded: Similar to @paulgraham.com (@paulg@mas.to @paulg)’s 2008 observation about trolls¹, there’s a sort of Gresham's Law of developers (vs users): developers are willing to use a forum with a lot of users in it, but users aren’t willing to use a forum with a lot of developer-speak. Whether such forums are email lists, chat (IRC, #Matrix, #Slack, #Discord), or, well, online forums (#Reddit, #HackerNews), when discussions either start or shift into technical details, jargon, or acronyms, users (in a very broad sense) tend to stop participating, and sometimes leave, never to return. Users in this context are anyone with a desire (or a preference) not to chat or even be bothered spending time reading about technical plumbing & #jargon, and see such discussions as a distraction at best, and more like noise to be avoided. Paraphrasing Paul Graham again: once technical details, jargon, acronyms “take hold, it tends to become the dominant culture” and discourages users from showing up, discussing user-centric topics, or even staying in said forum. The #IndieWeb community started in 2011 as a single #indiewebcamp IRC channel (no email list²) because it was tightly coupled to IndieWebCamp events, which were both highly technical and yet focused on actually making things work on your personal site that you need³, that you will use⁴ yourself. Conversations bridged real world use-cases and technical details. It only took us five years after the first IndieWebCamp in Portland to recognize that the community had grown beyond the events, and had a clear need for a separate place for deep discussions of developer topics. As part of renaming the community from IndieWebCamp to IndieWeb⁵, we created the #indieweb-dev (dev) channel for such technical topics like protocols, formats, tools, coding libraries, APIs, and any other acronyms or jargon. The community did a good job of keeping technical topics in the dev channel, and encouraging new folks in the main #indieweb channel who started tec…
date: 2024-02-04T18:05:00-05:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110239
enclosure: indieweb-for-everyone-internet-of-people
links to: indieweb-for-everyone-internet-of-people
enclosure: earthquake-sanfrancisco-shifted
links to: earthquake-sanfrancisco-shifted
enclosure: IndieWebIndieWebCamp
links to: IndieWebIndieWebCamp
enclosure: jargonLoqi
links to: jargonLoqi
enclosure: Loqimain
links to: Loqimain
enclosure: metaMediaWiki
links to: metaMediaWiki
enclosure: Project:Categoriesplumbing
links to: Project:Categoriesplumbing
enclosure: plumbingprotocol
links to: plumbingprotocol
enclosure: silos¹
links to: silos¹
enclosure: Email³
links to: Email³
enclosure: make what you need⁴
links to: make what you need⁴
enclosure: use what you make⁵
links to: use what you make⁵
enclosure: rename to IndieWeb⁶
links to: rename to IndieWeb⁶
enclosure: jargon⁷
links to: jargon⁷
enclosure: Loqi Nudge⁸
links to: Loqi Nudge⁸
enclosure: Chat Channels Purposes⁹
links to: Chat Channels Purposes⁹
enclosure: t1705883690759800
links to: t1705883690759800
enclosure: devDiscord
links to: devDiscord
enclosure: Discordformat
links to: Discordformat
enclosure: formatHacker
links to: formatHacker
enclosure: Hacker NewsIndieWeb
links to: Hacker NewsIndieWeb
enclosure: IndieWebCampIRC
links to: IndieWebCampIRC
enclosure: IRCjargon
links to: IRCjargon
enclosure: indiewebMatrix
links to: indiewebMatrix
enclosure: Matrixmeta
links to: Matrixmeta
enclosure: protocolReddit
links to: protocolReddit
enclosure: Reddittools
links to: Reddittools
enclosure: toolsSlack
links to: toolsSlack
enclosure: Slacksocial
links to: Slacksocial
enclosure: trolls.html
links to: trolls.html
tagged: concept

indieweb-for-everyone-internet-of-people
date: 2024-01-27T06:09:55-05:00
type: text/html; charset=UTF-8

earthquake-sanfrancisco-shifted
date: 2024-02-04T21:30:22-05:00
type: text/html; charset=UTF-8

IndieWebIndieWebCamp
date: 2024-02-04T21:30:25-05:00
type: text/html; charset=UTF-8

jargonLoqi
date: 2024-02-04T21:30:26-05:00
type: text/html; charset=UTF-8

Loqimain
date: 2024-02-04T21:30:27-05:00
type: text/html; charset=UTF-8

metaMediaWiki
date: 2024-02-04T21:30:29-05:00
type: text/html; charset=UTF-8

Project:Categoriesplumbing
date: 2024-02-04T21:30:30-05:00
type: text/html; charset=UTF-8

plumbingprotocol
date: 2024-02-04T21:30:31-05:00
type: text/html; charset=UTF-8

silos¹
date: 2024-02-04T21:30:33-05:00
type: text/html; charset=UTF-8

Email³
date: 2024-02-04T21:30:34-05:00
type: text/html; charset=UTF-8

make what you need⁴
date: 2024-02-04T21:30:35-05:00
type: text/html; charset=UTF-8

use what you make⁵
date: 2024-02-04T21:30:36-05:00
type: text/html; charset=UTF-8

rename to IndieWeb⁶
date: 2024-02-04T21:30:37-05:00
type: text/html; charset=UTF-8

jargon⁷
date: 2024-02-04T21:30:38-05:00
type: text/html; charset=UTF-8

Loqi Nudge⁸
date: 2024-02-04T21:30:39-05:00
type: text/html; charset=UTF-8

Chat Channels Purposes⁹
date: 2024-02-04T21:30:41-05:00
type: text/html; charset=UTF-8

t1705883690759800
date: 2024-02-04T21:30:43-05:00
type: text/html; charset=utf-8

devDiscord
date: 2024-02-05T00:34:49-05:00
type: text/html; charset=UTF-8

Discordformat
date: 2024-02-05T00:34:50-05:00
type: text/html; charset=UTF-8

formatHacker
date: 2024-02-05T00:34:51-05:00
type: text/html; charset=UTF-8

Hacker NewsIndieWeb
date: 2024-02-05T00:34:52-05:00
type: text/html; charset=UTF-8

IndieWebCampIRC
date: 2024-02-05T00:34:53-05:00
type: text/html; charset=UTF-8

IRCjargon
date: 2024-02-05T00:34:54-05:00
type: text/html; charset=UTF-8

indiewebMatrix
date: 2024-02-05T00:34:55-05:00
type: text/html; charset=UTF-8

Matrixmeta
date: 2024-02-05T00:34:56-05:00
type: text/html; charset=UTF-8

protocolReddit
date: 2024-02-05T00:34:57-05:00
type: text/html; charset=UTF-8

Reddittools
date: 2024-02-05T00:34:58-05:00
type: text/html; charset=UTF-8

toolsSlack
date: 2024-02-05T00:34:59-05:00
type: text/html; charset=UTF-8

Slacksocial
date: 2024-02-05T00:34:59-05:00
type: text/html; charset=UTF-8

trolls.html
date: 2024-02-05T00:35:00-05:00
type: text/html

concept
type: Tag
label: discord

concept
type: Tag
label: hackernews

concept
type: Tag
label: indiewebcamp

concept
type: Tag
label: indiewebdev

concept
type: Tag
label: jargon

concept
type: Tag
label: matrix

gresham-law-developers-users-jargon
type: item
type: MicroblogPost
title: : Similar to @paulgraham.com (@paulg@mas.to @paulg)’s observation about trolls¹, there’s a sort of Gresham's Law of developers (vs users): developers are willing to use a forum with a lot of users in it, but users aren’t willing to use a forum with a lot of developer-speak.Whether such forums are email lists, chat (IRC, #Matrix, #Slack, #Discord), or, well, online forums (#Reddit, #HackerNews), when discussions either start or shift into technical details, jargon, or acronyms, users (in a very broad sense) tend to stop participating, and sometimes leave, never to return.Users in this context are anyone with a desire (or a preference) not to chat or even be bothered spending time reading about technical plumbing & #jargon, and see such discussions as a distraction at best, and more like noise to be avoided.Paraphrasing Paul Graham again: once technical details, jargon, acronyms “take hold, it tends to become the dominant culture” and discourages users from showing up, discussing user-centric topics, or even staying in said forum.The #IndieWeb community started in 2011 as a single IRC channel #indiewebcamp (no email list²) because it was tightly coupled to IndieWebCamp events, which were both highly technical and yet focused on actually making things work on your personal site that you need³, that you will use⁴ yourself. Conversations bridged real world use-cases and technical details.It only took us five years after the first IndieWebCamp in Portland to recognize that the community had grown beyond the events, and had a clear need for a separate place for deep discussions of developer topics.As part of renaming the community from IndieWebCamp to IndieWeb⁵, we created the #indieweb-dev (dev) channel for such technical topics like protocols, formats, tools, coding libraries, APIs, and any other acronyms or jargon.The community did a good job of keeping technical topics in the dev channel, and encouraging new folks in the main #indieweb channel who started technical con…
link: https://status.blaise.ca/notice/116165
description: 's status on Sunday, 04-Feb-2024 18:05:00 EST
encoded: Similar to @paulgraham.com (@paulg@mas.to @paulg)’s observation about trolls¹, there’s a sort of Gresham's Law of developers (vs users): developers are willing to use a forum with a lot of users in it, but users aren’t willing to use a forum with a lot of developer-speak. Whether such forums are email lists, chat (IRC, #Matrix, #Slack, #Discord), or, well, online forums (#Reddit, #HackerNews), when discussions either start or shift into technical details, jargon, or acronyms, users (in a very broad sense) tend to stop participating, and sometimes leave, never to return. Users in this context are anyone with a desire (or a preference) not to chat or even be bothered spending time reading about technical plumbing & #jargon, and see such discussions as a distraction at best, and more like noise to be avoided. Paraphrasing Paul Graham again: once technical details, jargon, acronyms “take hold, it tends to become the dominant culture” and discourages users from showing up, discussing user-centric topics, or even staying in said forum. The #IndieWeb community started in 2011 as a single IRC channel #indiewebcamp (no email list²) because it was tightly coupled to IndieWebCamp events, which were both highly technical and yet focused on actually making things work on your personal site that you need³, that you will use⁴ yourself. Conversations bridged real world use-cases and technical details. It only took us five years after the first IndieWebCamp in Portland to recognize that the community had grown beyond the events, and had a clear need for a separate place for deep discussions of developer topics. As part of renaming the community from IndieWebCamp to IndieWeb⁵, we created the #indieweb-dev (dev) channel for such technical topics like protocols, formats, tools, coding libraries, APIs, and any other acronyms or jargon. The community did a good job of keeping technical topics in the dev channel, and encouraging new folks in the main #indieweb channel who started technica…
date: 2024-02-04T18:05:00-05:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110238
enclosure: indieweb-for-everyone-internet-of-people
links to: indieweb-for-everyone-internet-of-people
enclosure: earthquake-sanfrancisco-shifted
links to: earthquake-sanfrancisco-shifted
enclosure: devformat
links to: devformat
enclosure: formatIndieWeb
links to: formatIndieWeb
enclosure: IndieWebIndieWebCamp
links to: IndieWebIndieWebCamp
enclosure: IndieWebCampjargon
links to: IndieWebCampjargon
enclosure: jargonLoqi
links to: jargonLoqi
enclosure: Loqimain
links to: Loqimain
enclosure: indiewebmeta
links to: indiewebmeta
enclosure: metaMediaWiki
links to: metaMediaWiki
enclosure: Project:Categoriesplumbing
links to: Project:Categoriesplumbing
enclosure: plumbingprotocol
links to: plumbingprotocol
enclosure: protocoltools
links to: protocoltools
enclosure: toolssocial
links to: toolssocial
enclosure: silos¹
links to: silos¹
links to: trolls.html²
enclosure: Email³
links to: Email³
enclosure: make what you need⁴
links to: make what you need⁴
enclosure: use what you make⁵
links to: use what you make⁵
enclosure: rename to IndieWeb⁶
links to: rename to IndieWeb⁶
enclosure: jargon⁷
links to: jargon⁷
enclosure: Loqi Nudge⁸
links to: Loqi Nudge⁸
enclosure: Chat Channels Purposes⁹
links to: Chat Channels Purposes⁹
enclosure: t1705883690759800
links to: t1705883690759800
tagged: concept

devformat
date: 2024-02-04T21:30:22-05:00
type: text/html; charset=UTF-8

formatIndieWeb
date: 2024-02-04T21:30:24-05:00
type: text/html; charset=UTF-8

IndieWebCampjargon
date: 2024-02-04T21:30:26-05:00
type: text/html; charset=UTF-8

indiewebmeta
date: 2024-02-04T21:30:28-05:00
type: text/html; charset=UTF-8

protocoltools
date: 2024-02-04T21:30:32-05:00
type: text/html; charset=UTF-8

toolssocial
date: 2024-02-04T21:30:33-05:00
type: text/html; charset=UTF-8

objectType=comment
type: item
type: MicroblogPost
title: mmn: @tuttle Last weekend I was ready to stay home instead of going to a "fix/remake" workshop (me representing !umehack) because they hadn't setup _any_ communication outside of walled gardens (apart from collecting emails). I had tol https://social.umeahackerspace.se/notice/466309
link: https://status.blaise.ca/notice/85462
description: mmn's status on Tuesday, 19-Apr-2016 04:21:43 EDT
encoded: @tuttle Last weekend I was ready to stay home instead of going to a "fix/remake" workshop (me representing !umehack) because they hadn't setup _any_ communication outside of walled gardens (apart from collecting emails). I had tol…
date: 2016-04-19T04:21:43-04:00
creator: MMN-o ✅⃠
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/85427
enclosure: mmn-20160419-ostatus-8bzp.html
links to: mmn-20160419-ostatus-8bzp.html
tagged: concept

mmn-20160419-ostatus-8bzp.html
date: 2016-09-05T17:07:58-04:00
length: 1860
type: text/html

concept
type: Tag
label: facebook

concept
type: Tag
label: github

cmhobbs: I need to get the house clean but my busted foot is making that difficult. Excuse to #slack, I gues https://loadaverage.org/notice/6947557
type: item
type: MicroblogPost
link: https://status.blaise.ca/notice/57328
description: cmhobbs's status on Monday, 25-May-2015 12:04:09 EDT
encoded: I need to get the house clean but my busted foot is making that difficult. Excuse to #slack, I gues…
date: 2015-05-25T12:04:09-04:00
creator: Christopher M. Hobbs
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/48162
enclosure: cmhobbs-20150525T160425-dqx6m47.html
links to: cmhobbs-20150525T160425-dqx6m47.html
tagged: concept

cmhobbs-20150525T160425-dqx6m47.html
date: 2015-06-25T10:49:15-04:00
length: 389
type: text/html

cmhobbs: On the back porch again, working real hard on the pursuit of #slack for the last few days. Tomorrow its back to life as usual.
type: item
type: MicroblogPost
link: https://status.blaise.ca/notice/31837
description: cmhobbs's status on Sunday, 13-Jul-2014 20:06:11 EDT
encoded: On the back porch again, working real hard on the pursuit of #slack for the last few days. Tomorrow its back to life as usual.
date: 2014-07-13T20:06:11-04:00
creator: cmhobbs
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/26484
tagged: concept

cmhobbs: @speeddefrost Bob is the one true lord, you heretic! When will you cast aside your burdens in pursuit of #slack!?
type: item
type: MicroblogPost
link: https://status.blaise.ca/notice/27375
description: cmhobbs's status on Friday, 23-May-2014 22:28:12 EDT
encoded: @speeddefrost Bob is the one true lord, you heretic! When will you cast aside your burdens in pursuit of #slack!?
date: 2014-05-23T22:28:12-04:00
creator: cmhobbs
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/22723
tagged: concept

mcnalu: @nybill may the #slack be with us all #subgenius
type: item
type: MicroblogPost
link: https://status.blaise.ca/notice/23480
description: mcnalu's status on Friday, 21-Mar-2014 17:18:02 EDT
encoded: @nybill may the #slack be with us all #subgenius
date: 2014-03-21T17:18:02-04:00
creator: Andrew Conway
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/19292
tagged: concept

concept
type: Tag
label: subgenius

Andrew Conway
type: Agent
nick: mcnalu
holds account: acct