squeakytoy2, j12t, glennjones, snarfed, wolftune, davidmead, sparverius, mlncn, halorgium and tantek joined the channel
#tantek.comedited /IRC (+40) "update definition to be more about the channel than abbreviation, use keywords that can be further looked up" (view diff)
#LoqiInternet Relay Chat (abbreviated IRC), in particular the #indiewebcamp channel on the irc.freenode.net server, is the primary community discussion forum for IndieWebCamp and anything about the IndieWeb https://indiewebcamp.com/this_channel_about
#KartikPrabhutantek: shouldn't that question give the description of "what is indieweb" ?
#LoqiThe indieweb is about owning your domain and using it as your primary identity, to publish on your own site (optionally syndicate elsewhere), and ownyourdata https://indiewebcamp.com/indieweb
#tantekKartikPrabhu: nah, the channel is about both IndieWebCamp and IndieWeb
#GWGI've just tried to submit a patch to WordPress to add optional Microformats2 support. I'm predicting silence.
#tantekGWG, do you have an overall strategy for doing microformats2 support in WordPress *better* thatn what they did with classic microformats?
#tanteke.g. currently their support of classic microformats is split across core and themes, and as you know that has made it a major pain to make things work, fix things etc.
#GWGtantek: My plan involves fixing two elements to start
#tantekreally interesting how much more "attention" a Bridgy Publish FB POSSEd post (long note) gets as compared to a Twitter->FB POSSEd post.
#tantekGWG, indeed - such fundamental architecture questions are difficult to resolve in purely electronic communications
#GWGtantek: I'm learning though. I don't know if I'll ever get to the point where I can make such big changes. Working on little ones. One of my tickets just got, after some heavy modifications and review, committed for the next release of WordPress. It was one I opened based on my issues with getting useful notifications out of WordPress for webmentions.
#Loqirhiaro: tantek left you a message 2 days, 7 hours ago: in particular, the questions/issues you're running into are *very* key only-real-world-observable issues that are essential to the empirical methods we use in #indiewebcamp (and #microformats) in contrast to the more philosophically wishful methods of attempting to pre-define everything a priori that some other efforts attempt (and fail to touch on real world problems). http://indiewebcamp.com/irc/2015-09-11/line/1442025844957
#Zegnattantek: is there some way to have MediaWiki auto-populate those pages?
#tanteknot in any way that would decrease work. that is, then you introduce the maintenance task of whatever auto-population mechanism you come up with.
thehighfiveghost joined the channel
#tantekand currently HWC events are iterating/evolving sufficiently quickly, in content, structure, presentation, that it would be more work to attempt to update those aspects in an auto-population mechanism, than to "just" update them upon manual copy/paste
#tanteksuch premature automation can result in both more work and less reliability as a result
#tantekalso - such maintenance typically decreases the buscount (# of people that can do the maintenance) as compared to copy/paste, thus introducing a community bottleneck
#rhiarotantek: from 1st Oct tbrb will be in charge of HWC Edinburgh
#rhiarois pretty sure tbrb agreed to this at some point
#rhiaroWell, I said it in IRC now so it must be true
#rhiaroMaybe we could scout space downstairs in Potterow at that time, see if it's fairly empty, there's power and wifi
#ZegnatHmm, this thursday is also the 25th First Annual Ig Nobel Prize Ceremony, maybe someone wants to incorporate that into their HWC activities? Probably only relevant for US timezone ones. Possibly Edinburgh also, where they do HWC for 10 hours straight.
#ZegnatHmm, I hoped <code> would make it so that URL would not be auto-linked by mediawiki, but it still was. Is there any way to have the wiki not auto-link a URL?
#tantekand they call blog posts "stories", i.e. from medium.com/xoxo : About / XOXO 2015 / Stories from the intersection of independent art and technology, and the challenges that come from it.
#aaronpkthe Slack account for the conference was amazing. looks like someone is going to be doing an article about it so I'll add the link to it once it's published
#tantekyes - that's perhaps the biggest part that I felt FOMO about
#aaronpklots of fascinating behavior emerged from it, and really demonstrated a new way of interacting with people in the context of the event
shiflett_, stream7, shiflett and lewisnyman joined the channel
#voxpelliaaronpk: replicating that style through "u-category" linking to the publication maybe? or thinking of adding publications to Indienews?
#aaronpkthinking indienews would be the "publication", so it would just be a different view of the articles instead of the time-ordered list
#voxpelliah, you were thinking presentation rather than how to publish to it
#Zegnattantek: "nobody will actually access your pictures randomly" <-- this is false - search engines may still index them if someone direct links to them from HTML (from #indiechat) --- yes, but such is the nature of sharing, if I share an unlisted blog post with you, of course you can share it further. These URLs are not replacements for passwords, neither are they meant to be one-time-use. Unguessable URLs are meant to stay available, like we
#[snarfed]interesting too, kylewm's project is js, client side only. (?) smart!
#voxpelli[snarfed]: embed with JS? because server side code looks like python
#Zegnathttp://www.w3.org/TR/capability-urls/ (as linked by rhiaro in #indiechat) also lists some examples of unguessable URLs, though it seems to be more aimed at URLs to replace passwords and possibly only be temporary, while unguessable URLs like from Google are meant like real URLs, a fixed location for a resource that is meant to be shared.
#ZegnatShared, but not been able to automatically collect or guess
#snarfedfwiw unguessable URLs are fairly common. we use them in my day job (as one layer of security), we take security very seriously since we handle health data, and we're ok with them
#snarfedthey scare people since they're URLs, but yes, same in reality
KartikPrabhu joined the channel
#ZegnatThe way I see unguessable URLs they aren’t meant to ever be time-limited. And they are revokable only by removing whatever they point to. That’s how GitHub secret gists work, and Google photos
#tantekseems like "scary" might be a feature for unguessable URLs - because you want to discourage sharing and clicking by others
#tantekdoes anyone here segment their photos into "in-stream / fully public" and "unlisted" or "private" on their own site? and if so, how/what are you doing? with what UI/project?
#snarfedeven just whether to include photos (or any posts) in front page stream/feeds or not is a surprisingly useful distinction
#ZegnatThe unguessable part I am interested in stems from /YYYY/DDD/N/ becoming guessable. I can just try every N between 0 and 100 to find the ones you didn’t put publicly in the feed. So you need some other and unpredictable way to link to them
#aaronpkZegnat: no they are protected by indieauth
#tanteksnarfed - indeed the "recent interest" was a combination of KevinMarks actually documenting /publics on the wiki, and a side-effect of me starting to post *some* /photo posts on my own site!
#voxpelliI neither publish repliesm notes and such on my front page – but it's all discoverable
#Zegnatsnarfed: http://werd.io/2015/publish-on-your-own-site-reflect-inwardly#comments is really interesting, but I sometimes write posts that are meant to spread in a word-of-mouth fashion within certain circles without people or searchengines accidentally discovering them. But of course that is just my specific use-case.
tantek joined the channel
#tantekrealizing that I had feelings of greater comfort with some photos being posted "just" to Instagram rather than putting them all on my homepage, despite not feeling any discomfort with posting all my replies/RSVps to my home page
#tantekZegnat - it's a mix of the medium, and the apparent specific audience I seem to have acquired on IG
#tantekI'm still reflecting on it to gain further insights, but there's definitely some interesting emotional design aspects at play there that are worthy of greater understanding / documentation.
tvn joined the channel
#tantek.comedited /publics (+376) "/* IndieWeb Thoughts */ benwerd's thoughts and post, via snarfed" (view diff)
#voxpelliI have a general feeling of lesser comfort in posting stuff now that social media is so common and the smaller early adopter communities have vanished. In there I knew people much better, now it's much more anonymous and public
#tanteksince he was the only person that used the term on benwerd's blog post, I'll wait for him to return to define it.
#tantekironic that the last "comment" on benwerd's post is rhiaro "resharing" it - which of course potentially greatly expands the "public" of that post, especially if rhiaro POSSEs her repost!
shiflett joined the channel
#voxpellinot sure monoculture-like echo chambers are always a bad thing – sometimes its needed for some ideas to evolve – as long as one is not confined to only a few monocultures it can probably be somewhat healthy
#tantekvoxpelli: as long as it is ephemeral it can be very useful. it's the long-term monoculture inertia that's particularly bad
#aaronpkI wouldn't be so quick to call them a bad thing either. I've been a member of some private facebook groups which have been extremely helpful. They are private for various reasons.
#tantekok that's a fair / different characterization
#tallpaulre Facebook, since I have a child one thing I have noticed a lot recently is the pre-photo conversation establishing what the different participants are comfortable with in terms of where and how stuff gets posted/tagged, defining an acceptable consensus/who to includes
#tallpaulits a limited but quite sophisticated understanding of publics
#Zegnat[kevinmarks]: unguessable indeed, 72 characters is a huge pool, probably way more than is needed. My unguessable post links are going to be shorter. Thinking more like 30 chars at most
#aaronpkif I did my math right, 10 newbase60 chars is equivalent to 128 bits which should be plenty
#[kevinmarks]well, they're not random; snarfed knows how to decode them into database keys
#[kevinmarks]hm, voxpelli, is it possible to delete webmentions?
#[kevinmarks]I have some nasty ones from twitter on my xoxofest posts
#Zegnataaronpk: I’ll be running the numbers tomorrow to see how long I really need it to be if I post 10 things per day for 50 years and still want to guarantee only a 1 in 10^x chance of someone guessing an ID
#kylewmthat sounds like a lot more fun than what snarfed's doing
#[kevinmarks]Kartik, as I am lazy and delegate that part to webmention.herokuapp.com, it's more question fo who I get to add features to their service, kyle or voxpelli
#kylewmwell this is confusing "Snowflake is a service we will be using to generate unique Tweet IDs"
#kylewmwould bridgy also need to send 410's for people who are blocked some time after a response is backfed?
#kylewmis surprised to have almost 1400 people blocked
#[kevinmarks]I assume so - if I block that dude with the hitler avatar now, It would be good if it removed his comment
#[kevinmarks]though that means being sure voxpelli updates too
#[kevinmarks]so both services end up needing tombstone records