#j12tSo I am waiting in the Mozilla lobby in Mountain View today, and I idly gaze over their monitor installation there, and aaronpk's and tantek's names run by. Did not expect that. May have been from the IndieWebCamp Berlin @ Mozilla feed or so.
#sknebelMicro.blog takes care of the Microblog parts quite well and hopefully requires little to no maintenance, while at the same time keeping the longform blog on WP means using the already set up, familiar solution there
[chrisaldrich] joined the channel
#[chrisaldrich]tantek, perhaps I'm missing some context, but what is the need for [sdepolo] to want to move from a self-hosted wordpress solution to micro.blog? It's probably easier for her to continue publishing on her site and syndicate into micro.blog and participate that way.
#[tantek][chrisaldrich] as above, more moving parts to maintain.
#[tantek]The need is illustrated by the fact that adding more indieweb functionality is just harder (more steps, easier to get wrong) in WordPress than in micro.blog, the specific example above is setting up Aperture.
#[tantek]Thus for someone who is primarily looking to replace their social media usage with indieweb usage on their own domain, that use-case is currently better (fewer setup steps, less maintenance over time) solved with micro.blog
#jackydoes [sdepolo] identity as a gen4/gen3 user?
#[chrisaldrich]Given where things are some of that is true, but simultaneously a lot of the maintenance bar has been coming down over time (with respect to WordPress), and possibly with a WordPress microsub server on it's way shortly....
#[tantek]jacky, it's not clear the gen4/gen3 categorizations are that helpful any more - we've had discussions about this at the Summit and since
#[tantek]If OTOH for example you're looking to do cutting edge indieweb experiments like new post types, then WordPress allows you the most power, flexibility, experimentation (short of DIY)
#jackyohh (at the portland summit or a more recent one)
#[tantek][chrisaldrich] yes the maintenance tax of WordPress has been reduced over time, and that's great progress. It's still more than setting up / maintaining micro.blog
#[tantek]we can re-evaluate when said WordPress microsub server is available for setup
#[tantek][chrisaldrich] I think it's important to get a setup that works for you personally first, then have something that you can use to illuminate any self-hosting for day job etc. second.
#[chrisaldrich]I also suspect that [sdepolo] may want to keep her day job in mind with respect to the calculus of self-hosting, though the draw to less maintenance can certainly be a siren song.
#[tantek]What's clear is that [sdepolo] has tried repeatedly to use her WordPress instead of social media but, her words, keeps *checking* social media - that directly implies a need for an indieweb social reader to replace that, hence Aperture, hence where we ended up in our discussion.
#[tantek]something you can use today > coming soon > nothing > handwaving on email (an actual negative time suck)
#[tantek]the only possible exception to that is if you are building you're own coming soon that will satisfy your needs better than the things you can use today
#aaronpki fall into the "coming soon" trap for things I am even planning on building myself lol
#[chrisaldrich]Given the issues with import/export versus the trap of coming soon, my personal strategy would probably be to try out paid micro.blog to see if it actually suits my needs and then deal with importing data later.
#[chrisaldrich]That pesky import/export piece is a major barrier for many people. Attempting the import/export first to find the solution doesn't work at all can be an even deadlier trap.
#[tantek]aaronpk, fortunately when it's personal, those "traps" are just the side-effect of prioritizing more important things, not actually letting anyone down
#GWGAnd even I can be critical of it sometimes, but I like it
[sdepolo] joined the channel
#[sdepolo]Thanks [chrisaldrich] and [tantek] I’ll get on aperture after checking out micro.blog that I just signed up for. To do self hosted micro blog I think I need another domain if I wanna keep wp at my main .com for now, right? Maybe I Can use a sub domain like micro.staceydepolo.com?
[tantek], stevestreza, [Vincent], jgmac1106 and [jgmac1106] joined the channel
#jgmac1106[chrisaldrich] [gwg] using 2016-IndieWeb requires installing a theme from GitHib...and then knowing how to makre a child theme, and then be able to install updates to the master theme froma GitHub repo….not for the feint of heart
#LoqiJust generated this week's newsletter! You still have a few minutes to make changes, and I'll re-generate it 10 minutes before it gets sent out at 3pm Pacific time. https://indieweb.org/this-week/2018-11-16.html
#[tantek]gregorlove the problem was the "external" class mis-semantically applied to a non-external link because Mediawiki's backend logic on this is faulty
#[tantek]the only current mediawiki workaround for that is to use a native wiki link [[pagename|label]] and then hope it gets picked up as an implied u-url because mediawiki by default does not let you add class attributes to any links it generates via [[]] or [ ] or auto-linking
#[tantek]but that requires both simpler markup and only one a href hyperlink inside the h-event (for the implied u-url to work)
#gRegorLoveI should test now that we're on newer MW. There was some limitation with templates before that kept me from just wiki linking the event page directly.
#[tantek]and the time testing conditional (since Loqi sent out the newsletter at 2pm Pacific Time, not "at 3pm Pacific time" like he claimed he would)
#tantek.comedited /100DaysOfIndieWeb (+223) "note a 2018 100 Days of IndieWeb start by jgmac1106, document 8 days completed of t's 100PDPD attempt at year start" (view diff)