{
"type": "entry",
"published": "2018-02-14T13:18:59-05:00",
"summary": "This issue is for an in-development idea of being able to get a reply post into the micro.blog system when the post is created on an external site.",
"url": "https://eddiehinkle.com/2018/02/14/5/reply/",
"category": [
"indieweb"
],
"in-reply-to": [
"https://github.com/microdotblog/issues"
],
"name": "Adding support for cross-site replies",
"author": {
"type": "card",
"name": "Eddie Hinkle",
"url": "https://eddiehinkle.com",
"photo": null
},
"refs": {
"https://github.com/microdotblog/issues": {
"type": "entry",
"url": "https://github.com/microdotblog/issues",
"name": "https://github.com/microdotblog/issues"
}
},
"_id": "59859",
"_source": "39",
"_is_read": true
}
{
"type": "entry",
"author": {
"name": "Sarah Mundy",
"url": "https://sarahmundy.com/",
"photo": null
},
"url": "https://sarahmundy.com/2018/02/12/hello-world/",
"published": "2018-02-12T18:40:53+00:00",
"content": {
"html": "<p>This is my first personal blog or website in years that is not hosted on a silo. I\u2019ve been watching #IndieWeb get up and running, and played with all sorts of Facebook and Google alternatives\u2026 and I finally decided to give it a shot. I\u2019m planning on getting this set up as a sort of collection book for my thoughts, my projects, my current readings, my social lives, and I hope to have fun whilst doing it!</p>",
"text": "This is my first personal blog or website in years that is not hosted on a silo. I\u2019ve been watching #IndieWeb get up and running, and played with all sorts of Facebook and Google alternatives\u2026 and I finally decided to give it a shot. I\u2019m planning on getting this set up as a sort of collection book for my thoughts, my projects, my current readings, my social lives, and I hope to have fun whilst doing it!"
},
"name": "Introduction",
"_id": "124153",
"_source": "245",
"_is_read": true
}
{
"type": "entry",
"published": "2018-02-12T17:15:32+00:00",
"url": "https://cleverdevil.io/2018/editing-a-post-in-known-can-have-destructive-side-effects",
"in-reply-to": [
"https://github.com/idno/Known"
],
"name": "Editing a post in Known can have destructive side effects on content",
"content": {
"text": "There is a bug in Known which causes HTML posts published via Micropub to be changed (usually in bad ways) when \"editing\" the post, even when you don't actually make any changes to the post. I discovered this issue when publishing via Sunlit 2.0, which supports Micropub.\nI published two stories:\nCar Museum with William\nSan Diego with Lacey\nBecause Sunlit doesn't yet support syndication via Micropub, I clicked \"edit\" on one of the posts, and toggled on syndication to Twitter and Facebook, and then clicked \"save.\" The result was that the post's content was changed (in a destructive way, resulting in visual regressions), even though I hadn't actually edited the content, or even clicked into the content editor.\nSeems like this is a bug.",
"html": "<p>There is a bug in <a class=\"u-in-reply-to\" href=\"https://github.com/idno/Known\">Known</a> which causes HTML posts published via Micropub to be changed (usually in bad ways) when \"editing\" the post, even when you don't actually make any changes to the post. I discovered this issue when publishing via <a href=\"http://www.manton.org/2018/01/sunlit-beta-update.html\">Sunlit 2.0</a>, which supports Micropub.</p>\n<p>I published two stories:</p>\n<ul><li><a href=\"https://cleverdevil.io/2018/car-museum-with-william\">Car Museum with William</a></li>\n<li><a href=\"https://cleverdevil.io/2018/san-diego-with-lacey\">San Diego with Lacey</a></li>\n</ul><p>Because Sunlit doesn't yet support syndication via Micropub, I clicked \"edit\" on one of the posts, and toggled on syndication to Twitter and Facebook, and then clicked \"save.\" The result was that the post's content was changed (in a destructive way, resulting in visual regressions), even though I hadn't actually edited the content, or even clicked into the content editor.</p>\n<p>Seems like this is a bug.</p>"
},
"author": {
"type": "card",
"name": "Jonathan LaCour",
"url": "https://cleverdevil.io/profile/cleverdevil",
"photo": "https://cleverdevil.io/file/2fa19f964fb8970faaf20b909c69d6cb/thumb.png"
},
"_id": "49422",
"_source": "71",
"_is_read": true
}
In trying to decide on his indie web approach, Dries gives an excellent breakdown of the concepts of PESOS (Publish Elsewhere, Syndicate to Own Site) and POSSE (Publish to Own Site, Syndicate Elsewhere).
{
"type": "entry",
"published": "2018-02-11T01:30:41Z",
"url": "https://adactio.com/links/13427",
"category": [
"indieweb",
"pesos",
"posse",
"drupal",
"personal",
"publishing",
"social",
"networks",
"facebook",
"twitter",
"sharing"
],
"bookmark-of": [
"https://dri.es/to-pesos-or-to-posse"
],
"content": {
"text": "To PESOS or to POSSE? | Dries Buytaert\n\n\n\nIn trying to decide on his indie web approach, Dries gives an excellent breakdown of the concepts of PESOS (Publish Elsewhere, Syndicate to Own Site) and POSSE (Publish to Own Site, Syndicate Elsewhere).\n\nThere are some great responses in the comments too, like this one from Chris and this one from Tantek (syndicated from their own sites, obvs).",
"html": "<h3>\n<a class=\"p-name u-bookmark-of\" href=\"https://dri.es/to-pesos-or-to-posse\">\nTo PESOS or to POSSE? | Dries Buytaert\n</a>\n</h3>\n\n<p>In trying to decide on his indie web approach, Dries gives an excellent breakdown of the concepts of PESOS (Publish Elsewhere, Syndicate to Own Site) and POSSE (Publish to Own Site, Syndicate Elsewhere).</p>\n\n<p>There are some great responses in the comments too, like <a href=\"http://boffosocko.com/2018/02/07/reply-to-to-pesos-or-to-posse-by-dries-buytaert/\">this one from Chris</a> and <a href=\"http://tantek.com/2018/037/t1/posse-indieweb-twitter-facebook\">this one from Tantek</a> (syndicated from their own sites, obvs).</p>"
},
"_id": "46551",
"_source": "2",
"_is_read": true
}
I had a chat with some people from Name.com while I was in Denver for An Event Apart. Here’s a few minutes of me rambling on about web development and the indie web.
{
"type": "entry",
"published": "2018-02-10T11:04:24Z",
"url": "https://adactio.com/links/13420",
"category": [
"youtube",
"video",
"indieweb",
"posse",
"browsers",
"standards",
"web",
"development",
"evaluating",
"technology",
"interview"
],
"bookmark-of": [
"https://www.youtube.com/watch?v=tLAI02TY7vI"
],
"content": {
"text": "Jeremy Keith on your content, failing well, and the Indie Web Movement - YouTube\n\n\n\nI had a chat with some people from Name.com while I was in Denver for An Event Apart. Here\u2019s a few minutes of me rambling on about web development and the indie web.",
"html": "<h3>\n<a class=\"p-name u-bookmark-of\" href=\"https://www.youtube.com/watch?v=tLAI02TY7vI\">\nJeremy Keith on your content, failing well, and the Indie Web Movement - YouTube\n</a>\n</h3>\n\n<p>I had a chat with some people from Name.com while I was in Denver for An Event Apart. Here\u2019s a few minutes of me rambling on about web development and the indie web.</p>\n\n<a href=\"https://www.youtube.com/watch?v=tLAI02TY7vI\"><img src=\"https://i.ytimg.com/vi/tLAI02TY7vI/hqdefault.jpg\" alt=\"Jeremy Keith on your content, failing well, and the Indie Web Movement\" /></a>"
},
"_id": "46093",
"_source": "2",
"_is_read": true
}
While I think a Gallery object would be nice, eventually, I am not convinced that its necessarily the best way to go here. Its my understanding that pretty much all Entities support attachments, so doing it in the near-term in a more cross-cutting way would enable any type of post created via Micropub that contains multiple attachments to elegantly display the images.
{
"type": "entry",
"published": "2018-02-09T20:33:23+00:00",
"url": "https://cleverdevil.io/2018/while-i-think-a-gallery-object-would",
"in-reply-to": [
"https://github.com/idno/Known/issues/1991"
],
"content": {
"text": "While I think a Gallery object would be nice, eventually, I am not convinced that its necessarily the best way to go here. Its my understanding that pretty much all Entities support attachments, so doing it in the near-term in a more cross-cutting way would enable any type of post created via Micropub that contains multiple attachments to elegantly display the images."
},
"author": {
"type": "card",
"name": "Jonathan LaCour",
"url": "https://cleverdevil.io/profile/cleverdevil",
"photo": "https://cleverdevil.io/file/2fa19f964fb8970faaf20b909c69d6cb/thumb.png"
},
"_id": "49435",
"_source": "71",
"_is_read": true
}
{
"type": "entry",
"published": "2018-02-09T02:06:03+00:00",
"url": "https://miklb.com/blog/2018/02/09/3409/",
"syndication": [
"https://twitter.com/miklb/status/961783010604605441"
],
"name": "02:06# \n\t\t\t\t\t\t\t\t\t\t\t\t \n\t\t\t\t\t\t\t\t\t\t\t\nBeen in a dev rut, so to break out going to see how quickly I can go from 0 to live #indieweb site sending/receiving webmentions with @eleven_ty. Since it supports liquid, I can use my work from jekyll-indieweb as a heads start https://github.com/miklb/jekyll-indieweb",
"content": {
"text": "Been in a dev rut, so to break out going to see how quickly I can go from 0 to live #indieweb site sending/receiving webmentions with @eleven_ty. Since it supports liquid, I can use my work from jekyll-indieweb as a heads start https://github.com/miklb/jekyll-indieweb",
"html": "<p>Been in a dev rut, so to break out going to see how quickly I can go from 0 to live #indieweb site sending/receiving webmentions with <a href=\"https://twitter.com/eleven_ty\">@eleven_ty</a>. Since it supports liquid, I can use my work from jekyll-indieweb as a heads start <a href=\"https://github.com/miklb/jekyll-indieweb\">https://github.com/miklb/jekyll-indieweb</a>\n</p>"
},
"_id": "44475",
"_source": "42",
"_is_read": true
}
I've said before that I would like to bring a record of the things I mark at reading.am back to my notes website as Bookmarks. In theory, WithKnown makes this very easy, because every type of entry (Posts, Status updates, Bookmarks etc) has its own API, to which you can send correctly formatted POST requests. You can also send POST requests to Known's micropub endpoint. Unfortunately, neither option works for Bookmarks (and probably not for Likes and Reposts, but I haven't played with them).
More this way ...
{
"type": "entry",
"published": "2018-02-08T16:00:00+0100",
"summary": "I've said before that I would like to bring a record of the things I mark at reading.am back to my notes website as Bookmarks. In theory, WithKnown makes this very easy, because every type of entry (Posts, Status updates, Bookmarks etc) has its own API, to which you can send correctly formatted POST requests. You can also send POST requests to Known's micropub endpoint. Unfortunately, neither option works for Bookmarks (and probably not for Likes and Reposts, but I haven't played with them). \n\n More this way ...",
"url": "https://www.jeremycherfas.net/blog/why-i-cannot-post-bookmarks-to-known-automatically",
"name": "Why I cannot post bookmarks to Known automatically",
"content": {
"text": "I've said before that I would like to bring a record of the things I mark at reading.am back to my notes website as Bookmarks. In theory, WithKnown makes this very easy, because every type of entry (Posts, Status updates, Bookmarks etc) has its own API, to which you can send correctly formatted POST requests. You can also send POST requests to Known's micropub endpoint. Unfortunately, neither option works for Bookmarks (and probably not for Likes and Reposts, but I haven't played with them).\n\n More this way ...",
"html": "<p>I've said before that I would like to bring a record of the things I mark at reading.am back to my notes website as Bookmarks. In theory, WithKnown makes this very easy, because every type of entry (Posts, Status updates, Bookmarks etc) has its own API, to which you can send correctly formatted POST requests. You can also send POST requests to Known's micropub endpoint. Unfortunately, neither option works for Bookmarks (and probably not for Likes and Reposts, but I haven't played with them).</p>\n\n <p><a href=\"https://www.jeremycherfas.net/blog/why-i-cannot-post-bookmarks-to-known-automatically\">More this way ...</a></p>"
},
"_id": "100319",
"_source": "202",
"_is_read": true
}
Thanks Chris for expanding on Dries' super-welcome post about using Drupal to participate in the independent web first, and push to locked-down privatized pieces of the Internet like Facebook, Twitter, et. al. secondarily!
{
"type": "entry",
"published": "2018-02-07T23:53:22+0000",
"url": "https://mlncn.withknown.com/2018/thanks-chris-for-expanding-on-dries-super-welcome-post-about-using",
"category": [
"IndieWeb"
],
"syndication": [
"https://twitter.com/mlncn/status/961387444741419008",
"https://facebook.com/10152328966186123/posts/10155066805111123"
],
"in-reply-to": [
"http://boffosocko.com/2018/02/07/reply-to-to-pesos-or-to-posse-by-dries-buytaert/"
],
"content": {
"text": "Thanks Chris for expanding on Dries' super-welcome post about using Drupal to participate in the independent web first, and push to locked-down privatized pieces of the Internet like Facebook, Twitter, et. al. secondarily!\n\n\nI'm sure you didn't mean it this way \u2013 and honestly i was happy to be alerted to your post by https://withknown.com/ \u2013 but you seem to have pioneered a sort of webmention spam! I couldn't figure out where in your post you actually referenced me, like Known claimed, until i viewed source and saw that in empty links you had my https://mlncn.withknown.com/ blog and indeed my cooperative's post http://agaric.com/blogs/marking-drupals-blog-posts-indieweb as well as a link to the fantastic http://hongpong.com (he is more active on http://twitter.com/hongpong but is indeed working to push the #IndieWeb movement forward).\n\n\nWere you intending to alert us through webmentions, or had we come up in research but didn't end up being included in the finished post?",
"html": "Thanks Chris for expanding on Dries' super-welcome post about using Drupal to participate in the independent web first, and push to locked-down privatized pieces of the Internet like Facebook, Twitter, et. al. secondarily!<br /><br />\nI'm sure you didn't mean it this way \u2013 and honestly i was happy to be alerted to your post by <a href=\"https://withknown.com/\">https://withknown.com/</a> \u2013 but you seem to have pioneered a sort of webmention spam! I couldn't figure out where in your post you actually referenced me, like Known claimed, until i viewed source and saw that in empty links you had my <a href=\"https://mlncn.withknown.com/\">https://mlncn.withknown.com/</a> blog and indeed my cooperative's post <a href=\"http://agaric.com/blogs/marking-drupals-blog-posts-indieweb\">http://agaric.com/blogs/marking-drupals-blog-posts-indieweb</a> as well as a link to the fantastic <a href=\"http://hongpong.com\">http://hongpong.com</a> (he is more active on <a href=\"http://twitter.com/hongpong\">http://twitter.com/hongpong</a> but is indeed working to push the <a href=\"https://mlncn.withknown.com/tag/IndieWeb\" class=\"p-category\">#IndieWeb</a> movement forward).<br /><br />\nWere you intending to alert us through webmentions, or had we come up in research but didn't end up being included in the finished post?"
},
"author": {
"type": "card",
"name": "benjamin melan\u00e7on",
"url": "https://mlncn.withknown.com/profile/mlncn",
"photo": "https://mlncn.withknown.com/file/00c7d8e67682303419851cd5bf04d11d/thumb.jpg"
},
"_id": "123958",
"_source": "234",
"_is_read": true
}
{
"type": "entry",
"published": "2018-02-07T11:30:16-08:00",
"url": "https://aaronparecki.com/2018/02/07/7/indieauth",
"category": [
"indieauth",
"indieweb"
],
"name": "IndieAuth-Client-PHP 0.3.1",
"content": {
"text": "This release includes two new methods for quickly developing an IndieAuth client.\n\nThe library can now handle all the boilerplate work of generating a state parameter, URL canonicalization, and state management between the request and callback.\n\nDeveloping an IndieAuth client now requires just setting a few configuration variables and deciding how to show error messages in your application. See the code below for an example of using the new features!\n\nindex.php\n\n<form action=\"/login.php\" method=\"post\">\n <input type=\"url\" name=\"url\">\n <input type=\"submit\" value=\"Log In\">\n</form>\n\n\nlogin.php\n\n<?php\nrequire('vendor/autoload.php');\nif(!isset($_POST['url'])) {\n die('Missing URL');\n}\n\n// Start a session for the library to be able to save state between requests.\nsession_start();\n\n// You'll need to set up two pieces of information before you can use the client,\n// the client ID and and the redirect URL.\n// The client ID should be the home page of your app.\nIndieAuth\\Client::$clientID = 'https://example.com/client/';\n\n// The redirect URL is where the user will be returned to after they approve the request.\nIndieAuth\\Client::$redirectURL = 'https://example.com/client/redirect.php';\n\n// Pass the user's URL and your requested scope to the client.\n// If you are writing a Micropub client, you should include at least the \"create\" scope.\n// If you are just trying to log the user in, you can omit the second parameter.\nlist($authorizationURL, $error) = IndieAuth\\Client::begin($_POST['url']);\n// or list($authorizationURL, $error) = IndieAuth\\Client::begin($_POST['url']);\n\n// Check whether the library was able to discover the necessary endpoints\nif($error) {\n echo \"<p>Error: \".$error['error'].\"</p>\";\n echo \"<p>\".$error['error_description'].\"</p>\";\n} else {\n // Redirect the user to their authorization endpoint\n header('Location: '.$authorizationURL);\n}\n\n\nredirect.php\n\n<?php\nrequire('vendor/autoload.php');\n\nsession_start();\nIndieAuth\\Client::$clientID = 'https://example.com/client/';\nIndieAuth\\Client::$redirectURL = 'https://example.com/client/redirect.php';\n\nlist($user, $error) = IndieAuth\\Client::complete($_GET);\n\nif($error) {\n echo \"<p>Error: \".$error['error'].\"</p>\";\n echo \"<p>\".$error['error_description'].\"</p>\";\n} else {\n // Login succeeded!\n // If you requested a scope, then there will be an access token in the response.\n // Otherwise there will just be the user's URL.\n echo \"URL: \".$user['me'].\"\n\";\n if(isset($user['access_token'])) {\n echo \"Access Token: \".$user['access_token'].\"\n\";\n echo \"Scope: \".$user['scope'].\"\n\";\n }\n}",
"html": "<p>This release includes two new methods for quickly developing an IndieAuth client.</p>\n\n<p>The library can now handle all the boilerplate work of generating a state parameter, URL canonicalization, and state management between the request and callback.</p>\n\n<p>Developing an IndieAuth client now requires just setting a few configuration variables and deciding how to show error messages in your application. See the code below for an example of using the new features!</p>\n\n<h3>index.php</h3>\n\n<pre><code><form action=\"/login.php\" method=\"post\">\n <input type=\"url\" name=\"url\">\n <input type=\"submit\" value=\"Log In\">\n</form>\n</code></pre>\n\n<h3>login.php</h3>\n\n<pre><code><?php\nrequire('vendor/autoload.php');\nif(!isset($_POST['url'])) {\n die('Missing URL');\n}\n\n// Start a session for the library to be able to save state between requests.\nsession_start();\n\n// You'll need to set up two pieces of information before you can use the client,\n// the client ID and and the redirect URL.\n// The client ID should be the home page of your app.\nIndieAuth\\Client::$clientID = 'https://example.com/client/';\n\n// The redirect URL is where the user will be returned to after they approve the request.\nIndieAuth\\Client::$redirectURL = 'https://example.com/client/redirect.php';\n\n// Pass the user's URL and your requested scope to the client.\n// If you are writing a Micropub client, you should include at least the \"create\" scope.\n// If you are just trying to log the user in, you can omit the second parameter.\nlist($authorizationURL, $error) = IndieAuth\\Client::begin($_POST['url']);\n// or list($authorizationURL, $error) = IndieAuth\\Client::begin($_POST['url']);\n\n// Check whether the library was able to discover the necessary endpoints\nif($error) {\n echo \"<p>Error: \".$error['error'].\"</p>\";\n echo \"<p>\".$error['error_description'].\"</p>\";\n} else {\n // Redirect the user to their authorization endpoint\n header('Location: '.$authorizationURL);\n}\n</code></pre>\n\n<h3>redirect.php</h3>\n\n<pre><code><?php\nrequire('vendor/autoload.php');\n\nsession_start();\nIndieAuth\\Client::$clientID = 'https://example.com/client/';\nIndieAuth\\Client::$redirectURL = 'https://example.com/client/redirect.php';\n\nlist($user, $error) = IndieAuth\\Client::complete($_GET);\n\nif($error) {\n echo \"<p>Error: \".$error['error'].\"</p>\";\n echo \"<p>\".$error['error_description'].\"</p>\";\n} else {\n // Login succeeded!\n // If you requested a scope, then there will be an access token in the response.\n // Otherwise there will just be the user's URL.\n echo \"URL: \".$user['me'].\"<br>\";\n if(isset($user['access_token'])) {\n echo \"Access Token: \".$user['access_token'].\"<br>\";\n echo \"Scope: \".$user['scope'].\"<br>\";\n }\n}\n</code></pre>"
},
"author": {
"type": "card",
"name": "Aaron Parecki",
"url": "https://aaronparecki.com/",
"photo": "https://aaronparecki.com/images/profile.jpg"
},
"_id": "42695",
"_source": "16",
"_is_read": true
}
{
"type": "entry",
"published": "2018-02-05T10:12:51-08:00",
"url": "https://aaronparecki.com/2018/02/05/6/ownyourgram",
"category": [
"ownyourgram",
"indieweb",
"changelog"
],
"name": "OwnYourGram Updates",
"content": {
"text": "Just pushed a few changes to OwnYourGram this morning! Here's what changed:\nYou can now see the schedule of your account so you know when to expect photos! You'll see which tier you're at, and how long until your account is next polled.\nYou can now add a list of tags that will be sent along with every photo! This is useful if you want all your photos to be tagged \"photo\" or \"instagram\" for example.\n\n I also updated the documentation to include an example of the JSON post format that OwnYourGram can send.\u00a0\n \nIf your site has a Media Endpoint, then OwnYourGram will first upload your photos to your Media Endpoint, and include those URLs in the Micropub request.\u00a0\nThat's it for now! Happy OwnYourGramming!",
"html": "<p>Just pushed a few changes to OwnYourGram this morning! Here's what changed:</p>\n<p>You can now see the schedule of your account so you know when to expect photos! You'll see which tier you're at, and how long until your account is next polled.</p>\n<img src=\"https://aaronparecki.com/2018/02/05/6/image-1.png\" alt=\"\" /><p>You can now add a list of tags that will be sent along with every photo! This is useful if you want all your photos to be tagged \"photo\" or \"instagram\" for example.</p>\n<img src=\"https://aaronparecki.com/2018/02/05/6/image-2.png\" alt=\"\" /><p>\n I also updated the <a href=\"https://ownyourgram.com/docs\">documentation</a> to include an example of the JSON post format that OwnYourGram can send.\u00a0\n </p>\n<p>If your site has a <a href=\"https://www.w3.org/TR/micropub/#media-endpoint\">Media Endpoint</a>, then OwnYourGram will first upload your photos to your Media Endpoint, and include those URLs in the Micropub request.\u00a0</p>\n<p>That's it for now! Happy OwnYourGramming!</p>"
},
"author": {
"type": "card",
"name": "Aaron Parecki",
"url": "https://aaronparecki.com/",
"photo": "https://aaronparecki.com/images/profile.jpg"
},
"_id": "41032",
"_source": "16",
"_is_read": true
}
Wrapping up the next Micro.blog iOS update, which has more control over cross-posting. Decided to focus on Micro.blog’s own cross-posting for this release, and consider Micropub syndication later. (They are very different models. Just need to focus on the immediate need first.)
{
"type": "entry",
"author": {
"name": "manton",
"url": "http://www.manton.org",
"photo": null
},
"url": "http://www.manton.org/2018/02/6421.html",
"content": {
"html": "<p>Wrapping up the next Micro.blog iOS update, which has more control over cross-posting. Decided to focus on Micro.blog\u2019s own cross-posting for this release, and consider Micropub syndication later. (They are very different models. Just need to focus on the immediate need first.)</p>",
"text": "Wrapping up the next Micro.blog iOS update, which has more control over cross-posting. Decided to focus on Micro.blog\u2019s own cross-posting for this release, and consider Micropub syndication later. (They are very different models. Just need to focus on the immediate need first.)"
},
"published": "2018-02-04T15:28:27+00:00",
"updated": "2018-02-04T15:28:27+00:00",
"_id": "38768",
"_source": "12",
"_is_read": true
}
Remy outlines the process he uses for POSSEing to Medium now that they’ve removed their IFTTT integration.
At some point during 2017, Medium decided to pull their IFTTT applets that allows content to be posted into Medium. Which I think is a pretty shitty move since there was no notification that the applet was pulled (I only noticed after Medium just didn’t contain a few of my posts), and it smacks of “Medium should be the original source”…which may be fine for some people, but I’m expecting my own content to outlast the Medium web site.
{
"type": "entry",
"published": "2018-02-01T16:15:38Z",
"url": "https://adactio.com/links/13371",
"category": [
"indieweb",
"posse",
"medium",
"syndication",
"ifttt",
"rss"
],
"bookmark-of": [
"https://remysharp.com/2018/02/01/how-to-cross-post-to-medium"
],
"content": {
"text": "How to cross post to Medium\n\n\n\nRemy outlines the process he uses for POSSEing to Medium now that they\u2019ve removed their IFTTT integration.\n\n\n At some point during 2017, Medium decided to pull their IFTTT applets that allows content to be posted into Medium. Which I think is a pretty shitty move since there was no notification that the applet was pulled (I only noticed after Medium just didn\u2019t contain a few of my posts), and it smacks of \u201cMedium should be the original source\u201d\u2026which may be fine for some people, but I\u2019m expecting my own content to outlast the Medium web site.",
"html": "<h3>\n<a class=\"p-name u-bookmark-of\" href=\"https://remysharp.com/2018/02/01/how-to-cross-post-to-medium\">\nHow to cross post to Medium\n</a>\n</h3>\n\n<p>Remy outlines the process he uses for POSSEing to Medium now that they\u2019ve removed their IFTTT integration.</p>\n\n<blockquote>\n <p>At some point during 2017, Medium decided to pull their IFTTT applets that allows content to be posted into Medium. Which I think is a pretty shitty move since there was no notification that the applet was pulled (I only noticed after Medium just didn\u2019t contain a few of my posts), and it smacks of \u201cMedium should be the original source\u201d\u2026which may be fine for some people, but I\u2019m expecting my own content to outlast the Medium web site.</p>\n</blockquote>"
},
"_id": "35539",
"_source": "2",
"_is_read": true
}
{
"type": "entry",
"published": "2018-01-30T15:22:56-08:00",
"url": "https://aaronparecki.com/2018/01/30/23/",
"category": [
"indieweb"
],
"content": {
"text": "\"A photoblog is like Instagram, only it's harder to use, your friends aren't on it, and it's owned by you, not a megacorp.\" \ud83d\ude02 https://www.kickstarter.com/projects/davidfg/you-have-to-see-this-place",
"html": "\"A photoblog is like Instagram, only it's harder to use, your friends aren't on it, and it's owned by you, not a megacorp.\" <a href=\"https://aaronparecki.com/emoji/%F0%9F%98%82\">\ud83d\ude02</a> <a href=\"https://www.kickstarter.com/projects/davidfg/you-have-to-see-this-place\">https://www.kickstarter.com/projects/davidfg/you-have-to-see-this-place</a>"
},
"author": {
"type": "card",
"name": "Aaron Parecki",
"url": "https://aaronparecki.com/",
"photo": "https://aaronparecki.com/images/profile.jpg"
},
"_id": "41039",
"_source": "16",
"_is_read": true
}
I’m not a regular WordPress user, but willing to help however I can. There was some discussion in #indieweb-wordpress about capturing these in such a way they can be individually worked on.
{
"type": "entry",
"published": "2018-01-27 18:39-0800",
"url": "https://gregorlove.com/2018/01/im-not-a-regular-wordpress/",
"in-reply-to": [
"https://islandinthenet.com/indieweb-wordpress-feedback/"
],
"content": {
"text": "I\u2019m not a regular WordPress user, but willing to help however I can. There was some discussion in #indieweb-wordpress about capturing these in such a way they can be individually worked on.",
"html": "<p>I\u2019m not a regular WordPress user, but willing to help however I can. There was some discussion in #indieweb-wordpress about capturing these in such a way they can be individually worked on.</p>"
},
"author": {
"type": "card",
"name": "gRegor Morrill",
"url": "https://gregorlove.com/",
"photo": "https://gregorlove.com/site/assets/files/3473/profile-2016-med.jpg"
},
"refs": {
"https://islandinthenet.com/indieweb-wordpress-feedback/": {
"type": "entry",
"url": "https://islandinthenet.com/indieweb-wordpress-feedback/",
"content": {
"text": "gRegor, I agree with everything you wrote as it is similar to my initial experience with the IndieWeb \u201cGetting Started on WordPress\u201d page. Do you want to work together on fixing this?"
},
"author": {
"type": "card",
"name": "Kh\u00fcrt Williams",
"url": false,
"photo": "https://gregorlove.com/notes/"
}
}
},
"_id": "29812",
"_source": "95",
"_is_read": true
}
{
"type": "entry",
"published": "2018-01-26T08:49:05Z",
"url": "https://adactio.com/links/13356",
"category": [
"rss",
"syndication",
"reading",
"publishing",
"indieweb",
"blogging",
"sharing",
"writing",
"feedbin",
"reeder",
"history",
"personal"
],
"bookmark-of": [
"https://robinrendle.com/notes/how-to-read-the-internet/"
],
"content": {
"text": "Robin Rendle \u203a How to Read the Internet\n\n\n\nThe past, present and future of RSS.\n\n\n If I had to choose my Twitter account over my RSS setup I wouldn\u2019t hesitate for a second \u2014 I\u2019d throw Twitter right into the ocean.",
"html": "<h3>\n<a class=\"p-name u-bookmark-of\" href=\"https://robinrendle.com/notes/how-to-read-the-internet/\">\nRobin Rendle \u203a How to Read the Internet\n</a>\n</h3>\n\n<p>The past, present and future of RSS.</p>\n\n<blockquote>\n <p>If I had to choose my Twitter account over my RSS setup I wouldn\u2019t hesitate for a second \u2014 I\u2019d throw Twitter right into the ocean.</p>\n</blockquote>"
},
"_id": "27685",
"_source": "2",
"_is_read": true
}
Paul weighs up the pros and cons of using silos (like Twitter and Facebook) and using the Indie Web. This bit made me want to stand on my desk and cry, “Oh captain, my captain!”:
“The market has proven that consumers want freely available social networks that are easy to use, and used by everyone else. Only centralised services can provide this, not familiarity with a command line and a succession of acronyms and protocols”, says my not entirely fictional naysayer.
I’m not sure this argument follows. While the human desire to connect and communicate easily with each other has been proven many times over, it’s becoming clear that all-encompassing centralised networks are not the solution. That way lies algorithmically-skewed streams of consciousness, layered upon sordid business models and Californian ideology. Fuck that.
The web is agreement, but that doesn’t mean we agree to use the same websites.
{
"type": "entry",
"published": "2018-01-25T13:14:43Z",
"url": "https://adactio.com/links/13354",
"category": [
"indieweb",
"twitter",
"microblogging",
"publishing",
"personal",
"writing",
"sharing",
"decentralisation"
],
"bookmark-of": [
"https://paulrobertlloyd.com/2018/01/microblogging"
],
"content": {
"text": "Microblogging / Paul Robert Lloyd\n\n\n\nPaul weighs up the pros and cons of using silos (like Twitter and Facebook) and using the Indie Web. This bit made me want to stand on my desk and cry, \u201cOh captain, my captain!\u201d:\n\n\n \u201cThe market has proven that consumers want freely available social networks that are easy to use, and used by everyone else. Only centralised services can provide this, not familiarity with a command line and a succession of acronyms and protocols\u201d, says my not entirely fictional naysayer.\n \n I\u2019m not sure this argument follows. While the human desire to connect and communicate easily with each other has been proven many times over, it\u2019s becoming clear that all-encompassing centralised networks are not the solution. That way lies algorithmically-skewed streams of consciousness, layered upon sordid business models and Californian ideology. Fuck that.\n \n The web is agreement, but that doesn\u2019t mean we agree to use the same websites.",
"html": "<h3>\n<a class=\"p-name u-bookmark-of\" href=\"https://paulrobertlloyd.com/2018/01/microblogging\">\nMicroblogging / Paul Robert Lloyd\n</a>\n</h3>\n\n<p>Paul weighs up the pros and cons of using silos (like Twitter and Facebook) and using the Indie Web. This bit made me want to stand on my desk and cry, \u201cOh captain, my captain!\u201d:</p>\n\n<blockquote>\n <p>\u201cThe market has proven that consumers want freely available social networks that are easy to use, and used by everyone else. Only centralised services can provide this, not familiarity with a command line and a succession of acronyms and protocols\u201d, says my not entirely fictional naysayer.</p>\n \n <p>I\u2019m not sure this argument follows. While the human desire to connect and communicate easily with each other has been proven many times over, it\u2019s becoming clear that all-encompassing centralised networks are not the solution. That way lies algorithmically-skewed streams of consciousness, layered upon sordid business models and Californian ideology. Fuck that.</p>\n \n <p>The web is agreement, but that doesn\u2019t mean we agree to use the same websites.</p>\n</blockquote>"
},
"_id": "26441",
"_source": "2",
"_is_read": true
}
gRegor Morrill
liked
a post
on inessential.com
