Meetable RSVP user interface should prompt Code of Conduct agreement(s)

{
    "type": "entry",
    "published": "2020-03-02 15:12-0800",
    "url": "http://tantek.com/2020/062/b3/",
    "in-reply-to": [
        "https://github.com/aaronpk/Meetable/issues"
    ],
    "name": "Meetable RSVP user interface should prompt Code of Conduct agreement(s)",
    "content": {
        "text": "For Meetable events which have one or more Code of Conduct links\n(per #84), \nwhen the user interacts with the RSVP user interface to confirm participation, \nMeetable should prompt the user with a dialog with one or more links to Codes of Conduct with checkboxes next to each that acknowledges that the user has read and agreed to them.\n\n\nA minimum viable user interaction here would be just fine, and there is no need to create a whole ticketing and assignment system where different people would RSVP vs agree to the Code of Conduct link(s).\n\n\nWe can learn from the development, use, and iteration of this minimal user interface to then drive future protocol improvements in federated RSVPs via Webmention.",
        "html": "<p>\nFor Meetable events which have one or more Code of Conduct links\n(per <a href=\"https://github.com/aaronpk/Meetable/issues/84\">#84</a>), \nwhen the user interacts with the RSVP user interface to confirm participation, \nMeetable should prompt the user with a dialog with one or more links to Codes of Conduct with checkboxes next to each that acknowledges that the user has read and agreed to them.\n</p>\n<p>\nA minimum viable user interaction here would be just fine, and there is no need to create a whole ticketing and assignment system where different people would RSVP vs agree to the Code of Conduct link(s).\n</p>\n<p>\nWe can learn from the development, use, and iteration of this minimal user interface to then drive future protocol improvements in federated RSVPs via Webmention.\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/aaronpk/Meetable/issues": {
            "type": "entry",
            "url": "https://github.com/aaronpk/Meetable/issues",
            "name": "GitHub project \u201cMeetable\u201d",
            "post-type": "article"
        }
    },
    "_id": "9429811",
    "_source": "1",
    "_is_read": true
}

Meetable events should have a Code of Conduct field for one or more URLs

{
    "type": "entry",
    "published": "2020-03-02 14:56-0800",
    "url": "http://tantek.com/2020/062/b2/",
    "in-reply-to": [
        "https://github.com/aaronpk/Meetable/issues"
    ],
    "name": "Meetable events should have a Code of Conduct field for one or more URLs",
    "content": {
        "text": "Typical communty events require agreeing to a Code of Conduct in order to RSVP and participate. Meetable should have a field to enter one or more Code of Conduct URLs, and then show anyone who RSVPs (using Meetable\u2019s UI) a dialog of one or more links to Codes of Conduct with checkboxes next to each that acknowledges that the user has read them.\n\n\nUse-case for a Code of Conduct field: IndieWeb events always require agreeing to the \nIndieWeb Code of Conduct.\n\n\nUse-case for a field for multiple Code of Conduct URLs: IndieWeb events hosted at a Mozilla office require agreeing to both the IndieWeb Code of Conduct and the \nMozilla Community Participation Guidelines.\n\n\nThe Code of Conduct link(s) should be prominently publicly displayed on Meetable event pages.",
        "html": "<p>\nTypical communty events require agreeing to a Code of Conduct in order to RSVP and participate. Meetable should have a field to enter one or more Code of Conduct URLs, and then show anyone who RSVPs (using Meetable\u2019s UI) a dialog of one or more links to Codes of Conduct with checkboxes next to each that acknowledges that the user has read them.\n</p>\n<p>\nUse-case for a Code of Conduct field: IndieWeb events always require agreeing to the \n<a href=\"https://indieweb.org/code-of-conduct\">IndieWeb Code of Conduct</a>.\n</p>\n<p>\nUse-case for a field for multiple Code of Conduct URLs: IndieWeb events hosted at a Mozilla office require agreeing to both the IndieWeb Code of Conduct and the \n<a href=\"https://www.mozilla.org/en-US/about/governance/policies/participation/\">Mozilla Community Participation Guidelines</a>.\n</p>\n<p>\nThe Code of Conduct link(s) should be prominently publicly displayed on Meetable event pages.\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/aaronpk/Meetable/issues": {
            "type": "entry",
            "url": "https://github.com/aaronpk/Meetable/issues",
            "name": "GitHub project \u201cMeetable\u201d",
            "post-type": "article"
        }
    },
    "_id": "9428378",
    "_source": "1",
    "_is_read": true
}

Meetable events should clearly show event author/organizer and creation datetime

{
    "type": "entry",
    "published": "2020-03-02 14:33-0800",
    "url": "http://tantek.com/2020/062/b1/",
    "in-reply-to": [
        "https://github.com/aaronpk/Meetable/issues"
    ],
    "name": "Meetable events should clearly show event author/organizer and creation datetime",
    "content": {
        "text": "Typical popular events sites and services (Google Calendar, Facebook) prominently show who created and is organizing events, as well as when they were created. Meetable should do this by default, at a minimum using the author\u2019s personal site they used to sign-in via IndieAuth, and the datetime at which they created the event.\n\n\nThe author\u2019s personal site can be \nparsed for a representative h-card \nto use for their display name and image (h-card name and logo or photo), \nthough even showing the domain name of the author would be useful (absent an h-card display name or logo/photo).\n\n\nThis would at a minimum be very useful for the events.indieweb.org deployment of Meetable, as that was used to replace use of the wiki for events which had this information implicitly in the browsable edit history.\n\n\nWho created it use-cases: knowing who created an event helps clarify the potential legitimacy of the event and/or how much help the organizer may need (is it a known organizer of such events, the usual person, or a new person but still known to the community, or a random person who may need help). Additionally, having a clear organizer helps provide at least a default contact for any Code of Conduct follow-ups.\n\n\nWhen was it created use-cases: it is useful to know the when created information as a method for if an event was created long in advance and might not still be happening, or if it was created very recently and thus is much more likely to be happening.\n\n\nThis information should be prominently publicly displayed on Meetable event pages.",
        "html": "<p>\nTypical popular events sites and services (Google Calendar, Facebook) prominently show who created and is organizing events, as well as when they were created. Meetable should do this by default, at a minimum using the author\u2019s personal site they used to sign-in via IndieAuth, and the datetime at which they created the event.\n</p>\n<p>\nThe author\u2019s personal site can be \n<a href=\"http://microformats.org/wiki/representative-h-card-parsing\">parsed for a representative h-card</a> \nto use for their display name and image (h-card name and logo or photo), \nthough even showing the domain name of the author would be useful (absent an h-card display name or logo/photo).\n</p>\n<p>\nThis would at a minimum be very useful for the events.indieweb.org deployment of Meetable, as that was used to replace use of the wiki for events which had this information implicitly in the browsable edit history.\n</p>\n<p>\nWho created it use-cases: knowing who created an event helps clarify the potential legitimacy of the event and/or how much help the organizer may need (is it a known organizer of such events, the usual person, or a new person but still known to the community, or a random person who may need help). Additionally, having a clear organizer helps provide at least a default contact for any Code of Conduct follow-ups.\n</p>\n<p>\nWhen was it created use-cases: it is useful to know the when created information as a method for if an event was created long in advance and might not still be happening, or if it was created very recently and thus is much more likely to be happening.\n</p>\n<p>\nThis information should be prominently publicly displayed on Meetable event pages.\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/aaronpk/Meetable/issues": {
            "type": "entry",
            "url": "https://github.com/aaronpk/Meetable/issues",
            "name": "GitHub project \u201cMeetable\u201d",
            "post-type": "article"
        }
    },
    "_id": "9428379",
    "_source": "1",
    "_is_read": true
}

Google confirms Microformats are still a recommended metadata format for content

{
    "type": "entry",
    "summary": "Noting Google's continued support for Microformats as a metadata format.",
    "url": "https://www.jvt.me/posts/2020/03/02/google-microformats-support/",
    "name": "Google confirms Microformats are still a recommended metadata format for content",
    "author": {
        "type": "card",
        "name": "Jamie Tanna",
        "url": "https://www.jvt.me",
        "photo": "https://www.jvt.me/img/profile.png"
    },
    "post-type": "article",
    "_id": "9426619",
    "_source": "2169",
    "_is_read": true
}

{
    "type": "entry",
    "author": {
        "name": "Manton Reece",
        "url": "https://www.manton.org/",
        "photo": "https://micro.blog/manton/avatar.jpg"
    },
    "url": "https://www.manton.org/2020/03/02/normally-the-indieweb.html",
    "content": {
        "html": "<p>Normally the IndieWeb Meetup in Austin is the first Wednesday of the month, but we\u2019re going to skip it this week. See y\u2019all next month.</p>",
        "text": "Normally the IndieWeb Meetup in Austin is the first Wednesday of the month, but we\u2019re going to skip it this week. See y\u2019all next month."
    },
    "published": "2020-03-02T15:17:00-06:00",
    "post-type": "note",
    "_id": "9426452",
    "_source": "12",
    "_is_read": true
}

{
    "type": "entry",
    "author": {
        "name": "Colin Walker",
        "url": "https://colinwalker.blog/",
        "photo": null
    },
    "url": "https://colinwalker.blog/27-02-2020-1946/",
    "published": "2020-02-27T19:46:15+00:00",
    "content": {
        "html": "<p>I was thinking about comments and how I effectively use micro.blog as a commenting system; I receive m.b replies via webmention but they include the @mention at the start of the text.</p>\n<p>I thought about hooking in to <code>comment_post()</code> to strip the @mention from the front of the comment as it is submitted but this would leave a before and after situation. Instead, I decided to achieve the same thing nondestructively by checking for it at display time. Now my comment parser checks if the comment text starts with a link from micro.blog and strips it out for display purposes.</p>\n<p>See <a href=\"https://colinwalker.blog/27-02-2020-1454/#commentlist\">this post</a> for an example.</p>\n<p>I've often thought about this and found it to be a little jarring when viewing the comments in the context of the blog. As it's nondestructive I can always reverse the change if I find the flow of comments stop making sense but I prefer them this way.</p>",
        "text": "I was thinking about comments and how I effectively use micro.blog as a commenting system; I receive m.b replies via webmention but they include the @mention at the start of the text.\nI thought about hooking in to comment_post() to strip the @mention from the front of the comment as it is submitted but this would leave a before and after situation. Instead, I decided to achieve the same thing nondestructively by checking for it at display time. Now my comment parser checks if the comment text starts with a link from micro.blog and strips it out for display purposes.\nSee this post for an example.\nI've often thought about this and found it to be a little jarring when viewing the comments in the context of the blog. As it's nondestructive I can always reverse the change if I find the flow of comments stop making sense but I prefer them this way."
    },
    "post-type": "note",
    "_id": "9409912",
    "_source": "237",
    "_is_read": true
}

Announcing Micropub-Media-Endpoint-Proxy

{
    "type": "entry",
    "summary": "Announcing a web-based solution for uploading files to your Micropub media endpoint.",
    "url": "https://www.jvt.me/posts/2020/02/29/media-endpoint-proxy/",
    "name": "Announcing Micropub-Media-Endpoint-Proxy",
    "author": {
        "type": "card",
        "name": "Jamie Tanna",
        "url": "https://www.jvt.me",
        "photo": "https://www.jvt.me/img/profile.png"
    },
    "post-type": "article",
    "_id": "9372585",
    "_source": "2169",
    "_is_read": true
}

Removing IndieWeb WordPress Plugins

{
    "type": "entry",
    "author": {
        "name": "Kh\u00fcrt",
        "url": "https://islandinthenet.com/",
        "photo": null
    },
    "url": "https://islandinthenet.com/removing-indieweb-wordpress-plugins/",
    "published": "2020-02-29T11:11:00-05:00",
    "content": {
        "html": "<a href=\"https://islandinthenet.com/removing-indieweb-wordpress-plugins/\"><img src=\"https://islandinthenet.com/wp-content/uploads/2020/02/Fujifilm_X-T2_20200222_DSCF02561_blog-1.jpg\" alt=\"\" /></a>I am reevaluating my use of certain IndieWeb technologies. In 2018 I added a set of plugins to my website and started using a microformats 2 theme, SemPress to mark up my website so that content could be interpreted by other sites. SemPress is the only theme in the WordPress repository that is fully microformats2 [\u2026]",
        "text": "I am reevaluating my use of certain IndieWeb technologies. In 2018 I added a set of plugins to my website and started using a microformats 2 theme, SemPress to mark up my website so that content could be interpreted by other sites. SemPress is the only theme in the WordPress repository that is fully microformats2 [\u2026]"
    },
    "name": "Removing IndieWeb WordPress Plugins",
    "post-type": "article",
    "_id": "9366989",
    "_source": "242",
    "_is_read": true
}

{
    "type": "entry",
    "published": "2020-02-27T20:59:09-08:00",
    "url": "https://aaronparecki.com/2020/02/27/19/",
    "photo": [
        "https://aperture-media.p3k.io/aaronparecki.com/25efd5cfc95c8e540d680699db274949663c2c49fa73cda9f89a14417f477209.jpg"
    ],
    "content": {
        "text": "Today @indiewebcat was being real cute, just hanging out in the office together \ud83d\ude3b",
        "html": "Today <a href=\"https://indiewebcat.com\">@indiewebcat</a> was being real cute, just hanging out in the office together <a href=\"https://aaronparecki.com/emoji/%F0%9F%98%BB\">\ud83d\ude3b</a>"
    },
    "author": {
        "type": "card",
        "name": "Aaron Parecki",
        "url": "https://aaronparecki.com/",
        "photo": "https://aperture-media.p3k.io/aaronparecki.com/01ba90586726c9ac42a9894442f0b335432f9b4c0a98191142fb80e5661346dd.jpg"
    },
    "post-type": "photo",
    "_id": "9327104",
    "_source": "16",
    "_is_read": true
}

{
    "type": "entry",
    "published": "2020-02-27T22:49:00Z",
    "url": "https://www.jvt.me/mf2/2020/02/h3nqw/",
    "category": [
        "micropub",
        "open-source",
        "indieweb"
    ],
    "content": {
        "text": "It may not be ready by the #IndieWeb newsletter tomorrow, but I'm hoping my web-based Micropub media endpoint upload client will be live this weekend - exactly what would fit for https://jlelse.blog/micro/2020/01/2020-01-01-frviz/",
        "html": "<p>It may not be ready by the <a href=\"https://www.jvt.me/tags/indieweb/\">#IndieWeb</a> newsletter tomorrow, but I'm hoping my web-based Micropub media endpoint upload client will be live this weekend - exactly what would fit for <a href=\"https://jlelse.blog/micro/2020/01/2020-01-01-frviz/\">https://jlelse.blog/micro/2020/01/2020-01-01-frviz/</a></p>"
    },
    "author": {
        "type": "card",
        "name": "Jamie Tanna",
        "url": "https://www.jvt.me",
        "photo": "https://www.jvt.me/img/profile.png"
    },
    "post-type": "note",
    "_id": "9320504",
    "_source": "2169",
    "_is_read": true
}

{
    "type": "entry",
    "published": "2020-02-26T13:57:20+00:00",
    "url": "https://fireburn.ru/posts/1582725440",
    "category": [
        "KittyboxCompanion",
        "IndieAuth"
    ],
    "syndication": [
        "https://twitter.com/kisik21/status/1232665979945127936"
    ],
    "content": {
        "text": "OK so #KittyboxCompanion got #IndieAuth support on Android",
        "html": "<p>OK so #KittyboxCompanion got #IndieAuth support on Android</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": "9281095",
    "_source": "1371",
    "_is_read": true
}

{
    "type": "entry",
    "published": "2020-02-26 01:02:41",
    "url": "http://monkinetic.blog/2020/02/26/#txt-1f24862",
    "content": {
        "text": "I know I\u2019ve done a good job integrating my social media posting into my site when I want to reply to my own posts. #indieweb #posse",
        "html": "<p>I know I\u2019ve done a good job integrating my social media posting into my site when I want to reply to my own posts. <a href=\"http://monkinetic.blog/tag/indieweb\">#indieweb</a> <a href=\"http://monkinetic.blog/tag/posse\">#posse</a></p>"
    },
    "author": {
        "type": "card",
        "name": "Steve Ivy",
        "url": false,
        "photo": "http://monkinetic.blog/static/images/sivy_avatar_256.png"
    },
    "post-type": "note",
    "_id": "9261221",
    "_source": "4486",
    "_is_read": true
}

{
    "type": "entry",
    "published": "2020-02-25 14:36-0800",
    "url": "https://gregorlove.com/2020/02/hey-brian-hope-you-can/",
    "in-reply-to": [
        "https://pine.blog/u/sonicrocketman"
    ],
    "content": {
        "text": "Hey Brian, hope you can make the next Homebrew Website Club San Diego meetup: https://events.indieweb.org/2020/03/homebrew-website-club-san-diego-bSBT0ZceMIHo",
        "html": "<p>Hey Brian, hope you can make the next Homebrew Website Club San Diego meetup: <a href=\"https://events.indieweb.org/2020/03/homebrew-website-club-san-diego-bSBT0ZceMIHo\">https://events.indieweb.org/2020/03/homebrew-website-club-san-diego-bSBT0ZceMIHo</a></p>"
    },
    "post-type": "reply",
    "refs": {
        "https://pine.blog/u/sonicrocketman": {
            "type": "entry",
            "url": "https://pine.blog/u/sonicrocketman",
            "name": "https://pine.blog/u/sonicrocketman",
            "post-type": "article"
        }
    },
    "_id": "9259079",
    "_source": "95",
    "_is_read": true
}

Replies on your blog with Conversation.js

{
    "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/25/replies-on-your.html",
    "name": "Replies on your blog with Conversation.js",
    "content": {
        "html": "<p>During the project day at <a href=\"https://2020.indieweb.org/austin\">IndieWebCamp Austin</a> last weekend, I built a new feature for Micro.blog that I\u2019m calling <strong>Conversation.js</strong>. It\u2019s a JavaScript include that lets you take a conversation on Micro.blog and drop it into your blog.</p>\n\n<p>Like a lot of Micro.blog features, it works either as a simple feature you can enable with a click, or as a more advanced API that can be customized however you\u2019d like. If all you want to do is enable the feature, just click on Posts \u2192 Design and look for this checkbox:</p>\n\n<p><img src=\"https://www.manton.org/uploads/2020/55f704654c.png\" alt=\"Conversation checkbox\" border=\"0\" width=\"500\" height=\"119\" style=\"max-width:500px;\" /></p>\n\n<p>Behind the scenes, this checkbox is adding a new Hugo parameter <code>.Params.include_conversation</code> that can be used in a custom theme. All the built-in Micro.blog designs have been updated to check for this parameter and then add the following line of JavaScript:</p>\n\n<pre>\n&lt;script type=\"text/javascript\" src=\"https://micro.blog/conversation.js?url={{ .Permalink }}\"&gt;&lt;/script&gt;\n</pre>\n\n<p>This JavaScript include gathers the replies to the current blog post and adds them to your web page. The HTML elements all have class names so you can style the replies to match your site.</p>\n\n<p><a href=\"https://www.manton.org/2020/02/24/mimi-uploader-for.html\">See this page on my blog</a> for how the replies look on one of my blog posts.</p>\n\n<p>If you need even more control, you can request the conversation as JSON from apps or scripts by adding <code>format=jsonfeed</code> to the URL. Or you can add <code>format=jf2</code> to produce output that matches Webmention.io, so it\u2019s easier to repurpose tools that already work with Webmention.io.</p>\n\n<p>Speaking of Webmention, this is not just about taking Micro.blog-only replies and putting them on your blog. Because all Micro.blog-hosted blogs support Webmention, and Micro.blog can accept mentions even from blogs that have not yet registered on Micro.blog, with Conversation.js it now becomes much more useful for other blogs to send you replies. Those replies can appear on your blog, with Micro.blog mostly acting as glue so that both blogs can talk to each other.</p>\n\n<p>I\u2019ve been wanting to do something like this for a while. It didn\u2019t take long at IndieWebCamp Austin when I finally sat down to code it, but I think it opens up a lot of options for Micro.blog in the future, including acting as an IndieWeb-friendly replacement for Disqus and other commenting systems.</p>",
        "text": "During the project day at IndieWebCamp Austin last weekend, I built a new feature for Micro.blog that I\u2019m calling Conversation.js. It\u2019s a JavaScript include that lets you take a conversation on Micro.blog and drop it into your blog.\n\nLike a lot of Micro.blog features, it works either as a simple feature you can enable with a click, or as a more advanced API that can be customized however you\u2019d like. If all you want to do is enable the feature, just click on Posts \u2192 Design and look for this checkbox:\n\n\n\nBehind the scenes, this checkbox is adding a new Hugo parameter .Params.include_conversation that can be used in a custom theme. All the built-in Micro.blog designs have been updated to check for this parameter and then add the following line of JavaScript:\n\n\n<script type=\"text/javascript\" src=\"https://micro.blog/conversation.js?url={{ .Permalink }}\"></script>\n\n\nThis JavaScript include gathers the replies to the current blog post and adds them to your web page. The HTML elements all have class names so you can style the replies to match your site.\n\nSee this page on my blog for how the replies look on one of my blog posts.\n\nIf you need even more control, you can request the conversation as JSON from apps or scripts by adding format=jsonfeed to the URL. Or you can add format=jf2 to produce output that matches Webmention.io, so it\u2019s easier to repurpose tools that already work with Webmention.io.\n\nSpeaking of Webmention, this is not just about taking Micro.blog-only replies and putting them on your blog. Because all Micro.blog-hosted blogs support Webmention, and Micro.blog can accept mentions even from blogs that have not yet registered on Micro.blog, with Conversation.js it now becomes much more useful for other blogs to send you replies. Those replies can appear on your blog, with Micro.blog mostly acting as glue so that both blogs can talk to each other.\n\nI\u2019ve been wanting to do something like this for a while. It didn\u2019t take long at IndieWebCamp Austin when I finally sat down to code it, but I think it opens up a lot of options for Micro.blog in the future, including acting as an IndieWeb-friendly replacement for Disqus and other commenting systems."
    },
    "published": "2020-02-25T09:46:04-06:00",
    "category": [
        "Photos",
        "Essays"
    ],
    "post-type": "article",
    "_id": "9248893",
    "_source": "12",
    "_is_read": true
}

{
    "type": "entry",
    "published": "2020-02-23T14:45:44.31426-08:00",
    "url": "https://v2.jacky.wtf/post/4807d53e-37f2-4203-aab6-2427490bbf17",
    "category": [
        "test"
    ],
    "content": {
        "text": "Oh my gosh! It\u2019s either https://masilotti.com or https://masilotti.com/webmentions might be the source of truth!",
        "html": "<p>Oh my gosh! It\u2019s either <a href=\"https://masilotti.com\">https://masilotti.com</a> or <a href=\"https://masilotti.com/webmentions\">https://masilotti.com/webmentions</a> might be the source of truth! </p>\n<p></p>"
    },
    "author": {
        "type": "card",
        "name": "",
        "url": "https://v2.jacky.wtf",
        "photo": null
    },
    "post-type": "note",
    "_id": "9231437",
    "_source": "1886",
    "_is_read": true
}

{
    "type": "entry",
    "published": "2020-02-23T14:12:42.69018-08:00",
    "url": "https://v2.jacky.wtf/post/90fdbf93-ec2d-452c-9d60-322f3e547060",
    "category": [
        "indieweb"
    ],
    "content": {
        "text": "And we\u2019re live! #indieweb https://indieweb.live/",
        "html": "<p>And we\u2019re live! #<a href=\"https://v2.jacky.wtf/tags/75cedb2a-3173-4436-a86a-300f1a8d81b4\" class=\"p-category\">indieweb</a> <a href=\"https://indieweb.live/\">https://indieweb.live/</a></p>"
    },
    "author": {
        "type": "card",
        "name": "",
        "url": "https://v2.jacky.wtf",
        "photo": null
    },
    "post-type": "note",
    "_id": "9231438",
    "_source": "1886",
    "_is_read": true
}

{
    "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/24/thanks-everyone-who.html",
    "content": {
        "html": "<p>Thanks everyone who attended IndieWebCamp! This was our best turnout in Austin and I personally got a lot out of the weekend. There are more IndieWeb events this year, including London next month and Portland in June.</p>",
        "text": "Thanks everyone who attended IndieWebCamp! This was our best turnout in Austin and I personally got a lot out of the weekend. There are more IndieWeb events this year, including London next month and Portland in June."
    },
    "published": "2020-02-24T08:26:15-06:00",
    "post-type": "note",
    "_id": "9215438",
    "_source": "12",
    "_is_read": true
}

{
    "type": "entry",
    "published": "2020-02-23 21:26-0800",
    "url": "http://tantek.com/2020/054/t2/added-recent-photos-embed",
    "category": [
        "indieweb",
        "takebackyourweb",
        "ownyourphotos"
    ],
    "photo": [
        "https://aperture-media.p3k.io/indieweb.org/aaee5fa88110da7a16f86b10c6fd3e1d921b6d35f9d9510657ab601b2611a867.png"
    ],
    "content": {
        "text": "on iOS Firefox scrolled to show the Recent Photos embed of a 3x4 grid of the twelve most recent photo posts)\nAdded a Recent Photos embed to my homepage sidebar (or bottom of the mobile view) @IndieWebCamp Austin projects day! Still tweaking, yet quite happy with how it looks, e.g. compared to an @Instagram profile. #indieweb #takebackyourweb #ownyourphotos",
        "html": "<a href=\"http://tantek.com/tantek.com\"></a>on iOS Firefox scrolled to show the Recent Photos embed of a 3x4 grid of the twelve most recent photo posts)<br />Added a Recent Photos embed to my homepage sidebar (or bottom of the mobile view) <a class=\"h-cassis-username\" href=\"https://twitter.com/IndieWebCamp\">@IndieWebCamp</a> Austin projects day! Still tweaking, yet quite happy with how it looks, e.g. compared to an <a class=\"h-cassis-username\" href=\"https://twitter.com/Instagram\">@Instagram</a> profile. #<span class=\"p-category\">indieweb</span> #<span class=\"p-category\">takebackyourweb</span> #<span class=\"p-category\">ownyourphotos</span>"
    },
    "author": {
        "type": "card",
        "name": "Tantek \u00c7elik",
        "url": "http://tantek.com/",
        "photo": "https://aperture-media.p3k.io/tantek.com/acfddd7d8b2c8cf8aa163651432cc1ec7eb8ec2f881942dca963d305eeaaa6b8.jpg"
    },
    "post-type": "photo",
    "_id": "9206476",
    "_source": "1",
    "_is_read": true
}

My IndieWebCamp Austin 2020 Projects

{
    "type": "entry",
    "published": "2020-02-23 13:59-0800",
    "url": "https://gregorlove.com/2020/02/my-indiewebcamp-austin-2020-projects/",
    "name": "My IndieWebCamp Austin 2020 Projects",
    "content": {
        "text": "I often come into an IndieWebCamp without a specific project in mind. Sometimes I will get inspired by the discussions. If not, I always have a list of things to tweak on my site; or improvements to indiebookclub, indiewebify.me, or other indieweb tools.\n\nI have recently been working on updating my page header and the main content area. I launched this on my photos page just before the event and today I applied that to the notes page as well. Some things I am really liking about these updates:\n\nBetter responsive design. The header is wider on desktop, with the navigation beside the logo. There\u2019s a medium-size breakpoint where the navigation slips under the logo so they can all still appear on the page. Then there\u2019s a smaller breakpoint where the navigation is hidden and replaced with an open/close toggle.\n\tThe open/close toggle on the smaller size does not require javascript! It uses the CSS :target pseudo-class selector, so clicking different anchor links shows or hides the navigation. I got that idea from this Shellcreeper tutorial.\n\tThe main content area is still optimized for text lines about 70-characters long, which is good for readability. However, I wanted the option to make photos wider on larger screens. I pieced together something from various sources so the photos can break out of the main content area and be up to 960 pixels wide. This is best seen on the photos page. Notice the caption text is narrower under each photo. I think this will look really cool in blog posts that include a striking image.\n\tOn smaller screens, those images are now full-bleed. No left/right margins.\nIn a session yesterday we were talking about local communities and discovering content by region, e.g. \u201cshow me all the meetups around San Diego.\u201d As a starting point, I was thinking that microsub servers could parse feeds for location information and use that to suggest feeds near your location. I don\u2019t work on a microsub server myself and that\u2019s too big a project for me today, but I was able to easily add location to my homepage if anyone wants to parse it. I used the h-geo microformat.",
        "html": "<p>I often come into an IndieWebCamp without a specific project in mind. Sometimes I will get inspired by the discussions. If not, I always have a list of things to tweak on my site; or improvements to <a href=\"https://indiebookclub.biz\">indiebookclub</a>, <a href=\"https://indiewebify.me\">indiewebify.me</a>, or other indieweb tools.</p>\n\n<p>I have recently been working on updating my page header and the main content area. I launched this on my <a href=\"https://gregorlove.com/channels/photos/\">photos</a> page just before the event and today I applied that to the <a href=\"https://gregorlove.com/notes/\">notes</a> page as well. Some things I am really liking about these updates:</p>\n\n<ul><li>Better responsive design. The header is wider on desktop, with the navigation beside the logo. There\u2019s a medium-size breakpoint where the navigation slips under the logo so they can all still appear on the page. Then there\u2019s a smaller breakpoint where the navigation is hidden and replaced with an open/close toggle.</li>\n\t<li>The open/close toggle on the smaller size does <em>not</em> require javascript! It uses the CSS <code><a href=\"https://developer.mozilla.org/en-US/docs/Web/CSS/:target\">:target</a></code> pseudo-class selector, so clicking different anchor links shows or hides the navigation. I got that idea from <a href=\"https://shellcreeper.com/full-css-responsive-navigation-toggle-no-javascript/\">this Shellcreeper tutorial</a>.</li>\n\t<li>The main content area is still optimized for text lines about 70-characters long, which is good for readability. However, I wanted the option to make photos wider on larger screens. I pieced together something from various sources so the photos can break out of the main content area and be up to 960 pixels wide. This is best seen on the <a href=\"https://gregorlove.com/channels/photos/\">photos</a> page. Notice the caption text is narrower under each photo. I think this will look really cool in blog posts that include a striking image.</li>\n\t<li>On smaller screens, those images are now full-bleed. No left/right margins.</li>\n</ul><p>In a <a href=\"https://indieweb.org/2020/Austin/newaffordability\">session</a> yesterday we were talking about local communities and discovering content by region, e.g. \u201cshow me all the meetups around San Diego.\u201d As a starting point, I was thinking that <a href=\"https://indieweb.org/microsub\">microsub</a> servers could parse feeds for location information and use that to suggest feeds near your location. I don\u2019t work on a microsub server myself and that\u2019s too big a project for me today, but I was able to easily add location to my homepage if anyone wants to parse it. I used the <a href=\"http://microformats.org/wiki/h-geo\">h-geo microformat</a>.</p>"
    },
    "author": {
        "type": "card",
        "name": "gRegor Morrill",
        "url": "https://gregorlove.com/",
        "photo": "https://gregorlove.com/site/assets/files/3473/profile-2016-med.jpg"
    },
    "post-type": "article",
    "_id": "9204469",
    "_source": "179",
    "_is_read": true
}

{
    "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/23/indiewebcamp-austin-day.html",
    "content": {
        "html": "<p>IndieWebCamp Austin day 2 is winding down. I wrapped up my project to show replies on my blog posts and I\u2019ll be demoing it to the group soon, with a blog post to follow later this week. Looking forward to seeing what other folks worked on!</p>",
        "text": "IndieWebCamp Austin day 2 is winding down. I wrapped up my project to show replies on my blog posts and I\u2019ll be demoing it to the group soon, with a blog post to follow later this week. Looking forward to seeing what other folks worked on!"
    },
    "published": "2020-02-23T15:49:01-06:00",
    "post-type": "note",
    "_id": "9199624",
    "_source": "12",
    "_is_read": true
}