IndieWeb

monday.micro.blog

Episode 65: Greg McVerry, aka @jgmac1106

June 24, 2019 6:48am -06:00

{
    "type": "entry",
    "author": {
        "name": null,
        "url": "https://monday.micro.blog/",
        "photo": null
    },
    "url": "https://monday.micro.blog/2019/06/24/episode-greg-mcverry.html",
    "published": "2019-06-24T06:48:40-06:00",
    "content": {
        "html": "<p>This week\u2019s guest is <a href=\"https://micro.blog/jgmac1106\">Greg McVerry</a>, associate professor of education at Southern Connecticut State University and a leader in the IndieWeb movement. He will be attending the <a href=\"https://2019.indieweb.org/summit\">IndieWeb Summit</a>, coming up on June 29 &amp; 30, 2019, in Portland, Oregon. We talk about what happens at the event and why it is a great place to come and learn, whether you are a beginner or an expert, whether you attend in person or remotely.</p>\n\n<p>We also take a bit of a detour as Greg talks about the concept and history of the <a href=\"https://indieweb.org/commonplace_book\">commonplace book</a>. He quips that the instructions John Locke wrote in 1706 for maintaining one\u2019s commonplace book could be considered the original blogging documentation. Many IndieWeb bloggers use their site as a digital commonplace book.</p>\n\n<p>Greg believes in the power of people coming together to make the internet better by working on their individual blogs:</p>\n\n<blockquote>\n<p>When you organize around people who share your values and goals, by focusing on yourself you are also helping the larger group become better itself. So: Find A Passion. Get A Blog.</p>\n</blockquote>\n\n<p></p>",
        "text": "This week\u2019s guest is Greg McVerry, associate professor of education at Southern Connecticut State University and a leader in the IndieWeb movement. He will be attending the IndieWeb Summit, coming up on June 29 & 30, 2019, in Portland, Oregon. We talk about what happens at the event and why it is a great place to come and learn, whether you are a beginner or an expert, whether you attend in person or remotely.\n\nWe also take a bit of a detour as Greg talks about the concept and history of the commonplace book. He quips that the instructions John Locke wrote in 1706 for maintaining one\u2019s commonplace book could be considered the original blogging documentation. Many IndieWeb bloggers use their site as a digital commonplace book.\n\nGreg believes in the power of people coming together to make the internet better by working on their individual blogs:\n\n\nWhen you organize around people who share your values and goals, by focusing on yourself you are also helping the larger group become better itself. So: Find A Passion. Get A Blog."
    },
    "name": "Episode 65: Greg McVerry, aka @jgmac1106",
    "audio": [
        "https://monday.micro.blog/uploads/2019/a9f8b2ac37.mp3"
    ],
    "post-type": "audio",
    "_id": "8799779",
    "_source": "250",
    "_is_read": true
}

monday.micro.blog

Episode 50: Jonathan LaCour, aka @cleverdevil

February 25, 2019 12:41pm -06:00

{
    "type": "entry",
    "author": {
        "name": null,
        "url": "https://monday.micro.blog/",
        "photo": null
    },
    "url": "https://monday.micro.blog/2019/02/25/episode-jonathan-lacour.html",
    "published": "2019-02-25T12:41:19-06:00",
    "content": {
        "html": "<p>It\u2019s the 50th episode and Jonathan LaCour is our guest! \ud83d\udc83\ud83c\udf89\ud83c\udf7e</p>\n\n<p>You know him best as <a href=\"https://micro.blog/cleverdevil\">@cleverdevil</a>, the creator of utilities that enhance your microblog such as <a href=\"https://github.com/cleverdevil/microgram\">microgram</a> (an Instagram-like photo grid page), and <a href=\"https://github.com/cleverdevil/micromemories\">micromemories</a> (a Facebook-like \u201cOn This Day\u201d feature). We talk about the Indieweb and <a href=\"https://github.com/cleverdevil/ditchbook\">ditching Facebook with ditchbook</a>. We even mention dogs and karaoke.</p>\n\n<p></p>",
        "text": "It\u2019s the 50th episode and Jonathan LaCour is our guest! \ud83d\udc83\ud83c\udf89\ud83c\udf7e\n\nYou know him best as @cleverdevil, the creator of utilities that enhance your microblog such as microgram (an Instagram-like photo grid page), and micromemories (a Facebook-like \u201cOn This Day\u201d feature). We talk about the Indieweb and ditching Facebook with ditchbook. We even mention dogs and karaoke."
    },
    "name": "Episode 50: Jonathan LaCour, aka @cleverdevil",
    "audio": [
        "https://monday.micro.blog/uploads/2019/46946475e1.mp3"
    ],
    "post-type": "audio",
    "_id": "8799794",
    "_source": "250",
    "_is_read": true
}

monday.micro.blog

Micro Monday Extra: Late Night In The Airstream with @aaronpk at XOXO

September 9, 2018 8:51am -06:00

{
    "type": "entry",
    "author": {
        "name": null,
        "url": "https://monday.micro.blog/",
        "photo": null
    },
    "url": "https://monday.micro.blog/2018/09/09/145123.html",
    "published": "2018-09-09T08:51:23-06:00",
    "content": {
        "html": "<p>I get a second chance to record in the very cool Airstream podcast studio at <a href=\"https://2018.xoxofest.com/\">XOXO conference</a>, because I ran into <a href=\"https://micro.blog/aaronpk\">Aaron Parecki</a>. He is an organizer at <a href=\"https://streampdx.com/\">StreamPDX</a>, so he has the keys to the Airstream! Aaron is also one of the founders of the IndieWeb movement, so we talk about IndieWeb, Micro.blog, and the importance of having your own domain to control your content and your internet presence.</p>\n\n<p><a href=\"https://indieweb.org/\">IndieWebCamp</a></p>\n\n<p><a href=\"https://indiewebcat.com/\">IndieWebCat</a></p>\n\n<p><br /></p>",
        "text": "I get a second chance to record in the very cool Airstream podcast studio at XOXO conference, because I ran into Aaron Parecki. He is an organizer at StreamPDX, so he has the keys to the Airstream! Aaron is also one of the founders of the IndieWeb movement, so we talk about IndieWeb, Micro.blog, and the importance of having your own domain to control your content and your internet presence.\n\nIndieWebCamp\n\nIndieWebCat"
    },
    "name": "Micro Monday Extra: Late Night In The Airstream with @aaronpk at XOXO",
    "audio": [
        "http://monday.micro.blog/uploads/2018/55a79861bd.mp3"
    ],
    "post-type": "audio",
    "_id": "8799818",
    "_source": "250",
    "_is_read": true
}

monday.micro.blog

IndieWebCamp Online is this weekend. It’s all remote, so you can jump into the video chat and participate or lurk to learn about IndieWeb building blocks. And then in 2 weeks: IndieWebCamp Austin! 2-day event at Capital Factory.

February 7, 2020 8:26am -06:00

{
    "type": "entry",
    "author": {
        "name": "Manton Reece",
        "url": "https://www.manton.org/",
        "photo": "https://micro.blog/manton/avatar.jpg"
    },
    "url": "https://www.manton.org/2020/02/07/indiewebcamp-online-is.html",
    "content": {
        "html": "<p><a href=\"https://indieweb.org/2020/Online\">IndieWebCamp Online</a> is this weekend. It\u2019s all remote, so you can jump into the video chat and participate or lurk to learn about IndieWeb building blocks. And then in 2 weeks: <a href=\"https://2020.indieweb.org/austin\">IndieWebCamp Austin</a>! 2-day event at Capital Factory.</p>",
        "text": "IndieWebCamp Online is this weekend. It\u2019s all remote, so you can jump into the video chat and participate or lurk to learn about IndieWeb building blocks. And then in 2 weeks: IndieWebCamp Austin! 2-day event at Capital Factory."
    },
    "published": "2020-02-07T08:26:58-06:00",
    "post-type": "note",
    "_id": "8697439",
    "_source": "12",
    "_is_read": true
}

Vika fireburn.ru

Searching for an #IndieWeb thing I could implement in Go.

Maybe a rewrite of my #Micropub server? (although I didnt deploy the new async version yet)

February 7, 2020 12:11pm +00:00

{
    "type": "entry",
    "published": "2020-02-07T12:11:15+00:00",
    "url": "https://fireburn.ru/posts/1581077475",
    "syndication": [
        "https://twitter.com/kisik21/status/1225753910171840513"
    ],
    "content": {
        "text": "Searching for an #IndieWeb thing I could implement in Go.\nMaybe a rewrite of my #Micropub server? (although I didnt deploy the new async version yet)",
        "html": "<p>Searching for an #IndieWeb thing I could implement in Go.</p>\n<p>Maybe a rewrite of my #Micropub server? (although I didnt deploy the new async version yet)</p>"
    },
    "author": {
        "type": "card",
        "name": "Vika",
        "url": "https://fireburn.ru/",
        "photo": "https://fireburn.ru/media/f1/5a/fb/9b/081efafb97b4ad59f5025cf2fd0678b8f3e20e4c292489107d52be09.png"
    },
    "post-type": "note",
    "_id": "8693405",
    "_source": "1371",
    "_is_read": true
}

Tantek Çelik tantek.com

Local First, Undo Redo, JS-Optional, Create Edit Publish

February 6, 2020 1:11am -08:00

{
    "type": "entry",
    "published": "2020-02-06 01:11-0800",
    "url": "http://tantek.com/2020/037/b2/local-first-undo-redo-create-edit-publish",
    "name": "Local First, Undo Redo, JS-Optional, Create Edit Publish",
    "content": {
        "text": "For a while I have brainstormed designs for a user experience (UX) to create, edit, and publish notes and other types of posts, that is fully undoable (like Gmail\u2019s \"Undo Send\" yet generalized to to all user actions) and redoable, works local first, and lastly, uses progressive enhancement to work without scripts in the extreme fallback case of not being installed, and scripts not loading.\n\n\nI\u2019d like to be able to construct an entire post, like a photo post with caption, people tags, location tag etc. all locally, offline, without any need to access a network.\n\n\nThis is like how old email applications used to work. You could be completely offline, open your email application (there was no need to login to it!), create a message, add attachments, edit it etc., click \"Send\" and then forgot about it. Eventually it synced to the network but you didn\u2019t worry or care about when that step would happen, you just knew it would eventually work without you having to tend to it or watch it.\n\n\nI want to approach this from user-experience-first design perspective, rather than a bottom-up protocol/technology/backend first perspective. For one, I don\u2019t know if any existing protocols actually have the necessary features to support such a user experience (UX). \nMicropub has a lot of what\u2019s needed, and I won\u2019t know what else is needed until I build the user flows I want, and then use those drive any necessary Micropub feature additions. I absolutely do not want to limit my UX by what an existing protocol can or cannot do (essentally the software design version of the tail wags dog problem).\n\n\nLocal First\n\n\nI wrote up a brief stub article on the IndieWeb wiki on \nlocal first.\nI see local first as an essential aspect of an authoring experience that is maximally responsive to user input, and avoids any and all unnecessary ties to other services.\n\n\nI want a 100% local first offline capable creating / editing / posting workflow which then \u201cauto-syncs\u201d once the network shows up. The presence / absence of internet access should not affect user flow at all. Network presence or absence should only be a status indicator (e.g. whether / how much a post has been sent to the internet or not, any edits / updates etc.). It should never block any user actions. I\u2019ll say it again for emphasis:\n\n\nThe absence or presence of network access must not block any user actions. Ever. Any changes should be effective locally immediately, with zero data loss.\n\n\nOf course nearly no one actually builds apps like that today. Even typical mobile \u201cnative\u201d apps fail without network access (a couple of counter-examples are the iOS built-in Notes & Photos apps, as well as the independent maps.me 100% offline mapping program). Some \u201coffline first\u201d apps get close. But even those, especially on mobile, fail in both predictable (like requiring logging into site or service on the network, just to edit a local text document) and strange ways.\n\n\nFull Undo Redo\n\n\nEvery such user action should be undoable and redoable, again, without waiting for the network (it\u2019s reasonable to apply some time limits for some actions, e.g. Gmail Undo can be configured to work for 30 seconds). Now imagine that for any user action, especialy any user action that creates, edits, or deletes content or any aspects thereof (like name, tags, location etc.).\n\n\nJS-Optional\n\n\nIn the case where a web application has not yet been installed, I also want it to be 100% capable without depending on loading any external scripts. \nThis JS-Optional approach is more broadly known as \nprogressive enhancement, which does require that you have at least some connection, enough for a browser to submit form requests and retrieve static HTML (and preferably though not required, static CSS and image files too).\n\n\nObviously once you are connected and are running at least a service worker for the site, local first requires execution of some scripts, though even then dependencies on any external scripts should be minimized and preferably eliminated.\nI do have a Service Worker and offline reading support on my site so I\u2019m getting there.\n\n\nIncremental Progress\n\n\nI believe aspects of this experience can be built and deployed incrementally, iterating over time until the full system is built.\n\nI\u2019ve got a handful of paper sketches of local-first undoable/redoable user flows. I have a service worker deployed on my site that allows viewers to browse offline the pages they\u2019ve previously visited, and I have a form submission user interface that handles part of publishing. There\u2019s a lot more to do, and as I think of them I add them to \npart of my \u201cWorking On\u201d list on the IndieWeb Wiki, iteratively reprioritizing and making incremental progress at IndieWebCamps.\n\n\nOne building block at a time, collaboratively.",
        "html": "<p>\nFor a while I have brainstormed designs for a user experience (UX) to create, edit, and publish notes and other types of posts, that is fully undoable (like Gmail\u2019s \"Undo Send\" yet generalized to to all user actions) and redoable, works local first, and lastly, uses progressive enhancement to work without scripts in the extreme fallback case of not being installed, and scripts not loading.\n</p>\n<p>\nI\u2019d like to be able to construct an entire post, like a photo post with caption, people tags, location tag etc. all locally, offline, without any need to access a network.\n</p>\n<p>\nThis is like how old email applications used to work. You could be completely offline, open your email application (there was no need to login to it!), create a message, add attachments, edit it etc., click \"Send\" and then forgot about it. Eventually it synced to the network but you didn\u2019t worry or care about when that step would happen, you just knew it would eventually work without you having to tend to it or watch it.\n</p>\n<p>\nI want to approach this from user-experience-first design perspective, rather than a bottom-up protocol/technology/backend first perspective. For one, I don\u2019t know if any existing protocols actually have the necessary features to support such a user experience (UX). \n<a href=\"https://micropub.net/\">Micropub</a> has a lot of what\u2019s needed, and I won\u2019t know what else is needed until I build the user flows I want, and then use those drive any necessary Micropub feature additions. I absolutely do not want to limit my UX by what an existing protocol can or cannot do (essentally the software design version of the tail wags dog problem).\n</p>\n<h2>\nLocal First\n</h2>\n<p>\nI wrote up a brief stub article on the IndieWeb wiki on \n<a href=\"https://indieweb.org/local_first\">local first</a>.\nI see local first as an essential aspect of an authoring experience that is maximally responsive to user input, and avoids any and all unnecessary ties to other services.\n</p>\n<p>\nI want a 100% local first offline capable creating / editing / posting workflow which then \u201cauto-syncs\u201d once the network shows up. The presence / absence of internet access should not affect user flow at all. Network presence or absence should only be a status indicator (e.g. whether / how much a post has been sent to the internet or not, any edits / updates etc.). It should never block any user actions. I\u2019ll say it again for emphasis:\n</p>\n<p>\nThe absence or presence of network access must not block any user actions. Ever. Any changes should be effective locally immediately, with zero data loss.\n</p>\n<p>\nOf course nearly no one actually builds apps like that today. Even typical mobile \u201cnative\u201d apps fail without network access (a couple of counter-examples are the iOS built-in Notes &amp; Photos apps, as well as the independent <a href=\"https://maps.me\">maps.me</a> 100% offline mapping program). Some \u201coffline first\u201d apps get close. But even those, especially on mobile, fail in both predictable (like requiring logging into site or service on the network, just to edit a local text document) and strange ways.\n</p>\n<h2>\nFull Undo Redo\n</h2>\n<p>\nEvery such user action should be undoable and redoable, again, without waiting for the network (it\u2019s reasonable to apply some time limits for some actions, e.g. Gmail Undo can be configured to work for 30 seconds). Now imagine that for any user action, especialy any user action that creates, edits, or deletes content or any aspects thereof (like name, tags, location etc.).\n</p>\n<h2>\nJS-Optional\n</h2>\n<p>\nIn the case where a web application has not yet been installed, I also want it to be 100% capable without depending on loading any external scripts. \nThis JS-Optional approach is more broadly known as \n<a href=\"https://indieweb.org/progressive_enhancement\">progressive enhancement</a>, which does require that you have at least some connection, enough for a browser to submit form requests and retrieve static HTML (and preferably though not required, static CSS and image files too).\n</p>\n<p>\nObviously once you are connected and are running at least a service worker for the site, local first requires execution of some scripts, though even then dependencies on any external scripts should be minimized and preferably eliminated.\nI do have a Service Worker and offline reading support on my site so I\u2019m getting there.\n</p>\n<h2>\nIncremental Progress\n</h2>\n<p>\nI believe aspects of this experience can be built and deployed incrementally, iterating over time until the full system is built.\n</p>\n<p>I\u2019ve got a handful of paper sketches of local-first undoable/redoable user flows. I have a service worker deployed on my site that allows viewers to browse offline the pages they\u2019ve previously visited, and I have a form submission user interface that handles part of publishing. There\u2019s a lot more to do, and as I think of them I add them to \n<a href=\"https://indieweb.org/Falcon#better_post_creation_UI\">part of my \u201cWorking On\u201d list on the IndieWeb Wiki</a>, iteratively reprioritizing and making incremental progress at IndieWebCamps.\n</p>\n<p>\nOne building block at a time, collaboratively.\n</p>"
    },
    "author": {
        "type": "card",
        "name": "Tantek \u00c7elik",
        "url": "http://tantek.com/",
        "photo": "https://aperture-media.p3k.io/tantek.com/acfddd7d8b2c8cf8aa163651432cc1ec7eb8ec2f881942dca963d305eeaaa6b8.jpg"
    },
    "post-type": "article",
    "_id": "8656126",
    "_source": "1",
    "_is_read": true
}

events.indieweb.org/2020/02/homebrew-website-club-san-francisco-hqCpkmN9nNsL

Alex Kearney kongaloosh.com

I'm at my first Homebrew Website Club in three years, and It's the San Francisco Meetup in the Mozilla office! I feel like I've made a pilgrimage to a spiritual centre of the indieweb.

All of us indie-folks are really fortunate that the indieweb is such a warm and welcoming community.

At: Homebrew Website Club

From 2020-02-05T18:30 To 2020-02-05T20:00 indieweb dev

February 5, 2020 12:00am +00:00

{
    "type": "entry",
    "published": "2020-02-05 00:00:00",
    "url": "https://kongaloosh.com/e/2020/2/5/im-at-my-f",
    "photo": [
        "https://kongaloosh.com/data/2020/2/5/2020-02-05--23-59-50.jpg"
    ],
    "syndication": [
        "https://twitter.com/kongaloosh/status/1225286024122830848"
    ],
    "in-reply-to": [
        "https://events.indieweb.org/2020/02/homebrew-website-club-san-francisco-hqCpkmN9nNsL"
    ],
    "content": {
        "text": "I'm at my first Homebrew Website Club in three years, and It's the San Francisco Meetup in the Mozilla office! I feel like I've made a pilgrimage to a spiritual centre of the indieweb. \nAll of us indie-folks are really fortunate that the indieweb is such a warm and welcoming community. \n\n\n    \n    \n        \n    \n\n\n            \n\n        \n        \n            \n            \n        \n        \n\n\n        \n        \n            At: Homebrew Website Club\n            \nFrom 2020-02-05T18:30\n            To 2020-02-05T20:00\n        \n        \n\n\n                                 \n                                            \n                \n                \n                \n                indieweb\n                \n                dev",
        "html": "<p>I'm at my first Homebrew Website Club in three years, and It's the San Francisco Meetup in the Mozilla office! I feel like I've made a pilgrimage to a spiritual centre of the indieweb. </p>\n<p>All of us indie-folks are really fortunate that the indieweb is such a warm and welcoming community. </p>\n<p>\n</p>\n    \n    <a href=\"https://kongaloosh.com/images/data/2020/2/5/2020-02-05--23-59-50.jpg\">\n        </a>\n    \n\n\n            \n\n        \n        \n            <p></p>\n            \n        \n        \n\n\n        \n        \n            <h4>At: Homebrew Website Club</h4>\n            <p></p>\n<b>From</b> <a class=\"dt-start\">2020-02-05T18:30</a>\n            <b>To</b> <a class=\"dt-end\">2020-02-05T20:00</a>\n        \n        \n\n\n                                 \n                                            \n                \n                <i></i>\n                \n                <a href=\"https://kongaloosh.com/t/indieweb\">indieweb</a>\n                \n                <a href=\"https://kongaloosh.com/t/dev\">dev</a>"
    },
    "author": {
        "type": "card",
        "name": "Alex Kearney",
        "url": "http://kongaloosh.com",
        "photo": null
    },
    "post-type": "reply",
    "_id": "8656068",
    "_source": "228",
    "_is_read": true
}

Tantek Çelik tantek.com

Local First, Undo Redo, JS-Optional, Create Edit Publish UX

February 6, 2020 1:11am -08:00

{
    "type": "entry",
    "published": "2020-02-06 01:11-0800",
    "url": "http://tantek.com/2020/037/b2/local-first-undo-redo-create-edit-publish-ux",
    "name": "Local First, Undo Redo, JS-Optional, Create Edit Publish UX",
    "content": {
        "text": "For a while I have brainstormed designs for a user experience (UX) to create, edit, and publish notes and other types of posts, that is fully undoable (like Gmail\u2019s \"Undo Send\" yet generalized to to all user actions) and redoable, works local first, and lastly, uses progressive enhancement to work without scripts in the extreme fallback case of not being installed, and scripts not loading.\n\n\nI\u2019d like to be able to construct an entire post, like a photo post with caption, people tags, location tag etc. all locally, offline, without any need to access a network.\n\n\nThis is like how old email applications used to work. You could be completely offline, open your email application (there was no need to login to it!), create a message, add attachments, edit it etc., click \"Send\" and then forgot about it. Eventually it synced to the network but you didn\u2019t worry or care about when that step would happen, you just knew it would eventually work without you having to tend to it or watch it.\n\n\nI want to approach this from user-experience-first design perspective, rather than a bottom-up protocol/technology/backend first perspective. For one, I don\u2019t know if any existing protocols actually have the necessary features to support such a user experience (UX). \nMicropub has a lot of what\u2019s needed, and I won\u2019t know what else is needed until I build the user flows I want, and then use those drive any necessary Micropub feature additions. I absolutely do not want to limit my UX by what an existing protocol can or cannot do (essentally the software design version of the tail wags dog problem).\n\n\nLocal First\n\n\nI wrote up a brief stub article on the IndieWeb wiki on \nlocal first.\nI see local first as an essential aspect of an authoring experience that is maximally responsive to user input, and avoids any and all unnecessary ties to other services.\n\n\nI want a 100% local first offline capable creating / editing / posting workflow which then \u201cauto-syncs\u201d once the network shows up. The presence / absence of internet access should not affect user flow at all. Network presence or absence should only be a status indicator (e.g. whether / how much a post has been sent to the internet or not, any edits / updates etc.). It should never block any user actions. I\u2019ll say it again for emphasis:\n\n\nThe absence or presence of network access must not block any user actions. Ever. Any changes should be effective locally immediately, with zero data loss.\n\n\nOf course nearly no one actually builds apps like that today. Even typical mobile \u201cnative\u201d apps fail without network access (a couple of counter-examples are the iOS built-in Notes & Photos apps, as well as the independent maps.me 100% offline mapping program). Some \u201coffline first\u201d apps get close. But even those, especially on mobile, fail in both predictable (like requiring logging into site or service on the network, just to edit a local text document) and strange ways.\n\n\nFull Undo Redo\n\n\nEvery such user action should be undoable and redoable, again, without waiting for the network (it\u2019s reasonable to apply some time limits for some actions, e.g. Gmail Undo can be configured to work for 30 seconds). Now imagine that for any user action, especialy any user action that creates, edits, or deletes content or any aspects thereof (like name, tags, location etc.).\n\n\nJS-Optional\n\n\nIn the case where a web application has not yet been installed, I also want it to be 100% capable without depending on loading any external scripts. \nThis JS-Optional approach is more broadly known as \nprogressive enhancement, which does require that you have at least some connection, enough for a browser to submit form requests and retrieve static HTML (and preferably though not required, static CSS and image files too).\n\n\nObviously once you are connected and are running at least a service worker for the site, local first requires execution of some scripts, though even then dependencies on any external scripts should be minimized and preferably eliminated.\nI do have a Service Worker and offline reading support on my site so I\u2019m getting there.\n\n\nIncremental Progress\n\n\nI believe aspects of this experience can be built and deployed incrementally, iterating over time until the full system is built.\n\nI\u2019ve got a handful of paper sketches of local-first undoable/redoable user flows. I have a service worker deployed on my site that allows viewers to browse offline the pages they\u2019ve previously visited, and I have a form submission user interface that handles part of publishing. There\u2019s a lot more to do, and as I think of them I add them to \npart of my \u201cWorking On\u201d list on the IndieWeb Wiki, iteratively reprioritizing and making incremental progress at IndieWebCamps.\n\n\nOne building block at a time, collaboratively.",
        "html": "<p>\nFor a while I have brainstormed designs for a user experience (UX) to create, edit, and publish notes and other types of posts, that is fully undoable (like Gmail\u2019s \"Undo Send\" yet generalized to to all user actions) and redoable, works local first, and lastly, uses progressive enhancement to work without scripts in the extreme fallback case of not being installed, and scripts not loading.\n</p>\n<p>\nI\u2019d like to be able to construct an entire post, like a photo post with caption, people tags, location tag etc. all locally, offline, without any need to access a network.\n</p>\n<p>\nThis is like how old email applications used to work. You could be completely offline, open your email application (there was no need to login to it!), create a message, add attachments, edit it etc., click \"Send\" and then forgot about it. Eventually it synced to the network but you didn\u2019t worry or care about when that step would happen, you just knew it would eventually work without you having to tend to it or watch it.\n</p>\n<p>\nI want to approach this from user-experience-first design perspective, rather than a bottom-up protocol/technology/backend first perspective. For one, I don\u2019t know if any existing protocols actually have the necessary features to support such a user experience (UX). \n<a href=\"https://micropub.net/\">Micropub</a> has a lot of what\u2019s needed, and I won\u2019t know what else is needed until I build the user flows I want, and then use those drive any necessary Micropub feature additions. I absolutely do not want to limit my UX by what an existing protocol can or cannot do (essentally the software design version of the tail wags dog problem).\n</p>\n<h2>\nLocal First\n</h2>\n<p>\nI wrote up a brief stub article on the IndieWeb wiki on \n<a href=\"https://indieweb.org/local_first\">local first</a>.\nI see local first as an essential aspect of an authoring experience that is maximally responsive to user input, and avoids any and all unnecessary ties to other services.\n</p>\n<p>\nI want a 100% local first offline capable creating / editing / posting workflow which then \u201cauto-syncs\u201d once the network shows up. The presence / absence of internet access should not affect user flow at all. Network presence or absence should only be a status indicator (e.g. whether / how much a post has been sent to the internet or not, any edits / updates etc.). It should never block any user actions. I\u2019ll say it again for emphasis:\n</p>\n<p>\nThe absence or presence of network access must not block any user actions. Ever. Any changes should be effective locally immediately, with zero data loss.\n</p>\n<p>\nOf course nearly no one actually builds apps like that today. Even typical mobile \u201cnative\u201d apps fail without network access (a couple of counter-examples are the iOS built-in Notes &amp; Photos apps, as well as the independent <a href=\"https://maps.me\">maps.me</a> 100% offline mapping program). Some \u201coffline first\u201d apps get close. But even those, especially on mobile, fail in both predictable (like requiring logging into site or service on the network, just to edit a local text document) and strange ways.\n</p>\n<h2>\nFull Undo Redo\n</h2>\n<p>\nEvery such user action should be undoable and redoable, again, without waiting for the network (it\u2019s reasonable to apply some time limits for some actions, e.g. Gmail Undo can be configured to work for 30 seconds). Now imagine that for any user action, especialy any user action that creates, edits, or deletes content or any aspects thereof (like name, tags, location etc.).\n</p>\n<h2>\nJS-Optional\n</h2>\n<p>\nIn the case where a web application has not yet been installed, I also want it to be 100% capable without depending on loading any external scripts. \nThis JS-Optional approach is more broadly known as \n<a href=\"https://indieweb.org/progressive_enhancement\">progressive enhancement</a>, which does require that you have at least some connection, enough for a browser to submit form requests and retrieve static HTML (and preferably though not required, static CSS and image files too).\n</p>\n<p>\nObviously once you are connected and are running at least a service worker for the site, local first requires execution of some scripts, though even then dependencies on any external scripts should be minimized and preferably eliminated.\nI do have a Service Worker and offline reading support on my site so I\u2019m getting there.\n</p>\n<h2>\nIncremental Progress\n</h2>\n<p>\nI believe aspects of this experience can be built and deployed incrementally, iterating over time until the full system is built.\n</p>\n<p>I\u2019ve got a handful of paper sketches of local-first undoable/redoable user flows. I have a service worker deployed on my site that allows viewers to browse offline the pages they\u2019ve previously visited, and I have a form submission user interface that handles part of publishing. There\u2019s a lot more to do, and as I think of them I add them to \n<a href=\"https://indieweb.org/Falcon#better_post_creation_UI\">part of my \u201cWorking On\u201d list on the IndieWeb Wiki</a>, iteratively reprioritizing and making incremental progress at IndieWebCamps.\n</p>\n<p>\nOne building block at a time, collaboratively.\n</p>"
    },
    "author": {
        "type": "card",
        "name": "Tantek \u00c7elik",
        "url": "http://tantek.com/",
        "photo": "https://aperture-media.p3k.io/tantek.com/acfddd7d8b2c8cf8aa163651432cc1ec7eb8ec2f881942dca963d305eeaaa6b8.jpg"
    },
    "post-type": "article",
    "_id": "8656064",
    "_source": "1",
    "_is_read": true
}

github.com/snarfed/bridgy/issues

Tantek Çelik tantek.com

Consider support for Bridgy Publish to Micropub servers

#publish

February 6, 2020 12:24am -08:00

{
    "type": "entry",
    "published": "2020-02-06 00:24-0800",
    "url": "http://tantek.com/2020/037/b1/",
    "category": [
        "publish"
    ],
    "in-reply-to": [
        "https://github.com/snarfed/bridgy/issues"
    ],
    "name": "Consider support for Bridgy Publish to Micropub servers",
    "content": {
        "text": "Per and as promised in  \nmy reply to issue 796 \n(comment on #796),\nit may be of some value to add Micropub as a generic Bridgy Publish destination, \nthat is, Bridgy Publish acting as a Micropub client to post to Micropub servers.\n\n\nOne possible use-case would be Bridgy Publish to silo.pub, and thus potentially enabling use of Webmention to Bridgy Publish as a method to gain access to any additional destinations that silo.pub itself supports. I.e.:\n\n\nindiewebsite --Webmention-> Bridgy Publish --Micropub-> silo.pub --\u2744\ufe0fAPI-> silo\n\n\nLabel: publish.",
        "html": "<p>\nPer and as promised in  \n<a href=\"https://tantek.com/2018/057/t2/issue-name-micropub-bridgy-publish\">my reply to issue 796</a> \n(<a href=\"https://github.com/snarfed/bridgy/issues/796#issuecomment-368721844\">comment on #796</a>),\nit may be of some value to add Micropub as a generic Bridgy Publish destination, \nthat is, Bridgy Publish acting as a Micropub client <em>to</em> post to Micropub servers.\n</p>\n<p>\nOne possible use-case would be Bridgy Publish to silo.pub, and thus potentially enabling use of Webmention to Bridgy Publish as a method to gain access to any additional destinations that silo.pub itself supports. I.e.:\n</p>\n<p>\nindiewebsite --Webmention-&gt; Bridgy Publish --Micropub-&gt; silo.pub --\u2744\ufe0fAPI-&gt; silo\n</p>\n<p>\nLabel: <span class=\"p-category\">publish</span>.\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/snarfed/bridgy/issues": {
            "type": "entry",
            "url": "https://github.com/snarfed/bridgy/issues",
            "name": "GitHub project \u201cbridgy\u201d",
            "post-type": "article"
        }
    },
    "_id": "8654070",
    "_source": "1",
    "_is_read": true
}

kongaloosh.com/e/2020/2/5/im-at-my-f

Tantek Çelik tantek.com

@kongaloosh So good to finally meet you! Remember to RSVP to the next one too!
https://events.indieweb.org/2020/02/homebrew-website-club-san-francisco-eiKvWhy3hxoE

February 5, 2020 10:29pm -08:00

{
    "type": "entry",
    "published": "2020-02-05 22:29-0800",
    "url": "http://tantek.com/2020/036/t3/",
    "in-reply-to": [
        "https://kongaloosh.com/e/2020/2/5/im-at-my-f"
    ],
    "content": {
        "text": "@kongaloosh So good to finally meet you! Remember to RSVP to the next one too!\nhttps://events.indieweb.org/2020/02/homebrew-website-club-san-francisco-eiKvWhy3hxoE",
        "html": "<a class=\"h-cassis-username\" href=\"https://twitter.com/kongaloosh\">@kongaloosh</a> So good to finally meet you! Remember to RSVP to the next one too!<br /><a href=\"https://events.indieweb.org/2020/02/homebrew-website-club-san-francisco-eiKvWhy3hxoE\">https://events.indieweb.org/2020/02/homebrew-website-club-san-francisco-eiKvWhy3hxoE</a>"
    },
    "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://kongaloosh.com/e/2020/2/5/im-at-my-f": {
            "type": "entry",
            "url": "https://kongaloosh.com/e/2020/2/5/im-at-my-f",
            "name": "kongaloosh.com\u2019s post",
            "post-type": "article"
        }
    },
    "_id": "8651716",
    "_source": "1",
    "_is_read": true
}

Episode 65: Greg McVerry, aka @jgmac1106

Episode 50: Jonathan LaCour, aka @cleverdevil

Micro Monday Extra: Late Night In The Airstream with @aaronpk at XOXO

18: @EddieHinkle

Episode 17: @eli

Local First, Undo Redo, JS-Optional, Create Edit Publish

At: Homebrew Website Club

Local First, Undo Redo, JS-Optional, Create Edit Publish UX

Consider support for Bridgy Publish to Micropub servers