Yes, I use Indigenous on iOS which is what I use 90% of the time. But the benefit of the setup is if I’m on my computer I can use @aaronpk’s Monocle web App. (Although I’m looking forward to UIKit on the Mac so Indigenous can be everywhere). I send a webmention ping to https://micro.blog/webmention for every post I write, that way if the post I’m replying to is in the Micro.blog system, my reply appears here.
{
"type": "entry",
"published": "2018-08-23T10:12:59-04:00",
"summary": "Yes, I use Indigenous on iOS which is what I use 90% of the time. But the benefit of the setup is if I\u2019m on my computer I can use @aaronpk\u2019s Monocle web App. (Although I\u2019m looking forward to UIKit on the Mac so Indigenous can be everywhere). I send a webmention ping to https://micro.blog/webmention for every post I write, that way if the post I\u2019m replying to is in the Micro.blog system, my reply appears here.",
"url": "https://eddiehinkle.com/2018/08/23/5/reply/",
"in-reply-to": [
"https://micro.blog/amit/822193"
],
"content": {
"text": "Yes, I use Indigenous on iOS which is what I use 90% of the time. But the benefit of the setup is if I\u2019m on my computer I can use @aaronpk\u2019s Monocle web App. (Although I\u2019m looking forward to UIKit on the Mac so Indigenous can be everywhere). I send a webmention ping to https://micro.blog/webmention for every post I write, that way if the post I\u2019m replying to is in the Micro.blog system, my reply appears here.",
"html": "<p>Yes, I use Indigenous on iOS which is what I use 90% of the time. But the benefit of the setup is if I\u2019m on my computer I can use <a href=\"https://micro.blog/aaronpk\">@aaronpk</a>\u2019s Monocle web App. (Although I\u2019m looking forward to UIKit on the Mac so Indigenous can be everywhere). I send a webmention ping to https://micro.blog/webmention for every post I write, that way if the post I\u2019m replying to is in the Micro.blog system, my reply appears here.</p>"
},
"author": {
"type": "card",
"name": "Eddie Hinkle",
"url": "https://eddiehinkle.com/",
"photo": "https://aperture-proxy.p3k.io/cc9591b69c2c835fa2c6e23745b224db4b4b431f/68747470733a2f2f656464696568696e6b6c652e636f6d2f696d616765732f70726f66696c652e6a7067"
},
"post-type": "reply",
"refs": {
"https://micro.blog/amit/822193": {
"type": "entry",
"url": "https://micro.blog/amit/822193",
"name": "https://micro.blog/amit/822193",
"post-type": "article"
}
},
"_id": "850568",
"_source": "226",
"_is_read": true
}
I haven’t yet, I should…. but until them my set up is very similar to what @aaronpk wrote about here: https://aaronparecki.com/2018/04/20/46/indieweb-reader-my-new-home-on-the-internet
{
"type": "entry",
"published": "2018-08-23T10:07:39-04:00",
"summary": "I haven\u2019t yet, I should\u2026. but until them my set up is very similar to what @aaronpk wrote about here: https://aaronparecki.com/2018/04/20/46/indieweb-reader-my-new-home-on-the-internet",
"url": "https://eddiehinkle.com/2018/08/23/4/reply/",
"in-reply-to": [
"https://micro.blog/hjertnes/822187"
],
"content": {
"text": "I haven\u2019t yet, I should\u2026. but until them my set up is very similar to what @aaronpk wrote about here: https://aaronparecki.com/2018/04/20/46/indieweb-reader-my-new-home-on-the-internet",
"html": "<p>I haven\u2019t yet, I should\u2026. but until them my set up is very similar to what <a href=\"https://micro.blog/aaronpk\">@aaronpk</a> wrote about here: https://aaronparecki.com/2018/04/20/46/indieweb-reader-my-new-home-on-the-internet</p>"
},
"author": {
"type": "card",
"name": "Eddie Hinkle",
"url": "https://eddiehinkle.com/",
"photo": "https://aperture-proxy.p3k.io/cc9591b69c2c835fa2c6e23745b224db4b4b431f/68747470733a2f2f656464696568696e6b6c652e636f6d2f696d616765732f70726f66696c652e6a7067"
},
"post-type": "reply",
"refs": {
"https://micro.blog/hjertnes/822187": {
"type": "entry",
"url": "https://micro.blog/hjertnes/822187",
"name": "https://micro.blog/hjertnes/822187",
"post-type": "article"
}
},
"_id": "850569",
"_source": "226",
"_is_read": true
}
That makes sense. That’s how I use it too! Because I use a Social Reader that allows me to post replies to my website and then send a webmention to Micro.blog to alert it of my response, so I get the best of birth worlds, the RSS reader control but I don’t have to open up Micro.blog to reply, I can do it inline.
{
"type": "entry",
"published": "2018-08-23T10:02:03-04:00",
"summary": "That makes sense. That\u2019s how I use it too! Because I use a Social Reader that allows me to post replies to my website and then send a webmention to Micro.blog to alert it of my response, so I get the best of birth worlds, the RSS reader control but I don\u2019t have to open up Micro.blog to reply, I can do it inline.",
"url": "https://eddiehinkle.com/2018/08/23/3/reply/",
"in-reply-to": [
"https://hjertnes.blog/post/2018-08-22-mb/"
],
"content": {
"text": "That makes sense. That\u2019s how I use it too! Because I use a Social Reader that allows me to post replies to my website and then send a webmention to Micro.blog to alert it of my response, so I get the best of birth worlds, the RSS reader control but I don\u2019t have to open up Micro.blog to reply, I can do it inline.",
"html": "<p>That makes sense. That\u2019s how I use it too! Because I use a Social Reader that allows me to post replies to my website and then send a webmention to Micro.blog to alert it of my response, so I get the best of birth worlds, the RSS reader control but I don\u2019t have to open up Micro.blog to reply, I can do it inline.</p>"
},
"author": {
"type": "card",
"name": "Eddie Hinkle",
"url": "https://eddiehinkle.com/",
"photo": "https://aperture-proxy.p3k.io/cc9591b69c2c835fa2c6e23745b224db4b4b431f/68747470733a2f2f656464696568696e6b6c652e636f6d2f696d616765732f70726f66696c652e6a7067"
},
"post-type": "reply",
"refs": {
"https://hjertnes.blog/post/2018-08-22-mb/": {
"type": "entry",
"url": "https://hjertnes.blog/post/2018-08-22-mb/",
"name": "https://hjertnes.blog/post/2018-08-22-mb/",
"post-type": "article"
}
},
"_id": "849768",
"_source": "226",
"_is_read": true
}
{
"type": "entry",
"published": "2018-08-22T19:13:17-04:00",
"url": "https://martymcgui.re/2018/08/22/191317/",
"category": [
"HWC",
"IndieWeb",
"Baltimore",
"wrap-up"
],
"syndication": [
"https://www.facebook.com/events/653300001722538/permalink/655697154816156/",
"https://twitter.com/schmarty/status/1032408104917508097"
],
"name": "HWC Baltimore 2018-08-22 Wrap-Up",
"content": {
"text": "Baltimore's second Homebrew Website Club of August met at the Digital Harbor Foundation Tech Center on August 22nd! \n \n\nHere are some notes from the \"broadcast\" portion of the meetup:\n\n shawngrimes.me \u2014 Shawn has been working on teamruby.dog. Specifically, collecting content. It's a new WordPress site. Thought about Squarespace because of ease of maintenance but can't justify the pricing. Also trying to find a way to post some 360 panorama photos from a recent road trip through 19 states.\n \n\n\n martymcgui.re \u2014 Finally started the grueling work of translating his site's data from Jekyll into Hugo. It involved writing lots of little scripts to do things like maintain redirects for old date-based URL slugs, RSS for podcast feeds, and other plumbing. Next up is to port his existing templates over, which should be a big process. Also started a tribute site to his cat Nitro at nitro.rocks. Hoping to make it an IndieWeb-project by getting folks to contribute fun cat memories by posting to their own site and syndicating to nitro.rocks.\n \n\nOther discussion:\n\n Ways to showcase 360 photos. Ricoh apps can (could?) post interactive panoramas to Facebook/Twitter. Marty posted some interactive panoramas on his site back in 2016 (example), but isn't super happy with the experience.\n \n\n RSS (and Indie) readers\n Webmentions and notifications\n \n Badging (and politics)\n \n\nLeft-to-right: shawngrimes.me, teamruby.dog, martymcgui.reThanks to everybody who came out! We hope to see you all again at our next meeting on Wednesday September 5th at 6:30pm (quiet writing hour at 5:30pm)!",
"html": "<p>\n Baltimore's <a href=\"https://indieweb.org/events/2018-08-22-homebrew-website-club\">second Homebrew Website Club of August</a> met at the <a href=\"https://www.digitalharbor.org/\">Digital Harbor Foundation Tech Center</a> on August 22nd! \n <br /></p>\n<p>Here are some notes from the \"broadcast\" portion of the meetup:</p>\n<p>\n shawngrimes.me \u2014 Shawn has been working on <a href=\"http://teamruby.dog/\">teamruby.dog</a>. Specifically, collecting content. It's a new WordPress site. Thought about Squarespace because of ease of maintenance but can't justify the pricing. Also trying to find a way to post some 360 panorama photos from a recent road trip through 19 states.\n <br /></p>\n<p>\n martymcgui.re \u2014 Finally started the grueling work of translating his site's data from Jekyll into Hugo. It involved writing lots of little scripts to do things like maintain redirects for old date-based URL slugs, RSS for podcast feeds, and other plumbing. Next up is to port his existing templates over, which should be a big process. Also started a tribute site to his cat Nitro at nitro.rocks. Hoping to make it an IndieWeb-project by getting folks to contribute fun cat memories by posting to their own site and syndicating to nitro.rocks.\n <br /></p>\n<p>Other discussion:</p>\n<ul><li>\n Ways to showcase 360 photos. Ricoh apps can (could?) post interactive panoramas to Facebook/Twitter. Marty posted some interactive panoramas on his site back in 2016 (<a href=\"https://martymcgui.re/2016/08/28/114014/\">example</a>), but isn't super happy with the experience.\n <br /></li>\n <li>RSS (and Indie) readers</li>\n <li>Webmentions and notifications</li>\n <li>\n Badging (and politics)\n <br /></li>\n</ul><img src=\"https://martymcgui.re/imageproxy/960,fit,sXrUEXl9xePivTFAM7MuLTYc1T9PUTDhZL-cszcIZjs0=/https://media.martymcgui.re/c5/8f/67/36/3b42ba48e077770bb77a7464e785f9b6dc676dfd0bcf609fda387c6c.jpg\" alt=\"\" />Left-to-right: shawngrimes.me, teamruby.dog, martymcgui.re<p>Thanks to everybody who came out! We hope to see you all again at our next meeting on <strong>Wednesday</strong> <a href=\"https://indieweb.org/events/2018-09-05-homebrew-website-club\">September 5th</a> at <strong>6:30pm</strong> (quiet writing hour at 5:30pm)!</p>"
},
"author": {
"type": "card",
"name": "Marty McGuire",
"url": "https://martymcgui.re/",
"photo": "https://aperture-proxy.p3k.io/8275f85e3a389bd0ae69f209683436fc53d8bad9/68747470733a2f2f6d617274796d636775692e72652f696d616765732f6c6f676f2e6a7067"
},
"post-type": "article",
"_id": "846205",
"_source": "175",
"_is_read": true
}
{
"type": "entry",
"published": "2018-08-22T16:07:12-04:00",
"url": "https://martymcgui.re/2018/08/22/160712/",
"category": [
"podcast",
"IndieWeb",
"this-week-indieweb-podcast"
],
"audio": [
"https://aperture-proxy.p3k.io/9783205af48c0a56e03a5021831259beba13450b/68747470733a2f2f6d656469612e6d617274796d636775692e72652f65652f65332f38322f35642f32373534393739616163383433313738346562636133326465356536383338343963623261363965663562393839616539373833343433362e6d7033"
],
"syndication": [
"https://huffduffer.com/schmarty/498440",
"https://twitter.com/schmarty/status/1032359796194922496",
"https://www.facebook.com/marty.mcguire.54/posts/10212698191431646"
],
"name": "This Week in the IndieWeb Audio Edition \u2022 August 11th - 17th, 2018",
"content": {
"text": "Show/Hide Transcript \n \n #Deactiday, losing your followers, and lots of events! It\u2019s the audio edition for This Week in the IndieWeb for August 11th - 17th, 2018.\n\nYou can find all of my audio editions and subscribe with your favorite podcast app here: martymcgui.re/podcasts/indieweb/.\n\nMusic from Aaron Parecki\u2019s 100DaysOfMusic project: Day 85 - Suit, Day 48 - Glitch, Day 49 - Floating, Day 9, and Day 11\n\nThanks to everyone in the IndieWeb chat for their feedback and suggestions. Please drop me a note if there are any changes you\u2019d like to see for this audio edition!",
"html": "Show/Hide Transcript \n \n <p>#Deactiday, losing your followers, and lots of events! It\u2019s the audio edition for <a href=\"https://indieweb.org/this-week/2018-08-17.html\">This Week in the IndieWeb for August 11th - 17th, 2018</a>.</p>\n\n<p>You can find all of my audio editions and subscribe with your favorite podcast app here: <a href=\"https://martymcgui.re/podcasts/indieweb/\">martymcgui.re/podcasts/indieweb/</a>.</p>\n\n<p>Music from <a href=\"https://aaronparecki.com/\">Aaron Parecki</a>\u2019s <a href=\"https://100.aaronparecki.com/\">100DaysOfMusic project</a>: <a href=\"https://aaronparecki.com/2017/03/15/14/day85\">Day 85 - Suit</a>, <a href=\"https://aaronparecki.com/2017/02/06/7/day48\">Day 48 - Glitch</a>, <a href=\"https://aaronparecki.com/2017/02/07/4/day49\">Day 49 - Floating</a>, <a href=\"https://aaronparecki.com/2016/12/29/21/day-9\">Day 9</a>, and <a href=\"https://aaronparecki.com/2016/12/31/15/\">Day 11</a></p>\n\n<p>Thanks to everyone in the <a href=\"https://chat.indieweb.org/\">IndieWeb chat</a> for their feedback and suggestions. Please drop me a note if there are any changes you\u2019d like to see for this audio edition!</p>"
},
"author": {
"type": "card",
"name": "Marty McGuire",
"url": "https://martymcgui.re/",
"photo": "https://aperture-proxy.p3k.io/8275f85e3a389bd0ae69f209683436fc53d8bad9/68747470733a2f2f6d617274796d636775692e72652f696d616765732f6c6f676f2e6a7067"
},
"post-type": "audio",
"_id": "844681",
"_source": "175",
"_is_read": true
}
But as it stands, with only two minor edits to the mf2 plugin & suite of Indieweb WP plugins I already had installed, I’m using default twentysixteen WordPress theme. I’m syndicating to micro.blog, Twitter (via brid.gy) and Mastodon (via auto-poster plugin). I’m also receiving backfeed from all three. I can also comment and create GitHub issues as post on my site, again, using existing plugins and brid.gy. The work this community has done in the last 2 years is amazing.
{
"type": "entry",
"published": "2018-08-22T11:53:58-04:00",
"url": "https://miklb.com/blog/2018/08/22/4190/",
"syndication": [
"https://mastodon.social/@miklb/100594695503428942"
],
"in-reply-to": [
"https://miklb.com/blog/2018/08/22/4188/"
],
"content": {
"text": "But as it stands, with only two minor edits to the mf2 plugin & suite of Indieweb WP plugins I already had installed, I\u2019m using default twentysixteen WordPress theme. I\u2019m syndicating to micro.blog, Twitter (via brid.gy) and Mastodon (via auto-poster plugin). I\u2019m also receiving backfeed from all three. I can also comment and create GitHub issues as post on my site, again, using existing plugins and brid.gy. The work this community has done in the last 2 years is amazing.",
"html": "But as it stands, with only two minor edits to the mf2 plugin & suite of Indieweb WP plugins I already had installed, I\u2019m using default twentysixteen WordPress theme. I\u2019m syndicating to micro.blog, Twitter (via brid.gy) and Mastodon (via auto-poster plugin). I\u2019m also receiving backfeed from all three. I can also comment and create GitHub issues as post on my site, again, using existing plugins and brid.gy. The work this community has done in the last 2 years is amazing."
},
"author": {
"type": "card",
"name": "Michael Bishop",
"url": "https://miklb.com/",
"photo": "https://aperture-proxy.p3k.io/ea0271a66c081d9e09b200106fd14e4c49d9751c/68747470733a2f2f6d696b6c622e636f6d2f7061676573706565645f7374617469632f312e4a69426e4d71796c36532e676966"
},
"post-type": "reply",
"refs": {
"https://miklb.com/blog/2018/08/22/4188/": {
"type": "entry",
"url": "https://miklb.com/blog/2018/08/22/4188/",
"name": "Miklb Mindless Ramblings",
"author": {
"type": "card",
"name": "Michael Bishop",
"url": "https://miklb.com/",
"photo": "https://miklb.com/pagespeed_static/1.JiBnMqyl6S.gif"
},
"post-type": "article"
}
},
"_id": "842590",
"_source": "42",
"_is_read": true
}
So part way through my testing of the State of WordPress in IndieWeb and it really is so far less “broken” than I think a lot of us believed in regards to using the core 2016 theme. Still more testing to do.
{
"type": "entry",
"published": "2018-08-22T11:28:16-04:00",
"url": "https://miklb.com/blog/2018/08/22/4188/",
"syndication": [
"https://mastodon.social/@miklb/100594594447576363",
"https://twitter.com/miklb/status/1032288371467591681"
],
"content": {
"text": "So part way through my testing of the State of WordPress in IndieWeb and it really is so far less \u201cbroken\u201d than I think a lot of us believed in regards to using the core 2016 theme. Still more testing to do."
},
"author": {
"type": "card",
"name": "Michael Bishop",
"url": "https://miklb.com/",
"photo": "https://aperture-proxy.p3k.io/ea0271a66c081d9e09b200106fd14e4c49d9751c/68747470733a2f2f6d696b6c622e636f6d2f7061676573706565645f7374617469632f312e4a69426e4d71796c36532e676966"
},
"post-type": "note",
"_id": "842420",
"_source": "42",
"_is_read": true
}
Sorry to see there still seems to be issues getting Indigenous to work properly with your Aperture plugin. When you go back to the first screen of Indigenous, what appears? Earlier it said no Microsub endpoint found, is it now a white screen? The goal based on the view in Aperture for you would hopefully be that there is a channel listing with the “Home” channel listed.
If the screen is white, have you tried pull-to-refresh? If you just have a white screen after attempting pull-to-refresh, can you click “View Account Debug Info” and copy and paste that information in an email to eddie@eddiehinkle.com? I’m the developer of Indigenous, so that would help me debug what might be going on with Indigenous and if it’s an Indigenous or Aperture error.
The other thing you could do to troubleshoot that might provide some more information is Monocle has some great error messages (something that Indigenous could use more of). It’s a web-based Microsub reader so you won’t have to download anything additional.
{
"type": "entry",
"published": "2018-08-21T10:01:42-04:00",
"summary": "Sorry to see there still seems to be issues getting Indigenous to work properly with your Aperture plugin. When you go back to the first screen of Indigenous, what appears? Earlier it said no Microsub endpoint found, is it now a white screen? The goal based on the view in Aperture for you would hopefully be that there is a channel listing with the \u201cHome\u201d channel listed.\nIf the screen is white, have you tried pull-to-refresh? If you just have a white screen after attempting pull-to-refresh, can you click \u201cView Account Debug Info\u201d and copy and paste that information in an email to eddie@eddiehinkle.com? I\u2019m the developer of Indigenous, so that would help me debug what might be going on with Indigenous and if it\u2019s an Indigenous or Aperture error.\nThe other thing you could do to troubleshoot that might provide some more information is Monocle has some great error messages (something that Indigenous could use more of). It\u2019s a web-based Microsub reader so you won\u2019t have to download anything additional.",
"url": "https://eddiehinkle.com/2018/08/21/3/reply/",
"in-reply-to": [
"https://islandinthenet.com/aperture/"
],
"content": {
"text": "Sorry to see there still seems to be issues getting Indigenous to work properly with your Aperture plugin. When you go back to the first screen of Indigenous, what appears? Earlier it said no Microsub endpoint found, is it now a white screen? The goal based on the view in Aperture for you would hopefully be that there is a channel listing with the \u201cHome\u201d channel listed.\n\nIf the screen is white, have you tried pull-to-refresh? If you just have a white screen after attempting pull-to-refresh, can you click \u201cView Account Debug Info\u201d and copy and paste that information in an email to eddie@eddiehinkle.com? I\u2019m the developer of Indigenous, so that would help me debug what might be going on with Indigenous and if it\u2019s an Indigenous or Aperture error.\n\nThe other thing you could do to troubleshoot that might provide some more information is Monocle has some great error messages (something that Indigenous could use more of). It\u2019s a web-based Microsub reader so you won\u2019t have to download anything additional.",
"html": "<p>Sorry to see there still seems to be issues getting Indigenous to work properly with your Aperture plugin. When you go back to the first screen of Indigenous, what appears? Earlier it said no Microsub endpoint found, is it now a white screen? The goal based on the view in Aperture for you would hopefully be that there is a channel listing with the \u201cHome\u201d channel listed.</p>\n\n<p>If the screen is white, have you tried <a href=\"https://uxplanet.org/pull-to-refresh-ui-pattern-42a85f671cdf\">pull-to-refresh</a>? If you just have a white screen after attempting pull-to-refresh, can you click \u201cView Account Debug Info\u201d and copy and paste that information in an email to eddie@eddiehinkle.com? I\u2019m the developer of Indigenous, so that would help me debug what might be going on with Indigenous and if it\u2019s an Indigenous or Aperture error.</p>\n\n<p>The other thing you could do to troubleshoot that might provide some more information is <a href=\"https://monocle.p3k.io\">Monocle</a> has some great error messages (something that Indigenous could use more of). It\u2019s a web-based Microsub reader so you won\u2019t have to download anything additional.</p>"
},
"author": {
"type": "card",
"name": "Eddie Hinkle",
"url": "https://eddiehinkle.com/",
"photo": "https://aperture-proxy.p3k.io/cc9591b69c2c835fa2c6e23745b224db4b4b431f/68747470733a2f2f656464696568696e6b6c652e636f6d2f696d616765732f70726f66696c652e6a7067"
},
"post-type": "reply",
"refs": {
"https://islandinthenet.com/aperture/": {
"type": "entry",
"url": "https://islandinthenet.com/aperture/",
"name": "https://islandinthenet.com/aperture/",
"post-type": "article"
}
},
"_id": "834631",
"_source": "226",
"_is_read": true
}
Awesome! Used the form to request Micro.blog support and provided them links to the IndieAuth and Micropub spec pages that would allow them to add support for M.b easily.
{
"type": "entry",
"published": "2018-08-20T23:55:42-04:00",
"summary": "Awesome! Used the form to request Micro.blog support and provided them links to the IndieAuth and Micropub spec pages that would allow them to add support for M.b easily.",
"url": "https://eddiehinkle.com/2018/08/20/30/reply/",
"in-reply-to": [
"https://Fritz.micro.blog/2018/08/20/is-anyone-interested.html"
],
"content": {
"text": "Awesome! Used the form to request Micro.blog support and provided them links to the IndieAuth and Micropub spec pages that would allow them to add support for M.b easily.",
"html": "<p>Awesome! Used the form to request Micro.blog support and provided them links to the IndieAuth and Micropub spec pages that would allow them to add support for M.b easily.</p>"
},
"author": {
"type": "card",
"name": "Eddie Hinkle",
"url": "https://eddiehinkle.com/",
"photo": "https://aperture-proxy.p3k.io/cc9591b69c2c835fa2c6e23745b224db4b4b431f/68747470733a2f2f656464696568696e6b6c652e636f6d2f696d616765732f70726f66696c652e6a7067"
},
"post-type": "reply",
"refs": {
"https://Fritz.micro.blog/2018/08/20/is-anyone-interested.html": {
"type": "entry",
"url": "https://Fritz.micro.blog/2018/08/20/is-anyone-interested.html",
"name": "https://Fritz.micro.blog/2018/08/20/is-anyone-interested.html",
"post-type": "article"
}
},
"_id": "834033",
"_source": "226",
"_is_read": true
}
A little appropos seeing this quote shared by Matt today after I wrote this last night
“WordPress was orginally about making it easier to put words and pictures on the Internet. Gutenberg and 5.0 is about ushering in a new interface to do that. We should at least fight to make the full IndieWeb experience a little easier to be a part of that change.”
{
"type": "entry",
"url": "https://miklb.com/blog/2018/08/20/4167/",
"bookmark-of": [
"https://ma.tt/2018/08/light-heretofore-unkown/"
],
"content": {
"text": "A little appropos seeing this quote shared by Matt today after I wrote this last night\n\u201cWordPress was orginally about making it easier to put words and pictures on the Internet. Gutenberg and 5.0 is about ushering in a new interface to do that. We should at least fight to make the full IndieWeb experience a little easier to be a part of that change.\u201d",
"html": "A little appropos seeing this quote shared by Matt today after I wrote this last night\n<p>\u201cWordPress was orginally about making it easier to put words and pictures on the Internet. Gutenberg and 5.0 is about ushering in a new interface to do that. We should at least fight to make the full IndieWeb experience a little easier to be a part of that change.\u201d</p>"
},
"author": {
"type": "card",
"name": "Michael Bishop",
"url": "https://miklb.com/",
"photo": "https://aperture-proxy.p3k.io/fa0674caee1c8265a0b0a240a0ec9c5d99ee50a2/68747470733a2f2f7365637572652e67726176617461722e636f6d2f6176617461722f63333961316436646637333532353934356366653530653939646164613733303f733d353026643d64656661756c7426723d72"
},
"post-type": "bookmark",
"refs": {
"https://ma.tt/2018/08/light-heretofore-unkown/": {
"type": "entry",
"url": "https://ma.tt/2018/08/light-heretofore-unkown/",
"name": "Light Heretofore\u00a0Unknown",
"author": {
"type": "card",
"name": "JOHANNES GUTENBERG",
"url": false,
"photo": null
},
"post-type": "article"
}
},
"_id": "831845",
"_source": "42",
"_is_read": true
}
A good half-hour presentation by Stephen Rushe on the building blocks of the indie web. You can watch the video or look through the slides.
I’ve recently been exploring the world of the IndieWeb, and owning my own content rather than being reliant on the continued existence of “silos” to maintain it. This has led me to discover the varied eco-system of IndieWeb, such as IndieAuth, Microformats, Micropub, Webmentions, Microsub, POSSE, and PESOS.
{
"type": "entry",
"published": "2018-08-20T15:16:26Z",
"url": "https://adactio.com/links/14269",
"category": [
"indieweb",
"presentation",
"conference",
"talk",
"indieauth",
"webmentions",
"micropub",
"microformats",
"authentication"
],
"bookmark-of": [
"https://noti.st/srushe/7D5URN"
],
"content": {
"text": "Playing with the Indieweb\n\n\n\nA good half-hour presentation by Stephen Rushe on the building blocks of the indie web. You can watch the video or look through the slides.\n\n\n I\u2019ve recently been exploring the world of the IndieWeb, and owning my own content rather than being reliant on the continued existence of \u201csilos\u201d to maintain it. This has led me to discover the varied eco-system of IndieWeb, such as IndieAuth, Microformats, Micropub, Webmentions, Microsub, POSSE, and PESOS.",
"html": "<h3>\n<a class=\"p-name u-bookmark-of\" href=\"https://noti.st/srushe/7D5URN\">\nPlaying with the Indieweb\n</a>\n</h3>\n\n<p>A good half-hour presentation by Stephen Rushe on the building blocks of the indie web. You can watch the video or look through the slides.</p>\n\n<blockquote>\n <p>I\u2019ve recently been exploring the world of the IndieWeb, and owning my own content rather than being reliant on the continued existence of \u201csilos\u201d to maintain it. This has led me to discover the varied eco-system of IndieWeb, such as IndieAuth, Microformats, Micropub, Webmentions, Microsub, POSSE, and PESOS.</p>\n</blockquote>"
},
"post-type": "bookmark",
"_id": "828706",
"_source": "2",
"_is_read": true
}
Interesting, definitely good food for thought! I appreciate your analysis on not only Micro.blog but the IndieWeb in general. All things take time to mature into the best version of itself. As more people hear about the IndieWeb it allows each new ring of people to help provide input on what blockades exist for the next ring of people.
{
"type": "entry",
"published": "2018-08-20T01:05:39-04:00",
"summary": "Interesting, definitely good food for thought! I appreciate your analysis on not only Micro.blog but the IndieWeb in general. All things take time to mature into the best version of itself. As more people hear about the IndieWeb it allows each new ring of people to help provide input on what blockades exist for the next ring of people.",
"url": "https://eddiehinkle.com/2018/08/20/3/reply/",
"in-reply-to": [
"https://vega.micro.blog/2018/08/20/diversity-on-microblog.html"
],
"content": {
"text": "Interesting, definitely good food for thought! I appreciate your analysis on not only Micro.blog but the IndieWeb in general. All things take time to mature into the best version of itself. As more people hear about the IndieWeb it allows each new ring of people to help provide input on what blockades exist for the next ring of people.",
"html": "<p>Interesting, definitely good food for thought! I appreciate your analysis on not only Micro.blog but the IndieWeb in general. All things take time to mature into the best version of itself. As more people hear about the IndieWeb it allows each new ring of people to help provide input on what blockades exist for the next ring of people.</p>"
},
"author": {
"type": "card",
"name": "Eddie Hinkle",
"url": "https://eddiehinkle.com/",
"photo": "https://aperture-proxy.p3k.io/cc9591b69c2c835fa2c6e23745b224db4b4b431f/68747470733a2f2f656464696568696e6b6c652e636f6d2f696d616765732f70726f66696c652e6a7067"
},
"post-type": "reply",
"refs": {
"https://vega.micro.blog/2018/08/20/diversity-on-microblog.html": {
"type": "entry",
"url": "https://vega.micro.blog/2018/08/20/diversity-on-microblog.html",
"name": "https://vega.micro.blog/2018/08/20/diversity-on-microblog.html",
"post-type": "article"
}
},
"_id": "827263",
"_source": "226",
"_is_read": true
}
My OwnYourSwarm/WordPress relationship is a love/hate one. Keep having the account disabled due to “Your Micropub endpoint returned an error too many times in a row.“
Sometimes manually adding previous check-ins through the dashboard works.
{
"type": "entry",
"url": "http://davidjohnmead.com/blog/2018/08/20/20058/",
"content": {
"text": "My OwnYourSwarm/WordPress relationship is a love/hate one. Keep having the account disabled due to \u201cYour Micropub endpoint returned an error too many times in a row.\u201c\n\nSometimes manually adding previous check-ins through the dashboard works.",
"html": "<p>My OwnYourSwarm/WordPress relationship is a love/hate one. Keep having the account disabled due to \u201c<span style=\"background-color:rgb(255,246,246);color:rgb(159,58,56);\">Your Micropub endpoint returned an error too many times in a row.</span>\u201c</p>\n<p></p>\n<p>Sometimes manually adding previous check-ins through the dashboard works.</p>"
},
"post-type": "note",
"_id": "826335",
"_source": "194",
"_is_read": true
}
{
"type": "entry",
"url": "https://miklb.com/blog/2018/08/19/live-testing-the-state-of-affairs-in-wordpress-the-indieweb/",
"syndication": [
"https://twitter.com/miklb/status/1031359000162516999"
],
"name": "Live Testing the State of Affairs in WordPress & the IndieWeb",
"content": {
"text": "Suffice to say I\u2019ve said a lot about WordPress and the IndieWeb. Here and in #indieweb-wordpress in IRC. But the gist is, I don\u2019t know what issues there are summer of 2018 with a core WordPress theme and the suite of IndieWeb plugins. No one seems to be able to point to anything specific.\nThere are efforts under way to bypass the mf2 in the markup and pass a mf2 feed for parsers to use. It is an honest attempt to find a solution right now. But the elegance of semantic classes in proper HTML5 markup is what drew me to the technology in the first place. I would hate to ditch that approach without attempting to find a solution that includes the underlying markup in WordPress themes.\nMy base understanding is that there are microformats 1 in core. Over time folks have used those semantic classes as styling hooks. A pull request was sent and was closed as wontfix due to concern of \u201cbreaking\u201d legacy themes that used the mf1 semantic class as styling hook.\nThat was 2 years ago. I don\u2019t know if anything has changed since then. A lot has changed in the Indieweb landscape including improvements to backward compatibility in the mf2 parses.\nSo, if you consume this feed in any kind of reader and see weird output, please send a webmention to this post so I can collect them in one place and document. Feel free to send a webmention without an issue just so I can assess replies as well.\nAlso, if you\u2019ve done this excercise in the last few months, please share your experience.",
"html": "Suffice to say I\u2019ve said a lot about WordPress and the IndieWeb. Here and in #indieweb-wordpress in IRC. But the gist is, I don\u2019t know what issues there are summer of 2018 with a core WordPress theme and the suite of IndieWeb plugins. No one seems to be able to point to anything specific.\n<p>There are efforts under way to bypass the mf2 in the markup and pass a mf2 feed for parsers to use. It is an honest attempt to find a solution right now. But the elegance of semantic classes in proper HTML5 markup is what drew me to the technology in the first place. I would hate to ditch that approach without attempting to find a solution that includes the underlying markup in WordPress themes.</p>\n<p>My base understanding is that there are microformats 1 in core. Over time folks have used those semantic classes as styling hooks. A <a href=\"https://core.trac.wordpress.org/ticket/30783\">pull request was sent</a> and was closed as <code>wontfix</code> due to concern of \u201cbreaking\u201d legacy themes that used the mf1 semantic class as styling hook.</p>\n<p>That was 2 years ago. I don\u2019t know if anything has changed since then. A lot has changed in the Indieweb landscape including improvements to backward compatibility in the mf2 parses.</p>\n<p>So, if you consume this feed in any kind of reader and see weird output, please send a webmention to this post so I can collect them in one place and document. Feel free to send a webmention without an issue just so I can assess replies as well.</p>\n<p>Also, if you\u2019ve done this excercise in the last few months, <strong>please</strong> share your experience.</p>"
},
"post-type": "article",
"_id": "825401",
"_source": "42",
"_is_read": true
}
{
"type": "entry",
"syndication": [
"https://twitter.com/miklb/status/1031359000162516999"
],
"name": "Live Testing the State of Affairs in WordPress & the IndieWeb",
"content": {
"text": "Suffice to say I\u2019ve said a lot about WordPress and the IndieWeb. Here and in #indieweb-wordpress in IRC. But the gist is, I don\u2019t know what issues there are summer of 2018 with a core WordPress theme and the suite of IndieWeb plugins. No one seems to be able to point to anything specific.\nThere are efforts under way to bypass the mf2 in the markup and pass a mf2 feed for parsers to use. It is an honest attempt to find a solution right now. But the elegance of semantic classes in proper HTML5 markup is what drew me to the technology in the first place. I would hate to ditch that approach without attempting to find a solution that includes the underlying markup in WordPress themes.\nMy base understanding is that there are microformats 1 in core. Over time folks have used those semantic classes as styling hooks. A pull request was sent and was closed as wontfix due to concern of \u201cbreaking\u201d legacy themes that used the mf1 semantic class as styling hook.\nThat was 2 years ago. I don\u2019t know if anything has changed since then. A lot has changed in the Indieweb landscape including improvements to backward compatibility in the mf2 parses.\nSo, if you consume this feed in any kind of reader and see weird output, please send a webmention to this post so I can collect them in one place and document. Feel free to send a webmention without an issue just so I can assess replies as well.\nAlso, if you\u2019ve done this excercise in the last few months, please share your experience.",
"html": "Suffice to say I\u2019ve said a lot about WordPress and the IndieWeb. Here and in #indieweb-wordpress in IRC. But the gist is, I don\u2019t know what issues there are summer of 2018 with a core WordPress theme and the suite of IndieWeb plugins. No one seems to be able to point to anything specific.\n<p>There are efforts under way to bypass the mf2 in the markup and pass a mf2 feed for parsers to use. It is an honest attempt to find a solution right now. But the elegance of semantic classes in proper HTML5 markup is what drew me to the technology in the first place. I would hate to ditch that approach without attempting to find a solution that includes the underlying markup in WordPress themes.</p>\n<p>My base understanding is that there are microformats 1 in core. Over time folks have used those semantic classes as styling hooks. A <a href=\"https://core.trac.wordpress.org/ticket/30783\">pull request was sent</a> and was closed as <code>wontfix</code> due to concern of \u201cbreaking\u201d legacy themes that used the mf1 semantic class as styling hook.</p>\n<p>That was 2 years ago. I don\u2019t know if anything has changed since then. A lot has changed in the Indieweb landscape including improvements to backward compatibility in the mf2 parses.</p>\n<p>So, if you consume this feed in any kind of reader and see weird output, please send a webmention to this post so I can collect them in one place and document. Feel free to send a webmention without an issue just so I can assess replies as well.</p>\n<p>Also, if you\u2019ve done this excercise in the last few months, <strong>please</strong> share your experience.</p>"
},
"post-type": "article",
"_id": "824890",
"_source": "42",
"_is_read": true
}
The #indieweb recognizes that right now it’s still at that stage but is constantly working towards easier and more access https://indieweb.org/generations
{
"type": "entry",
"syndication": [
"https://twitter.com/miklb/status/1027238585441890305"
],
"in-reply-to": [
"https://twitter.com/ChrisHardie/status/1027237085525237765"
],
"content": {
"text": "The #indieweb recognizes that right now it\u2019s still at that stage but is constantly working towards easier and more access https://indieweb.org/generations"
},
"post-type": "reply",
"refs": {
"https://twitter.com/ChrisHardie/status/1027237085525237765": {
"type": "entry",
"url": "https://twitter.com/ChrisHardie/status/1027237085525237765",
"post-type": "note"
}
},
"_id": "824808",
"_source": "42",
"_is_read": true
}
