The @IndieWebCamp community has been busy this weekend at IndieWebCamp Online! (https://indieweb.org/2020/Online)
Virtual keynotes & sessions yesterday (see link), great projects & people creating today: https://indieweb.org/2020/Online#Hack_Day_Goals.2FProjects
Join in! https://chat.indieweb.org/
{
"type": "entry",
"published": "2020-02-09 15:56-0800",
"url": "http://tantek.com/2020/040/t1/indiewebcamp-online-keynotes-sessions-projects",
"content": {
"text": "The @IndieWebCamp community has been busy this weekend at IndieWebCamp Online! (https://indieweb.org/2020/Online)\nVirtual keynotes & sessions yesterday (see link), great projects & people creating today: https://indieweb.org/2020/Online#Hack_Day_Goals.2FProjects\n\nJoin in! https://chat.indieweb.org/",
"html": "The <a class=\"h-cassis-username\" href=\"https://twitter.com/IndieWebCamp\">@IndieWebCamp</a> community has been busy this weekend at IndieWebCamp Online! (<a href=\"https://indieweb.org/2020/Online\">https://indieweb.org/2020/Online</a>)<br />Virtual keynotes & sessions yesterday (see link), great projects & people creating today: <a href=\"https://indieweb.org/2020/Online#Hack_Day_Goals.2FProjects\">https://indieweb.org/2020/Online#Hack_Day_Goals.2FProjects</a><br /><br />Join in! <a href=\"https://chat.indieweb.org/\">https://chat.indieweb.org/</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": "8769787",
"_source": "1",
"_is_read": true
}
I was invited to IndieWebCamp Online 2020and I will be there :3 I hope it will be fun!
#IndieWebCamp
{
"type": "entry",
"published": "2020-02-08T12:47:30+00:00",
"rsvp": "i was invited to indiewebcamp online 2020and i will be there :3 i hope it will be fun!",
"url": "https://fireburn.ru/posts/1581166050",
"category": [
"IndieWebCamp"
],
"in-reply-to": [
"https://events.indieweb.org/2020/02/indiewebcamp-online-gUpSVUxbUKhv"
],
"content": {
"text": "I was invited to IndieWebCamp Online 2020and I will be there :3 I hope it will be fun!\n\n#IndieWebCamp",
"html": "<p class=\"p-rsvp\">I was invited to <a href=\"https://events.indieweb.org/2020/02/indiewebcamp-online-gUpSVUxbUKhv\" class=\"u-in-reply-to\">IndieWebCamp Online 2020</a>and I will be there :3 I hope it will be fun!</p>\n\n<p>#IndieWebCamp</p>"
},
"author": {
"type": "card",
"name": "Vika",
"url": "https://fireburn.ru/",
"photo": "https://fireburn.ru/media/f1/5a/fb/9b/081efafb97b4ad59f5025cf2fd0678b8f3e20e4c292489107d52be09.png"
},
"post-type": "rsvp",
"_id": "8728445",
"_source": "1371",
"_is_read": true
}
@indiewebcat jumping at a sparkly ball from above
{
"type": "entry",
"published": "2020-02-07T21:38:51-08:00",
"url": "https://aaronparecki.com/2020/02/07/16/kitten",
"category": [
"mbfeb"
],
"photo": [
"https://aperture-media.p3k.io/aaronparecki.com/0955475616af671d06761de885d98cf3a0ea9bac0d2d96b99a84e015718a9a1c.jpg"
],
"content": {
"text": "@indiewebcat jumping at a sparkly ball from above",
"html": "<a href=\"https://indiewebcat.com\">@indiewebcat</a> jumping at a sparkly ball from above"
},
"author": {
"type": "card",
"name": "Aaron Parecki",
"url": "https://aaronparecki.com/",
"photo": "https://aperture-media.p3k.io/aaronparecki.com/41061f9de825966faa22e9c42830e1d4a614a321213b4575b9488aa93f89817a.jpg"
},
"post-type": "photo",
"_id": "8720109",
"_source": "16",
"_is_read": true
}
{
"type": "entry",
"published": "2020-02-07 16:36-0800",
"rsvp": "yes",
"url": "http://tantek.com/2020/038/t2/hosting-homebrew-website-club-sf",
"in-reply-to": [
"https://events.indieweb.org/2020/02/homebrew-website-club-san-francisco-eiKvWhy3hxoE"
],
"content": {
"text": "hosting Homebrew Website Club SF!\n\ud83d\uddd3 17:30 Wed 2020-02-19\n\ud83d\udccd @MozSF\n\ud83c\udf9f RSVP etc. https://events.indieweb.org/2020/02/homebrew-website-club-san-francisco-eiKvWhy3hxoE\n\u2709\ufe0f Join us! @brb_irl @Kongaloosh @indirect @JackyAlcine @generativist @AndiGalpern @allaboutgeorge @benwerd @dietrich @pvh @JohnMattDavis @html5cat et al",
"html": "hosting Homebrew Website Club SF!<br />\ud83d\uddd3 17:30 Wed 2020-02-19<br />\ud83d\udccd <a class=\"h-cassis-username\" href=\"https://twitter.com/MozSF\">@MozSF</a><br />\ud83c\udf9f RSVP etc. <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><br />\u2709\ufe0f Join us! <a class=\"h-cassis-username\" href=\"https://twitter.com/brb_irl\">@brb_irl</a> <a class=\"h-cassis-username\" href=\"https://twitter.com/Kongaloosh\">@Kongaloosh</a> <a class=\"h-cassis-username\" href=\"https://twitter.com/indirect\">@indirect</a> <a class=\"h-cassis-username\" href=\"https://twitter.com/JackyAlcine\">@JackyAlcine</a> <a class=\"h-cassis-username\" href=\"https://twitter.com/generativist\">@generativist</a> <a class=\"h-cassis-username\" href=\"https://twitter.com/AndiGalpern\">@AndiGalpern</a> <a class=\"h-cassis-username\" href=\"https://twitter.com/allaboutgeorge\">@allaboutgeorge</a> <a class=\"h-cassis-username\" href=\"https://twitter.com/benwerd\">@benwerd</a> <a class=\"h-cassis-username\" href=\"https://twitter.com/dietrich\">@dietrich</a> <a class=\"h-cassis-username\" href=\"https://twitter.com/pvh\">@pvh</a> <a class=\"h-cassis-username\" href=\"https://twitter.com/JohnMattDavis\">@JohnMattDavis</a> <a class=\"h-cassis-username\" href=\"https://twitter.com/html5cat\">@html5cat</a> et al"
},
"author": {
"type": "card",
"name": "Tantek \u00c7elik",
"url": "http://tantek.com/",
"photo": "https://aperture-media.p3k.io/tantek.com/acfddd7d8b2c8cf8aa163651432cc1ec7eb8ec2f881942dca963d305eeaaa6b8.jpg"
},
"post-type": "rsvp",
"refs": {
"https://events.indieweb.org/2020/02/homebrew-website-club-san-francisco-eiKvWhy3hxoE": {
"type": "entry",
"url": "https://events.indieweb.org/2020/02/homebrew-website-club-san-francisco-eiKvWhy3hxoE",
"name": "an IndieWeb event",
"post-type": "article"
}
},
"_id": "8714360",
"_source": "1",
"_is_read": true
}
{
"type": "entry",
"published": "2020-02-07 16:32-0800",
"url": "http://tantek.com/2020/038/t1/",
"in-reply-to": [
"https://twitter.com/generativist/status/1225927392725594112"
],
"content": {
"text": "@generativist @MozSF @allaboutgeorge @brb_irl @jackyalcine @benwerd @dietrich @pvh @johnmattdavis @html5cat We had a nice meetup and have organized the next one already! https://events.indieweb.org/2020/02/homebrew-website-club-san-francisco-eiKvWhy3hxoE\nI should post an RSVP myself :)",
"html": "<a class=\"h-cassis-username\" href=\"https://twitter.com/generativist\">@generativist</a> <a class=\"h-cassis-username\" href=\"https://twitter.com/MozSF\">@MozSF</a> <a class=\"h-cassis-username\" href=\"https://twitter.com/allaboutgeorge\">@allaboutgeorge</a> <a class=\"h-cassis-username\" href=\"https://twitter.com/brb_irl\">@brb_irl</a> <a class=\"h-cassis-username\" href=\"https://twitter.com/jackyalcine\">@jackyalcine</a> <a class=\"h-cassis-username\" href=\"https://twitter.com/benwerd\">@benwerd</a> <a class=\"h-cassis-username\" href=\"https://twitter.com/dietrich\">@dietrich</a> <a class=\"h-cassis-username\" href=\"https://twitter.com/pvh\">@pvh</a> <a class=\"h-cassis-username\" href=\"https://twitter.com/johnmattdavis\">@johnmattdavis</a> <a class=\"h-cassis-username\" href=\"https://twitter.com/html5cat\">@html5cat</a> We had a nice meetup and have organized the next one already! <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><br />I should post an RSVP myself :)"
},
"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://twitter.com/generativist/status/1225927392725594112": {
"type": "entry",
"url": "https://twitter.com/generativist/status/1225927392725594112",
"name": "@generativist\u2019s tweet",
"post-type": "article"
}
},
"_id": "8714362",
"_source": "1",
"_is_read": true
}
Ah no - since getting involved in the #IndieWeb I've been trying to use my site as the owner for my content, wherever it's for, and then pushing it out to silos after
{
"type": "entry",
"published": "2020-02-07T23:17:00Z",
"url": "https://www.jvt.me/mf2/2020/02/zs3rw/",
"category": [
"indieweb"
],
"in-reply-to": [
"https://twitter.com/karlicoss/status/1225918301693411328"
],
"content": {
"text": "Ah no - since getting involved in the #IndieWeb I've been trying to use my site as the owner for my content, wherever it's for, and then pushing it out to silos after",
"html": "<p>Ah no - since getting involved in the <a href=\"https://www.jvt.me/tags/indieweb/\">#IndieWeb</a> I've been trying to use my site as the owner for my content, wherever it's for, and then pushing it out to silos after</p>"
},
"author": {
"type": "card",
"name": "Jamie Tanna",
"url": "https://www.jvt.me",
"photo": "https://www.jvt.me/img/profile.png"
},
"post-type": "reply",
"_id": "8711714",
"_source": "2169",
"_is_read": true
}
In terms of how I get the data? I publish content to my site first, then syndicate it elsewhere afterwards https://indieweb.org/POSSE - which mostly happens automagically
I do this even for things like https://lobste.rs which doesn't have an API so I manually post it with a link back to the comment on my site
{
"type": "entry",
"published": "2020-02-07T22:52:00Z",
"url": "https://www.jvt.me/mf2/2020/02/hokzn/",
"in-reply-to": [
"https://twitter.com/karlicoss/status/1225907857461260288"
],
"content": {
"text": "In terms of how I get the data? I publish content to my site first, then syndicate it elsewhere afterwards https://indieweb.org/POSSE - which mostly happens automagicallyI do this even for things like https://lobste.rs which doesn't have an API so I manually post it with a link back to the comment on my site",
"html": "<p></p><p>In terms of how I get the data? I publish content to my site first, then syndicate it elsewhere afterwards <a href=\"https://indieweb.org/POSSE\">https://indieweb.org/POSSE</a> - which mostly happens automagically</p><p>I do this even for things like <a href=\"https://lobste.rs\">https://lobste.rs</a> which doesn't have an API so I manually post it with a link back to the comment on my site</p>"
},
"author": {
"type": "card",
"name": "Jamie Tanna",
"url": "https://www.jvt.me",
"photo": "https://www.jvt.me/img/profile.png"
},
"post-type": "reply",
"_id": "8711054",
"_source": "2169",
"_is_read": true
}
Hey which feed? I've got RSS/Atom, Microformats2 and JSON Feed!
All of which are generated from Hugo with custom templates
{
"type": "entry",
"published": "2020-02-07T22:49:00Z",
"url": "https://www.jvt.me/mf2/2020/02/2h317/",
"in-reply-to": [
"https://twitter.com/karlicoss/status/1225907857461260288"
],
"content": {
"text": "Hey which feed? I've got RSS/Atom, Microformats2 and JSON Feed!All of which are generated from Hugo with custom templates",
"html": "<p></p><p>Hey which feed? I've got RSS/Atom, Microformats2 and JSON Feed!</p><p>All of which are generated from Hugo with custom templates</p>"
},
"author": {
"type": "card",
"name": "Jamie Tanna",
"url": "https://www.jvt.me",
"photo": "https://www.jvt.me/img/profile.png"
},
"post-type": "reply",
"_id": "8711055",
"_source": "2169",
"_is_read": true
}
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.
{
"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
}
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)
{
"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
}
{
"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 & 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
}
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
{
"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
}
{
"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 & 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
}
{
"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-> Bridgy Publish --Micropub-> silo.pub --\u2744\ufe0fAPI-> 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
}
{
"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
}
{
"type": "entry",
"published": "2020-02-05 19:51-0800",
"url": "http://tantek.com/2020/036/t2/",
"in-reply-to": [
"https://twitter.com/brb_irl/status/1225267170537398273"
],
"content": {
"text": "@brb_irl Sounds delightful. Enjoy disinterneting and see if you can RSVP when you return ^_^/ https://events.indieweb.org/2020/02/homebrew-website-club-san-francisco-eiKvWhy3hxoE",
"html": "<a class=\"h-cassis-username\" href=\"https://twitter.com/brb_irl\">@brb_irl</a> Sounds delightful. Enjoy disinterneting and see if you can RSVP when you return ^_^/ <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://twitter.com/brb_irl/status/1225267170537398273": {
"type": "entry",
"url": "https://twitter.com/brb_irl/status/1225267170537398273",
"name": "@brb_irl\u2019s tweet",
"post-type": "article"
}
},
"_id": "8651138",
"_source": "1",
"_is_read": true
}
{
"type": "entry",
"published": "2020-02-05 19:51-0800",
"url": "http://tantek.com/2020/036/t1/",
"in-reply-to": [
"https://twitter.com/brb_irl/status/1225260585949859840"
],
"content": {
"text": "@brb_irl welcome and nice to meet you!\n\nP.S. coming up this weekend: @IndieWebCamp Online!\nhttps://events.indieweb.org/2020/02/indiewebcamp-online-gUpSVUxbUKhv",
"html": "<a class=\"h-cassis-username\" href=\"https://twitter.com/brb_irl\">@brb_irl</a> welcome and nice to meet you!<br /><br />P.S. coming up this weekend: <a class=\"h-cassis-username\" href=\"https://twitter.com/IndieWebCamp\">@IndieWebCamp</a> Online!<br /><a href=\"https://events.indieweb.org/2020/02/indiewebcamp-online-gUpSVUxbUKhv\">https://events.indieweb.org/2020/02/indiewebcamp-online-gUpSVUxbUKhv</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://twitter.com/brb_irl/status/1225260585949859840": {
"type": "entry",
"url": "https://twitter.com/brb_irl/status/1225260585949859840",
"name": "@brb_irl\u2019s tweet",
"post-type": "article"
}
},
"_id": "8650027",
"_source": "1",
"_is_read": true
}
{
"type": "entry",
"published": "2020-02-05 17:11-0800",
"url": "http://tantek.com/2020/036/b1/indieweb-redirect-to-content-new",
"category": [
"enhancement"
],
"in-reply-to": [
"https://github.com/indieweb/this-week/issues"
],
"name": "IndieWeb newsletter should treat pages edited from a redirect to actual content as new pages",
"content": {
"text": "The IndieWeb This Week newsletter\u2019s \"New Wiki Pages\" section, e.g. \n2020-01-31 New Wiki Pages \nshould also include pages that are not literally new in MediaWiki terms, \nbut were a redirect page, \nand during the the week before the newsletter were edited to no longer redirect, \nand have their own content instead.\n\n\nCurrently in order to make a redirect page that\u2019s been converted to a content page \nshow up in the \"New Wiki Pages\" section, you have to delete the redirect page, \nand then recreate it with the new content. For example I did this today with the \nlocal first page. \nIdeally there would be no need to take that extra step of deleting the redirect page first.\n\n\nLabel: enhancement.",
"html": "<p>\nThe IndieWeb This Week newsletter\u2019s \"New Wiki Pages\" section, e.g. \n<a href=\"https://indieweb.org/this-week/2020-01-31.html#new-wiki-pages\">2020-01-31 New Wiki Pages</a> \nshould also include pages that are not literally new in MediaWiki terms, \nbut were a redirect page, \nand during the the week before the newsletter were edited to no longer redirect, \nand have their own content instead.\n</p>\n<p>\nCurrently in order to make a redirect page that\u2019s been converted to a content page \nshow up in the \"New Wiki Pages\" section, you have to delete the redirect page, \nand then recreate it with the new content. For example I did this today with the \n<a href=\"https://indieweb.org/local_first\">local first page</a>. \nIdeally there would be no need to take that extra step of deleting the redirect page first.\n</p>\n<p>\nLabel: <span class=\"p-category\">enhancement</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/indieweb/this-week/issues": {
"type": "entry",
"url": "https://github.com/indieweb/this-week/issues",
"name": "GitHub project \u201cthis-week\u201d",
"post-type": "article"
}
},
"_id": "8647515",
"_source": "1",
"_is_read": true
}
Reminder that the IndieWeb Meetup is tonight at Mozart’s Coffee for anyone in the Austin area. It is going to be cold. We’ll try to find a table inside, otherwise downstairs where it’s mostly enclosed. 6:30pm.
{
"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/05/reminder-that-the.html",
"content": {
"html": "<p>Reminder that the IndieWeb Meetup is tonight at Mozart\u2019s Coffee for anyone in the Austin area. It is going to be cold. We\u2019ll try to find a table inside, otherwise downstairs where it\u2019s mostly enclosed. 6:30pm.</p>",
"text": "Reminder that the IndieWeb Meetup is tonight at Mozart\u2019s Coffee for anyone in the Austin area. It is going to be cold. We\u2019ll try to find a table inside, otherwise downstairs where it\u2019s mostly enclosed. 6:30pm."
},
"published": "2020-02-05T10:21:10-06:00",
"post-type": "note",
"_id": "8631103",
"_source": "12",
"_is_read": true
}
Thanks for taking a look at the changes! And thanks for the response!
While I agree that I could wrap the entries on my archive page in an h-feed, I disagree that every collection of h-entry “is a feed”.
The microformats2 spec for h-feed is still a draft and open to change. Even so, it states that h-feed is “for publishing a stream or feed”. The use cases listed there, and on indieweb.org/h-feed specifically discuss feeds and feed readers subscribing to content.
I made the specific choice not to make the archive pages into a feed, because I don’t want to encourage folks to subscribe to something only to find that it becomes static over time.
In my thinking, an microformats2-capable crawler should be capable of handling a collection of h-entry in a page whether or not they are wrapped in an h-feed. There was some brief discussion about it today in the #indieweb-dev chat.
{
"type": "entry",
"published": "2020-02-04T15:43:29-0500",
"url": "https://martymcgui.re/2020/02/04/154329/",
"in-reply-to": [
"https://ignite.digitalignition.net/2020/02/04/98588/"
],
"content": {
"text": "Thanks for taking a look at the changes! And thanks for the response!\n\nWhile I agree that I could wrap the entries on my archive page in an h-feed, I disagree that every collection of h-entry \u201cis a feed\u201d.\n\nThe microformats2 spec for h-feed is still a draft and open to change. Even so, it states that h-feed is \u201cfor publishing a stream or feed\u201d. The use cases listed there, and on indieweb.org/h-feed specifically discuss feeds and feed readers subscribing to content.\n\nI made the specific choice not to make the archive pages into a feed, because I don\u2019t want to encourage folks to subscribe to something only to find that it becomes static over time.\n\nIn my thinking, an microformats2-capable crawler should be capable of handling a collection of h-entry in a page whether or not they are wrapped in an h-feed. There was some brief discussion about it today in the #indieweb-dev chat.",
"html": "<p>Thanks for taking a look at the changes! And thanks for the response!</p>\n\n<p>While I agree that I <em>could</em> wrap the entries on my archive page in an <code>h-feed</code>, I disagree that every collection of <code>h-entry</code> \u201cis a feed\u201d.</p>\n\n<p>The <a href=\"http://microformats.org/wiki/h-feed\">microformats2 spec for h-feed</a> is still a draft and open to change. Even so, it states that h-feed is \u201cfor publishing a stream or feed\u201d. The use cases listed there, and on <a href=\"https://indieweb.org/h-feed#Why\">indieweb.org/h-feed</a> specifically discuss feeds and feed readers subscribing to content.</p>\n\n<p>I made the specific choice <em>not</em> to make the archive pages into a feed, because I don\u2019t want to encourage folks to subscribe to something only to find that it becomes static over time.</p>\n\n<p>In my thinking, an microformats2-capable crawler should be capable of handling a collection of <code>h-entry</code> in a page whether or not they are wrapped in an <code>h-feed</code>. There was some <a href=\"https://chat.indieweb.org/dev/2020-02-04#t1580847242308700\">brief discussion about it today in the #indieweb-dev chat</a>.</p>"
},
"author": {
"type": "card",
"name": "Marty McGuire",
"url": "https://martymcgui.re/",
"photo": "https://martymcgui.re/images/logo.jpg"
},
"post-type": "reply",
"refs": {
"https://ignite.digitalignition.net/2020/02/04/98588/": {
"type": "entry",
"published": "2020-02-04T03:22:25+0000",
"summary": "Thanks for your updates Marty, I\u2019ll get them into the app.\u00a0 I just wanted to touch on one thing you wrote in your post, and that\u2019s:",
"url": "https://ignite.digitalignition.net/2020/02/04/98588/",
"author": {
"type": "card",
"name": "Ruxton",
"url": "https://ignite.digitalignition.net/author/ruxton/",
"photo": "https://res.cloudinary.com/schmarty/image/fetch/w_60,c_fill/https://secure.gravatar.com/avatar/8401de9afbdfada34ca21681a2394340?s=40&d=mm&r=g"
},
"post-type": "note"
}
},
"_id": "8608114",
"_source": "175",
"_is_read": true
}
