Marty McGuire
{
"type": "entry",
"published": "2018-11-06T04:02:28-05:00",
"url": "https://martymcgui.re/2018/11/06/040228/",
"category": [
"IndieWeb",
"comic"
],
"content": {
"text": "Oh gosh this IndieWeb comic by yulia is simply delightful:\nhttp://hag.codes/social/2018/11/05/indieweb-comic.html",
"html": "<p>Oh gosh this IndieWeb comic by <a href=\"http://hag.codes/\">yulia</a> is simply delightful:</p>\n<p><a href=\"http://hag.codes/social/2018/11/05/indieweb-comic.html\">http://hag.codes/social/2018/11/05/indieweb-comic.html</a></p>"
},
"author": {
"type": "card",
"name": "Marty McGuire",
"url": false,
"photo": "https://aperture-proxy.p3k.io/8275f85e3a389bd0ae69f209683436fc53d8bad9/68747470733a2f2f6d617274796d636775692e72652f696d616765732f6c6f676f2e6a7067"
},
"post-type": "note",
"_id": "1352003",
"_source": "175",
"_is_read": true
}
{
"type": "entry",
"published": "2018-11-06T02:53:56+0000",
"url": "http://known.kevinmarks.com/2018/sending-webmentions-for-all-links-in-mentiontech-indieweb-yesvember",
"name": "sending webmentions for all links in mention.tech #indieweb #yesvember",
"content": {
"text": "A while back I built\u00a0mention.tech\u00a0which is a webmention sending tool with a couple of differences - you\u00a0can set it as your webmention endpoint, and it will pass through webmentions, but it will also cache the mentions itself, in case the linked URL doesn't have an endpoint.What it didn't have was a way to look for all outbound mentions and send them for a post, so I added that tonight. It may need to work more carefully wiht h-feeds, but with an h-entry it should be OK.Try it out at\u00a0mention.tech/mentionall\u00a0",
"html": "<p>A while back I built\u00a0<a href=\"https://mention.tech/\">mention.tech</a>\u00a0which is a webmention sending tool with a couple of differences - you\u00a0can set it as your webmention endpoint, and it will pass through webmentions, but it will also <a href=\"https://mention.tech/listmentions?target=https%3A%2F%2Fmention.tech%2Fmentionall\">cache the mentions itself</a>, in case the linked URL doesn't have an endpoint.</p><p>What it didn't have was a way to look for all outbound mentions and send them for a post, so I added that tonight. It may need to work more carefully wiht h-feeds, but with an h-entry it should be OK.</p><p>Try it out at\u00a0<a href=\"https://mention.tech/mentionall\">mention.tech/mentionall</a></p><p>\u00a0</p>"
},
"author": {
"type": "card",
"name": "Kevin Marks",
"url": "http://known.kevinmarks.com/profile/kevinmarks",
"photo": "https://aperture-proxy.p3k.io/ed7979fd10a648fc253eae0b54e66fb36e57d3d4/687474703a2f2f6b6e6f776e2e6b6576696e6d61726b732e636f6d2f66696c652f3932353536353636363931373362373836376162383339656536353536663965"
},
"post-type": "article",
"_id": "1350046",
"_source": "205",
"_is_read": true
}
{
"type": "entry",
"author": {
"name": "Kh\u00fcrt Williams",
"url": "https://islandinthenet.com/",
"photo": null
},
"url": "https://islandinthenet.com/2018-11-05-20-40-51/",
"published": "2018-11-06T01:40:51+00:00",
"content": {
"html": "<p>Test 1 Test 2 Test 3 Test 4 Test 5 Test 6 Test 7 Test 8 Test 9 Test 10 Test 11 Test 12 Test 13 Test 14 Test 15 Test 16 Test 17 Test 18 Test 19 Test 20 Test 21 Test 22 Test 23 https://webmention.rocks/update/1/part/2</p>",
"text": "Test 1 Test 2 Test 3 Test 4 Test 5 Test 6 Test 7 Test 8 Test 9 Test 10 Test 11 Test 12 Test 13 Test 14 Test 15 Test 16 Test 17 Test 18 Test 19 Test 20 Test 21 Test 22 Test 23 https://webmention.rocks/update/1/part/2"
},
"name": "2018-11-05 20.40.51",
"post-type": "article",
"_id": "1349419",
"_source": "242",
"_is_read": true
}
No matter what happens tomorrow, the next day there will still be work to do on Micro.blog and the IndieWeb. Join us Wednesday for Homebrew Website Club in Austin. 6:30pm at Mozart’s Coffee!
{
"type": "entry",
"author": {
"name": null,
"url": "https://www.manton.org/",
"photo": null
},
"url": "https://www.manton.org/2018/11/05/223922.html",
"content": {
"html": "<p>No matter what happens tomorrow, the next day there will still be work to do on Micro.blog and the IndieWeb. Join us Wednesday for Homebrew Website Club in Austin. 6:30pm at Mozart\u2019s Coffee!</p>",
"text": "No matter what happens tomorrow, the next day there will still be work to do on Micro.blog and the IndieWeb. Join us Wednesday for Homebrew Website Club in Austin. 6:30pm at Mozart\u2019s Coffee!"
},
"published": "2018-11-05T14:39:22-08:00",
"post-type": "note",
"_id": "1349072",
"_source": "12",
"_is_read": true
}
{
"type": "entry",
"author": {
"name": "Kh\u00fcrt Williams",
"url": "https://islandinthenet.com/",
"photo": null
},
"url": "https://islandinthenet.com/testing-webmentions-2/",
"published": "2018-11-05T23:19:48+00:00",
"content": {
"html": "<p>Testing 1, 2, 3. Test 1 Test 2 Test 3 Test 4 Test 5 Test 6 Test 7 Test 8 Test 9 Test 10 Test 11 Test 12 Test 13 Test 14 Test 15 Test 16 Test 17 Test 18 Test 19 Test 20 Test 21 Test 22 Test 23</p>",
"text": "Testing 1, 2, 3. Test 1 Test 2 Test 3 Test 4 Test 5 Test 6 Test 7 Test 8 Test 9 Test 10 Test 11 Test 12 Test 13 Test 14 Test 15 Test 16 Test 17 Test 18 Test 19 Test 20 Test 21 Test 22 Test 23"
},
"name": "Testing Webmentions",
"post-type": "article",
"_id": "1348478",
"_source": "242",
"_is_read": true
}
{
"type": "entry",
"author": {
"name": "Kh\u00fcrt Williams",
"url": "https://islandinthenet.com/",
"photo": null
},
"url": "https://islandinthenet.com/testing-webmentions/",
"published": "2018-11-05T23:02:56+00:00",
"content": {
"html": "<p>Argh!</p>",
"text": "Argh!"
},
"name": "Testing Webmentions",
"post-type": "article",
"_id": "1348479",
"_source": "242",
"_is_read": true
}
{
"type": "entry",
"author": {
"name": "Kh\u00fcrt Williams",
"url": "https://islandinthenet.com/",
"photo": null
},
"url": "https://islandinthenet.com/2018-11-05-17-57-53/",
"published": "2018-11-05T22:57:53+00:00",
"content": {
"html": "<p>Jacky, if you abandon Isso, how will your new website support comments for people who don\u2019t have their own website or who are not using a platform (blogger, Tumblr, wordpress.com) that supports webmentions?</p>",
"text": "Jacky, if you abandon Isso, how will your new website support comments for people who don\u2019t have their own website or who are not using a platform (blogger, Tumblr, wordpress.com) that supports webmentions?"
},
"name": "2018-11-05 17.57.53",
"post-type": "article",
"_id": "1348480",
"_source": "242",
"_is_read": true
}
At #IndieWebCamp @MozillaBerlin, coded some archive navigation in @Falcon: sequential previous/next navigation across day archives. More to do, like link from home page to more entries, skip days without posts, but happy with progress.
Next steps: https://indieweb.org/Falcon#archive_pages
Related #indieweb pages:
* https://indieweb.org/navigation
* https://indieweb.org/pagination
* https://indieweb.org/archive_navigation
{
"type": "entry",
"published": "2018-11-04 08:00-0800",
"url": "http://tantek.com/2018/308/t2/indiewebcamp-archive-navigation-day-archives",
"category": [
"IndieWebCamp",
"indieweb"
],
"content": {
"text": "At #IndieWebCamp @MozillaBerlin, coded some archive navigation in @Falcon: sequential previous/next navigation across day archives. More to do, like link from home page to more entries, skip days without posts, but happy with progress. \n\nNext steps: https://indieweb.org/Falcon#archive_pages\n\nRelated #indieweb pages:\n* https://indieweb.org/navigation\n* https://indieweb.org/pagination\n* https://indieweb.org/archive_navigation",
"html": "At #<span class=\"p-category\">IndieWebCamp</span> <a class=\"h-cassis-username\" href=\"https://twitter.com/MozillaBerlin\">@MozillaBerlin</a>, coded some archive navigation in <a class=\"h-cassis-username\" href=\"https://twitter.com/Falcon\">@Falcon</a>: sequential previous/next navigation across day archives. More to do, like link from home page to more entries, skip days without posts, but happy with progress. <br /><br />Next steps: <a href=\"https://indieweb.org/Falcon#archive_pages\">https://indieweb.org/Falcon#archive_pages</a><br /><br />Related #<span class=\"p-category\">indieweb</span> pages:<br />* <a href=\"https://indieweb.org/navigation\">https://indieweb.org/navigation</a><br />* <a href=\"https://indieweb.org/pagination\">https://indieweb.org/pagination</a><br />* <a href=\"https://indieweb.org/archive_navigation\">https://indieweb.org/archive_navigation</a>"
},
"author": {
"type": "card",
"name": "Tantek \u00c7elik",
"url": "http://tantek.com/",
"photo": "https://aperture-media.p3k.io/tantek.com/acfddd7d8b2c8cf8aa163651432cc1ec7eb8ec2f881942dca963d305eeaaa6b8.jpg"
},
"post-type": "note",
"_id": "1337007",
"_source": "1",
"_is_read": true
}
{
"type": "entry",
"published": "2018-11-04 05:25-0800",
"url": "http://tantek.com/2018/308/b1/received-webmention-update-source-redirect",
"in-reply-to": [
"https://github.com/w3c/webmention/issues/"
],
"name": "Received webmention update with source redirect should update comment link",
"content": {
"text": "In 3.2.4 Updating existing Webmentions, there needs to be a step to keep track of a source redirect e.g. for a new slug, or updating http to https, and to save and use that new URL instead of the original source in places like linking a received comment back to its original.",
"html": "<p>\nIn <a href=\"https://webmention.net/draft/#updating-existing-webmentions\">3.2.4 Updating existing Webmentions</a>, there needs to be a step to keep track of a source redirect e.g. for a new slug, or updating http to https, and to save and use that new URL instead of the original source in places like linking a received comment back to its original.\n</p>"
},
"author": {
"type": "card",
"name": "Tantek \u00c7elik",
"url": "http://tantek.com/",
"photo": "https://aperture-media.p3k.io/tantek.com/acfddd7d8b2c8cf8aa163651432cc1ec7eb8ec2f881942dca963d305eeaaa6b8.jpg"
},
"post-type": "reply",
"refs": {
"https://github.com/w3c/webmention/issues/": {
"type": "entry",
"url": "https://github.com/w3c/webmention/issues/",
"name": "GitHub project \u201cwebmention\u201d",
"post-type": "article"
}
},
"_id": "1337009",
"_source": "1",
"_is_read": true
}
Really happy to have my database cache auto-updating bugs fixed so that my posts are now instantly indexed in my website 🙂 Now if I can just switch my TV Show and Movie "watch" posts to use Micropub, because all of this logic is tied to my Micropub endpoint and the way I currently log tv shows and movies circumvents my Micropub endpoint. 🤦♂️
{
"type": "entry",
"published": "2018-11-04T13:33:53-05:00",
"url": "https://eddiehinkle.com/2018/11/04/10/note/",
"category": [
"tech"
],
"syndication": [
"https://micro.blog/EddieHinkle",
"https://twitter.com/eddiehinkle"
],
"content": {
"text": "Really happy to have my database cache auto-updating bugs fixed so that my posts are now instantly indexed in my website \ud83d\ude42 Now if I can just switch my TV Show and Movie \"watch\" posts to use Micropub, because all of this logic is tied to my Micropub endpoint and the way I currently log tv shows and movies circumvents my Micropub endpoint. \ud83e\udd26\u200d\u2642\ufe0f"
},
"author": {
"type": "card",
"name": "Eddie Hinkle",
"url": "https://eddiehinkle.com/",
"photo": "https://aperture-proxy.p3k.io/cc9591b69c2c835fa2c6e23745b224db4b4b431f/68747470733a2f2f656464696568696e6b6c652e636f6d2f696d616765732f70726f66696c652e6a7067"
},
"post-type": "note",
"_id": "1336929",
"_source": "226",
"_is_read": true
}
{
"type": "entry",
"published": "2018-11-04T16:19:51+0000",
"url": "http://known.kevinmarks.com/2018/rel-me-mastodon-and-browser-plugins",
"category": [
"indieweb",
"yesvember"
],
"name": "Rel-me, mastodon and browser plugins",
"content": {
"text": "If you go to an account on mastodon.social, like\u00a0mastodon.social/@kevinmarks\u00a0you can see that it now verifies rel=me links:However not all mastodon instances have updated to 2.6.1 yet, eg\u00a0xoxo.zone/@kevinmarksHelp is at hand though - with the\u00a0verify-me\u00a0chrome plugin\u00a0it will check when you click the green tick:And if you go try this on the mastodon.social version, you can check their checkmarks should be checked:Which is helps see if aral is being sneaky.#indieweb #yesvember",
"html": "<p>If you go to an account on mastodon.social, like\u00a0<a href=\"https://mastodon.social/@kevinmarks\">mastodon.social/@kevinmarks</a>\u00a0you can see that it now verifies rel=me links:</p><p><img src=\"https://aperture-proxy.p3k.io/169095d61be6b646d04d42a63ed489b78498097f/687474703a2f2f6b6e6f776e2e6b6576696e6d61726b732e636f6d2f66696c652f3865633264333939363136663330376433623939626135663333656630323439\" alt=\"\" width=\"656\" height=\"724\" /></p><p>However not all mastodon instances have updated to 2.6.1 yet, eg\u00a0<a href=\"https://xoxo.zone/@kevinmarks\">xoxo.zone/@kevinmarks</a></p><p><img src=\"https://aperture-proxy.p3k.io/0da4999b75c9fa1b510bce0c098c0e5df474e8d5/687474703a2f2f6b6e6f776e2e6b6576696e6d61726b732e636f6d2f66696c652f6538633532663836313934336661313661386237326466643833633137336236\" alt=\"\" width=\"624\" height=\"642\" /></p><p>Help is at hand though - with the\u00a0<a href=\"https://chrome.google.com/webstore/detail/verify-me/nnefkajddpfponfnmaflddipljfdlcjb/related?hl=en-GB&gl=GB\">verify-me\u00a0chrome plugin</a>\u00a0it will check when you click the green tick:</p><p><img src=\"https://aperture-proxy.p3k.io/f7105954cfd48531f6f81ac4664ae1aaaf5eb22e/687474703a2f2f6b6e6f776e2e6b6576696e6d61726b732e636f6d2f66696c652f6430383763376661303038396162643637336336313433623665303262616632\" alt=\"\" width=\"628\" height=\"634\" /></p><p>And if you go try this on the mastodon.social version, you can check their checkmarks should be checked:</p><p><img src=\"https://aperture-proxy.p3k.io/49e80a1bdf2f82c2628be24a542e2ca4817ba44f/687474703a2f2f6b6e6f776e2e6b6576696e6d61726b732e636f6d2f66696c652f3032623339343735323462323535656630333636656338626635613134616361\" alt=\"\" width=\"648\" height=\"758\" /></p><p>Which is helps see if <a href=\"https://mastodon.ar.al/@aral/100996368149632908\">aral is being sneaky</a>.</p><p><a href=\"http://known.kevinmarks.com/tag/indieweb\" class=\"p-category\">#indieweb</a> <a href=\"http://known.kevinmarks.com/tag/yesvember\" class=\"p-category\">#yesvember</a></p>"
},
"author": {
"type": "card",
"name": "Kevin Marks",
"url": "http://known.kevinmarks.com/profile/kevinmarks",
"photo": "https://aperture-proxy.p3k.io/ed7979fd10a648fc253eae0b54e66fb36e57d3d4/687474703a2f2f6b6e6f776e2e6b6576696e6d61726b732e636f6d2f66696c652f3932353536353636363931373362373836376162383339656536353536663965"
},
"post-type": "article",
"_id": "1335754",
"_source": "205",
"_is_read": true
}
{
"type": "entry",
"published": "2018-11-03T21:13:06-04:00",
"url": "https://eddiehinkle.com/2018/11/03/17/article/",
"category": [
"indieweb",
"tech"
],
"syndication": [
"https://micro.blog/EddieHinkle",
"https://news.indieweb.org/en",
"https://twitter.com/eddiehinkle"
],
"name": "Thinking through the IWC Berlin displaying responses session",
"content": {
"text": "I remotely attended the Displaying Responses session of IndieWebCamp Berlin 2018. It was very interesting and they made some good progress thinking though how to deal with how and when to display responses received to posts on your website.\nThey came to the conclusion that there are four groups of people that you want to treat their responses differently:\nAccepted / Immediate Connections\n2nd level connections\nEveryone\nMute or Blocked\nAccepted / Immediate Connections\nThese are essentially your friends on Facebook or your follow list on Twitter. These are people that you have chosen to connect with in some way and this logical conclusions can be drawn around the level of interactions you're willing to have.\nMy plan is to display these responses completely (name, photo and content of response). This list will be generated for me by adding anyone I follow, as well as anyone I have sent a reply to. This will NOT add people to whom I have liked, emoji reacted, quoted, or bookmarked. Those are lower level responses that do not indicate a deeper level of a desire to connect with that person.\n2nd Level Connections\nThese are \"friends of friends\". You can assume they won't do anything TOO bad, but you might not want them posting all over your site. There is a deeper level of trust here because of mutual connection but still some care should be taken. This can be determined through different ways. One way that has been brainstormed in the IndieWeb is Vouch.\nI don't currently track 2nd level connections but I liked how Tantek thought this through, so my plan is for replies to display their photo and name as \"other people that have responded to this post\", but not display the content of their reply. I also think if they send a like, emoji reaction or quote, I'll display it just like I would an Immediate Connection.\nEveryone\nThis is the World Wide Web, and anyone could send anything to my website via webmention. So this is a category you likely want to moderate.\nMy initial thought is I will accept likes, quotes and emoji reactions from them but I won't list attribution of who did it while moderated, just the reaction itself. For replies I am considering potentially listing the url of the author of the post under \"other people who have replied\" but no name, photo or content while moderated.\nMute or Blocked\nThese are people who you do not trust for whatever reasons have happened for you. You don't want to associate with them in any way.\nResponses are not displayed from these people and they are not listed in the moderation queue.\nSome thoughts on moderation\nThis means I'll need a moderation queue. Anything from a 2nd level connection or from the Everyone group will enter the moderation queue. Responses from 2nd level connections should appear higher in the queue than responses from the Everyone group. From there I can choose to:\napprove a response (display it like an immediate connection)\napprove response and accept author (makes this author an immediate connection so they aren't moderated anymore)\nignore response (this leaves the response as is, it leaves the queue but doesn't display additional details)\nremove response (this removes the response from my storage)\nremove response and block author (this both removes the response from my storage and makes sure I don't receive responses from them in the future)\nAll in all, it was a great session that I really enjoyed and I'm looking forward to actually working on implementing some of these features into my site.",
"html": "I remotely attended the <a href=\"https://etherpad.indieweb.org/responses\">Displaying Responses session</a> of <a href=\"https://indieweb.org/2018/Berlin#Sessions\">IndieWebCamp Berlin 2018</a>. It was very interesting and they made some good progress thinking though how to deal with how and when to display responses received to posts on your website.\n<p>They came to the conclusion that there are four groups of people that you want to treat their responses differently:</p>\n<ul><li>Accepted / Immediate Connections</li>\n<li>2nd level connections</li>\n<li>Everyone</li>\n<li>Mute or Blocked</li>\n</ul><h2>Accepted / Immediate Connections</h2>\n<p>These are essentially your friends on Facebook or your follow list on Twitter. These are people that you have chosen to connect with in some way and this logical conclusions can be drawn around the level of interactions you're willing to have.</p>\n<p>My plan is to display these responses completely (name, photo and content of response). This list will be generated for me by adding anyone I follow, as well as anyone I have sent a reply to. This will NOT add people to whom I have liked, emoji reacted, quoted, or bookmarked. Those are lower level responses that do not indicate a deeper level of a desire to connect with that person.</p>\n<h2>2nd Level Connections</h2>\n<p>These are \"friends of friends\". You can assume they won't do anything TOO bad, but you might not want them posting all over your site. There is a deeper level of trust here because of mutual connection but still some care should be taken. This can be determined through different ways. One way that has been brainstormed in the IndieWeb is Vouch.</p>\n<p>I don't currently track 2nd level connections but I liked how <a href=\"http://tantek.com\">Tantek</a> thought this through, so my plan is for replies to display their photo and name as \"other people that have responded to this post\", but not display the content of their reply. I also think if they send a like, emoji reaction or quote, I'll display it just like I would an Immediate Connection.</p>\n<h2>Everyone</h2>\n<p>This is the World Wide Web, and anyone could send anything to my website via webmention. So this is a category you likely want to moderate.</p>\n<p>My initial thought is I will accept likes, quotes and emoji reactions from them but I won't list attribution of who did it while moderated, just the reaction itself. For replies I am considering potentially listing the url of the author of the post under \"other people who have replied\" but no name, photo or content while moderated.</p>\n<h2>Mute or Blocked</h2>\n<p>These are people who you do not trust for whatever reasons have happened for you. You don't want to associate with them in any way.</p>\n<p>Responses are not displayed from these people and they are not listed in the moderation queue.</p>\n<h2>Some thoughts on moderation</h2>\n<p>This means I'll need a moderation queue. Anything from a 2nd level connection or from the Everyone group will enter the moderation queue. Responses from 2nd level connections should appear higher in the queue than responses from the Everyone group. From there I can choose to:</p>\n<ul><li>approve a response (display it like an immediate connection)</li>\n<li>approve response and accept author (makes this author an immediate connection so they aren't moderated anymore)</li>\n<li>ignore response (this leaves the response as is, it leaves the queue but doesn't display additional details)</li>\n<li>remove response (this removes the response from my storage)</li>\n<li>remove response and block author (this both removes the response from my storage and makes sure I don't receive responses from them in the future)</li>\n</ul><p>All in all, it was a great session that I really enjoyed and I'm looking forward to actually working on implementing some of these features into my site.\n</p>"
},
"author": {
"type": "card",
"name": "Eddie Hinkle",
"url": "https://eddiehinkle.com/",
"photo": "https://aperture-proxy.p3k.io/cc9591b69c2c835fa2c6e23745b224db4b4b431f/68747470733a2f2f656464696568696e6b6c652e636f6d2f696d616765732f70726f66696c652e6a7067"
},
"post-type": "article",
"_id": "1335053",
"_source": "226",
"_is_read": true
}
{
"type": "entry",
"published": "2018-11-04T10:38:33+0000",
"url": "http://known.kevinmarks.com/2018/the-verify-me-plugin-is-now-approved-at",
"category": [
"Indieweb",
"Yesvember"
],
"in-reply-to": [
"http://known.kevinmarks.com/2018/i-updated-the-verify-me-plugin-atindiewebverify-me-to"
],
"content": {
"text": "The verify-me plugin is now approved at the Chrome store: https://chrome.google.com/webstore/detail/verify-me/nnefkajddpfponfnmaflddipljfdlcjb/related?hl=en-G... \n\nNot sure how to get the firefox version updated. #Indieweb #Yesvember",
"html": "The verify-me plugin is now approved at the Chrome store: <a href=\"https://chrome.google.com/webstore/detail/verify-me/nnefkajddpfponfnmaflddipljfdlcjb/related?hl=en-GB&gl=GB\">https://chrome.google.com/webstore/detail/verify-me/nnefkajddpfponfnmaflddipljfdlcjb/related?hl=en-G...</a> <br />\nNot sure how to get the firefox version updated. <a href=\"http://known.kevinmarks.com/tag/Indieweb\" class=\"p-category\">#Indieweb</a> <a href=\"http://known.kevinmarks.com/tag/Yesvember\" class=\"p-category\">#Yesvember</a>"
},
"author": {
"type": "card",
"name": "Kevin Marks",
"url": "http://known.kevinmarks.com/profile/kevinmarks",
"photo": "https://aperture-proxy.p3k.io/ed7979fd10a648fc253eae0b54e66fb36e57d3d4/687474703a2f2f6b6e6f776e2e6b6576696e6d61726b732e636f6d2f66696c652f3932353536353636363931373362373836376162383339656536353536663965"
},
"post-type": "reply",
"_id": "1334012",
"_source": "205",
"_is_read": true
}
I updated the verify-me plugin at
https://github.com/indieweb/verify-me to use Martijn's local code instead of http://indiewebify.me - it's pending review at the chrome store #Indieweb #Yesvember
{
"type": "entry",
"published": "2018-11-04T03:08:30+0000",
"url": "http://known.kevinmarks.com/2018/i-updated-the-verify-me-plugin-atindiewebverify-me-to",
"category": [
"Indieweb",
"Yesvember"
],
"content": {
"text": "I updated the verify-me plugin at\nhttps://github.com/indieweb/verify-me to use Martijn's local code instead of http://indiewebify.me - it's pending review at the chrome store #Indieweb #Yesvember",
"html": "I updated the verify-me plugin at<br /><a href=\"https://github.com/indieweb/verify-me\">https://github.com/indieweb/verify-me</a> to use Martijn's local code instead of <a href=\"http://indiewebify.me\">http://indiewebify.me</a> - it's pending review at the chrome store <a href=\"http://known.kevinmarks.com/tag/Indieweb\" class=\"p-category\">#Indieweb</a> <a href=\"http://known.kevinmarks.com/tag/Yesvember\" class=\"p-category\">#Yesvember</a>"
},
"author": {
"type": "card",
"name": "Kevin Marks",
"url": "http://known.kevinmarks.com/profile/kevinmarks",
"photo": "https://aperture-proxy.p3k.io/ed7979fd10a648fc253eae0b54e66fb36e57d3d4/687474703a2f2f6b6e6f776e2e6b6576696e6d61726b732e636f6d2f66696c652f3932353536353636363931373362373836376162383339656536353536663965"
},
"post-type": "note",
"_id": "1332941",
"_source": "205",
"_is_read": true
}
Day one of Indie Web Camp Berlin is done, and it was great! Here’s Charlie’s recap of the sessions she attended.
{
"type": "entry",
"published": "2018-11-03T23:10:53Z",
"url": "https://adactio.com/links/14474",
"category": [
"indieweb",
"iwc",
"berlin",
"indiewebcamp",
"microsub",
"microformats",
"webmentions"
],
"bookmark-of": [
"https://www.sonniesedge.co.uk/notes/1548"
],
"content": {
"text": "2018-11-03, 21:54 - sonniesedge.co.uk\n\n\n\nDay one of Indie Web Camp Berlin is done, and it was great! Here\u2019s Charlie\u2019s recap of the sessions she attended.",
"html": "<h3>\n<a class=\"p-name u-bookmark-of\" href=\"https://www.sonniesedge.co.uk/notes/1548\">\n2018-11-03, 21:54 - sonniesedge.co.uk\n</a>\n</h3>\n\n<p>Day one of Indie Web Camp Berlin is done, and it was <em>great</em>! Here\u2019s Charlie\u2019s recap of the sessions she attended.</p>"
},
"post-type": "bookmark",
"_id": "1331822",
"_source": "2",
"_is_read": true
}
The youngest IndieWebCamp remote attendee at IndieWebCamp Berlin: 3 months and 6 days old and already learning how to display responses on his website.
{
"type": "entry",
"published": "2018-11-03T11:18:19-04:00",
"url": "https://eddiehinkle.com/2018/11/03/4/photo/",
"category": [
"indieweb",
"family",
"tech"
],
"photo": [
"https://aperture-proxy.p3k.io/512389da5b462c6f90d379385d84222e93c48580/68747470733a2f2f656464696568696e6b6c652e636f6d2f6d656469612f36316161343161623863303437623865626336353831343264396565366435362e6a706567"
],
"syndication": [
"https://micro.blog/EddieHinkle",
"https://twitter.com/eddiehinkle"
],
"content": {
"text": "The youngest IndieWebCamp remote attendee at IndieWebCamp Berlin: 3 months and 6 days old and already learning how to display responses on his website."
},
"author": {
"type": "card",
"name": "Eddie Hinkle",
"url": "https://eddiehinkle.com/",
"photo": "https://aperture-proxy.p3k.io/cc9591b69c2c835fa2c6e23745b224db4b4b431f/68747470733a2f2f656464696568696e6b6c652e636f6d2f696d616765732f70726f66696c652e6a7067"
},
"post-type": "photo",
"_id": "1329029",
"_source": "226",
"_is_read": true
}
{
"type": "entry",
"published": "2018-11-03T03:50:54+0000",
"url": "http://known.kevinmarks.com/2018/how-do-we-replace-flickr-indieweb-yesvember",
"name": "How do we replace Flickr? #Indieweb #Yesvember",
"content": {
"text": "Flickr, like all successful social software, is different things to different people. When something is done well, we internalize the communities that we interact with on it as part of the character of the place.\nFlickr was intentionally built as a community - it had\u00a0community guidelines\u00a0and a welcoming presence from Heather Champ and George Oates, who tummelled it brilliantly, welcoming new people and setting the tone.Don MacAskill,\u00a0Smugmug CEO and new owner of Flickr,\u00a0wants to retain this:We bought Flickr because it\u2019s the largest photographer-focused community in the world. I\u2019ve been a fan for 14 years. There\u2019s nothing else like it. It\u2019s the best place to explore, discover, and connect with amazing photographers and their beautiful photography. Flickr is a priceless Internet treasure for everyone and we\u2019re so excited to be investing in its future. Together, hand-in-hand with the the most amazing community on the planet, we can shape the future of photography.\u00a0\u00a0However, he also wants to change things, in particular he wants to\u00a0undo Yahoo's 'Free TB of storage' model:\nIn 2013, Yahoo lost sight of what makes Flickr truly special and responded to a changing landscape in online photo sharing by giving every Flickr user a staggering terabyte of free storage. This, and numerous related changes to the Flickr product during that time, had strongly negative consequences.\nFirst, and most crucially, the free terabyte largely attracted members who were drawn by the free storage, not by engagement with other lovers of photography. This caused a significant tonal shift in our platform, away from the community interaction and exploration of shared interests that makes Flickr the best shared home for photographers in the world. We know those of you who value a vibrant community didn\u2019t like this shift, and with this change we\u2019re re-committing Flickr to focus on fostering this interaction.\nI get this, but the heuristic that Don has chosen\u2014free photos will be limted to 1000, and the oldest ones will be deleted first\u2014is likely to damage the original community feeling that he wants to preserve.\u00a0Ton\u00a0points out the Creative Commons ethos, but it is an earlier mode that I want to point to.In the early years, before cameras in cellphones and huge bandwidth became commonplace enough that we all had phtostreams, Flickr was the place where we shared a community record of events. We'd\u00a0upload our photos and tag them together to make a shared sense of occasion.\u00a0I know if I want to remember etech,\u00a0microformats\u00a0first anniversary or\u00a0the\u00a0vloggies, the photos will be there.However, a lot of these photos are from free users, and they may have gone over 1000, so the collages will be ruined.I'd like to suggest a more subtle heuristic. If images are public, and tagged, and especially if they are creative commons, Flickr should retain them to preserve this archive. If as Don says there are 3% of users with many thousands of photos that are private, they will still be hit by this without enclosing the commons.On the creative commons side, the Internet Archive can download those:\nWe are definitely thinking creatively and engaging directly with Creative Commons. I love CC. See here: https://t.co/Z9aksDbbSB\n\u2014 Don MacAskill (@DonMacAskill) November 1, 2018\n\nAs for the pople who want a big private archive of photos for free, send them to Google Photos, who love users like that (and will run machine learning over them for fun and profit).\nSounds like a great use case for datatransferproject.dev/ to me - wire that up and let people who want to keep big private photo libraries move off flickr\n\u2014 Kevin Marks (@kevinmarks) November 2, 2018\nMeanwhile, over in the fediverse,\u00a0pixelfed\u00a0is just getting started.",
"html": "<p>Flickr, like all successful social software, is different things to different people. When something is done well, we internalize the communities that we interact with on it as part of the character of the place.</p><p><a title=\"Just two average guys, minding their own business, walking down the street in SF. The usual. This is usual, right?\" href=\"https://www.flickr.com/photos/maryhodder/49958404/in/photolist-9yZrK-5q3TN-6xd92E\"><img src=\"https://aperture-proxy.p3k.io/1705641848c0f7f4fd8afee25781f7595cef3311/68747470733a2f2f6661726d312e737461746963666c69636b722e636f6d2f33332f34393935383430345f646437343636333165335f622e6a7067\" alt=\"Just two average guys, minding their own business, walking down the street in SF. The usual. This is usual, right?\" /></a></p><p>\n</p><p>Flickr was intentionally built as a community - it had\u00a0<a href=\"https://www.flickr.com/help/guidelines\">community guidelines</a>\u00a0and a welcoming presence from <a href=\"http://tummelvision.tv/2010/01/29/tummel-vision-episode-3-wheather-champ-and-george-oates-theyre-watching-you/\">Heather Champ and George Oates</a>, who tummelled it brilliantly, welcoming new people and setting the tone.</p><p>Don MacAskill,\u00a0Smugmug CEO and new owner of Flickr,\u00a0<a href=\"http://blog.flickr.net/2018/11/01/a-sharper-focus-for-flickr/\">wants to retain this</a>:</p><blockquote><p>We bought Flickr because it\u2019s the largest photographer-focused community in the world. I\u2019ve been a fan for 14 years. There\u2019s nothing else like it. It\u2019s the best place to explore, discover, and connect with amazing photographers and their beautiful photography. Flickr is a priceless Internet treasure for everyone and we\u2019re so excited to be investing in its future. Together, hand-in-hand with the the most amazing community on the planet, we can shape the future of photography.\u00a0\u00a0</p></blockquote><p>However, he also wants to change things, in particular he wants to\u00a0<a href=\"https://blog.flickr.net/en/2018/11/01/changing-flickr-free-accounts-1000-photos/\">undo</a> Yahoo's 'Free TB of storage' model:</p><blockquote>\n<p style=\"color:#212124;\">In 2013, Yahoo lost sight of what makes Flickr truly special and responded to a changing landscape in online photo sharing by giving every Flickr user a staggering terabyte of free storage. This, and numerous related changes to the Flickr product during that time, had strongly negative consequences.</p>\n<p style=\"color:#212124;\">First, and most crucially, the free terabyte largely attracted members who were drawn by the free storage, not by engagement with other lovers of photography. This caused a significant tonal shift in our platform, away from the community interaction and exploration of shared interests that makes Flickr the best shared home for photographers in the world. We know those of you who value a vibrant community didn\u2019t like this shift, and with this change we\u2019re re-committing Flickr to focus on fostering this interaction.</p>\n</blockquote><p style=\"color:#212124;\">I get this, but the heuristic that Don has chosen\u2014free photos will be limted to 1000, and the oldest ones will be deleted first\u2014is likely to damage the original community feeling that he wants to preserve.\u00a0<a href=\"https://www.zylstra.org/blog/2018/11/flickr-account-changes-and-bringing-things-home/\">Ton</a>\u00a0points out the Creative Commons ethos, but it is an earlier mode that I want to point to.</p><p style=\"color:#212124;\">In the early years, before cameras in cellphones and huge bandwidth became commonplace enough that we all had phtostreams, Flickr was the place where we shared a community record of events. We'd\u00a0upload our photos and tag them together to make a shared sense of occasion.\u00a0I know if I want to remember <a href=\"https://www.flickr.com/search/?sort=interestingness-desc&safe_search=1&text=etech05&view_all=1\">etech</a>,\u00a0<a href=\"https://www.flickr.com/search/?sort=interestingness-desc&safe_search=1&text=microformats1&view_all=1\">microformats</a><span style=\"color:#000000;\">\u00a0first anniversary or\u00a0</span>the\u00a0<a href=\"https://www.flickr.com/search/?text=vloggies&view_all=1\">vloggies</a>, the photos will be there.</p><p><a title=\"DSCN0375\" href=\"https://www.flickr.com/photos/olivepress/6549788/in/photolist-zz2o-zBm9-Gtzf-CpTM-AsE4-AiHr-AiMq-AxrP-Cqm3-zDQE-27vhU-AGhC-AxrD-CquE-Cqa7-zBpT-zjmH-zBxj-yNEj-zjmY-zjkc-AGtR-A5m3-A4Vm-C6PR-CrcY-zXv2-Ai9N-C5Ya-AGqD-zBpC-AhH8-Athi-Cqef-Crcz-Axrg-AhNP-AGr3-AGtG-zjmy-zDP8-C6FV-zXvu-Cqrx-27uUf-A4TQ-zDNW-AGk5-Aour-AsCP\"><img src=\"https://aperture-proxy.p3k.io/221f1bb1ac8388e9b37e7df9202839e9799e51bd/68747470733a2f2f6661726d312e737461746963666c69636b722e636f6d2f332f363534393738385f383762326661633238375f6d2e6a7067\" alt=\"DSCN0375\" width=\"174\" height=\"240\" /></a><a title=\"Microformats One Year Anniversary Party\" href=\"https://www.flickr.com/photos/laughingsquid/171847277/in/photolist-gbSHu-gbL8f-gg12Z-gbLdm-gbL6w-gbLd6-geiRW-gbL9d-gbLbj-gbL7r-ggbj5-goor2-gbTcf-gtmKk-gtmFy-gbL4H-gbSBY-gbTcZ-gokQ1-gej34-gbSMQ-ggbhR-gooen-gomiR-gmiZq-gokPV-gbSLo-gomiL-go7E3-gbSPY-gbSZQ-gomiX-gbSDk-gbSX2-gokQ3-gbSDV-go8Lc-gokPW-go8Lb-gtmPB-gokPZ-gmiZs-gbLcf-gbL9K\"><img src=\"https://aperture-proxy.p3k.io/8b57b71a3569b718d80dc9765205cec1e06a8efa/68747470733a2f2f6661726d312e737461746963666c69636b722e636f6d2f35382f3137313834373237375f333036633630326239625f6d2e6a7067\" alt=\"Microformats One Year Anniversary Party\" height=\"240\" /></a><a title=\"Like Father, Like Son\" href=\"https://www.flickr.com/photos/thomashawk/416449908/in/photolist-CNq3Q-sMMY9-KRr3Q-6i4w5C-5uTDpP-72oEHP-rHkNX-D9Aw5-5PwFF9-D6MLZ-6DUJof-rEamW-sfYEW-CWUkh-tLjMR-rD2tg-ryHDk-rCWK6-rFXyb-rFR9S-qHz9j-ryGFU-rDRcq-rHZPg-rA4J9-rB8rL-ryxs5-rFZuD-tLkR8-ryGQt-Fi8X7-rCZDE-rCViR-rABzN-ryGEo-rHZk8-rEamP-CYyPw-rCY1p-rAGzY-ru5ZU-rC1Rc-rA7TZ-FXeqj-ryGHk-CWSRD-rCW8H-tLjMx-ryyB3-ryHCo\"><img src=\"https://aperture-proxy.p3k.io/012c628fba543f0e37539fd29e22f5406fe54204/68747470733a2f2f6661726d312e737461746963666c69636b722e636f6d2f3138342f3431363434393930385f353066383166663035625f6d2e6a7067\" alt=\"Like Father, Like Son\" width=\"148\" height=\"240\" /></a></p><p>However, a lot of these photos are from free users, and they may have gone over 1000, so the collages will be ruined.</p><p>I'd like to suggest a more subtle heuristic. If images are public, and tagged, and especially if they are creative commons, Flickr should retain them to preserve this archive. If as Don says there are 3% of users with many thousands of photos that are private, they will still be hit by this without enclosing the commons.</p><p>On the creative commons side, the Internet Archive can download those:</p><blockquote>\n<p dir=\"ltr\" lang=\"en\" xml:lang=\"en\">We are definitely thinking creatively and engaging directly with Creative Commons. I love CC. See here: <a href=\"https://t.co/Z9aksDbbSB\"></a><a href=\"https://t.co/Z9aksDbbSB\">https://t.co/Z9aksDbbSB</a></p>\n<p>\u2014 Don MacAskill (@DonMacAskill) <a href=\"https://twitter.com/DonMacAskill/status/1058145086821683200?ref_src=twsrc%5Etfw\">November 1, 2018</a></p>\n</blockquote><p>\n</p><p>As for the pople who want a big private archive of photos for free, send them to Google Photos, who love users like that (and will run machine learning over them for fun and profit).</p><blockquote>\n<p dir=\"ltr\" lang=\"en\" xml:lang=\"en\">Sounds like a great use case for <a href=\"https://datatransferproject.dev/\">datatransferproject.dev/</a> to me - wire that up and let people who want to keep big private photo libraries move off flickr</p>\n<p>\u2014 Kevin Marks (@kevinmarks) <a href=\"https://twitter.com/kevinmarks/status/1058465840511754240?ref_src=twsrc%5Etfw\">November 2, 2018</a></p>\n</blockquote><p>Meanwhile, over in the fediverse,\u00a0<a href=\"https://pixelfed.org/\">pixelfed</a>\u00a0is just getting started.</p>"
},
"author": {
"type": "card",
"name": "Kevin Marks",
"url": "http://known.kevinmarks.com/profile/kevinmarks",
"photo": "https://aperture-proxy.p3k.io/ed7979fd10a648fc253eae0b54e66fb36e57d3d4/687474703a2f2f6b6e6f776e2e6b6576696e6d61726b732e636f6d2f66696c652f3932353536353636363931373362373836376162383339656536353536663965"
},
"post-type": "article",
"_id": "1326497",
"_source": "205",
"_is_read": true
}
Oops! I realized that when I added a new post, the new posts weren't updating my database cache 😁 Hopefully this post updates correctly! 🤞
{
"type": "entry",
"published": "2018-11-02T15:21:47-04:00",
"url": "https://eddiehinkle.com/2018/11/02/8/note/",
"category": [
"tech",
"indieweb"
],
"syndication": [
"https://micro.blog/EddieHinkle"
],
"content": {
"text": "Oops! I realized that when I added a new post, the new posts weren't updating my database cache \ud83d\ude01 Hopefully this post updates correctly! \ud83e\udd1e"
},
"author": {
"type": "card",
"name": "Eddie Hinkle",
"url": "https://eddiehinkle.com/",
"photo": "https://aperture-proxy.p3k.io/cc9591b69c2c835fa2c6e23745b224db4b4b431f/68747470733a2f2f656464696568696e6b6c652e636f6d2f696d616765732f70726f66696c652e6a7067"
},
"post-type": "note",
"_id": "1324440",
"_source": "226",
"_is_read": true
}
Just flipped the switch and now main feeds on my website are powered by my new database cache and my js server. 🤞 Hopefully nothing breaks! Now every feed page should have a JSONFeed, by adding .json even tag pages (ex Apple tag page has a JSONFeed)
{
"type": "entry",
"published": "2018-11-02T13:11:36-04:00",
"url": "https://eddiehinkle.com/2018/11/02/7/note/",
"category": [
"tech",
"indieweb"
],
"syndication": [
"https://micro.blog/EddieHinkle",
"https://news.indieweb.org/en"
],
"content": {
"text": "Just flipped the switch and now main feeds on my website are powered by my new database cache and my js server. \ud83e\udd1e Hopefully nothing breaks! Now every feed page should have a JSONFeed, by adding .json even tag pages (ex Apple tag page has a JSONFeed)",
"html": "Just flipped the switch and now main feeds on my website are powered by my new database cache and my js server. \ud83e\udd1e Hopefully nothing breaks! Now every feed page should have a JSONFeed, by adding .json even tag pages (ex <a href=\"https://eddiehinkle.com/tag/apple\">Apple tag page</a> has a <a href=\"https://eddiehinkle.com/tag/apple.json\">JSONFeed</a>)"
},
"author": {
"type": "card",
"name": "Eddie Hinkle",
"url": "https://eddiehinkle.com/",
"photo": "https://aperture-proxy.p3k.io/cc9591b69c2c835fa2c6e23745b224db4b4b431f/68747470733a2f2f656464696568696e6b6c652e636f6d2f696d616765732f70726f66696c652e6a7067"
},
"post-type": "note",
"_id": "1324070",
"_source": "226",
"_is_read": true
}
{
"type": "entry",
"published": "2018-11-01T22:55:35+01:00",
"url": "https://david.shanske.com/2018/11/01/syndication-links-4-0-0-released/",
"syndication": [
"https://news.indieweb.org/en/david.shanske.com/2018/11/01/syndication-links-4-0-0-released/",
"https://twitter.com/dshanske/status/1058115454676426753"
],
"name": "Syndication Links 4.0.0 Released",
"content": {
"text": "Today, from my hotel room in Berlin, Germany, where I am preparing to attend Indiewebcamp Berlin, my first European Indiewebcamp, I released Syndication Links 4.0.0.\nThe major version number change is because in this version, Syndication Links takes on a new role. As promised previously, I\u2019ve built new syndication code and added supported for Bridgy and Indienews, which both uses Webmentions to trigger a syndication action. This is disabled by default.\nAs my first live use outside of testing, I\u2019m using the plugin to send this post to Indienews and Twitter(via Bridgy).\nThe new code adds the concept of a syndication provider, which, when registered, adds the provider as a syndication target for Micropub clients as well as adds it to the WordPress classic editor as a series of checkboxes, er postone for each service.\nThe Bridgy Publish plugin I announced deprecation on had additional options on a per post and a global level. While the global settings will be coming back in a future version, I likely will not bring back the per-post settings.\nInstead, I\u2019d like to add more intelligence behind these decisions, based on other properties of the post. A checkbox is all you should need. The same with auto-syndication. If you decide you want everything to go to Twitter or some site, it shouldn\u2019t check the box\u2026there shouldn\u2019t be a box at all. It should just go, even if there are some more parameters to make that decision\u2026type of post, etc.\nSo, you are either all in, or in on a per post basis.\nI look forward to feedback. This is only the beginning. I hope to do what I did for displaying syndication links, and interface with existing plugins in addition to writing my own integrations.",
"html": "Today, from my hotel room in Berlin, Germany, where I am preparing to attend Indiewebcamp Berlin, my first European Indiewebcamp, I released Syndication Links 4.0.0.\n<p>The major version number change is because in this version, Syndication Links takes on a new role. As promised previously, I\u2019ve built new syndication code and added supported for Bridgy and Indienews, which both uses Webmentions to trigger a syndication action. This is disabled by default.</p>\n<p>As my first live use outside of testing, I\u2019m using the plugin to send this post to Indienews and Twitter(via Bridgy).</p>\n<p>The new code adds the concept of a syndication provider, which, when registered, adds the provider as a syndication target for Micropub clients as well as adds it to the WordPress classic editor as a series of checkboxes, er postone for each service.</p>\n<p>The Bridgy Publish plugin I announced deprecation on had additional options on a per post and a global level. While the global settings will be coming back in a future version, I likely will not bring back the per-post settings.</p>\n<p>Instead, I\u2019d like to add more intelligence behind these decisions, based on other properties of the post. A checkbox is all you should need. The same with auto-syndication. If you decide you want everything to go to Twitter or some site, it shouldn\u2019t check the box\u2026there shouldn\u2019t be a box at all. It should just go, even if there are some more parameters to make that decision\u2026type of post, etc.</p>\n<p>So, you are either all in, or in on a per post basis.</p>\n<p>I look forward to feedback. This is only the beginning. I hope to do what I did for displaying syndication links, and interface with existing plugins in addition to writing my own integrations.</p>"
},
"author": {
"type": "card",
"name": "David Shanske",
"url": "https://david.shanske.com/",
"photo": "https://david.shanske.com/wp-content/uploads/avatar-privacy/cache/gravatar/2/c/2cb1f8afd9c8d3b646b4071c5ed887c970d81d625eeed87e447706940e2c403d-125.png"
},
"post-type": "article",
"_id": "1317223",
"_source": "5",
"_is_read": true
}