#aaronpkonce I set it up to be able to log essentially arbitrary IRC channels it would be able to publish any channel on freenode
#aaronpkso yes the work I need to do to make this work with other IndieWeb channels also makes it work for any channel
#gRegorLoveWould Loqi's other functionality be limited to #indieweb* channels?
#aaronpkI'm separately rebuilding Loqi and will be able to make him join other channels easier as well as selectively enable various Loqi features per channel
#aaronpkit seems weird to publish non IndieWeb channels under IndieWeb.org
#tantekit feels like a bridgy like resource in that regard though
#tantekespecially if/when the logs start sending/accepting webmentions
#tantekif the logs showed /reacji then that would be another feature-parity thing with Slack ;)
#tantekpublishing a subdomain like that then turns into "a tool incubated at/by indieweb community" rather than just "a tool of the indieweb community"
#tantekthat starts to bring the subdomain semantic closer to e.g. news.ycombinator
#tantekbesides, just going to point out that there's clearly an opportunity here to provide a general open web resource ("brought to you by the IndieWeb community") to replace the krijn IRC archives which used to be essential for #whatwg etc.
#tantekand someone adding fuel to the subdomain fire as it were - since those are all reasons to potentially prefer a subdomain over just a subdirectory (opposite to my current vote)
#Loqitantek meant to say: and somewhat adding fuel to the subdomain fire as it were - since those are all reasons to potentially prefer a subdomain over just a subdirectory (opposite to my current vote)
#bearwiring up other chat protocols becomes a translation layer
#aaronpkThe only redeeming quality IRC has is that it's a relatively standard protocol so there are at least multiple clients you can use to connect to a server like freenode
#tantek.comedited /rename_to_IndieWeb (+984) "/* docs subdomain */ agree with some/most of shaners, bnvk problem statements about content/design, but 100% disagreed with the illogical leap to subdomain/plumbing changes both because they don't help, will distract from solving actual problems" (view diff)
#tantek.comedited /rename_to_IndieWeb (+642) "/* chat subdomain */ subdomains hurt branding, noting examples of big orgs that launched without or ditched subdomains deliberately, "uniform header bar" needs real world examples" (view diff)
#ben_thatmustbemetantek: you really should comment on others votes, not up/down vote others votes
#tantek.comedited /rename_to_IndieWeb (+93) "/* chat subdirectory */ simplified/focused reasoning, plus noted subdomain considerations with brainstorming beyond IndieWeb community (i.e. if "chat" were to grow to become an open web resource in general, like how we archive socialwg logs)" (view diff)
#tantekben_thatmustbeme: the up/down is on the reasoning, not the vote
#tantekalso, not sure where this started getting called "votes" - the intent - as with /Planning, has been about *polling*
#tantekto gather opinions, and resolve differences in opinion
#tantekwe had an initial "vote" *only* for should we rename indiewebcamp.com to indieweb.org at all, which was a unanimous proposal put forward from IndieWeb Leaders Summit
#tantekeverything else should have been explicitly labeled a poll
#tantekwe had a simple plan from the leaders summit, and then sorry to say but all the subdomain stuff went way overboard afterwards
#ben_thatmustbemestill if many people +1 to something and you -1 a response to everyone it give it the appearance of a lot of conflict, whereas keeping the +/- 1/0 to the main level keeps things clear
#tantekbetter to document conflict / dissent than not
#tantek.comedited /rename_to_IndieWeb (+121) "/* Brainstorming */ clarify this section is gathering opinions, not voting, since these are all evolving brainstorms with multiple options, more/better options encouraged (per brainstorming)" (view diff)
#bearI don't feel comfortable with "simple plan from the leaders summit" and "illogical leap to subdomain/plumbing changes" as it is telling me that my experience with plumbing is making the "simple plan" complicated just by expressing the opinion
#tantekben_thatmustbeme: I'll try to reduce redundant text, agreed that's not helpful.
#bearit also implies (which I admit may be a misreading) that simply because the plan was simple and drawn up by the leadership summit, that it shouldn't be weighed down by feature creep
#tantekchecks to see if he wrote illogical on that page
#bearit's from the change message "# 02:08 tantek.com edited /rename_to_IndieWeb (+984) "/* docs subdomain */ agree with some/most of shaners, bnvk problem statements about content/design, but 100% disagreed with the illogical leap to subdomain/plumbing changes both because they don't help, will distract from solving actual problems" "
#tantekbear, do you have a better suggestion for how to move forward when there are parts that have agreeemnt, and parts that do not? Especially when such parts are separable / capable of being done asynchronously or iteratively over time?
#bearthe discussion happening now is what I thought was the plan - to gather ideas, discuss and reach consensus
#bear"illogical leap" and "simple plan" all carry overtones that imply we shouldn't bother with discussing things as they have been already been discussed and given
#tantekpoint being, when there are parts that have rough consensus and can proceed forward, there's no need (in fact it is bad to) tie them to optional incremental parts which do not have rough consensus
#tanteksuch tying tends to doom the ability to take simple forward steps
#bear1) I have no idea what that even is and 2) your making assumptions on what I am saying and thinking
#tantekbear, no I'm merely explaining my arguments I captured on that page
#tantekabout "improve content" having nothing to do with "change subdomain / plumbing"
#tantekwhich the proposals sound(ed) like they were asking for. e.g. the jekyll proposal
#tantekthis is not about what you are saying / thinking, but what is proposed in those brainstorms
#bearthe one thing i'm taking away from this whole conversation across the last couple of days is that the set of items that need to be done and the discussion about them has been haphazard and not directed
#ben_thatmustbemetantek: side note, any points of why microformats.org uses /wiki ? just because that was how it was done at the time and not really thought out?
#bearbecause I keep trying to talk about certain specific points and keep getting swept up in a general discussion about the plan as a whole
#tantekbear, yeah, have seen that happen more often than not in "group" projects, too easy for feature creep because it's easier to "want" something from a group effort than to make it happen
#bearthat page needs to go away and get broken down into a list of problems and then start iterating on each one as an item
#tantekhence my attempt to separate into *a* simple step, and additional async brainstorming items
#tantekbear, it was like that until all the subdomain stuff got added. then I tried to separate those at least into brainstorming vs. critical path
#bearI don't think that was a clear as that - "all the subdomain stuff" is an alternative way of implementing what the solution to the given problem is
#bearwe have a bunch of issues, some have concise solutions but a handful have multiple solutions
#bearone change I would welcome is to remove implementation details, which includes subdomain or not, from the discussion and make sure we are focusing on what the issue is
#Loqibear meant to say: one change I would welcome is to remove implementation details, which includes subdomain , from the discussion and make sure we are focusing on what the issue is
#tantekbear, agreed on focusing on / documenting issues first
#tantekthat's kinda how all this debate started on Monday - I asked for documentation of the issues / use-cases first
#tantekrather than the leap to all the subdomain proposals which got landed in one big edit
#tantekI think I've already had that discussion with aaronpk though and I think we're good there
#beara lot of what people are reacting to is that the framing of the discussion was not clear and multiple threads were attempted to be settled by the brainstorming section
#tantekbear, I think I agree with you more than not
#tantekand frankly, those aspects (methodology of documenting issues first, and only second offering possible *solutions* (plural)) concern me much more than any particular problem or solution
#bearthis is one area where consensus building by mailing list works better (pains me to say) - because you can follow the thread of changing opinions
#tanteksorry to disagree with that because I've almost never found that to be true in email
#tantekas replies to replies build up and you can't tell what got agreed to and dropped vs. what is still being debated
#tantekat least with the wiki we have a *chance* of capturing / collecting / documenting points of agreement
#bearwell, i've been fortunate to have had small groups to work with and haven't run into that
#tantekwhereas with email threads, the only things that keep going are the points of *disagreement*
#tantekit's like the exact opposite of what you want to maintain
#bearyea, that's where you need a good lead to step in and declare consensus
#bearthe other item I have concern with is I don't know what is already being implemented and what the consensus was that allowed it to be started
#tantekbear, trying hard to not be (too?) dependent on any particular "lead"
#tantekthat too is a type of bottleneck / bus factor, even if socially / culturally
#bearsure, that is something to worry about if it's always the same lead, but guess what - the implementations have always been the same leads
#tantek.comedited /rename_to_IndieWeb (+683) "expand my opninion, focused on agreements with others' problem statements, and offering of different reasoning as a summary/pointer instead of inline" (view diff)
#tantekbear, even if the implementations have always been the same leads, that's not a justification with further burdening them with that responsibility / expectation
#bearsome of the discussion is about the why and what of new core features
#tantekwhen we discussed this at the leaders summit, the only *new* *potential* feature we discussed was 'events.' and we also recognized that wasn't built, and was not something we should do for July 4
#bearand i'm trying (badly I know but i'm also very tired and have had to deal with things about my dad) to get across some of the vibe i've gotten from conversations i've seen
#tantekall other feature creep happened later, in a much smaller private group
#tantekwhich is why I gave such pushback against that
#bearthat last item is now making me aware that we are sensing the same vibe
#tantekright, hence the preference to see issue documented first
#Loqitantek meant to say: right, hence the preference to see issues documented first
#bearcool - sorry, I was taking a long and slow path to the point because I didn't want to come across as confrontational or get emotionally involved in the point
#bear(and your much better and smarter at these conversations so it was taking me more time to find the words)
#tantekbear, all good, and no, not better/smarter, just in a different timezone
#bearbut lets see what the very smart community we have can do over the weekend with our feedback
#tantekhonestly some of the particular (e.g. chat. subdomain) I'd consider much more / be more potentially positive about, if they were clearly separated from the domain name change
#bearthanks for letting me work my way along the path at my own pace (another reason why I like this community)
#tanteklike we're going to have to redirect indiewebcamp.com/irc/ URLs *anyway*, so having to also eventually redirect indieweb.org/irc/ URLs is not a big enough deal to justify a whole new project
#bearmy only concern is that all of what your saying applies to the human indieweb - APIs may still have a place for some of the service plumbing but we should resist implementing them until we show that it can't be handled by mf2 markup
#bearI would suggest some variation of "Use the existing mf2 markup your website already contains as your API. Remember that we should always be human first and application second."
#tantek!tell ben_thatmustbeme re: "any points of why microformats.org uses /wiki ? just because that was how it was done at the time and not really thought out?" Because at the time it seemed to make sense to have a home page blog, a few static top level pages, and then the wiki only for research, proposals, brainstorms, specs, etc. And over time we (founders + active community) discovered that was a mistake, static pages were neglected
#tantekwiki was latest / out-improved them. Ease of editing > "pretty".
#tantek!tell ben_thatmustbeme wiki was latest / out-improved both the blog and the prettier "few static top level pages" . Turned out ease of editing > "pretty / friendly pages" which were more about people having time to do text+graphics than URL/backend choices.
#tantek!tell bnvk re: onboarding, we have /Getting_Started but that's about getting started with your own site. Do you mean onboarding into the community? Hopefully that's minimal work, but the important parts are in /wikifying - feel free to ask Qs to help with that.
#aaronpki realize that jumping to the conclusion that subdomains for everything as the solution was not the best approach
#tantekand in that case, then we should move it to another page
#aaronpki also agree with ben_thatmustbeme that regardless of whether you call this "polling" or "voting", it *looks* like voting and so everything looks more adversarial than it should
#aaronpkand -1'ing someones vote/opinion looks like an attack on them personally, rather than expressing your opinion in relation to the proposal
#Loqi[tantek] like we're going to have to redirect indiewebcamp.com/irc/ URLs *anyway*, so having to also eventually redirect indieweb.org/irc/ URLs is not a big enough deal to justify a whole new project...
#aaronpkand "whole new project" is an exaggeration, since what's really going to happen is i'm going to end up modifying the existing logs until it works with multiple channels
#aaronpkreviewing http://indiewebcamp.com/rename_to_IndieWeb ... the only thing there that 1) wasn't previously discussed AND 2) is not something we have to decide before the july 4 move is the docs subdomain.
#tantekbut perhaps we should generalize that to "site improvements" or something.
#tantekBTW this kind of polling (with updates and current state *and* contextual documentation) is something that a wiki page does better than a GH issue
#tantekaaronpk - crazy suggestion: what if we scaled back the multiple channels switch for July 4? and only switch #indiewebcamp -> #indieweb on that day?
#aaronpkwell that wasn't what we all agreed to so we'd need to poll everyone ;-)
#tantekthat buys us time to get the (/)chat(.) stuff more correct (or at least more consensus) figured out
#tantekcutting stuff is less controversial than adding
#tantekbesides, there's nothing stopping from *logging* those channels like *today*
#aaronparecki.comedited /rename_to_IndieWeb (+2) ""flip the switch" does not accurately reflect the work required to make the change, and makes it sound easier than it actually is" (view diff)
#tanteknow I see how a "must fix this to ship" issue became a "hey this is a better overall solution" change/update to the plan which allowed consideration of "new" features as well
#tantekit is starting to make more sense how it happened.
#tantekinteresting "product" launch trade-offs thinking/discussion, when an issue suggests more development, sometimes scaling back the scope can be better
#aaronparecki.comedited /indieweb.org (+4612) "move docs subdomain section to this page since it is a new proposal and not required as part of renaming indiewebcamp.com to indieweb.org" (view diff)
#aaronpkthe "brainstorming" header on /rename_to_IndieWeb is not intended to be future brainstorming, it is intended to be implementation details of the rename
#aaronpknow that docs subdomain is out of there does that make more sense?
#tantekI labeled / moved everything to that "Brainstorming" header that did not seem essential for July 4
#aaronpkif we launch new chat rooms on july 4 then the chat logs section is essential
#aaronpknews.indiewebcamp.com is not technically essential since it can stay there while everything else moves, but from a branding perspective it is connected to the move
#tantekright, might be good to start separating "essential" from "good to have"
#tantekand obviously stuff like "events." is full on "future stuff not built"
#aaronpkthat's why events is not on the rename page
#aaronpkthe name "offtopic" was brought up after summit, but iirc we didn't come to a conclusion on what the name of that channel would be during summit
#tantekdespite the silo-pref, I suggest "indieweb-random", following Slack naming conventions, may be *more* friendly to non-devs / and further Generations 2+ etc. since they are more likely to have used Slack than IRC. instead of indieweb-offtopic
#aaronpkslack's default channels are "#general" and "#random", but i've seen people rename "#random" to "#offtopic"
#tantekaaronpk: we did. during summit we had a full set
#Loqibnvk: tantek left you a message 2 hours, 53 minutes ago: re: onboarding, we have /Getting_Started but that's about getting started with your own site. Do you mean onboarding into the community? Hopefully that's minimal work, but the important parts are in /wikifying - feel free to ask Qs to help with that. http://indiewebcamp.com/irc/2016-06-25/line/1466866100263
#tantek.comedited /rename_to_IndieWeb (+1211) "/* new name for off topic channel */ offering another alternative, "indieweb-random" based on Slack default, and small data sampling, 50% of teams seem to have random, more than any other option, and zero have "offtopic"" (view diff)
#tantekbnvk np, glad to have you back here and re-engaging!
#tantekI remember saying it once by accident in an IWC and seeing people's faces give that quizzical huh? what did you mean? look
#tantekand realizing that oops, that's a W3C jargon phrase
#tantekand all such jargon phrases are more likely than not inessential weirdnesses
#aaronpki have no record of you saying that in my irc logs
#tantekhmm - that reminds me, I need to suggest somewhere some way to build our own backend flat search for the logs. Google's indexing has gotten really incomplete
#Loqi[tantek] ben_thatmustbeme: re: "maybe we should have just an indiewebcampofftopic room", perhaps #indiechat?
terminalpixel and [kevinmarks] joined the channel
#[kevinmarks]You do use off topic and on topic to racoon people into different channels
#tantekaaronpk yes yes ;) I'm *trying* to be more "next generations" empathetic here with the "random" proposal. I know "off topic" is a comfort zone for me :P
#bearrandom always annoys me when I find it on a slack community - but I get why it's helpful if other channels are supposed to be rigid about the topic
[kylewm] joined the channel
#[kylewm]agree it’s a good idea to ask people in person … “random” feels very 90s valley (the other valley)
#[kylewm](in line with all of Slack’s copywriting)
#bearhmm, I should get food before settling in to a day of brainstorming/documenting chat ideas
#voxpelliRegarding Slack's #random, it's a bit different in Slack because it has an additional level that IRC doesn't – you have the Slack itself and then different topic channels within Slack, so everything can be on topic somewhere
#voxpelli#random is often seen as #watercooler, but sometimes also as just everything not #general
#voxpelliunderstands he should actually write that in the wiki instead, but too tired for that at the moment
#aaronpkyes the default channels you get with a new slack instance are "#general" and "#random"
#gRegorLoveAh. I must have removed #random on ours.
#aaronpkit's also important to note that design decisions made by Slack should not necessarily be given a lot of weight because Slack was designed for communication within a company, and explicitly not for public/community chat
#aaronpklooking at behaviours that have emerged in public/community slacks is valuable though
#tantekaaronpk, perhaps you can make some suggestions / provide some data based on XOXO's use of slack
wolftune, KevinMarks__, KevinMarks and [shurcool] joined the channel
#[shurcool]The 29th is only a few days away, I'm excited \o/
#bearmy suggestion for default chat rooms would be to pick the smallest set that solves the immediate need- indieweb-chat indieweb-dev indieweb-offtopic (because they are what terms we use now) and then see what the rate of conversations are in each and put in the topic a feedback link
#bearthen we go for 3 months and look at the result; iterate
#bearmy worry about comparisons to xoxo (tho it is a great community I hear) is that it's general community and not a focused one like ours
#[chrisaldrich]I'm putting together a potential IndieWeb intro session for WordCamp Los Angeles as an overview (particularly in anticipation of IndieWebCamp in LA in November). Does anyone have a suggestion for a catchy (maybe even linkbaity) title?
#[chrisaldrich]I've got a pretty good idea of what to cover, but any pointers from others who've done similar spiels is welcome.
#[chrisaldrich]thanks bear, yeah, I've seen that and a bevy of youtube videos... Ideally I'd like to recruit gen1 users, but want to be welcoming of gen2 and 3 who will certainly be there in spades.
#beardo you know what the solution set for gen1 is and what it would be for gen2+ ? knowing what topics are unique to them and then riffing off of those items would be a good starting point
#bearfor gen2 I always imagine that we need to target the desire to have one place to post that doesn't change every time a new fangled app arrives
snarfed joined the channel
#[chrisaldrich]They're doing 35min of presentation with 10 min for Q&A, so it'll have to be a relatively quick intro; the goal is to infect as large an audience with the overall concept with the anticipation that those interested will join us a week/month later for the IndieWebCamp in LA/Santa Monica
#[chrisaldrich]I'm a biomedical engineer with a background in microbiology, so I always think infect first, but inspire is probably the better word -- thanks aaronpk!
#[chrisaldrich]bear: I think your intuition on having one place to post (plus the added value of owning all your own data) is certainly one of the most valuable pieces for gen2
#bearwhat are the hot-button items associated with that is what I am thinking of now - privacy, tracking, ads, malware...
#[chrisaldrich]I've lately been thinking about the marketing community, for whom owning data is/could be a much larger value. Many apps and platforms are geared toward syndicating content, why shouldn't it be built into one's platform de novo?
#[chrisaldrich]Kevin, I know you've been at it for a while, but how is it you have a blogpost on almost any topic worth thinking about? :wink:
#[chrisaldrich]Though on first blush reading the first, I find it interesting to think that Twitter's API program was "self-innoculated" which seemed to have heavily slowed their growth...
#bear.imedited /chat (+810) "/* Brainstorming */ first draft of a possible flow" (view diff)
#aaronpkspeaking of jumping ahead to implementation, i'm realizing a lot of the work i've done so far in rebuilding Loqi has been without a clear design in mind, so... back to the drawing board as it were
#snarfedsent a couple PRs for the wordpress webmention and semantic linkbacks plugins just now
#bear.imedited /chat (-140) "edits and text moves between high level categories" (view diff)
wolftune joined the channel
#ben_thatmustbemeaaronpk: re: the indiewebcampofftopic, it was the idea of a logged off-topic chat, it was all happening at an IWC, seemed to be missed by tantek at the time
#Loqiben_thatmustbeme: tantek left you a message 7 hours, 56 minutes ago: re: "any points of why microformats.org uses /wiki ? just because that was how it was done at the time and not really thought out?" Because at the time it seemed to make sense to have a home page blog, a few static top level pages, and then the wiki only for research, proposals, brainstorms, specs, etc. And over time we (founders + active community) discovered that was a mistake, static pages were neglected http://indiewebcamp.com/irc/2016-06-25/line/1466864933808
#Loqiben_thatmustbeme: tantek left you a message 7 hours, 55 minutes ago: wiki was latest / out-improved both the blog and the prettier "few static top level pages" . Turned out ease of editing > "pretty / friendly pages" which were more about people having time to do text+graphics than URL/backend choices. http://indiewebcamp.com/irc/2016-06-25/line/1466865009116
#bearand it's nothing but a series of producers and consumers
#bearwith logging and presentation just a specialized consumer
#bearv1 was all xml; v2 json; v3 I am going to use as a test bed for all of this and use mf2 marked up html with json caches
#sknebelwhat is the important difference between "chat-interface" and "traditional" readers for you? more compact presentation? different notion of read/unread (read as soon as you've seen the headline, not on interaction?)
#bearfor me it really boils down to decades of seeing data flow across a terminal
#bearmy whole habit is wired towards being able to process that
#aaronpkfor me, one aspect that differs from traditional readers is that i segment my chat channels by topic rather than by source
#bearyea, I have a filter that allows me to have a "important" channel and it puts different items into it based on who or where the item comes from
#sknebelthat sounds like something a traditional reader-like system could implement as well, it's just easier to DIY/script in chat tools you are used to hacking on?
#bearoh sure, I imagine someone else would do a much better version of this
#bearI just have xmpp tools in python that let me add features quickly
#bearit's all this feature-rich content that has made me want to change
#aaronpksknebel: yeah sure but for whatever reason, none have
#sknebelfor me a big issue is selecting what I want to pay attention to. right now I basically go through the headlines, "star" what I'd like to read, then mark everything as read, which is kinda kludgy. (using inoreader, which is fairly google-reader-ish in its UI)
#bear.imedited /chat (+3120) "/* dragons lurk below */ add irc conversation about two reactions to the page so far" (view diff)
#bearsknebel - part of that is why I am trying to use as much of mf2 as I can - because star'ing and replys and the like will all come along for the ride
#sknebelis the key point for you and aaronpk is that you want it to be more like a stream, less like an e-mail UI (which IMHO forces you to have some kind of interaction with everything)? Does that make sense?
#aaronpki guess that's what I mean by "chat UI" style?
#bearI am trying to see if I can use h-feed default category as a channel definition
#aaronpkah, tagging the feed at the source is interesting
#aaronpkthat's *almost* like how i want it to work
#bearoh, that does make things simpler - just have an h-feed and let the *consumer* decide what tags to use
#aaronpkbear: the reason i think they're different is that if you look at the posts on my site with categories (tags), it's very likely i will want some of those to be pushed to different "chat rooms" based on things other than the values of the categories
#bearthen it is a syndication choice regardless of tag/category of the note
#aaronpki actually recently added "#indiewebcamp on freenode" as a syndication destination in my site, so I can click that in Quill and it'll post in IRC as me
#KevinMarks_right, that is one of my key things - no unread counts needed
#aaronpkthinks about what it means to syndicate a post to IRC that includes a photo
#aaronpkThis post looks out of context on my site, but it's syndicated to #indiewebcamp on Freenode because I clicked that button in my posting interface.
#Loqi[Aaron Parecki] This post looks out of context on my site, but it's syndicated to #indiewebcamp on Freenode because I clicked that button in my posting interface....
#bearmy thinking on posts losing context would be to handle it like loqi does now - try and see what mf2 helper data is available and construct an IRC message that makes sense -- url's, see-also's and other items
#KevinMarks_sknebel - whta yOU call a strema i call a flow it doesn't present an unread count of messages, just a list of recent ones, so you don't have email's inbox problem - the implicit pressure to turn bold things plain and get that unread number down. Instead, you can dip in and out of it, when you have time, and what you see is notes from people you care about."
#KevinMarks_hm, Pubsubhubbub sounds more suited for the chat case than webmention
#aaronpkusing pubsub for it would imply that the "chat server" would be subscribing to a feed of yours. whereas webmention implies that you push to the server each message
#sknebel(I'm somehow imagining a bunch of xLoqis in a chatroom somewhere "quick, somebody in #indiewebcamp asked what X is!" "X is ...", everybody with a different sub-skillset)