{
    "type": "entry",
    "author": {
        "name": "@josh",
        "url": "https://josh.tel/@josh",
        "photo": null
    },
    "url": "https://josh.tel/@josh/109672351436464142",
    "content": {
        "html": "<p>Disabling notifications from all my corporate social accounts, while leaving them on for Fediverse social accounts: an accidental stroke of genius  <img alt=\":blobcatmaths:\" height=\"16\" src=\"https://files.mastodon.social/cache/custom_emojis/images/000/441/678/original/0c2192664d0c125d.png\" title=\":blobcatmaths:\" width=\"16\" /></p><p>It helps me prioritize where I truly want to spend my time <img alt=\":fedi:\" height=\"16\" src=\"https://files.mastodon.social/cache/custom_emojis/images/000/484/889/original/deb4552c6181a8b5.png\" title=\":fedi:\" width=\"16\" /><a href=\"https://josh.tel/tags/IndieWeb\">#<span>IndieWeb</span></a></p>",
        "text": "Disabling notifications from all my corporate social accounts, while leaving them on for Fediverse social accounts: an accidental stroke of genius  It helps me prioritize where I truly want to spend my time #IndieWeb"
    },
    "published": "2023-01-11T20:01:16+00:00",
    "post-type": "note",
    "_id": "34341324",
    "_source": "7235",
    "_is_read": false
}

{
    "type": "entry",
    "author": {
        "name": "@rtud",
        "url": "https://mastodon.social/@rtud",
        "photo": null
    },
    "url": "https://mastodon.social/@rtud/109672150260826815",
    "content": {
        "html": "<p><span class=\"h-card\"><a class=\"u-url\" href=\"https://mastodon.social/@hrbf\">@<span>hrbf</span></a></span> thank you and I appreciate it!</p><p>Still haven\u2019t heard back from <a href=\"https://mastodon.social/tags/tumblr\">#<span>tumblr</span></a> customer support, after 8 days. I won\u2019t be going back, but I\u2019m hoping to at least get back my content.</p><p>I\u2019ve decided to move forward with a flat file CMS for my personal website and I\u2019m currently leaning towards <span class=\"h-card\"><a class=\"u-url\" href=\"https://mastodon.social/@getkirby\">@<span>getkirby</span></a></span> (old favorite of mine) or <span class=\"h-card\"><a class=\"u-url\" href=\"https://fosstodon.org/@eleventy\">@<span>eleventy</span></a></span></p><p>I see there are good enough options for both to get some <a href=\"https://mastodon.social/tags/IndieWeb\">#<span>IndieWeb</span></a> goodness going (e.g. webmentions).</p><p>What do you think?</p>",
        "text": "@hrbf thank you and I appreciate it!Still haven\u2019t heard back from #tumblr customer support, after 8 days. I won\u2019t be going back, but I\u2019m hoping to at least get back my content.I\u2019ve decided to move forward with a flat file CMS for my personal website and I\u2019m currently leaning towards @getkirby (old favorite of mine) or @eleventyI see there are good enough options for both to get some #IndieWeb goodness going (e.g. webmentions).What do you think?"
    },
    "published": "2023-01-11T19:10:06+00:00",
    "post-type": "note",
    "_id": "34340620",
    "_source": "7235",
    "_is_read": false
}

Jeremy Keith adactio.com

{
    "type": "entry",
    "published": "2023-01-11T17:54:25Z",
    "url": "https://adactio.com/links/19823",
    "category": [
        "blogs",
        "blogging",
        "indieweb",
        "personal",
        "publishing",
        "silos",
        "writing",
        "sharing"
    ],
    "bookmark-of": [
        "https://cdevroe.com/2023/01/11/blogging-is-alive"
    ],
    "content": {
        "text": "Colin Devroe - Blogging is alive and well\n\n\n\nThe past, present and future of blogs.",
        "html": "<h3>\n<a class=\"p-name u-bookmark-of\" href=\"https://cdevroe.com/2023/01/11/blogging-is-alive\">\nColin Devroe - Blogging is alive and well\n</a>\n</h3>\n\n<p>The past, present and future of blogs.</p>"
    },
    "author": {
        "type": "card",
        "name": "Jeremy Keith",
        "url": "https://adactio.com/",
        "photo": "https://adactio.com/images/photo-150.jpg"
    },
    "post-type": "bookmark",
    "_id": "34339529",
    "_source": "2",
    "_is_read": false
}

{
    "type": "entry",
    "author": {
        "name": "@KelsonV",
        "url": "https://wandering.shop/@KelsonV",
        "photo": null
    },
    "url": "https://wandering.shop/@KelsonV/109671921890123042",
    "content": {
        "html": "<p>Thinking about this post on \"permanence\" with <a href=\"https://wandering.shop/tags/SocialMedia\">#<span>SocialMedia</span></a> / <a href=\"https://wandering.shop/tags/IndieWeb\">#<span>IndieWeb</span></a> / <a href=\"https://wandering.shop/tags/SelfHosting\">#<span>SelfHosting</span></a> (for things that you *want* to keep permanent, anyway), balancing questions like are you going to outlive Facebook or the other way around, etc.</p><p><a href=\"https://hyperborea.org/journal/2019/11/online-permanence/\"><span>https://</span><span>hyperborea.org/journal/2019/11</span><span>/online-permanence/</span></a></p><p>I still think an \"export to static site\" option should be standard on any CMS as an exit strategy (on top of actual data portability) for cases where you no longer have the resources, time, inclination, etc. to maintain it.</p>",
        "text": "Thinking about this post on \"permanence\" with #SocialMedia / #IndieWeb / #SelfHosting (for things that you *want* to keep permanent, anyway), balancing questions like are you going to outlive Facebook or the other way around, etc.https://hyperborea.org/journal/2019/11/online-permanence/I still think an \"export to static site\" option should be standard on any CMS as an exit strategy (on top of actual data portability) for cases where you no longer have the resources, time, inclination, etc. to maintain it."
    },
    "published": "2023-01-11T18:12:02+00:00",
    "post-type": "note",
    "_id": "34339191",
    "_source": "7235",
    "_is_read": false
}

{
    "type": "entry",
    "author": {
        "name": "@m0bi13",
        "url": "https://mastodon.social/@m0bi13",
        "photo": null
    },
    "url": "https://mastodon.social/@m0bi13/109671642573468496",
    "content": {
        "html": "<p><span class=\"h-card\"><a class=\"u-url\" href=\"https://mastodon.online/@rozie\">@<span>rozie</span></a></span> <span class=\"h-card\"><a class=\"u-url\" href=\"https://soc.citizen4.eu/profile/miklo\">@<span>miklo</span></a></span> Rozdzielmy tutaj zwi\u0119kszanie zasi\u0119gu rozumiane jak w publikacjach naukowych: cytujesz, dajesz przypis, tre\u015b\u0107 mo\u017ce dotrze\u0107 w miejsca, w kt\u00f3re inaczej by nie dotar\u0142a, od zwi\u0119kszania zasi\u0119gu w sensie algorytmu / systemu informatycznego nap\u0119dzaj\u0105cego sieci spo\u0142eczno\u015bciowe.</p><p>Nieporozumienia mog\u0105 si\u0119 bra\u0107 imo z tego, \u017ce r\u00f3\u017cne rzeczy mamy na my\u015bli, pisz\u0105c \"zwi\u0119kszanie zasi\u0119gu\".</p><p>Poinformowanie autora za\u0142atwia ju\u017c <a href=\"https://mastodon.social/tags/indieweb\">#<span>indieweb</span></a>, <a href=\"https://mastodon.social/tags/wordpress\">#<span>wordpress</span></a> (ping back) czy wzmiankowanie w <a href=\"https://mastodon.social/tags/ActivityPub\">#<span>ActivityPub</span></a>/#Mastodon</p>",
        "text": "@rozie @miklo Rozdzielmy tutaj zwi\u0119kszanie zasi\u0119gu rozumiane jak w publikacjach naukowych: cytujesz, dajesz przypis, tre\u015b\u0107 mo\u017ce dotrze\u0107 w miejsca, w kt\u00f3re inaczej by nie dotar\u0142a, od zwi\u0119kszania zasi\u0119gu w sensie algorytmu / systemu informatycznego nap\u0119dzaj\u0105cego sieci spo\u0142eczno\u015bciowe.Nieporozumienia mog\u0105 si\u0119 bra\u0107 imo z tego, \u017ce r\u00f3\u017cne rzeczy mamy na my\u015bli, pisz\u0105c \"zwi\u0119kszanie zasi\u0119gu\".Poinformowanie autora za\u0142atwia ju\u017c #indieweb, #wordpress (ping back) czy wzmiankowanie w #ActivityPub/#Mastodon"
    },
    "published": "2023-01-11T17:01:00+00:00",
    "post-type": "note",
    "_id": "34337713",
    "_source": "7235",
    "_is_read": false
}

Manton Reece www.manton.org

{
    "type": "entry",
    "author": {
        "name": "Manton Reece",
        "url": "https://www.manton.org/",
        "photo": "https://micro.blog/manton/avatar.jpg"
    },
    "url": "https://www.manton.org/2023/01/11/cant-shake-a.html",
    "content": {
        "html": "<p>Can\u2019t shake a comment that someone liked Micro.blog but it didn\u2019t have many features. Blogs, themes, plug-ins, social network, podcast hosting, read-later bookmarks, cross-posts, archiving, highlights, email newsletters, bookshelves, IndieWeb, fediverse\u2026 Missing: marketing.</p>",
        "text": "Can\u2019t shake a comment that someone liked Micro.blog but it didn\u2019t have many features. Blogs, themes, plug-ins, social network, podcast hosting, read-later bookmarks, cross-posts, archiving, highlights, email newsletters, bookshelves, IndieWeb, fediverse\u2026 Missing: marketing."
    },
    "published": "2023-01-11T09:14:57-06:00",
    "post-type": "note",
    "_id": "34336722",
    "_source": "12",
    "_is_read": false
}

{
    "type": "entry",
    "author": {
        "name": "@ApisNecros",
        "url": "https://ioc.exchange/@ApisNecros",
        "photo": null
    },
    "url": "https://ioc.exchange/@ApisNecros/109671430320940204",
    "content": {
        "html": "<p>Added two new characters to my kinning red flags, Dr. Horrible, and Rick Sanchez</p><p><a href=\"https://ioc.exchange/tags/IndieWeb\">#<span>IndieWeb</span></a> <br /><a href=\"https://www.vzqk50.com/blog/mens-kinning-red-flags/#dr-horrible\"><span>https://www.</span><span>vzqk50.com/blog/mens-kinning-r</span><span>ed-flags/#dr-horrible</span></a></p>",
        "text": "Added two new characters to my kinning red flags, Dr. Horrible, and Rick Sanchez#IndieWeb \nhttps://www.vzqk50.com/blog/mens-kinning-red-flags/#dr-horrible"
    },
    "published": "2023-01-11T16:07:01+00:00",
    "post-type": "note",
    "_id": "34336167",
    "_source": "7235",
    "_is_read": false
}

Tantek Çelik tantek.com

{
    "type": "entry",
    "published": "2023-01-10 23:59-0800",
    "url": "http://tantek.com/2023/010/t2/build-use-services",
    "category": [
        "IndieWeb",
        "webDevelopment",
        "100DaysOfIndieWeb",
        "100Days"
    ],
    "content": {
        "text": "Once you have a domain^1, and connect it to an #IndieWeb service like https://micro.blog, or a https://indieweb.org/CMS on https://indieweb.org/web_hosting, you can focus^2 on your writing.\n\nOr if you enjoy #webDevelopment and want to build (option three^3), use developer services to more rapidly add IndieWeb building blocks^4 to your site so you too can focus on creating & owning your content^5.\n\nHere are some of the most common and popular developer services:\n1. Webmention sending: https://webmention.app/ by https://remysharp.com/ (@rem@front-end.social), or https://mention.tech/ by https://kevinmarks.com/ (@kevinmarks@xoxo.zone)\n2. Webmention receiving: https://webmention.io/ (I use this) by https://aaronparecki.com/ or https://webmention.herokuapp.com/ by https://voxpelli.com/ (@voxpelli@mastodon.social) \n3. POSSE & backfeed: https://brid.gy/ by Ryan of https://snarfed.org/ (@schnarfed)\n4. ActivityPub federating: https://fed.brid.gy/ also by Ryan. More on Bridgy & Bridgy Fed^6.\n\nUsing a developer service to support IndieWeb protocols saves you time. You can also contribute to the community by filing suggestions for improvements, or participating on their GitHub repositories.\n\nIf you prefer that your site not depend on any external services, you can do that too.\n\nMost of the above services are also open source that you can install and fully manage yourself. For example:\n* Webmention installable services: https://indieweb.org/Webmention#Publisher_Services\n\nAnother option is to use one of many open source libraries to more rapidly implement support for IndieWeb standards^7. The wiki pages for each standard list libraries in a variety of programming languages, e.g.:\n* https://indieweb.org/Webmention-developer#Libraries\n\nIf you choose the path of installing or building something new with libraries or by directly implementing an IndieWeb standard, be sure to test your implementation with its test suite, e.g.:\n* https://webmention.rocks/\n\nAs a web developer, you can choose how much of your #IndieWeb support you want to implement yourself (and time to invest) vs build on the services, libraries, and other open source that the community has produced and is actively supporting.\n\nThis is day 10 of #100DaysOfIndieWeb #100Days.\n\n\u2190 Day 9: https://tantek.com/2023/009/t2/edit-reply-comment-update\n\u2192 \ud83d\udd2e\n\n^1 https://tantek.com/2023/004/t1/choosing-domain-name-indieweb\n^2 https://tantek.com/2023/005/t3/indieweb-simpler-approach\n^3 https://tantek.com/2023/003/t1/indieweb-path-chosen-why\n^4 https://indieweb.org/building_blocks\n^5 https://tantek.com/2023/001/t1/own-your-notes\n^6 https://tantek.com/2023/008/t7/bridgy-indieweb-posse-backfeed\n^7 https://spec.indieweb.org/",
        "html": "Once you have a domain^1, and connect it to an #<span class=\"p-category\">IndieWeb</span> service like <a href=\"https://micro.blog\">https://micro.blog</a>, or a <a href=\"https://indieweb.org/CMS\">https://indieweb.org/CMS</a> on <a href=\"https://indieweb.org/web_hosting\">https://indieweb.org/web_hosting</a>, you can focus^2 on your writing.<br /><br />Or if you enjoy #<span class=\"p-category\">webDevelopment</span> and want to build (option three^3), use developer services to more rapidly add IndieWeb building blocks^4 to your site so you too can focus on creating &amp; owning your content^5.<br /><br />Here are some of the most common and popular developer services:<br />1. Webmention sending: <a href=\"https://webmention.app/\">https://webmention.app/</a> by <a href=\"https://remysharp.com/\">https://remysharp.com/</a> (<a class=\"h-cassis-username\" href=\"https://twitter.com/rem@front\">@rem@front</a>-<a href=\"http://end.social\">end.social</a>), or <a href=\"https://mention.tech/\">https://mention.tech/</a> by <a href=\"https://kevinmarks.com/\">https://kevinmarks.com/</a> (<a href=\"http://xoxo.zone/@kevinmarks\">@kevinmarks@xoxo.zone</a>)<br />2. Webmention receiving: <a href=\"https://webmention.io/\">https://webmention.io/</a> (I use this) by <a href=\"https://aaronparecki.com/\">https://aaronparecki.com/</a> or <a href=\"https://webmention.herokuapp.com/\">https://webmention.herokuapp.com/</a> by <a href=\"https://voxpelli.com/\">https://voxpelli.com/</a> (<a href=\"http://mastodon.social/@voxpelli\">@voxpelli@mastodon.social</a>) <br />3. POSSE &amp; backfeed: <a href=\"https://brid.gy/\">https://brid.gy/</a> by Ryan of <a href=\"https://snarfed.org/\">https://snarfed.org/</a> (<a class=\"h-cassis-username\" href=\"https://twitter.com/schnarfed\">@schnarfed</a>)<br />4. ActivityPub federating: <a href=\"https://fed.brid.gy/\">https://fed.brid.gy/</a> also by Ryan. More on Bridgy &amp; Bridgy Fed^6.<br /><br />Using a developer service to support IndieWeb protocols saves you time. You can also contribute to the community by filing suggestions for improvements, or participating on their GitHub repositories.<br /><br />If you prefer that your site not depend on any external services, you can do that too.<br /><br />Most of the above services are also open source that you can install and fully manage yourself. For example:<br />* Webmention installable services: <a href=\"https://indieweb.org/Webmention#Publisher_Services\">https://indieweb.org/Webmention#Publisher_Services</a><br /><br />Another option is to use one of many open source libraries to more rapidly implement support for IndieWeb standards^7. The wiki pages for each standard list libraries in a variety of programming languages, e.g.:<br />* <a href=\"https://indieweb.org/Webmention-developer#Libraries\">https://indieweb.org/Webmention-developer#Libraries</a><br /><br />If you choose the path of installing or building something new with libraries or by directly implementing an IndieWeb standard, be sure to test your implementation with its test suite, e.g.:<br />* <a href=\"https://webmention.rocks/\">https://webmention.rocks/</a><br /><br />As a web developer, you can choose how much of your #<span class=\"p-category\">IndieWeb</span> support you want to implement yourself (and time to invest) vs build on the services, libraries, and other open source that the community has produced and is actively supporting.<br /><br />This is day 10 of #<span class=\"p-category\">100DaysOfIndieWeb</span> #<span class=\"p-category\">100Days</span>.<br /><br />\u2190 Day 9: <a href=\"https://tantek.com/2023/009/t2/edit-reply-comment-update\">https://tantek.com/2023/009/t2/edit-reply-comment-update</a><br />\u2192 \ud83d\udd2e<br /><br />^1 <a href=\"https://tantek.com/2023/004/t1/choosing-domain-name-indieweb\">https://tantek.com/2023/004/t1/choosing-domain-name-indieweb</a><br />^2 <a href=\"https://tantek.com/2023/005/t3/indieweb-simpler-approach\">https://tantek.com/2023/005/t3/indieweb-simpler-approach</a><br />^3 <a href=\"https://tantek.com/2023/003/t1/indieweb-path-chosen-why\">https://tantek.com/2023/003/t1/indieweb-path-chosen-why</a><br />^4 <a href=\"https://indieweb.org/building_blocks\">https://indieweb.org/building_blocks</a><br />^5 <a href=\"https://tantek.com/2023/001/t1/own-your-notes\">https://tantek.com/2023/001/t1/own-your-notes</a><br />^6 <a href=\"https://tantek.com/2023/008/t7/bridgy-indieweb-posse-backfeed\">https://tantek.com/2023/008/t7/bridgy-indieweb-posse-backfeed</a><br />^7 <a href=\"https://spec.indieweb.org/\">https://spec.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": "34336157",
    "_source": "1",
    "_is_read": false
}

{
    "type": "entry",
    "author": {
        "name": "@evenstar",
        "url": "https://mas.to/@evenstar",
        "photo": null
    },
    "url": "https://mas.to/@evenstar/109670912167005349",
    "content": {
        "html": "<p>dear lord, if you MUST put white text on an only very slightly darker background, would it be too much to ask to beg you NOT to use a super-aliased pixel-based font, for the love of all that is holy? actually, look, <a href=\"https://mas.to/tags/indieweb\">#<span>indieweb</span></a> folks, can we please, PLEASE stop using pixel fonts for paragraphs of text altogether? readability is nobody's enemy AND it can look good, too. no, really.</p>",
        "text": "dear lord, if you MUST put white text on an only very slightly darker background, would it be too much to ask to beg you NOT to use a super-aliased pixel-based font, for the love of all that is holy? actually, look, #indieweb folks, can we please, PLEASE stop using pixel fonts for paragraphs of text altogether? readability is nobody's enemy AND it can look good, too. no, really."
    },
    "published": "2023-01-11T13:55:15+00:00",
    "post-type": "note",
    "_id": "34333135",
    "_source": "7235",
    "_is_read": false
}

{
    "type": "entry",
    "author": {
        "name": "@charlesroper",
        "url": "https://indieweb.social/@charlesroper",
        "photo": null
    },
    "url": "https://indieweb.social/@charlesroper/109670499905125154",
    "content": {
        "html": "<p><span class=\"h-card\"><a class=\"u-url\" href=\"https://mastodon.social/@OohDirectory\">@<span>OohDirectory</span></a></span> Other reason I ask is because, back in the day (early 00s) when Netscape and Microsoft were embattled in a bitter browser war of increasing incompatibility (you might remember this), the community rallied around Web Standards. It became *the thing* to blog about Web Standards and a whole community flourished. It was multiplicative and wonderful.</p><p>I just wish there were more ways people could rally around <a href=\"https://indieweb.social/tags/IndieWeb\">#<span>IndieWeb</span></a>, which is spiritually the same community as before rising up again.</p>",
        "text": "@OohDirectory Other reason I ask is because, back in the day (early 00s) when Netscape and Microsoft were embattled in a bitter browser war of increasing incompatibility (you might remember this), the community rallied around Web Standards. It became *the thing* to blog about Web Standards and a whole community flourished. It was multiplicative and wonderful.I just wish there were more ways people could rally around #IndieWeb, which is spiritually the same community as before rising up again."
    },
    "published": "2023-01-11T12:10:24+00:00",
    "post-type": "note",
    "_id": "34330766",
    "_source": "7235",
    "_is_read": false
}

Tantek Çelik tantek.com

{
    "type": "entry",
    "published": "2023-01-10 22:31-0800",
    "url": "http://tantek.com/2023/010/t1/",
    "category": [
        "BridgyFed"
    ],
    "in-reply-to": [
        "https://xoxo.zone/@KevinMarks/109665366036600650"
    ],
    "content": {
        "text": "https://kevinmarks.com/ good catch and thanks. Fixed the typos and resent a Webmention to #BridgyFed using https://mention.tech/ \u2014 we\u2019ll see if the cache of my post on your instance is updated.",
        "html": "<a href=\"https://kevinmarks.com/\">https://kevinmarks.com/</a> good catch and thanks. Fixed the typos and resent a Webmention to #<span class=\"p-category\">BridgyFed</span> using <a href=\"https://mention.tech/\">https://mention.tech/</a> \u2014 we\u2019ll see if the cache of my post on your instance is updated."
    },
    "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://xoxo.zone/@KevinMarks/109665366036600650": {
            "type": "entry",
            "url": "https://xoxo.zone/@KevinMarks/109665366036600650",
            "name": "xoxo.zone user KevinMarks\u2019s post",
            "post-type": "article"
        }
    },
    "_id": "34328920",
    "_source": "1",
    "_is_read": false
}

{
    "type": "entry",
    "author": {
        "name": "@CrowderSoup",
        "url": "https://hachyderm.io/@CrowderSoup",
        "photo": null
    },
    "url": "https://hachyderm.io/@CrowderSoup/109669025605973188",
    "content": {
        "html": "<p>My fifth day of <a href=\"https://hachyderm.io/tags/100daysofindieweb\">#<span>100daysofindieweb</span></a> is coming to a close. I worked more on grouping tweets by type based on the markdown output of my Twitter Archive.</p><p>I wrote about it here: <a href=\"https://crowdersoup.com/posts/projects/indieweb/100-days/day-5-classifying-tweets-continued/\"><span>https://</span><span>crowdersoup.com/posts/projects</span><span>/indieweb/100-days/day-5-classifying-tweets-continued/</span></a></p><p><a href=\"https://hachyderm.io/tags/Indieweb\">#<span>Indieweb</span></a></p>",
        "text": "My fifth day of #100daysofindieweb is coming to a close. I worked more on grouping tweets by type based on the markdown output of my Twitter Archive.I wrote about it here: https://crowdersoup.com/posts/projects/indieweb/100-days/day-5-classifying-tweets-continued/#Indieweb"
    },
    "published": "2023-01-11T05:55:28+00:00",
    "post-type": "note",
    "_id": "34325577",
    "_source": "7235",
    "_is_read": false
}

{
    "type": "entry",
    "author": {
        "name": "@evenstar",
        "url": "https://fandom.ink/@evenstar",
        "photo": null
    },
    "url": "https://fandom.ink/@evenstar/109668702628959712",
    "content": {
        "html": "<p>opened: the Shoujo Kakumei Utena fanlisting <a href=\"https://sku.anthy.net\"><span>https://</span><span>sku.anthy.net</span><span></span></a></p><p><a href=\"https://fandom.ink/tags/ShoujoKakumeiUtena\">#<span>ShoujoKakumeiUtena</span></a> <a href=\"https://fandom.ink/tags/RevolutionaryGirlUtena\">#<span>RevolutionaryGirlUtena</span></a> <a href=\"https://fandom.ink/tags/fanlisting\">#<span>fanlisting</span></a> <a href=\"https://fandom.ink/tags/fansite\">#<span>fansite</span></a> <a href=\"https://fandom.ink/tags/staticwebsite\">#<span>staticwebsite</span></a> <a href=\"https://fandom.ink/tags/oldweb\">#<span>oldweb</span></a> <a href=\"https://fandom.ink/tags/handmadehtml\">#<span>handmadehtml</span></a> <a href=\"https://fandom.ink/tags/indieweb\">#<span>indieweb</span></a> <a href=\"https://fandom.ink/tags/retroweb\">#<span>retroweb</span></a></p>",
        "text": "opened: the Shoujo Kakumei Utena fanlisting https://sku.anthy.net#ShoujoKakumeiUtena #RevolutionaryGirlUtena #fanlisting #fansite #staticwebsite #oldweb #handmadehtml #indieweb #retroweb"
    },
    "published": "2023-01-11T04:33:20+00:00",
    "post-type": "note",
    "_id": "34324964",
    "_source": "7235",
    "_is_read": false
}

Intentionally Positive

{
    "type": "entry",
    "author": {
        "name": "Will Norris",
        "url": "https://willnorris.com/",
        "photo": null
    },
    "url": "https://willnorris.com/2021/intentionally-positive/",
    "published": "2021-07-07T16:25:59-07:00",
    "content": {
        "html": "<img src=\"https://willnorris.com/hand-heart.jpg\" alt=\"Woman holding her hands in the shape of a heart, framing a sunset.\" /><p>Over the last decade or so, many companies (especially in tech) have adopted a\n\u201cNo Jerks\u201d policy.  The idea is to have policies in place for dealing with\nworkplace bullies and jerks, and to have safeguards in the recruiting and hiring\npipeline to prevent them from being hired in the first place. Much of this wave\nof emphasizing workplace civility seems to have begun with Robert Sutton\u2019s 2007\nbook, <em><a href=\"https://en.wikipedia.org/wiki/The_No_Asshole_Rule\">The No Asshole Rule</a></em> and the numerous articles that followed.  When I\nwas at Google, this topic was emphasized in a 2013 internal memo from a senior\nexecutive that was (and still is) widely circulated around the company.</p>\n<p>These kinds of articles and memos can serve as great introductions to\nunderstanding the impact bullies and jerks have on teams and the entire\norganization, and the more extreme examples of this behavior are often easy to\nspot.  However, I found that some of the examples in Sutton\u2019s book, while true\nreports of actual situations, were <strong>so</strong> extreme that they bordered on caricature.\nIt became all too easy to dismiss them, feeling that <em>my</em> workplace doesn\u2019t have\nany of <em>those</em> people.</p>\n<p>But what I have found in my experience is that <strong>most</strong> people are not overtly\njerks <strong>most</strong> of the time.  People tend to be far more nuanced, and the\nbehaviors that can lead to discord on a team are far more subtle, and often\nunintentional.</p>\n<p>The risk of teams and organizations only focusing on avoiding negative behavior\nis that they will, at best, trend toward neutral behavior.  It\u2019s not enough to\nsimply not be a jerk.  We must strive to be <strong>intentionally positive</strong>.</p>\n<p>Being <em>intentionally positive</em> is not something that happens by accident.  It\u2019s\nnot something you stumble into, and I suspect that it does not come naturally to\nmany people.  By definition, being intentionally positive is a conscious and\ndeliberate choice to behave in a particular way.</p>\n<p>So what does it mean to be intentionally positive in the workplace?  It\u2019s really\nnothing profound or surprising.  It\u2019s about being respectful to coworkers,\nempathetic and thoughtful in communication, quick to correct and apologize when\nyou make a mistake, and quick to forgive when others do.  I\u2019ve always worked in\nengineering organizations, so I\u2019ll give two concrete examples from my experience\nthere, but the lessons apply to any kind of work.</p>\n<h2>Building a better future</h2>\n<p>Any sufficiently complex software project is going to\nhave bugs.  The documentation is never as clear as you would like, and the tests\nare never as thorough.  Decisions  or policies that were made years ago might no\nlonger make sense, and there may be no one left that even remembers how or why\nthey were made in the first place.  We nearly always work in imperfect\nsituations, but the attitude we have toward that can have a big impact on a\nteam.</p>\n<p>Off-handed remarks about how poorly a piece of work has been done, or how\nshort-sighted a decision was, sets the tone for how other\u2019s work is evaluated.\nWhen done in a critical rather than constructive manner, it only serves to tear\npeople down, even if they\u2019re no longer around to hear it.  In fact, it\u2019s\nespecially important if they\u2019re no longer around, since this signals to the\ncurrent team how they should expect their own work to be discussed after they\u2019re\ngone.</p>\n<p>There\u2019s a concept in improvisational acting and comedy called \u201cYes, and\u2026\u201d.  It\u2019s\na technique of accepting whatever idea or direction your partner gives you (the\n\u201cyes\u201d), and then building on that (the \u201cand\u201d).  Even if the idea seems\npreposterous or isn\u2019t where you were wanting to go.  In business settings, this\nis often discussed in connection with brainstorming sessions, but I think it\napplies here as well because it\u2019s really about attitude.  If we\u2019re dealing with\nlegacy code or unclear policies, we accept whatever we have today, and then\nbuild on it.  We may still end up changing it, even drastically, but it means we\nwill do so with an intentionally positive attitude.</p>\n<p>Bob Ross was famous for saying that \u201cwe don\u2019t make mistakes, we have happy\naccidents\u201d.  What is that, if not applying \u201cyes, and\u2026\u201d to his painting?  Yes\nthis thing happened, and we\u2019re going to work with it and turn it into something\npositive.</p>\n<h2>Communicating with care</h2>\n<p>I think one of the hardest skills in life, and one I\u2019m\nnot sure I\u2019ll ever truly master, is effective communication.  Especially as more\npeople are working remotely, and conversations are split across a variety of\ncommunication channels, the opportunity for misunderstandings is ever\nincreasing.  Whether it\u2019s a simple code or design review for a teammate, or\nanswering the same customer question for the 100th time by a new-hire that\ndoesn\u2019t know any better, there is a huge opportunity to be intentionally\npositive in our communication.</p>\n<p>In technical reviews in particular, I have found that short, to-the-point\ncomments meant to be expedient can also be received as brusque, impatient, or\ndismissive.  Projects like <a href=\"https://conventionalcomments.org/\">Conventional Comments</a> suggest a structured way to\nprefix comments with additional context, but I\u2019ve also found that simply\nresponding in complete sentences often leads to clearer communication.  Or\nasking questions rather than giving commands: \u201cHave you considered X here?\u201d\nrather than \u201cdo X here\u201d.  (I\u2019ve also seen this backfire where such a Socratic\nmethod led to frustration with a reviewer that clearly seemed to have an opinion\nbut just wouldn\u2019t outright say it.)</p>\n<p>When dealing with customer questions, we can start by being careful to fully\nunderstand their specific situation, since it may actually not be the same as\nthose before them.  And then we can be friendly, helpful, and understanding of\ntheir problem.  This isn\u2019t about platitudes or fake hospitality (that really\ndrives me crazy); this is about genuine empathy and kindness.</p>\n<p>While being intentionally positive with how we communicate toward others, it\u2019s\nequally (if not more) important to take the same attitude when we\u2019re on the\nreceiving end. This is often described as \u201cassuming good intent\u201d or the\nprinciple of charity.  If something that someone says could be interpreted\nmultiple ways, assume that they meant it in the best possible interpretation.\nEven if you know that they didn\u2019t, it can sometimes be effective to simply\nignore that fact and respond as if they did.</p>\n<h2>The cost of being intentionally positive</h2>\n<p>Like any other skill, this will not come naturally for everyone (I know it often\ndoesn\u2019t for me).  It may require conscious effort, and it may feel awkward at\ntimes.  And that may mean that it takes longer to reply to an email or complete\na code review because you have to spend extra time thinking about how you\nrespond.  That\u2019s okay.  As a manager, <strong>I\u2019m willing to sacrifice velocity in\norder to improve team health</strong> because I know that we will only get better at it\nand it will come more naturally with practice.</p>\n<p>The only way to build the kind of team that I would like to work on is to make\ndeliberate decisions to be that team each day.</p>\n<p>(I picked up the term \u201cintentionally positive\u201d from the <a href=\"https://indieweb.org/code-of-conduct\">IndieWeb Code of\nConduct</a> which begins, \u201cIndieWeb is an intentionally positive community\u201d, which\nI absolutely love and it\u2019s always stuck with me.  I did some digging, and it\nwas added by <a href=\"https://tantek.com/\">Tantek \u00c7elik</a> in <a href=\"https://indieweb.org/wiki/index.php?title=code-of-conduct&amp;type=revision&amp;diff=1939&amp;oldid=1938\">February 2013</a>.)</p>",
        "text": "Over the last decade or so, many companies (especially in tech) have adopted a\n\u201cNo Jerks\u201d policy.  The idea is to have policies in place for dealing with\nworkplace bullies and jerks, and to have safeguards in the recruiting and hiring\npipeline to prevent them from being hired in the first place. Much of this wave\nof emphasizing workplace civility seems to have begun with Robert Sutton\u2019s 2007\nbook, The No Asshole Rule and the numerous articles that followed.  When I\nwas at Google, this topic was emphasized in a 2013 internal memo from a senior\nexecutive that was (and still is) widely circulated around the company.\nThese kinds of articles and memos can serve as great introductions to\nunderstanding the impact bullies and jerks have on teams and the entire\norganization, and the more extreme examples of this behavior are often easy to\nspot.  However, I found that some of the examples in Sutton\u2019s book, while true\nreports of actual situations, were so extreme that they bordered on caricature.\nIt became all too easy to dismiss them, feeling that my workplace doesn\u2019t have\nany of those people.\nBut what I have found in my experience is that most people are not overtly\njerks most of the time.  People tend to be far more nuanced, and the\nbehaviors that can lead to discord on a team are far more subtle, and often\nunintentional.\nThe risk of teams and organizations only focusing on avoiding negative behavior\nis that they will, at best, trend toward neutral behavior.  It\u2019s not enough to\nsimply not be a jerk.  We must strive to be intentionally positive.\nBeing intentionally positive is not something that happens by accident.  It\u2019s\nnot something you stumble into, and I suspect that it does not come naturally to\nmany people.  By definition, being intentionally positive is a conscious and\ndeliberate choice to behave in a particular way.\nSo what does it mean to be intentionally positive in the workplace?  It\u2019s really\nnothing profound or surprising.  It\u2019s about being respectful to coworkers,\nempathetic and thoughtful in communication, quick to correct and apologize when\nyou make a mistake, and quick to forgive when others do.  I\u2019ve always worked in\nengineering organizations, so I\u2019ll give two concrete examples from my experience\nthere, but the lessons apply to any kind of work.\nBuilding a better future\nAny sufficiently complex software project is going to\nhave bugs.  The documentation is never as clear as you would like, and the tests\nare never as thorough.  Decisions  or policies that were made years ago might no\nlonger make sense, and there may be no one left that even remembers how or why\nthey were made in the first place.  We nearly always work in imperfect\nsituations, but the attitude we have toward that can have a big impact on a\nteam.\nOff-handed remarks about how poorly a piece of work has been done, or how\nshort-sighted a decision was, sets the tone for how other\u2019s work is evaluated.\nWhen done in a critical rather than constructive manner, it only serves to tear\npeople down, even if they\u2019re no longer around to hear it.  In fact, it\u2019s\nespecially important if they\u2019re no longer around, since this signals to the\ncurrent team how they should expect their own work to be discussed after they\u2019re\ngone.\nThere\u2019s a concept in improvisational acting and comedy called \u201cYes, and\u2026\u201d.  It\u2019s\na technique of accepting whatever idea or direction your partner gives you (the\n\u201cyes\u201d), and then building on that (the \u201cand\u201d).  Even if the idea seems\npreposterous or isn\u2019t where you were wanting to go.  In business settings, this\nis often discussed in connection with brainstorming sessions, but I think it\napplies here as well because it\u2019s really about attitude.  If we\u2019re dealing with\nlegacy code or unclear policies, we accept whatever we have today, and then\nbuild on it.  We may still end up changing it, even drastically, but it means we\nwill do so with an intentionally positive attitude.\nBob Ross was famous for saying that \u201cwe don\u2019t make mistakes, we have happy\naccidents\u201d.  What is that, if not applying \u201cyes, and\u2026\u201d to his painting?  Yes\nthis thing happened, and we\u2019re going to work with it and turn it into something\npositive.\nCommunicating with care\nI think one of the hardest skills in life, and one I\u2019m\nnot sure I\u2019ll ever truly master, is effective communication.  Especially as more\npeople are working remotely, and conversations are split across a variety of\ncommunication channels, the opportunity for misunderstandings is ever\nincreasing.  Whether it\u2019s a simple code or design review for a teammate, or\nanswering the same customer question for the 100th time by a new-hire that\ndoesn\u2019t know any better, there is a huge opportunity to be intentionally\npositive in our communication.\nIn technical reviews in particular, I have found that short, to-the-point\ncomments meant to be expedient can also be received as brusque, impatient, or\ndismissive.  Projects like Conventional Comments suggest a structured way to\nprefix comments with additional context, but I\u2019ve also found that simply\nresponding in complete sentences often leads to clearer communication.  Or\nasking questions rather than giving commands: \u201cHave you considered X here?\u201d\nrather than \u201cdo X here\u201d.  (I\u2019ve also seen this backfire where such a Socratic\nmethod led to frustration with a reviewer that clearly seemed to have an opinion\nbut just wouldn\u2019t outright say it.)\nWhen dealing with customer questions, we can start by being careful to fully\nunderstand their specific situation, since it may actually not be the same as\nthose before them.  And then we can be friendly, helpful, and understanding of\ntheir problem.  This isn\u2019t about platitudes or fake hospitality (that really\ndrives me crazy); this is about genuine empathy and kindness.\nWhile being intentionally positive with how we communicate toward others, it\u2019s\nequally (if not more) important to take the same attitude when we\u2019re on the\nreceiving end. This is often described as \u201cassuming good intent\u201d or the\nprinciple of charity.  If something that someone says could be interpreted\nmultiple ways, assume that they meant it in the best possible interpretation.\nEven if you know that they didn\u2019t, it can sometimes be effective to simply\nignore that fact and respond as if they did.\nThe cost of being intentionally positive\nLike any other skill, this will not come naturally for everyone (I know it often\ndoesn\u2019t for me).  It may require conscious effort, and it may feel awkward at\ntimes.  And that may mean that it takes longer to reply to an email or complete\na code review because you have to spend extra time thinking about how you\nrespond.  That\u2019s okay.  As a manager, I\u2019m willing to sacrifice velocity in\norder to improve team health because I know that we will only get better at it\nand it will come more naturally with practice.\nThe only way to build the kind of team that I would like to work on is to make\ndeliberate decisions to be that team each day.\n(I picked up the term \u201cintentionally positive\u201d from the IndieWeb Code of\nConduct which begins, \u201cIndieWeb is an intentionally positive community\u201d, which\nI absolutely love and it\u2019s always stuck with me.  I did some digging, and it\nwas added by Tantek \u00c7elik in February 2013.)"
    },
    "name": "Intentionally Positive",
    "post-type": "article",
    "_id": "34324629",
    "_source": "248",
    "_is_read": false
}

IndieWeb Summit 2016 Demo

{
    "type": "entry",
    "author": {
        "name": "Will Norris",
        "url": "https://willnorris.com/",
        "photo": null
    },
    "url": "https://willnorris.com/2016/indieweb-demo/",
    "published": "2016-06-04T11:44:49-07:00",
    "content": {
        "html": "<p>Demoing my simple publishing workflow at IndieWeb Summit 2016.</p>",
        "text": "Demoing my simple publishing workflow at IndieWeb Summit 2016."
    },
    "name": "IndieWeb Summit 2016 Demo",
    "post-type": "article",
    "_id": "34324633",
    "_source": "248",
    "_is_read": false
}

Attending IndieWeb Summit 2016

{
    "type": "entry",
    "author": {
        "name": "Will Norris",
        "url": "https://willnorris.com/",
        "photo": null
    },
    "url": "https://willnorris.com/2016/indieweb-summit/",
    "published": "2016-05-25T12:44:41-07:00",
    "content": {
        "html": "<img src=\"https://willnorris.com/indiewebcamp-logo-lockup-color.svg\" alt=\"\" /><p>I\u2019ll be attending <a href=\"http://2016.indieweb.org/\">IndieWeb Summit</a> in Portland next week,  probably working on the\n<a href=\"https://willnorris.com/go/microformats\">go microformats library</a> which I started focusing on a few weeks ago as part of a\nwebmention service I\u2019ve been thinking about lately.  As I\u2019ve been working on that library though,\nI\u2019ve found a few discrepancies between the different popular microformat libraries, so there\u2019s a\npretty good chance I\u2019ll spend at least a little time building a little service to compare the\nresults from those.</p>",
        "text": "I\u2019ll be attending IndieWeb Summit in Portland next week,  probably working on the\ngo microformats library which I started focusing on a few weeks ago as part of a\nwebmention service I\u2019ve been thinking about lately.  As I\u2019ve been working on that library though,\nI\u2019ve found a few discrepancies between the different popular microformat libraries, so there\u2019s a\npretty good chance I\u2019ll spend at least a little time building a little service to compare the\nresults from those."
    },
    "name": "Attending IndieWeb Summit 2016",
    "post-type": "article",
    "_id": "34324634",
    "_source": "248",
    "_is_read": false
}

Attending IndieWebCamp SF 2015

{
    "type": "entry",
    "author": {
        "name": "Will Norris",
        "url": "https://willnorris.com/",
        "photo": null
    },
    "url": "https://willnorris.com/2015/attending-indiewebcamp/",
    "published": "2015-10-23T09:28:15-07:00",
    "content": {
        "html": "<p>I\u2019m looking forward to attending <a href=\"https://kylewm.com/2015/12/indiewebcamp-sf-2015\">IndieWebCamp SF 2015</a> this year.  I\u2019ve missed the last couple of events for\nvarious reasons, and really want to get back into things.  I\u2019m thinking about maybe hacking on <a href=\"https://camlistore.org/\">Camlistore</a> a bit this year, perhaps doing some <a href=\"https://github.com/camlistore/camlistore/commits?author=willnorris\">more work</a> on\ndocumentation.</p>",
        "text": "I\u2019m looking forward to attending IndieWebCamp SF 2015 this year.  I\u2019ve missed the last couple of events for\nvarious reasons, and really want to get back into things.  I\u2019m thinking about maybe hacking on Camlistore a bit this year, perhaps doing some more work on\ndocumentation."
    },
    "name": "Attending IndieWebCamp SF 2015",
    "post-type": "article",
    "_id": "34324637",
    "_source": "248",
    "_is_read": false
}

{
    "type": "entry",
    "author": {
        "name": "#indieweb",
        "url": "https://mastodon.social/tags/indieweb",
        "photo": null
    },
    "url": "https://boffosocko.com/2023/01/10/55813650/",
    "content": {
        "html": "<p></p><p><a href=\"https://hcommons.social/@cplong\">@cplong</a> <a href=\"https://hcommons.social/@sramsay\">@sramsay</a><br />\nIndieWeb, blogging, fountain pens?!<a class=\"u-in-reply-to\" href=\"https://hcommons.social/@sramsay/109660599682539192\">?</a> I almost hate to mention it for the rabbit hole it may become, but you\u2019ll get a bit of all three here: <a href=\"https://micro.blog/discover/pens\">https://micro.blog/discover/pens</a>. Happy New Year!<br /></p><p><a class=\"u-tag u-category\" href=\"https://boffosocko.com/tag/blogging/\">#blogging</a> <a class=\"u-tag u-category\" href=\"https://boffosocko.com/tag/fountain-pens/\">#fountain-pens</a> <a class=\"u-tag u-category\" href=\"https://boffosocko.com/tag/indieweb/\">#indieweb</a> <a class=\"u-tag u-category\" href=\"https://boffosocko.com/tag/micro-blog/\">#micro-blog</a></p><p><a href=\"https://boffosocko.com/2023/01/10/55813650/\">https://boffosocko.com/2023/01/10/55813650/</a></p>",
        "text": "@cplong @sramsay\n\nIndieWeb, blogging, fountain pens?!? I almost hate to mention it for the rabbit hole it may become, but you\u2019ll get a bit of all three here: https://micro.blog/discover/pens. Happy New Year!\n#blogging #fountain-pens #indieweb #micro-bloghttps://boffosocko.com/2023/01/10/55813650/"
    },
    "published": "2023-01-11T00:23:33+00:00",
    "post-type": "note",
    "_id": "34322032",
    "_source": "7235",
    "_is_read": false
}

{
    "type": "entry",
    "author": {
        "name": "@meadowhawk",
        "url": "https://indieweb.social/@meadowhawk",
        "photo": null
    },
    "url": "https://indieweb.social/@meadowhawk/109667340383822248",
    "content": {
        "html": "<p>Since I simply fake it as a front end developer I always find myself needing icons and never knowing where to get them.  So I ran across this in tldr today and sharing it as much as saving it for future reference. <a href=\"https://iconoir.com\"><span>https://</span><span>iconoir.com</span><span></span></a> </p><p>It's MIT Licensed and open source, feels nice and helpful in <a href=\"https://indieweb.social/tags/IndieWeb\">#<span>IndieWeb</span></a> circles!</p>",
        "text": "Since I simply fake it as a front end developer I always find myself needing icons and never knowing where to get them.  So I ran across this in tldr today and sharing it as much as saving it for future reference. https://iconoir.com It's MIT Licensed and open source, feels nice and helpful in #IndieWeb circles!"
    },
    "published": "2023-01-10T22:46:53+00:00",
    "post-type": "note",
    "_id": "34319864",
    "_source": "7235",
    "_is_read": false
}

{
    "type": "entry",
    "author": {
        "name": "@tmichellemoore",
        "url": "https://mastodon.social/@tmichellemoore",
        "photo": null
    },
    "url": "https://mastodon.social/@tmichellemoore/109667244278052950",
    "content": {
        "html": "<p>Project Journal: A School System Implementing Computers in Schools</p><p>Introduction</p><p>Today\u2019s project journal is a memory of being on the edge of a project to install computers and networks in a school system. </p><p><a href=\"https://mastodon.social/tags/100DaysofIndieWeb\">#<span>100DaysofIndieWeb</span></a>, <a href=\"https://mastodon.social/tags/IndieWeb\">#<span>IndieWeb</span></a>, <a href=\"https://mastodon.social/tags/ProjectJournal\">#<span>ProjectJournal</span></a>, <a href=\"https://mastodon.social/tags/ProjectManagement\">#<span>ProjectManagement</span></a></p><p>Day 3 of 100</p><p>When I</p><p><a href=\"https://tmichellemoore.com/blog/project-journal-a-school-system-implementing-computers-in-schools/\"><span>https://</span><span>tmichellemoore.com/blog/projec</span><span>t-journal-a-school-system-implementing-computers-in-schools/</span></a></p><p><a href=\"https://mastodon.social/tags/100DaysOfIndieWeb\">#<span>100DaysOfIndieWeb</span></a> <a href=\"https://mastodon.social/tags/IndieWeb\">#<span>IndieWeb</span></a> <a href=\"https://mastodon.social/tags/ProgramManagement\">#<span>ProgramManagement</span></a> <a href=\"https://mastodon.social/tags/ProjectJournal\">#<span>ProjectJournal</span></a> <a href=\"https://mastodon.social/tags/ProjectManagement\">#<span>ProjectManagement</span></a></p>",
        "text": "Project Journal: A School System Implementing Computers in SchoolsIntroductionToday\u2019s project journal is a memory of being on the edge of a project to install computers and networks in a school system. #100DaysofIndieWeb, #IndieWeb, #ProjectJournal, #ProjectManagementDay 3 of 100When Ihttps://tmichellemoore.com/blog/project-journal-a-school-system-implementing-computers-in-schools/#100DaysOfIndieWeb #IndieWeb #ProgramManagement #ProjectJournal #ProjectManagement"
    },
    "published": "2023-01-10T22:22:27+00:00",
    "post-type": "note",
    "_id": "34319335",
    "_source": "7235",
    "_is_read": false
}