But the FAQ says that when I use the app or web those comments get stored seperatelly and are not send to my blog. Is there a technical reason why that is? Couldn't they been send via MicroPub to my blog?
{
"type": "entry",
"published": "2018-05-01T21:22:52Z",
"url": "https://jeena.net/notes/933",
"content": {
"text": "@manton I read http://help.micro.blog/2018/replies-and-mentions/ and am somehow conflicted, I'd like to own my replies too, and with normal IndieWeb I do, I have them in a special comments section: https://jeena.net/comments\n\nBut the FAQ says that when I use the app or web those comments get stored seperatelly and are not send to my blog. Is there a technical reason why that is? Couldn't they been send via MicroPub to my blog?",
"html": "<p></p><p><a href=\"https://twitter.com/manton\">@manton</a> I read <a href=\"http://help.micro.blog/2018/replies-and-mentions/\">http://help.micro.blog/2018/replies-and-mentions/</a> and am somehow conflicted, I'd like to own my replies too, and with normal IndieWeb I do, I have them in a special comments section: <a href=\"https://jeena.net/comments\">https://jeena.net/comments</a></p>\n\n<p>But the FAQ says that when I use the app or web those comments get stored seperatelly and are not send to my blog. Is there a technical reason why that is? Couldn't they been send via MicroPub to my blog?</p>"
},
"author": {
"type": "card",
"name": "Jeena",
"url": "https://jeena.net/",
"photo": "https://aperture-media.p3k.io/jeena.net/d265fd0a7b0bc15c7d4df4534b596d15b6039da1eab9482dda49db1a62fe1919.jpg"
},
"_id": "284182",
"_source": "201",
"_is_read": true
}
{
"type": "entry",
"published": "2018-04-30T14:16:42-04:00",
"rsvp": "yes",
"url": "https://martymcgui.re/2018/04/30/141642/",
"syndication": [
"https://twitter.com/schmarty/status/991022038738448385",
"https://www.facebook.com/marty.mcguire.54/posts/10211946071269112"
],
"in-reply-to": [
"https://martymcgui.re/2018/04/20/125343/"
],
"content": {
"text": "I'm going!Homebrew Website Club Baltimore returns!\nRoving IndieWeb developer grant.codes, lead developer of the Together indie reader, will also be joining us!",
"html": "I'm going!<p>Homebrew Website Club Baltimore returns!</p>\n<p>Roving IndieWeb developer <a href=\"https://grant.codes/\">grant.codes</a>, lead developer of the <a href=\"https://alltogethernow.io/\">Together</a> indie reader, will also be joining us!</p>"
},
"author": {
"type": "card",
"name": "Marty McGuire",
"url": "https://martymcgui.re/",
"photo": "https://aperture-media.p3k.io/martymcgui.re/4f9fac2b9e3ae62998c557418143efe288bca8170a119921a9c6bfeb0a1263a2.jpg"
},
"refs": {
"https://martymcgui.re/2018/04/20/125343/": {
"type": "entry",
"published": "2018-04-20T12:53:43-04:00",
"summary": "Reminder: We are now meeting on Tuesdays instead of the usual Wednesdays. Be sure to double-check your calendars! Join us for an evening of quiet writing, IndieWeb demos, and discussions! Create or update your personal web site! Finish that blog post you\u2019ve been writing, edit the wiki! Demos of recent IndieWeb breakthroughs, share what you\u2019ve gotten working! Join a community...",
"url": "https://martymcgui.re/2018/04/20/125343/",
"name": "Homebrew Website Club Baltimore",
"author": {
"type": "card",
"name": "martymcgui.re",
"url": "http://martymcgui.re",
"photo": null
}
}
},
"_id": "280243",
"_source": "175",
"_is_read": true
}
{
"type": "entry",
"published": "2018-04-29T21:18:20-04:00",
"url": "https://david.shanske.com/2018/04/29/an-indieweb-podcast-episode-3-syndication/",
"category": [
"http://boffosock.com"
],
"audio": [
"https://aperture-media.p3k.io/david.shanske.com/bfea3adf4ec0ef19341c5ff52b911274d7d1812dc1bcfd6a3f58dc19cc42ec94.mp3"
],
"syndication": [
"https://www.facebook.com/100002356503167/posts/1678599458895255",
"https://twitter.com/dshanske/status/990762262507020288",
"https://news.indieweb.org/en/david.shanske.com/2018/04/29/an-indieweb-podcast-episode-3-syndication/"
],
"name": "An Indieweb Podcast - Episode 3: Syndication",
"content": {
"text": "This podcast is partly being used to develop Indieweb podcasting tools for WordPress. As a result, it will get better each time I post. At the time of this post, there was no direct download option being generated, so if there is one here now, I\u2019ve upgraded. Also, duration is missing. But unlike previous episodes, the system will now autogenerate the enclosure for RSS feeds, so you can subscribe.\u00a0\nThe current podcast feed on this site can be found in a variety of ways.\n\n\u00a0Audio Posts on this Site \u2013 This is a feed of all my audio posts.\n\nAn Indieweb Podcast\u00a0 \u2013 I have something called Series on my site, so this is the feed for this as a series. I probably should have a feed called Podcast.\nCo-Host: Chris Aldrich of Boffosocko.com\nShow Notes\nFacebook has announced ending publishing by API\u2026and David is thinking about what it means for the community and his current project.\nFacebook is ending posting via API on August 1, 2018 https://developers.facebook.com/blog/post/2018/04/24/new-facebook-platform-product-changes-policy-updates/\n\nBridgy Announces the coming changes: https://snarfed.org/2018-04-26_bridgy-publish-for-facebook-shuts-down-in-august\n\nBuffer responds, but then checks itself: https://twitter.com/buffer/status/988915108620505088\n\nI\u2019m done with Syndication. Let\u2019s help people be themselves on the web. By Ben Werdmuller https://werd.io/2018/im-done-with-syndication-lets-help-people-be-themselves-on\n\nDeprecating and Replacing Bridgy Publish for WordPress by David Shanske https://david.shanske.com/2018/04/28/deprecating-and-replacing-bridgy-publish-for-wordpress/\n\nHistory:\nThinkUP from Anil Dash and Gina Trapani ultimately died trying to fight the API wars with various social silos. They spent all their time trying to keep up with no guarantee that the silos would cooperate. All their engineering resources were spent trying to keep up instead of innovating on a stable platform.\nRelated IndieWeb wiki pages\ncrossposting\nPOSSE\nPESOS\nManual until it hurts\nBrid.gy Publish\nWordPress Plugins:\nBridgy Publish Plugin\nSNAP\nJetPack",
"html": "<em>This podcast is partly being used to develop Indieweb podcasting tools for WordPress. As a result, it will get better each time I post. At the time of this post, there was no direct download option being generated, so if there is one here now, I\u2019ve upgraded. Also, duration is missing. But unlike previous episodes, the system will now autogenerate the enclosure for RSS feeds, so you can subscribe.\u00a0</em>\n<p><em>The current podcast feed on this site can be found in a variety of ways.</em></p>\n<ul><li>\n<a href=\"https://david.shanske.com/kind/audio\">\u00a0Audio Posts on this Site</a> \u2013 This is a feed of all my audio posts.</li>\n<li>\n<a href=\"https://david.shanske.com/series/indieweb-podcast/\">An Indieweb Podcast</a>\u00a0 \u2013 I have something called Series on my site, so this is the feed for this as a series. I probably should have a feed called Podcast.</li>\n</ul><p>Co-Host: <a class=\"u-category\" href=\"http://boffosock.com\">Chris Aldrich</a> of Boffosocko.com</p>\n<p><strong>Show Notes</strong></p>\n<p>Facebook has announced ending publishing by API\u2026and David is thinking about what it means for the community and his current project.</p>\n<ul><li>Facebook is ending posting via API on August 1, 2018 <a href=\"https://developers.facebook.com/blog/post/2018/04/24/new-facebook-platform-product-changes-policy-updates/\">https://developers.facebook.com/blog/post/2018/04/24/new-facebook-platform-product-changes-policy-updates/</a>\n</li>\n<li>Bridgy Announces the coming changes: <a href=\"https://snarfed.org/2018-04-26_bridgy-publish-for-facebook-shuts-down-in-august\">https://snarfed.org/2018-04-26_bridgy-publish-for-facebook-shuts-down-in-august</a>\n</li>\n</ul><ul><li>Buffer responds, but then checks itself: <a href=\"https://twitter.com/buffer/status/988915108620505088\">https://twitter.com/buffer/status/988915108620505088</a>\n</li>\n<li>I\u2019m done with Syndication. Let\u2019s help people be themselves on the web. By Ben Werdmuller <a href=\"https://werd.io/2018/im-done-with-syndication-lets-help-people-be-themselves-on\">https://werd.io/2018/im-done-with-syndication-lets-help-people-be-themselves-on</a>\n</li>\n<li>Deprecating and Replacing Bridgy Publish for WordPress by David Shanske <a href=\"https://david.shanske.com/2018/04/28/deprecating-and-replacing-bridgy-publish-for-wordpress/\">https://david.shanske.com/2018/04/28/deprecating-and-replacing-bridgy-publish-for-wordpress/</a>\n</li>\n</ul><p><strong>History:</strong></p>\n<p>ThinkUP from Anil Dash and Gina Trapani ultimately died trying to fight the API wars with various social silos. They spent all their time trying to keep up with no guarantee that the silos would cooperate. All their engineering resources were spent trying to keep up instead of innovating on a stable platform.</p>\n<p><strong>Related IndieWeb wiki pages</strong></p>\n<ul><li>crossposting</li>\n<li><a href=\"https://indieweb.org/POSSE\">POSSE</a></li>\n<li><a href=\"https://indieweb.org/PESOS\">PESOS</a></li>\n<li><a href=\"https://indieweb.org/manual_until_it_hurts\">Manual until it hurts</a></li>\n<li><a href=\"https://indieweb.org/Bridgy\">Brid.gy Publish</a></li>\n</ul><p><strong>WordPress Plugins:</strong></p>\n<ul><li><a href=\"https://wordpress.org/plugins/bridgy-publish/\">Bridgy Publish Plugin</a></li>\n<li><a href=\"https://wordpress.org/plugins/social-networks-auto-poster-facebook-twitter-g/\">SNAP</a></li>\n<li><a href=\"https://wordpress.org/plugins/jetpack/\">JetPack</a></li>\n</ul>"
},
"author": {
"type": "card",
"name": "David Shanske",
"url": "https://david.shanske.com/",
"photo": "https://aperture-media.p3k.io/secure.gravatar.com/ee1cea4a5d6465ac3bd8e56fc0bbfdacd25be40ef0968e6b2b2e8016103cb826.png"
},
"_id": "278087",
"_source": "5",
"_is_read": true
}
{
"type": "entry",
"published": "2018-04-29T21:43:02+0000",
"url": "http://known.kevinmarks.com/2018/a-handful-of-enormous-tech-companies-curate",
"category": [
"Indieweb"
],
"syndication": [
"https://twitter.com/kevinmarks/status/990708061466542080"
],
"content": {
"text": "\u201cA handful of enormous tech companies curate the public library we conjure into existence every day, and they can and do delete it at a whim.\u201d https://www.buzzfeed.com/amphtml/evanhill/silicon-valley-cant-be-trusted-with-our-history?utm_term=4... #Indieweb",
"html": "\u201cA handful of enormous tech companies curate the public library we conjure into existence every day, and they can and do delete it at a whim.\u201d <a href=\"https://www.buzzfeed.com/amphtml/evanhill/silicon-valley-cant-be-trusted-with-our-history?utm_term=4ldqpgm&amp;bftwuk=&amp;__indieweb_impression=true\">https://www.buzzfeed.com/amphtml/evanhill/silicon-valley-cant-be-trusted-with-our-history?utm_term=4...</a> <a href=\"http://known.kevinmarks.com/tag/Indieweb\" class=\"p-category\">#Indieweb</a>"
},
"author": {
"type": "card",
"name": "Kevin Marks",
"url": "http://known.kevinmarks.com/profile/kevinmarks",
"photo": "https://aperture-media.p3k.io/known.kevinmarks.com/f893d11435a62200ec9585e0ea3d84b2bdc478aa0a056dda35a43ce4c04d58a0.jpg"
},
"_id": "277914",
"_source": "205",
"_is_read": true
}
“ I warned (at Blogtalk Downunder) that comments kill weblogs, and I was right. Facebook and Twitter are platforms for comments that dispense with the weblog; they give us all the disadvantages and keep all the profit.” http://www.markbernstein.org/Apr18/OnNotBlogging.html#indieweb
{
"type": "entry",
"published": "2018-04-29T21:15:55+0000",
"url": "http://known.kevinmarks.com/2018/-i-warned-at-blogtalk-downunder-that",
"category": [
"indieweb"
],
"syndication": [
"https://twitter.com/kevinmarks/status/990701237535322112"
],
"content": {
"text": "\u201c I warned (at Blogtalk Downunder) that comments kill weblogs, and I was right. Facebook and Twitter are platforms for comments that dispense with the weblog; they give us all the disadvantages and keep all the profit.\u201d http://www.markbernstein.org/Apr18/OnNotBlogging.html #indieweb",
"html": "\u201c I warned (at Blogtalk Downunder) that comments kill weblogs, and I was right. Facebook and Twitter are platforms for comments that dispense with the weblog; they give us all the disadvantages and keep all the profit.\u201d <a href=\"http://www.markbernstein.org/Apr18/OnNotBlogging.html\">http://www.markbernstein.org/Apr18/OnNotBlogging.html</a> <a href=\"http://known.kevinmarks.com/tag/indieweb\" class=\"p-category\">#indieweb</a>"
},
"author": {
"type": "card",
"name": "Kevin Marks",
"url": "http://known.kevinmarks.com/profile/kevinmarks",
"photo": "https://aperture-media.p3k.io/known.kevinmarks.com/f893d11435a62200ec9585e0ea3d84b2bdc478aa0a056dda35a43ce4c04d58a0.jpg"
},
"_id": "277915",
"_source": "205",
"_is_read": true
}
{
"type": "entry",
"published": "2018-04-28T22:54:11-04:00",
"url": "https://david.shanske.com/2018/04/28/deprecating-and-replacing-bridgy-publish-for-wordpress/",
"syndication": [
"https://twitter.com/dshanske/status/990423991692288000",
"https://www.facebook.com/100002356503167/posts/1677710918984109"
],
"name": "Deprecating and Replacing Bridgy Publish for WordPress",
"content": {
"text": "I\u2019ve decided to take a different direction for the Bridgy plugin for WordPress. I\u2019ve never quite been able to explain to people it doesn\u2019t actually do anything. It\u2019s a user interface for the Bridgy service. I\u2019ve decided that the best thing to do is to is to change the approach radically.\nBridgy is a service that integrates with various sites\u2026Facebook, Flickr, Twitter, Github, and sends back comments, likes, etc to the original copies of the same posts on your site. There are a few similar services I\u2019ve integrated with. It also has a feature called Publish where it allows you to syndicate your posts to those services.\nThis is something of an arms race, as APIs change all the time. Sometimes, there is no official established API. Ryan Barrett, the creator of Bridgy, announced in a blog post this week that due to Facebook API changes scheduled to take effect on August 1st, the Publish features of Bridgy for Facebook would be discontinued at the same time.\nI\u2019m writing this partly to lay out my plan in my mind as I\u2019m working on writing this now. I\u2019ve gone through a few different versions of this idea before settling on this.\nThe Bridgy plugin consists of two parts: The first part is a UI that is added to the post editor that consists of a series of checkboxes, and the corresponding code that triggers the same action from a post made over Micropub. The second part was added last summer, and is basically a registration page for registering for Bridgy.\nI\u2019ve opened an issue for discussion on whether I should move the second part into the main Indieweb plugin. Newcomers to the Indieweb could install the plugin, register for Bridgy inside it, and instantly start getting backfeed from other sites.\nThat brings us to the first part. The checkboxes. They will need to be rewritten, if I want them to continue, for the new post editor, Gutenberg, at some point. But, I don\u2019t just want to syndicate via Bridgy. I want to syndicate to anywhere I can or choose to integrate in, both using the WordPress post editor and Micropub.\nSo, I\u2019ve decided to integrate the top level of this, the logic that gets a request for syndication from the post editor or Micropub, inside Syndication Links.\nSyndication Links displays icons which link to syndicated copies of posts. You\u2019ll see them on this post. I keep adding in integrations to other plugins as people ask. I have Mastodon Auto Post, Keyring Social Importer, Medium, Social Network Auto Poster, and a few more. And I\u2019ll likely continue to look at plugins that syndicate to other sites, figure out where they store their data, and display it as part of this plugin.\nBut now, this second part will expand the plugin into this territory of being a middleman for actually syndicating content. This is similar to what I did in Simple Location, where I have a series of providers for weather, location, maps, etc. and anyone could write a plugin(though only I have so far) that adds another provider.\nTo start, the first provider I\u2019ll be including will be a rewritten version of Bridgy Publish, as well as my plan to add Indienews, as both are triggered by sending a webmention to a site.\nAt the point that I finish the alternative with feature parity to the existing code, I will discontinue development on the separate Bridgy plugin. It will mean one less plugin to maintain. Anyone who does not want to use the new features in Syndication Links\u2026they will be off by default to start with.\nIt also means that, if I wanted to, I could add native publishing support for services in future. While there are certainly no end of Twitter/Facebook/etc plugins for WordPress, none of them quite understand syndicating a favorite to Twitter doesn\u2019t mean a new tweet, it means something else. I can continue to write integrations for other plugins, or add new providers myself.\nNot saying I\u2019m going to do that. I\u2019m only committing to what I\u2019ve said above.\nFinally, to all of you who liked the Bridgy Publish plugin\u2026I\u2019m curious to hear your comments on this. Bear in mind, I built the Bridgy Publish plugin to use it, and I still never migrated myself over to it. I would like to finally leave what I am using, and this would mean I could change providers without changing interfaces if I ever add something in future.",
"html": "<img src=\"https://aperture-media.p3k.io/brid.gy/cbec617f9ad918d9de2c086021c37ad959a0049366c2d8f375c03bb127cabfc7.jpg\" width=\"1024\" height=\"400\" alt=\"bridgy_logo.jpg\" /><p>I\u2019ve decided to take a different direction for the Bridgy plugin for WordPress. I\u2019ve never quite been able to explain to people it doesn\u2019t actually do anything. It\u2019s a user interface for the Bridgy service. I\u2019ve decided that the best thing to do is to is to change the approach radically.</p>\n<p>Bridgy is a service that integrates with various sites\u2026Facebook, Flickr, Twitter, Github, and sends back comments, likes, etc to the original copies of the same posts on your site. There are a few similar services I\u2019ve integrated with. It also has a feature called Publish where it allows you to syndicate your posts to those services.</p>\n<p>This is something of an arms race, as APIs change all the time. Sometimes, there is no official established API. Ryan Barrett, the creator of Bridgy, announced in a <a href=\"https://snarfed.org/2018-04-26_bridgy-publish-for-facebook-shuts-down-in-august\">blog post</a> this week that due to Facebook API changes scheduled to take effect on August 1st, the Publish features of Bridgy for Facebook would be discontinued at the same time.</p>\n<p>I\u2019m writing this partly to lay out my plan in my mind as I\u2019m working on writing this now. I\u2019ve gone through a few different versions of this idea before settling on this.</p>\n<p>The Bridgy plugin consists of two parts: The first part is a UI that is added to the post editor that consists of a series of checkboxes, and the corresponding code that triggers the same action from a post made over Micropub. The second part was added last summer, and is basically a registration page for registering for Bridgy.</p>\n<p>I\u2019ve opened an <a href=\"https://github.com/indieweb/wordpress-indieweb/issues/102\">issue</a> for discussion on whether I should move the second part into the main Indieweb plugin. Newcomers to the Indieweb could install the plugin, register for Bridgy inside it, and instantly start getting <a href=\"https://indieweb.org/backfeed\">backfeed</a> from other sites.</p>\n<p>That brings us to the first part. The checkboxes. They will need to be rewritten, if I want them to continue, for the new post editor, Gutenberg, at some point. But, I don\u2019t just want to syndicate via Bridgy. I want to syndicate to anywhere I can or choose to integrate in, both using the WordPress post editor and Micropub.</p>\n<p>So, I\u2019ve decided to integrate the top level of this, the logic that gets a request for syndication from the post editor or Micropub, inside <a href=\"https://wordpress.org/plugins/syndication-links/\">Syndication Links</a>.</p>\n<p>Syndication Links displays icons which link to syndicated copies of posts. You\u2019ll see them on this post. I keep adding in integrations to other plugins as people ask. I have Mastodon Auto Post, Keyring Social Importer, Medium, Social Network Auto Poster, and a few more. And I\u2019ll likely continue to look at plugins that syndicate to other sites, figure out where they store their data, and display it as part of this plugin.</p>\n<p>But now, this second part will expand the plugin into this territory of being a middleman for actually syndicating content. This is similar to what I did in Simple Location, where I have a series of providers for weather, location, maps, etc. and anyone could write a plugin(though only I have so far) that adds another provider.</p>\n<p>To start, the first provider I\u2019ll be including will be a rewritten version of Bridgy Publish, as well as my plan to add <a href=\"https://news.indieweb.org/\">Indienews</a>, as both are triggered by sending a webmention to a site.</p>\n<p>At the point that I finish the alternative with feature parity to the existing code, I will discontinue development on the separate Bridgy plugin. It will mean one less plugin to maintain. Anyone who does not want to use the new features in Syndication Links\u2026they will be off by default to start with.</p>\n<p>It also means that, if I wanted to, I could add native publishing support for services in future. While there are certainly no end of Twitter/Facebook/etc plugins for WordPress, none of them quite understand syndicating a favorite to Twitter doesn\u2019t mean a new tweet, it means something else. I can continue to write integrations for other plugins, or add new providers myself.</p>\n<p>Not saying I\u2019m going to do that. I\u2019m only committing to what I\u2019ve said above.</p>\n<p>Finally, to all of you who liked the Bridgy Publish plugin\u2026I\u2019m curious to hear your comments on this. Bear in mind, I built the Bridgy Publish plugin to use it, and I still never migrated myself over to it. I would like to finally leave what I am using, and this would mean I could change providers without changing interfaces if I ever add something in future.</p>"
},
"author": {
"type": "card",
"name": "David Shanske",
"url": "https://david.shanske.com/",
"photo": "https://aperture-media.p3k.io/secure.gravatar.com/ee1cea4a5d6465ac3bd8e56fc0bbfdacd25be40ef0968e6b2b2e8016103cb826.png"
},
"_id": "276407",
"_source": "5",
"_is_read": true
}
{
"type": "entry",
"published": "2018-04-28T19:09:50-04:00",
"url": "https://martymcgui.re/2018/04/28/190950/",
"category": [
"podcast",
"IndieWeb",
"this-week-indieweb-podcast"
],
"audio": [
"https://aperture-media.p3k.io/media.martymcgui.re/1b2d59b59dee7c6e4531d4f4282b0a66ca8e9baf5af6b1b7176111e7ef2d13b0.mp3"
],
"syndication": [
"https://huffduffer.com/schmarty/474116",
"https://twitter.com/schmarty/status/990369099753644032",
"https://www.facebook.com/marty.mcguire.54/posts/10211935034873209"
],
"name": "This Week in the IndieWeb Audio Edition \u2022 April 21st-27th, 2018",
"content": {
"text": "Show/Hide Transcript \n \n Readers on the rise, APIs on the decline, and Reddit regrets. It\u2019s the audio edition for This Week in the IndieWeb for April 21st - 27th, 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>Readers on the rise, APIs on the decline, and Reddit regrets. It\u2019s the audio edition for <a href=\"https://indieweb.org/this-week/2018-04-27.html\">This Week in the IndieWeb for April 21st - 27th, 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-media.p3k.io/martymcgui.re/4f9fac2b9e3ae62998c557418143efe288bca8170a119921a9c6bfeb0a1263a2.jpg"
},
"_id": "275710",
"_source": "175",
"_is_read": true
}
“I spent some time this morning doing a dry run through setting up a suite of IndieWeb plugins on a fresh WordPress installation. Going off of a scant outline I talked for almost two hours describing IndieWeb functionality as I set it all up.”
{
"type": "entry",
"published": "2018-04-28T13:45:34-04:00",
"url": "https://martymcgui.re/2018/04/28/134534/",
"category": [
"IndieWeb",
"WordPress",
"howto"
],
"bookmark-of": [
"http://boffosocko.com/2018/04/27/setting-up-wordpress-for-indieweb-use/"
],
"content": {
"text": "\ud83d\udd16 Bookmarked http://boffosocko.com/2018/04/27/setting-up-wordpress-for-indieweb-use/\n \n \n \n Setting up WordPress for IndieWeb use\n \n \n\u201cI spent some time this morning doing a dry run through setting up a suite of IndieWeb plugins on a fresh WordPress installation. Going off of a scant outline I talked for almost two hours describing IndieWeb functionality as I set it all up.\u201d",
"html": "\ud83d\udd16 Bookmarked <a class=\"u-bookmark-of\" href=\"http://boffosocko.com/2018/04/27/setting-up-wordpress-for-indieweb-use/\">http://boffosocko.com/2018/04/27/setting-up-wordpress-for-indieweb-use/</a>\n \n \n \n <a class=\"u-url p-name\" href=\"http://boffosocko.com/2018/04/27/setting-up-wordpress-for-indieweb-use/\">Setting up WordPress for IndieWeb use</a>\n \n <blockquote class=\"p-summary\">\n<p>\u201cI spent some time this morning doing a dry run through setting up a suite of IndieWeb plugins on a fresh WordPress installation. Going off of a scant outline I talked for almost two hours describing IndieWeb functionality as I set it all up.\u201d</p>\n</blockquote>"
},
"author": {
"type": "card",
"name": "Marty McGuire",
"url": "https://martymcgui.re/",
"photo": "https://aperture-media.p3k.io/martymcgui.re/4f9fac2b9e3ae62998c557418143efe288bca8170a119921a9c6bfeb0a1263a2.jpg"
},
"refs": {
"http://boffosocko.com/2018/04/27/setting-up-wordpress-for-indieweb-use/": {
"type": "entry",
"summary": "\u201cI spent some time this morning doing a dry run through setting up a suite of IndieWeb plugins on a fresh WordPress installation. Going off of a scant outline I talked for almost two hours describing IndieWeb functionality as I set it all up.\u201d",
"url": "http://boffosocko.com/2018/04/27/setting-up-wordpress-for-indieweb-use/",
"name": "Setting up WordPress for IndieWeb use"
}
},
"_id": "274926",
"_source": "175",
"_is_read": true
}
{
"type": "entry",
"published": "2018-04-28T08:48:38+0000",
"url": "http://known.kevinmarks.com/2018/its-clear-that-security-research-is-a",
"category": [
"Indieweb"
],
"syndication": [
"https://twitter.com/kevinmarks/status/990150789262852097"
],
"content": {
"text": "\u201cit\u2019s clear that security research is a form of user experience design. Design should reciprocate, and become a form of security research.\u201d https://ourdataourselves.tacticaltech.org/posts/30-on-weaponised-design/ #Indieweb",
"html": "\u201cit\u2019s clear that security research is a form of user experience design. Design should reciprocate, and become a form of security research.\u201d <a href=\"https://ourdataourselves.tacticaltech.org/posts/30-on-weaponised-design/\">https://ourdataourselves.tacticaltech.org/posts/30-on-weaponised-design/</a> <a href=\"http://known.kevinmarks.com/tag/Indieweb\" class=\"p-category\">#Indieweb</a>"
},
"author": {
"type": "card",
"name": "Kevin Marks",
"url": "http://known.kevinmarks.com/profile/kevinmarks",
"photo": "https://aperture-media.p3k.io/known.kevinmarks.com/f893d11435a62200ec9585e0ea3d84b2bdc478aa0a056dda35a43ce4c04d58a0.jpg"
},
"_id": "273696",
"_source": "205",
"_is_read": true
}
{
"type": "entry",
"published": "2018-04-26T16:26:51+00:00",
"url": "https://werd.io/2018/im-done-with-syndication-lets-help-people-be-themselves-on",
"syndication": [
"https://twitter.com/benwerd/status/989541325455396871"
],
"name": "I\u2019m done with syndication. Let\u2019s help people be themselves on the web.",
"content": {
"text": "The IndieWeb has long promoted the idea of POSSE: Publish on your Own Site, Syndicate Elsewhere. In the wake of the Cambridge Analytica scandal, lots of platforms are re-evaluating their API policies.This is kind of rearranging the deck chairs on the privacy Titanic, because the problem was that all this data was collected in one place, not that there was an API that allowed third party apps to publish on a user\u2019s behalf. (To be fair, the publish API possibly enabled algorithmic propaganda / marketing campaigns to operate more efficiently.)Still, here we are. I think this is a good opportunity to reconsider how the independent social web thinks of itself. I\u2019ve long stopped syndicating posts to Twitter, and instead just post there directly. But I do try and post anything of substance on my blog.POSSE requires participation from the networks. I think it might be more effective to move all the value away: publish on your own site, and use independent readers like Woodwind or Newsblur to consume content. Forget using social networks as the conduit. Let\u2019s go full indie.The effect of independence is practical, not just ideological: if you publish on your own site, your words are much more likely to stand the test of time and still be online years later. Social networks come and go, adjust their policies, etc. And there\u2019s a business value to being able to point to a single space online that holds your body of thought and work.Back when I was working on Known, investors would ask about the supplier risk of being so heavily dependent on third party APIs to provide a lot of the core value. They were right. Time to stop trying to integrate, and to double down on helping people own their own identities online in a way that helps them achieve their goals.",
"html": "<p style=\"color:#454545;\">The IndieWeb has long promoted the idea of POSSE: Publish on your Own Site, Syndicate Elsewhere. In the wake of the Cambridge Analytica scandal, lots of platforms are re-evaluating their API policies.</p><p style=\"color:#454545;\">This is kind of rearranging the deck chairs on the privacy Titanic, because the problem was that all this data was collected in one place, not that there was an API that allowed third party apps to publish on a user\u2019s behalf. (To be fair, the publish API possibly enabled algorithmic propaganda / marketing campaigns to operate more efficiently.)</p><p style=\"color:#454545;\">Still, here we are. I think this is a good opportunity to reconsider how the independent social web thinks of itself. I\u2019ve long stopped syndicating posts to Twitter, and instead just post there directly. But I do try and post anything of substance on my blog.</p><p style=\"color:#454545;\">POSSE requires participation from the networks. I think it might be more effective to move all the value away: publish on your own site, and use independent readers like Woodwind or Newsblur to consume content. Forget using social networks as the conduit. Let\u2019s go full indie.</p><p style=\"color:#454545;\">The effect of independence is practical, not just ideological: if you publish on your own site, your words are much more likely to stand the test of time and still be online years later. Social networks come and go, adjust their policies, etc. And there\u2019s a business value to being able to point to a single space online that holds your body of thought and work.</p><p style=\"color:#454545;\">Back when I was working on Known, investors would ask about the supplier risk of being so heavily dependent on third party APIs to provide a lot of the core value. They were right. Time to stop trying to integrate, and to double down on helping people own their own identities online in a way that helps them achieve their goals.</p>"
},
"author": {
"type": "card",
"name": "Ben Werdm\u00fcller",
"url": "https://werd.io/profile/benwerd",
"photo": "https://aperture-media.p3k.io/werd.io/a9fdaf4aeac1df38b1efb7ba304eca77f4e32caf8b0ca6652431d0e1abc06145.jpg"
},
"_id": "269994",
"_source": "191",
"_is_read": true
}
{
"type": "entry",
"published": "2018-04-27T00:23:38+00:00",
"url": "http://stream.boffosocko.com/2018/indiewebasaservice-anyone-this-sounds-like-the-kind-of-thing-schnarfed",
"category": [
"indiewebasaservice"
],
"syndication": [
"https://twitter.com/ChrisAldrich/status/989661331027578880"
],
"content": {
"text": "#indiewebasaservice anyone? This sounds like the kind of thing @schnarfed will show up with at camp and it'll be fully built out using WebSub. \nhttps://twitter.com/mattmaldre/status/984800729973100544",
"html": "<a href=\"http://stream.boffosocko.com/tag/indiewebasaservice\" class=\"p-category\">#indiewebasaservice</a> anyone? This sounds like the kind of thing @schnarfed will show up with at camp and it'll be fully built out using WebSub. <br /><a href=\"https://twitter.com/mattmaldre/status/984800729973100544\">https://twitter.com/mattmaldre/status/984800729973100544</a>"
},
"author": {
"type": "card",
"name": "Chris Aldrich",
"url": "http://stream.boffosocko.com/profile/chrisaldrich",
"photo": "https://aperture-media.p3k.io/stream.boffosocko.com/d0ba9f65fcbf0cef3bdbcccc0b6a1f42b1310f7ab2e07208c7a396166cde26b1.jpg"
},
"_id": "269485",
"_source": "192",
"_is_read": true
}
@rustybrick I won't presume to speak for @martijnvdven, but if he's had the same experience I've had with @disqus, their system tends to mark anything with a useful link in it as spam and one's (considered) responses are thus moderated out of existence. It's far better to write and own your response on your own site as he has.
It looks like @martijnvdven's site sends and receives webmentions (a W3C recommended spec), so if @seroundtable's site did (or Disqus did on its behalf), then the comment would exist both on Martjin's site as well as SER's as well.I suspect that since your site doesn't, he used Twitter to push across the notification so you'd be aware.
It might be more useful for @seroundtable to provide links to portions of their conversations/content (like the one I'm replying to on Twitter) syndicated to other platforms like Twitter on the site (similar to the way you did for the "forum discussion"), so they're easier to find and participate in--especially for those who don't want to sign up for a Disqus account.
{
"type": "entry",
"published": "2018-04-26T20:52:06+00:00",
"url": "http://stream.boffosocko.com/2018/rustybrick-i-wont-presume-to-speak-for-martijnvdven-but-if",
"syndication": [
"https://twitter.com/ChrisAldrich/status/989608086829699073"
],
"in-reply-to": [
"https://twitter.com/rustybrick/status/989550469948297217"
],
"content": {
"text": "@rustybrick I won't presume to speak for @martijnvdven, but if he's had the same experience I've had with @disqus, their system tends to mark anything with a useful link in it as spam and one's (considered) responses are thus moderated out of existence. It's far better to write and own your response on your own site as he has.\n\n\nIt looks like @martijnvdven's site sends and receives webmentions (a W3C recommended spec), so if @seroundtable's site did (or Disqus did on its behalf), then the comment would exist both on Martjin's site as well as SER's as well.I suspect that since your site doesn't, he used Twitter to push across the notification so you'd be aware.\n\n\nIt might be more useful for @seroundtable to provide links to portions of their conversations/content (like the one I'm replying to on Twitter) syndicated to other platforms like Twitter on the site (similar to the way you did for the \"forum discussion\"), so they're easier to find and participate in--especially for those who don't want to sign up for a Disqus account.",
"html": "<a href=\"https://twitter.com/rustybrick\">@rustybrick</a> I won't presume to speak for <a href=\"https://twitter.com/martijnvdven\">@martijnvdven</a>, but if he's had the same experience I've had with <a href=\"https://twitter.com/disqus\">@disqus</a>, their system tends to mark anything with a useful link in it as spam and one's (considered) responses are thus moderated out of existence. It's far better to write and own your response on your own site as he has.<br /><br />\nIt looks like <a href=\"https://twitter.com/martijnvdven\">@martijnvdven</a>'s site sends and receives webmentions (a W3C recommended spec), so if <a href=\"https://twitter.com/seroundtable\">@seroundtable</a>'s site did (or Disqus did on its behalf), then the comment would exist both on Martjin's site as well as SER's as well.I suspect that since your site doesn't, he used Twitter to push across the notification so you'd be aware.<br /><br />\nIt might be more useful for <a href=\"https://twitter.com/seroundtable\">@seroundtable</a> to provide links to portions of their conversations/content (like the one I'm replying to on Twitter) syndicated to other platforms like Twitter on the site (similar to the way you did for the \"forum discussion\"), so they're easier to find and participate in--especially for those who don't want to sign up for a Disqus account."
},
"author": {
"type": "card",
"name": "Chris Aldrich",
"url": "http://stream.boffosocko.com/profile/chrisaldrich",
"photo": "https://aperture-media.p3k.io/stream.boffosocko.com/d0ba9f65fcbf0cef3bdbcccc0b6a1f42b1310f7ab2e07208c7a396166cde26b1.jpg"
},
"_id": "269486",
"_source": "192",
"_is_read": true
}
I was flying home yesterday, and one of the habits I've got into is loading a bunch of content into my reader before putting my phone in flight mode. Unfortunately I got distracted early into the flight and brushed a button on my phone, which needlessly triggers loading the previous page in the browser.
I store content in local storage, so it's pretty annoying to know it's still there but I can't access it. Adding support for offline mode and service workers to my website just moved up the priority list slightly.
{
"type": "entry",
"published": "2018-04-26T11:05:18+10:00",
"url": "https://unicyclic.com/mal/2018-04-26-I_was_flying_home_yesterday_and_one_of_the_habits",
"category": [
"itches",
"indieweb"
],
"content": {
"text": "I was flying home yesterday, and one of the habits I've got into is loading a bunch of content into my reader before putting my phone in flight mode. Unfortunately I got distracted early into the flight and brushed a button on my phone, which needlessly triggers loading the previous page in the browser.\n\n\nI store content in local storage, so it's pretty annoying to know it's still there but I can't access it. Adding support for offline mode and service workers to my website just moved up the priority list slightly.",
"html": "I was flying home yesterday, and one of the habits I've got into is loading a bunch of content into my reader before putting my phone in flight mode. Unfortunately I got distracted early into the flight and brushed a button on my phone, which needlessly triggers loading the previous page in the browser.<br /><br />\nI store content in local storage, so it's pretty annoying to know it's still there but I can't access it. Adding support for offline mode and service workers to my website just moved up the priority list slightly."
},
"author": {
"type": "card",
"name": "Malcolm Blaney",
"url": "https://unicyclic.com/mal",
"photo": "https://aperture-media.p3k.io/unicyclic.com/bdad1528925264a15ecd0bdb92bdc5836d965b0d5f4db8797489eec259fa32de.png"
},
"_id": "269412",
"_source": "243",
"_is_read": true
}
In March I said I was leaving Facebook but I hadn’t set a date. Because of Facebook’s API changes that will stop me from posting from my website, I will no longer be posting on Facebook as of August 1st #deleteFacebook#indieweb
{
"type": "entry",
"published": "2018-04-26T00:55:00-04:00",
"summary": "In March I said I was leaving Facebook but I hadn\u2019t set a date. Because of Facebook\u2019s API changes that will stop me from posting from my website, I will no longer be posting on Facebook as of August 1st #deleteFacebook #indieweb",
"url": "https://eddiehinkle.com/2018/04/26/3/note/",
"category": [
"silo-quit",
"Facebook",
"deleteFacebook",
"indieweb"
],
"content": {
"text": "In March I said I was leaving Facebook but I hadn\u2019t set a date. Because of Facebook\u2019s API changes that will stop me from posting from my website, I will no longer be posting on Facebook as of August 1st #deleteFacebook #indieweb",
"html": "<p>In March <a href=\"https://eddiehinkle.com/2018/03/22/5/article/\">I said I was leaving Facebook</a> but I hadn\u2019t set a date. Because of Facebook\u2019s API changes that will stop me from posting from my website, I will no longer be posting on Facebook as of August 1st <a href=\"https://eddiehinkle.com/tag/deleteFacebook/\">#deleteFacebook</a> <a href=\"https://eddiehinkle.com/tag/indieweb/\">#indieweb</a></p>"
},
"author": {
"type": "card",
"name": "Eddie Hinkle",
"url": "https://eddiehinkle.com/",
"photo": "https://aperture-media.p3k.io/eddiehinkle.com/cf9f85e26d4be531bc908d37f69bff1c50b50b87fd066b254f1332c3553df1a8.jpg"
},
"_id": "266235",
"_source": "226",
"_is_read": true
}
Inspired by Tweetbot, I have reply if you swipe from left to right and conversation/detailed view if you swipe right to left on my IndieWeb reader app. As a Tweetbot fan, that feels very natural to me
{
"type": "entry",
"published": "2018-04-25T10:28:26-04:00",
"summary": "Inspired by Tweetbot, I have reply if you swipe from left to right and conversation/detailed view if you swipe right to left on my IndieWeb reader app. As a Tweetbot fan, that feels very natural to me",
"url": "https://eddiehinkle.com/2018/04/25/2/reply/",
"in-reply-to": [
"https://micro.blog/hartlco/510197"
],
"content": {
"text": "Inspired by Tweetbot, I have reply if you swipe from left to right and conversation/detailed view if you swipe right to left on my IndieWeb reader app. As a Tweetbot fan, that feels very natural to me",
"html": "<p>Inspired by Tweetbot, I have reply if you swipe from left to right and conversation/detailed view if you swipe right to left on my IndieWeb reader app. As a Tweetbot fan, that feels very natural to me</p>"
},
"author": {
"type": "card",
"name": "Eddie Hinkle",
"url": "https://eddiehinkle.com/",
"photo": "https://aperture-media.p3k.io/eddiehinkle.com/cf9f85e26d4be531bc908d37f69bff1c50b50b87fd066b254f1332c3553df1a8.jpg"
},
"refs": {
"https://micro.blog/hartlco/510197": {
"type": "entry",
"url": "https://micro.blog/hartlco/510197",
"name": "https://micro.blog/hartlco/510197"
}
},
"_id": "263995",
"_source": "226",
"_is_read": true
}
{
"type": "entry",
"published": "2018-04-24T06:43:06-04:00",
"url": "https://david.shanske.com/2018/04/24/how-i-set-up-my-indieweb-wordpress-site-2018-edition/",
"syndication": [
"https://www.facebook.com/100002356503167/posts/1673006202787914",
"https://twitter.com/dshanske/status/988730048013324288"
],
"name": "How I Set Up My Indieweb WordPress Site \u2013 2018 Edition",
"content": {
"text": "This is an update to my 2014 article on how I set up my WordPress site. It was requested I update it.\n\nStandard Plugins\n\n\nCharacter Count for Post Content and Excerpt(Link) \u2013 Because I need to be aware of the 140 character limit of Twitter, one of the services I send my content to, I need to know the character count of what I\u2019m typing. This adds that to my editing screen. No longer using this plugin and could not find a replacement.\nEWWW Image Optimizer(Link) \u2013 It reduces file sizes for images to ensure faster loading\nPushover Notifications(Link)or the forked alternative Pushbullet Notifications(Link) for WordPress \u2013 This plugin sends notifications of site events to my phone. The Pushover version is actively maintained and allows for extensions.\nSimple Local Avatars(Link) \u2013 Overrides the default of using the Gravatar service for profile pictures to storing them locally. However, this plugin hasn\u2019t been updated in years. May look for a new one.\n\nWordPress SEO by Yoast(Link) \u2013 While I\u2019m not obsessive about Search Engine Optimization, I find this plugin assists in my writing by reminding me about the importance of certain elements. While this is still a popular plugin and good for many people, it\u2019s become a bit too aggressive for me.\nThe SEO Framework (Link) \u2013 Sometimes, I think about getting rid of all SEO plugins. I\u2019m not really obsessed with this. This does add non-Indieweb markup for some sites that require it. It isn\u2019t worth it for me to manually add this right now.\nHum(Link) \u2013 This is a simple URL shortener. So for each post, there is an equivalent URL address at di5.us. This allows me to give out easier to enter links to longer post titles.\nJSON Feed(Link) \u2013 Adds a JSON Feed to a WordPress site. This is an alternative to RSS as a feed. I\u2019ve used it to feed my content to Micro.blog more effectively, as the specification was co-created by Manton Reece, who is the creator of that service. The plugin could stand some enhancement.\nSeries(Link) \u2013 Creates a simple taxonomy called \u2018Series\u2019. I added this to my site to allow creating series of articles.\nWP Photo Sphere(Link) \u2013 For the rare occasions that I post 360 degree images. Rare as in I\u2019ve only posted one.\nSocial Network Auto Poster(Link) \u2013 I keep wanting to get rid of this thing. But I haven\u2019t spent the time to replace it. Thinking of doing that soon.\nSimple Location(Link) \u2013 You can call this an Indieweb plugin, but it isn\u2019t specifically an Indieweb technology(although it does use Microformats markup). It adds location and weather awareness to a post. So, you can click to add your location and the current weather conditions at that location to a post.\nHome Assistant for WordPress(Link) \u2013 I use Home Assistant for my Home Automation integration. Since it has an API, I wrote this simple plugin. While at the moment, I hope to add the ability to display information from any sensor and to update a sensor on the Home Assistant side from WordPress, I use it right now as an enhancement to Simple Location. Instead of getting my location from the browser, it gets it from my Home Assistant installation, which tracks my presence.\nThe Indieweb Stuff\nWordPress Webmention(Link) \u2013 Adds webmention support for WordPress. This allows communications between sites.\nSemantic Linkbacks(Link) \u2013 Adds richer content to WordPress comments received by Webmention. For example, interprets them as reply, repost, like, favorite, mention, etc. This allows different displays and actions to be done with them.\n\nSemantic Comments(Link) \u2013 One of my own plugins. It changes the display of WordPress comments based on the information from Semantic Linkbacks. It presents the profile pictures in a Facepile for the various types of mentions with the comments separately below. This functionality has now been rolled into Semantic Linkbacks and is even better than it was.\n\nIndieweb Taxonomy(Link) \u2013 Semantic Linkbacks is all about receiving webmentions for the various semantic types. But this plugin, another one of mine(although I credit several with contributions), adds new terms to WordPress posts for responding to content on another site. So, a post on this site can be a reply to another site, a like, etc. It will automatically send a webmention to the other site, if that site supports it, of course. Replaced by Post Kinds\nPost Kinds (Link) \u2013 This replaced Indieweb Taxonomy. It is a replacement for the WordPress Post Formats which uses Indieweb post types. It allows you to respond to content on other sites, generates previews of those sites for context, allows you to post activity type posts(like watching, listening, reading, etc).\nSyndication Links(Link) \u2013 Another project, which adds fields to a post for the corresponding versions on other networks. It also adds links to same to the post.\n\nH-Card Tools \u2013 Still under development and not yet available for download, this is just the profile widget marked up appropriately, in the sidebar of the site. Some of this was rolled into the Indieweb plugin\nIndieweb Plugin(Link) \u2013 The Indieweb plugin is not only a plugin installer, but it contains tools for adding rel-me links based on your profile, declaring the default author for your site, and adding a simple h-card widget to show off a primary author.\nA Few Choices\nThere is an alternative to my Syndication Links plugin\u2026a plugin called WordPress Syndication (Link). \u00a0It automatically adds the links to the post, and extracts the data from a variety of sources that post to other sites. This includes NextScripts Social Network Auto-Poster(Link) or Mailchimp\u2019s Social plugin(Link), and even Bridgy(we\u2019ll get back to Bridgy in a moment).\nThe theme I use is a custom one I built, but the most popular theme for Indieweb sites is Sempress(Link). My theme isn\u2019t quite refined, but if you want it, a copy can be downloaded here. The version in use on my site is just a colored version of the minimal style the theme offers. I am currently using a fork of the WordPress Twenty-Sixteen theme(link) I modified for Microformats and support of the plugins I use.\nBridgy\nBridgy is not a WordPress plugin, or something you need to install(although you can host it yourself). Bridgy now has a WordPress plugin(link) which acts as a UI for registering and posting to Bridgy. Oddly enough, I wrote the plugin, but don\u2019t actively use it. I need to fix my handling of syndication.\nBridgy is a service that you can link your accounts on places like Twitter, Github and Facebook to, and it will pull in comments, likes, etc from those sites and send them to your site to be integrated. This requires the Webmention and Semantic Linkback plugins to understand what is being sent.\nTo the Future\nI enjoy developing this site as a learning tool. I hadn\u2019t done much WordPress development before this and it is very useful to know.\nFor anyone who comes here considering trying my setup, I\u2019m always available to help. For those who are trying my plugins\u2026they are still being refined, but feedback and contributions(of code) are appreciated.\nThis site is under development, so it does change regularly. I will often summarize some of the changes with a post, but sometimes not.",
"html": "<p class=\"p-name\"><em>This is an update to my 2014 <a href=\"https://david.shanske.com/2014/10/02/site-setup/\">article</a> on how I set up my WordPress site. It was requested I update it.</em></p>\n\n<h2 class=\"e-content\">Standard Plugins</h2>\n\n<ol><li>\n<del>Character Count for Post Content and Excerpt(<a href=\"https://wordpress.org/plugins/character-count-for-post-content-excerpt/\">Link</a>) \u2013 Because I need to be aware of the 140 character limit of Twitter, one of the services I send my content to, I need to know the character count of what I\u2019m typing. This adds that to my editing screen.</del> No longer using this plugin and could not find a replacement.</li>\n<li>EWWW Image Optimizer(<a href=\"https://wordpress.org/plugins/ewww-image-optimizer/\">Link</a>) \u2013 It reduces file sizes for images to ensure faster loading</li>\n<li>Pushover Notifications(<a href=\"https://wordpress.org/plugins/pushover-notifications/changelog/\">Link</a>)or the forked alternative Pushbullet Notifications(<a href=\"https://wordpress.org/plugins/pushbullet-notification/\">Link</a>) for WordPress \u2013 This plugin sends notifications of site events to my phone. The Pushover version is actively maintained and allows for extensions.</li>\n<li>Simple Local Avatars(<a href=\"https://wordpress.org/plugins/simple-local-avatars/\">Link</a>) \u2013 Overrides the default of using the Gravatar service for profile pictures to storing them locally. However, this plugin hasn\u2019t been updated in years. May look for a new one.</li>\n<li>\n<del>WordPress SEO by Yoast(<a href=\"https://wordpress.org/plugins/wordpress-seo/\">Link</a>) \u2013 While I\u2019m not obsessive about Search Engine Optimization, I find this plugin assists in my writing by reminding me about the importance of certain elements.</del> While this is still a popular plugin and good for many people, it\u2019s become a bit too aggressive for me.</li>\n<li>The SEO Framework (<a href=\"https://wordpress.org/plugins/autodescription/\">Link</a>) \u2013 Sometimes, I think about getting rid of all SEO plugins. I\u2019m not really obsessed with this. This does add non-Indieweb markup for some sites that require it. It isn\u2019t worth it for me to manually add this right now.</li>\n<li>Hum(<a href=\"https://wordpress.org/plugins/hum/\">Link</a>) \u2013 This is a simple URL shortener. So for each post, there is an equivalent URL address at di5.us. This allows me to give out easier to enter links to longer post titles.</li>\n<li>JSON Feed(<a href=\"https://wordpress.org/plugins/jsonfeed/\">Link</a>) \u2013 Adds a JSON Feed to a WordPress site. This is an alternative to RSS as a feed. I\u2019ve used it to feed my content to Micro.blog more effectively, as the specification was co-created by Manton Reece, who is the creator of that service. The plugin could stand some enhancement.</li>\n<li>Series(<a href=\"https://wordpress.org/plugins/series/\">Link</a>) \u2013 Creates a simple taxonomy called \u2018Series\u2019. I added this to my site to allow creating series of articles.</li>\n<li>WP Photo Sphere(<a href=\"https://wordpress.org/plugins/wp-photo-sphere/\">Link</a>) \u2013 For the rare occasions that I post 360 degree images. Rare as in I\u2019ve only posted one.</li>\n<li>Social Network Auto Poster(<a href=\"https://wordpress.org/plugins/social-networks-auto-poster-facebook-twitter-g/\">Link</a>) \u2013 I keep wanting to get rid of this thing. But I haven\u2019t spent the time to replace it. Thinking of doing that soon.</li>\n<li>Simple Location(<a href=\"https://wordpress.org/plugins/simple-location\">Link</a>) \u2013 You can call this an Indieweb plugin, but it isn\u2019t specifically an Indieweb technology(although it does use Microformats markup). It adds location and weather awareness to a post. So, you can click to add your location and the current weather conditions at that location to a post.</li>\n<li>Home Assistant for WordPress(<a href=\"https://github.com/dshanske/wordpress-homeassistant\">Link</a>) \u2013 I use <a href=\"https://home-assistant.io/\">Home Assistant</a> for my Home Automation integration. Since it has an API, I wrote this simple plugin. While at the moment, I hope to add the ability to display information from any sensor and to update a sensor on the Home Assistant side from WordPress, I use it right now as an enhancement to Simple Location. Instead of getting my location from the browser, it gets it from my Home Assistant installation, which tracks my presence.</li>\n</ol><h2>The Indieweb Stuff</h2>\n<ul><li>WordPress Webmention(<a href=\"https://wordpress.org/plugins/webmention/\">Link</a>) \u2013 Adds webmention support for WordPress. This allows communications between sites.</li>\n<li>Semantic Linkbacks(<a href=\"https://wordpress.org/plugins/semantic-linkbacks/\">Link</a>) \u2013 Adds richer content to WordPress comments received by Webmention. For example, interprets them as reply, repost, like, favorite, mention, etc. This allows different displays and actions to be done with them.</li>\n<li>\n<del>Semantic Comments(<a href=\"https://david.shanske.com/projects/indieweb/semantic-comments/\">Link</a>) \u2013 One of my own plugins. It changes the display of WordPress comments based on the information from Semantic Linkbacks. It presents the profile pictures in a Facepile for the various types of mentions with the comments separately below.</del> This functionality has now been rolled into Semantic Linkbacks and is even better than it was.</li>\n<li>\n<del>Indieweb Taxonomy(<a href=\"https://david.shanske.com/projects/indieweb/indieweb-taxonomy/\">Link</a>) \u2013 Semantic Linkbacks is all about receiving webmentions for the various semantic types. But this plugin, another one of mine(although I credit several with contributions), adds new terms to WordPress posts for responding to content on another site. So, a post on this site can be a reply to another site, a like, etc. It will automatically send a webmention to the other site, if that site supports it, of course. </del>Replaced by Post Kinds</li>\n<li>Post Kinds (<a href=\"https://wordpress.org/plugins/indieweb-post-kinds/\">Link</a>) \u2013 This replaced Indieweb Taxonomy. It is a replacement for the WordPress Post Formats which uses Indieweb post types. It allows you to respond to content on other sites, generates previews of those sites for context, allows you to post activity type posts(like watching, listening, reading, etc).</li>\n<li>Syndication Links(<a href=\"https://wordpress.org/plugins/syndication-links\">Link</a>) \u2013 Another project, which adds fields to a post for the corresponding versions on other networks. It also adds links to same to the post.</li>\n<li>\n<del>H-Card Tools \u2013 Still under development and not yet available for download, this is just the profile widget marked up appropriately, in the sidebar of the site. </del>Some of this was rolled into the Indieweb plugin</li>\n<li>Indieweb Plugin(<a href=\"https://wordpress.org/plugins/indieweb/\">Link</a>) \u2013 The Indieweb plugin is not only a plugin installer, but it contains tools for adding rel-me links based on your profile, declaring the default author for your site, and adding a simple h-card widget to show off a primary author.</li>\n</ul><h2>A Few Choices</h2>\n<ul><li>There is an alternative to my Syndication Links plugin\u2026a plugin called WordPress Syndication (<a href=\"https://github.com/jihaisse/wordpress-syndication\">Link</a>). \u00a0It automatically adds the links to the post, and extracts the data from a variety of sources that post to other sites. This includes NextScripts Social Network Auto-Poster(<a href=\"https://wordpress.org/plugins/social-networks-auto-poster-facebook-twitter-g/\">Link</a>) or Mailchimp\u2019s Social plugin(<a href=\"https://wordpress.org/plugins/social/\">Link</a>), and even Bridgy(we\u2019ll get back to Bridgy in a moment).</li>\n<li>The theme I use is a custom one I built, but the most popular theme for Indieweb sites is Sempress(<a href=\"https://wordpress.org/themes/sempress\">Link</a>). My theme isn\u2019t quite refined, but if you want it, <del>a copy can be downloaded <a href=\"https://github.com/dshanske/mf2_bootstrap\">here</a>. The version in use on my site is just a colored version of the minimal style the theme offers.</del> I am currently using a fork of the WordPress Twenty-Sixteen theme(<a href=\"https://github.com/dshanske/twentysixteen-indieweb\">link</a>) I modified for Microformats and support of the plugins I use.</li>\n</ul><h2>Bridgy</h2>\n<p><a href=\"https://www.brid.gy/\">Bridgy</a> is <del>not a WordPress plugin, or something you need to install(although you can host it yourself)</del>. Bridgy now has a WordPress plugin(<a href=\"https://wordpress.org/plugins/bridgy-publish/\">link</a>) which acts as a UI for registering and posting to Bridgy. Oddly enough, I wrote the plugin, but don\u2019t actively use it. I need to fix my handling of syndication.</p>\n<p>Bridgy is a service that you can link your accounts on places like Twitter, Github and Facebook to, and it will pull in comments, likes, etc from those sites and send them to your site to be integrated. This requires the Webmention and Semantic Linkback plugins to understand what is being sent.</p>\n<h2>To the Future</h2>\n<p>I enjoy developing this site as a learning tool. I hadn\u2019t done much WordPress development before this and it is very useful to know.</p>\n<p>For anyone who comes here considering trying my setup, I\u2019m always available to help. For those who are trying my plugins\u2026they are still being refined, but feedback and contributions(of code) are appreciated.</p>\n<p>This site is under development, so it does change regularly. I will often summarize some of the changes with a post, but sometimes not.</p>"
},
"author": {
"type": "card",
"name": "David Shanske",
"url": "https://david.shanske.com/",
"photo": "https://aperture-media.p3k.io/secure.gravatar.com/ee1cea4a5d6465ac3bd8e56fc0bbfdacd25be40ef0968e6b2b2e8016103cb826.png"
},
"_id": "260654",
"_source": "5",
"_is_read": true
}
{
"type": "entry",
"author": {
"name": "Kh\u00fcrt Williams",
"url": "https://islandinthenet.com/",
"photo": null
},
"url": "https://islandinthenet.com/congrats-chris/",
"published": "2018-04-23T23:07:33+00:00",
"content": {
"html": "<p><a href=\"https://islandinthenet.com/\">Island in the Net - A personal website by Kh\u00fcrt Williams, with imagery, and inchoate ramblings on coffee, beer, and geekery.</a></p>\n\n\n\n<a href=\"http://boffosocko.com/2018/04/23/9000-comments-and-reactions/\">Chris Aldrich</a> by <a href=\"http://www.boffosocko.com/\"><img src=\"http://1.gravatar.com/avatar/d5fb4e498fe609cc29b04e5b7ad688c4?s=49&d=mm&r=pg\" alt=\"Congrats, Chris! %name\" title=\"Congrats, Chris!\" />Chris Aldrich</a><em> (Chris Aldrich | BoffoSocko)</em>\n<blockquote>Today, with the help of Webmention and tools like Brid.gy, I\u2019ve just passed the 9,000 reactions mark (and added many new friends in the process)!</blockquote>\n\nCongrats, Chris!\n<p>The post <a href=\"https://islandinthenet.com/congrats-chris/\">Congrats, Chris!</a> by <a href=\"https://islandinthenet.com/\">Kh\u00fcrt Williams</a> appeared first on <a href=\"https://islandinthenet.com/\">Island in the Net</a>.</p>",
"text": "Island in the Net - A personal website by Kh\u00fcrt Williams, with imagery, and inchoate ramblings on coffee, beer, and geekery.\n\n\n\nChris Aldrich by Chris Aldrich (Chris Aldrich | BoffoSocko)\nToday, with the help of Webmention and tools like Brid.gy, I\u2019ve just passed the 9,000 reactions mark (and added many new friends in the process)!\n\nCongrats, Chris!\nThe post Congrats, Chris! by Kh\u00fcrt Williams appeared first on Island in the Net."
},
"name": "Congrats, Chris!",
"_id": "258176",
"_source": "242",
"_is_read": true
}
@johnbrayton Adding Microsub servers would be an excellent addition to Unread! Microsub is a client-Server communication spec that allows for people to host their own RSS feeds and use different clients to see the data: https://indieweb.org/Microsub-spec
{
"type": "entry",
"published": "2018-04-23T18:06:11-04:00",
"summary": "@johnbrayton Adding Microsub servers would be an excellent addition to Unread! Microsub is a client-Server communication spec that allows for people to host their own RSS feeds and use different clients to see the data: https://indieweb.org/Microsub-spec",
"url": "https://eddiehinkle.com/2018/04/23/20/note/",
"category": [
"Microsub",
"indieweb"
],
"content": {
"text": "@johnbrayton Adding Microsub servers would be an excellent addition to Unread! Microsub is a client-Server communication spec that allows for people to host their own RSS feeds and use different clients to see the data: https://indieweb.org/Microsub-spec",
"html": "<p><a href=\"https://micro.blog/johnbrayton\">@johnbrayton</a> Adding Microsub servers would be an excellent addition to Unread! Microsub is a client-Server communication spec that allows for people to host their own RSS feeds and use different clients to see the data: <a href=\"https://indieweb.org/Microsub-spec\">https://indieweb.org/Microsub-spec</a></p>"
},
"author": {
"type": "card",
"name": "Eddie Hinkle",
"url": "https://eddiehinkle.com/",
"photo": "https://aperture-media.p3k.io/eddiehinkle.com/cf9f85e26d4be531bc908d37f69bff1c50b50b87fd066b254f1332c3553df1a8.jpg"
},
"_id": "258146",
"_source": "226",
"_is_read": true
}
