Marty McGuire martymcgui.re

Updating my Tor mirror to Onion Service V3

{
    "type": "entry",
    "published": "2021-05-02T00:52:46-0400",
    "url": "https://martymcgui.re/2021/05/02/updating-my-tor-mirror-to-onion-service-v3/",
    "category": [
        "tor",
        "site-update",
        "onion"
    ],
    "syndication": [
        "https://news.indieweb.org/en/martymcgui.re/2021/05/02/updating-my-tor-mirror-to-onion-service-v3/"
    ],
    "name": "Updating my Tor mirror to Onion Service V3",
    "content": {
        "text": "TL;DR: the Tor .onion mirror of this site has moved. The old .onion address will forward to the new .onion address until Onion Service V2 is deprecated later in 2021.\n    \n\n\n\n  I've got a new home on the anonymizing Tor network! It's:\n  \n\nhttp://martymcgfuraocsgy2a25btl5srhifcdud6m4eiphz2mq6fafttwh7qd.onion/\nTor What Now?\nTor aka \"the onion router\" is an anonymizing network that protects the identity and location of users by bouncing their traffic through a set of volunteer servers, with encryption at each layer to make it harder for any given server to figure out who is sending what to whom.\nTor can also protect the identity and location of the sites and services that users are accessing, using a \"rendezvous server\" where the user's encrypted layers meet a similar set of encrypted layers to the server.\n\n  These were originally known as \"hidden services\", and are often what folks are referring to when they speak mysteriously of the \"dark web\". In recent years, to shake off some of the suspicion raised by the word \"hidden\", these have been renamed to Onion Services.\n  \n\n\n  A Partial History\n  \n\n\n  I first set up a \".onion\" address for my site back in mid-2016 when I was playing with some decentralized web projects (decentralized web projects which I later forgot \ud83d\ude2c). I used a tool called Shallot to generate a \"vanity\" URL that started with my usual online handle of schmarty. Once it was up and running, you could visit http://schmartyp7qtjzn7.onion/ and see the same content as my main domain https://martymcgui.re/ \n  \n\nSometime later (2019?) I got the hint from a (now lost to me) blog post to use Apache's mod_substitute to rewrite the HTML you get when visiting the site. This let me replace URLs for images, video, and other files from the not-onion website with .onion URLs. This cleanup keeps network requests for my content inside the Tor network.\nLast year, the Tor Project announced Onion-Location, a way for sites to announce when they have a .onion version available. I added Onion-Location to my site so folks viewing it in the Tor browser could be redirected to the .onion version in one click. They also sent me some stickers for my trouble. Pretty neat!\nMeanwhile, back in late 2017, Tor rolled out a new Onion Service version 3, with several improvements, including new, longer (and incompatible-with-V2) .onion domains. Folks running Onion Services were encouraged to move to the new system and in mid-2020 a timeline was announced to shut down V2 Onion Services.\n\n  I've had the upgrade on my list for a while and just hadn't got around to it. Then some discussion about V2 and V3 .onions in the IndieWeb chat got a little spicy and reminded me that I should just buckle up and do it.\n  \n\nEnough History, What About the Update?\n\n  What's in a (.onion) Name?\n  \n\n\n  Today I hope that I am less vain than I was in 2016. I still wanted a little bit of myself in my new .onion address! So I grabbed mkp224o, a program for generating and filtering .onion address keys. The probability of generating a key with the a sequence that you want goes down very quickly as you make the sequence longer. So, the more specific your vanity desires, the longer you'll need to run a tool like mkp244o to have a chance to a .onion that you like. At 8 characters, \"martymcg\" seemed like pressing my luck, but I started it up and let it run overnight.\n  \n\nThe next day, bless random number generation, I had a hit! This gave me the keys I'd need to run a site at martymcgfuraocsgy2a25btl5srhifcdud6m4eiphz2mq6fafttwh7qd.onion.\n\n  Is This Server Maintenance? \ud83d\udc81\ud83c\udffb\u200d\u2642\ufe0f\ud83e\udd8b\n  \n\n With keys in hand, I set about getting this new onion service set up on the frankly ancient and creaky server that hosts my site.\n\n  I wasn't sure what minimum version of tor I'd need, and the server was running \u2013 oh my gosh \u2013 Ubuntu 14.04. So the update paused here while I reflexively upgraded to 16.04, breaking a bunch of my Python sites. After some time struggling to solve Apache mod_wsgi segmentation faults (!), I invoked YOLO Ops and upgraded to 18.04. Miracle of miracles \u2013 my sites worked again! Having pressed my luck once I decided not to go for 20.04 today. Did I learn anything from this? Probably not.\n  \n\nUnfortunately (and perhaps obvious in hindsight) the Ubuntu 18.04 package for tor was an obsolete version. Ultimately I added the Tor PPA and am, finally, running the recommended recent version of tor.\n\n  I Thought this was About an Onion Service\n  \n\nAt last I was ready to set up this new V3 onion service. I copied over the files generated by mkp224o to a new folder under /var/lib/tor and updated the file permissions to match tor's expectations. (Seriously, make sure to follow the mkp224o README instructions for file ownership and permissions exactly or tor just won't start).\nWith the key files in place, I edited /etc/tor/torrc to make a new onion service definition for the domain, pointed at my web server. Shortly after, I could see my web server's default site at my new .onion domain and the rest of the process was more familiar website plumbing.\nI copied the Apache virtualhost config from my old V2 .onion to a new config for the V3 .onion. This was pretty much just a copy/paste/find-replace job. With the new virtualhost enabled and Apache restarted, I could see my site!\nTor Browser screenshot showing the new .onion address and part of my homepage.To make things official, it was time to clean up more Apache configs. I updated my main site to use the new .onion domain for Onion-Location, so Tor Browser users will be prompted to go there automatically. I also updated the old V2 .onion domain to redirect to the new one.\n\n  What's Next?\n  \n\nV2 .onions are set to stop working on Tor Browser in July 2021, and be entirely removed from the network in October 2021. At that point I'll shut down the old service.\nWhile this website's update is done, I'm not finished upgrading personal onion services. I've got several that I've set up over the years for server-to-server connections and for services like Home Assistant that only \"exist\" on my home network but that I might occasionally access from out in the world. They're great for punching through firewalls!\n\n  What Does This Have to Do with IndieWeb?\n  \n\nThe somewhat cataclysmic end of V2 onion services had folks in the IndieWeb chat questioning whether a .onion could ever be trustworthy for identity. It's true that the Tor Project is likely someday to replace and sunset V3 domains if a security need arises! .onion domain longevity is not a promised feature.\n\n  That said, V2 onion services were around for the past 15 years! My own V2 .onion domain has been up trouble-free for 5 years. That's longer than I've held many \"real\" domains! And, I didn't have to give my identity information and money to register my .onion like a regular TLD, or remember to feed the blockchain like Namecoin's .bit TLD, or worry about a DNS registrar bumping up prices, serving a takedown notice, letting a scammer transfer it away, squatting or selling it because I forgot to update my payment info, or getting caught up in trade and border disputes. Domains change and people move their stuff around. We figure it out.\n  \n\nI think a much (much) bigger barrier to IndieWeb adoption of .onions is the requirement of running a tor service and making requests through it in order to access onion services. Maybe it's not a big surprise (or hardship) that folks can only visit a .onion website via a specialized browser like Tor Browser. However, for many of the interactive building blocks of the IndieWeb to work, sites need to be able to talk server-to-server. Following feeds on .onion sites, or sending and receiving Webmentions with them, would require making a wide plurality of software \"onion-aware\".\nIs that doable? Yeah, with a lot of goodwill, motivation, and collaboration.\n\n  Is it likely to happen? I guess that depends on how many folks make a .onion site their home on the web. \ud83d\ude0f",
        "html": "<p>\n  <i>\n    TL;DR: the Tor .onion mirror of this site has moved. The <a href=\"http://schmartyp7qtjzn7.onion/\">old .onion address</a> will forward to <a href=\"http://martymcgfuraocsgy2a25btl5srhifcdud6m4eiphz2mq6fafttwh7qd.onion/\">the new .onion address</a> until <a href=\"https://blog.torproject.org/v2-deprecation-timeline\">Onion Service V2</a> is deprecated later in 2021.\n    <br /></i>\n</p>\n<p>\n  I've got a new home on the <a href=\"https://www.torproject.org/\">anonymizing Tor network</a>! It's:\n  <br /></p>\n<p>http://martymcgfuraocsgy2a25btl5srhifcdud6m4eiphz2mq6fafttwh7qd.onion/</p>\n<h2>Tor What Now?</h2>\n<p>Tor aka \"the onion router\" is an anonymizing network that protects the identity and location of users by bouncing their traffic through a set of volunteer servers, with encryption at each layer to make it harder for any given server to figure out who is sending what to whom.</p>\n<p>Tor can <i>also</i> protect the identity and location of the <i>sites and services</i> that users are accessing, using a \"rendezvous server\" where the user's encrypted layers meet a similar set of encrypted layers to the server.</p>\n<p>\n  These were originally known as \"hidden services\", and are often what folks are referring to when they speak mysteriously of the \"dark web\". In recent years, to shake off some of the suspicion raised by the word \"hidden\", these have been renamed to Onion Services.\n  <br /></p>\n<h2>\n  A Partial History\n  <br /></h2>\n<p>\n  I first set up a \".onion\" address for my site back in mid-2016 when I was playing with some decentralized web projects (<a href=\"https://martymcgui.re/2020/12/19/a-slightly-messy-visit-to-the-decentralized-web/\">decentralized web projects which I later forgot</a> \ud83d\ude2c). I used a tool called <a href=\"https://github.com/katmagic/Shallot\">Shallot</a> to generate a \"vanity\" URL that started with my usual online handle of schmarty. Once it was up and running, you could visit http://schmartyp7qtjzn7.onion/ and see the same content as my main domain https://martymcgui.re/ \n  <br /></p>\n<p>Sometime later (2019?) I got the hint from a (now lost to me) blog post to use <a href=\"https://httpd.apache.org/docs/2.4/mod/mod_substitute.html\">Apache's mod_substitute</a> to rewrite the HTML you get when visiting the site. This let me replace URLs for images, video, and other files from the not-onion website with .onion URLs. This cleanup keeps network requests for my content inside the Tor network.</p>\n<p>Last year, the Tor Project announced <a href=\"https://blog.torproject.org/more-onions-porfavor\">Onion-Location, a way for sites to announce when they have a .onion version available</a>. <a href=\"https://martymcgui.re/2020/07/08/190614/\">I added Onion-Location to my site</a> so folks viewing it in the Tor browser could be redirected to the .onion version in one click. They also sent me some stickers for my trouble. Pretty neat!</p>\n<p>Meanwhile, back in late 2017, <a href=\"https://blog.torproject.org/we-want-you-test-next-gen-onion-services\">Tor rolled out a new Onion Service version 3</a>, with several improvements, including new, longer (and incompatible-with-V2) .onion domains. Folks running Onion Services were encouraged to move to the new system and <a href=\"https://blog.torproject.org/v2-deprecation-timeline\">in mid-2020 a timeline was announced to shut down V2 Onion Services</a>.</p>\n<p>\n  I've had the upgrade on my list for <i>a while</i> and just hadn't got around to it. Then some <a href=\"https://chat.indieweb.org/dev/2021-04-30#t1619814580915900\">discussion about V2 and V3 .onions in the IndieWeb chat</a> got a little spicy and reminded me that I should just buckle up and do it.\n  <br /></p>\n<h2>Enough History, What About the Update?</h2>\n<h3>\n  What's in a (.onion) Name?\n  <br /></h3>\n<p>\n  Today I hope that I am less vain than I was in 2016. I still wanted a little bit of myself in my new .onion address! So I grabbed <a href=\"https://github.com/cathugger/mkp224o#readme\">mkp224o, a program for generating and filtering .onion address keys</a>. The probability of generating a key with the a sequence that you want goes down very quickly as you make the sequence longer. So, the more specific your vanity desires, the longer you'll need to run a tool like mkp244o to have a chance to a .onion that you like. At 8 characters, \"martymcg\" seemed like pressing my luck, but I started it up and let it run overnight.\n  <br /></p>\n<p>The next day, bless random number generation, I had a hit! This gave me the keys I'd need to run a site at martymcgfuraocsgy2a25btl5srhifcdud6m4eiphz2mq6fafttwh7qd.onion.</p>\n<h3>\n  Is This Server Maintenance? \ud83d\udc81\ud83c\udffb\u200d\u2642\ufe0f\ud83e\udd8b\n  <br /></h3>\n<p> With keys in hand, I set about getting this new onion service set up on the frankly ancient and creaky server that hosts my site.</p>\n<p>\n  I wasn't sure what minimum version of tor I'd need, and the server was running \u2013 oh my gosh \u2013 Ubuntu 14.04. So the update paused here while I reflexively upgraded to 16.04, breaking a bunch of my Python sites. After some time struggling to solve Apache mod_wsgi segmentation faults (!), I invoked YOLO Ops and upgraded to 18.04. Miracle of miracles \u2013 my sites worked again! Having pressed my luck once I decided not to go for 20.04 today. Did I learn anything from this? Probably not.\n  <br /></p>\n<p>Unfortunately (and perhaps obvious in hindsight) the Ubuntu 18.04 package for tor was an obsolete version. Ultimately I added the <a href=\"https://support.torproject.org/apt/tor-deb-repo/\">Tor PPA</a> and am, finally, running the recommended recent version of tor.</p>\n<h3>\n  I Thought this was About an Onion Service\n  <br /></h3>\n<p>At last I was ready to set up this new V3 onion service. I copied over the files generated by mkp224o to a new folder under /var/lib/tor and updated the file permissions to match tor's expectations. (Seriously, make sure to follow the mkp224o README instructions for file ownership and permissions exactly or tor just won't start).</p>\n<p>With the key files in place, I edited /etc/tor/torrc to make a new onion service definition for the domain, pointed at my web server. Shortly after, I could see my web server's default site at my new .onion domain and the rest of the process was more familiar website plumbing.</p>\n<p>I copied the Apache virtualhost config from my old V2 .onion to a new config for the V3 .onion. This was pretty much just a copy/paste/find-replace job. With the new virtualhost enabled and Apache restarted, I could see my site!</p>\n<img src=\"https://media.martymcgui.re/a1/da/0b/00/83b99ddc5a184713ef0aa67e11140c592d6ee0fc9f8037b3f783790b.png\" alt=\"\" />Tor Browser screenshot showing the new .onion address and part of my homepage.<p>To make things official, it was time to clean up more Apache configs. I updated my main site to use the new .onion domain for Onion-Location, so Tor Browser users will be prompted to go there automatically. I also updated the old V2 .onion domain to redirect to the new one.</p>\n<h2>\n  What's Next?\n  <br /></h2>\n<p>V2 .onions are set to stop working on Tor Browser in July 2021, and be entirely removed from the network in October 2021. At that point I'll shut down the old service.</p>\n<p>While this website's update is done, I'm not finished upgrading personal onion services. I've got several that I've set up over the years for server-to-server connections and for services like Home Assistant that only \"exist\" on my home network but that I might occasionally access from out in the world. They're great for punching through firewalls!</p>\n<h2>\n  What Does This Have to Do with IndieWeb?\n  <br /></h2>\n<p>The somewhat cataclysmic end of V2 onion services had folks in the <a href=\"https://indieweb.org/discuss\">IndieWeb chat</a> questioning whether a .onion could ever be trustworthy for identity. It's true that the Tor Project is likely someday to replace and sunset V3 domains if a security need arises! .onion domain longevity is not a promised feature.</p>\n<p>\n  That said, V2 onion services were around for the past 15 years! My own V2 .onion domain has been up trouble-free for 5 years. That's longer than I've held many \"real\" domains! And, I didn't have to give my identity information and money to register my .onion like a regular TLD, or remember to feed the blockchain like Namecoin's .bit TLD, or worry about a DNS registrar bumping up prices, serving a takedown notice, letting a scammer transfer it away, squatting or selling it because I forgot to update my payment info, or <a href=\"https://www.theregister.com/2019/01/07/brit_eu_domain_owners/\">getting caught up in trade and border disputes</a>. Domains change and people move their stuff around. <a href=\"https://indieweb.org/migration\">We figure it out</a>.\n  <br /></p>\n<p>I think a much (much) bigger barrier to IndieWeb adoption of .onions is the requirement of running a tor service and making requests through it in order to access onion services. Maybe it's not a big surprise (or hardship) that folks can only visit a .onion website via a specialized browser like Tor Browser. However, for many of the interactive building blocks of the IndieWeb to work, sites need to be able to talk server-to-server. Following feeds on .onion sites, or sending and receiving Webmentions with them, would require making a wide plurality of software \"onion-aware\".</p>\n<p>Is that doable? Yeah, with a lot of goodwill, motivation, and collaboration.</p>\n<p>\n  Is it likely to happen? I guess that depends on how many folks make a .onion site their home on the web. \ud83d\ude0f\n  <br /></p>"
    },
    "author": {
        "type": "card",
        "name": "Marty McGuire",
        "url": "https://martymcgui.re/",
        "photo": "https://martymcgui.re/images/logo.jpg"
    },
    "post-type": "article",
    "_id": "20185860",
    "_source": "175",
    "_is_read": true
}

Jessica Smith www.jayeless.net

{
    "type": "entry",
    "author": {
        "name": "Jessica Smith",
        "url": "https://www.jayeless.net/",
        "photo": "https://avatars.micro.blog/avatars/2021/64321.jpg"
    },
    "url": "https://www.jayeless.net/2021/05/micropub-baby-steps.html",
    "content": {
        "html": "<p>So, I\u2019m taking the teensiest little baby steps towards creating a <a href=\"https://indieweb.org/Micropub/Servers\">Micropub endpoint</a> for my Hugo blog \ud83d\ude48 So far, I can\u2026 authenticate, and submit content. The part where that content is actually saved anywhere or published, that\u2019s still in progress. But it\u2019s a start!</p>",
        "text": "So, I\u2019m taking the teensiest little baby steps towards creating a Micropub endpoint for my Hugo blog \ud83d\ude48 So far, I can\u2026 authenticate, and submit content. The part where that content is actually saved anywhere or published, that\u2019s still in progress. But it\u2019s a start!"
    },
    "published": "2021-05-02T01:29:00+00:00",
    "post-type": "note",
    "_id": "33380024",
    "_source": "7224",
    "_is_read": true
}

Vika fireburn.ru

{
    "type": "entry",
    "published": "2021-04-27T21:48:32+00:00",
    "url": "https://fireburn.ru/posts/1619560112",
    "category": [
        "IndieWeb"
    ],
    "content": {
        "text": "In case you don\u2019t read my Twitter: I\u2019ve decided to stop syndicating my posts there for a while. I think it simply becomes annoying for me to handle. I\u2019ll use it to read, and maybe to reply sometimes, but I\u2019m gonna shitpost on my own website like a proper #IndieWeb adopter.",
        "html": "<p>In case you don\u2019t read my Twitter: I\u2019ve decided to stop syndicating my posts there for a while. I think it simply becomes annoying for me to handle. I\u2019ll use it to read, and maybe to reply sometimes, but I\u2019m gonna shitpost on my own website like a proper #IndieWeb adopter.</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": "20079427",
    "_source": "1371",
    "_is_read": true
}

Publish untappd check-ins to micro.blog

{
    "type": "entry",
    "author": {
        "name": "Kh\u00fcrt Williams",
        "url": "https://islandinthenet.com/",
        "photo": null
    },
    "url": "https://islandinthenet.com/publish-untappd-check-ins-to-micro-blog/",
    "published": "2021-04-27T10:50:46-04:00",
    "content": {
        "html": "<img src=\"https://i0.wp.com/islandinthenet.com/wp-content/uploads/2021/04/Screen-Shot-2021-04-27-at-10.34.24-AM.jpeg?fit=891%2C892&amp;quality=100&amp;ssl=1\" alt=\"screen shot from Zapier\" /><p>Carl Rustung wrote his original post, <a href=\"https://carlrustung.no/blog/insta-zapier-howto/\">Zapping Instagram pics to micro.blog</a> on Wed. January 30th, 2019. I wanted my Untappd check-ins automatically posted to my micro.blog. With some trial and error, I was able to tweak his Zap to do it for me.</p>\n<p>Here\u2019s how:</p>\n<ul><li>Set up a new <a href=\"https://micro.blog/account/apps\">access token</a> for Zapier in your micro.blog account settings.</li>\n<li>Make a new Zap. Choose Untappd for your Trigger App and trigger the zap on \u201cNew Check-In\u201d.</li>\n<li>Connect your Untappd account.</li>\n<li>Select a sample post.</li>\n<li>Add \u201cWebhooks\u201d for your Action step, and select the POST request.</li>\n</ul><img src=\"https://i0.wp.com/islandinthenet.com/wp-content/uploads/2021/04/Screen-Shot-2021-04-27-at-10.40.00-AM.jpeg?resize=888%2C368&amp;quality=100&amp;ssl=1\" alt=\"Zapier screen shot\" />Add \u201cWebhooks\u201d for your Action step, and select the POST request.<ul><li>Use <a href=\"https://micro.blog/micropub\">micro.blog/micropub</a> as the URL and \u201cForm\u201d as the Payload Type</li>\n<li>Under Data, you\u2019re going to need 4 key-value pairs:</li>\n<li>\n<ul><li>h: entry (literally, write \u201centry\u201d)</li>\n</ul></li>\n<li>\n<ul><li>access_token: [your access token from step 1]</li>\n</ul></li>\n</ul><img src=\"https://i0.wp.com/islandinthenet.com/wp-content/uploads/2021/04/Screen-Shot-2021-04-27-at-10.34.24-AM.jpeg?resize=891%2C892&amp;quality=100&amp;ssl=1\" alt=\"screen shot from Zapier\" />Use the Zapier tokens to create the content you want<ul><li>content: Use the Zapier tokens to create the content you want. I used the following.</li>\n</ul><pre><code><br />&lt;p&gt;&lt;a href=\"https://untappd.com/user/khurtwilliams/checkin/{{110699014__checkin_id}}\"&gt;{{110699014__beer__beer_name}}&lt;/a&gt; ({{110699014__beer__beer_abv}}% ABV {{110699014__beer__beer_style}}) by &lt;a href=\"https://untappd.com/{{110699014__brewery__brewery_page_url}}\" /&gt;{{110699014__brewery__brewery_name}}&lt;/a&gt; ({{110699014__brewery__location__brewery_city}}, {{110699014__brewery__location__brewery_state}}). Rating:{{110699014__rating_score}}/5&lt;/p&gt;\n\n\n&lt;p&gt;{{110699014__checkin_comment}}&lt;/p&gt;\n\n\n&lt;p&gt;&lt;figure&gt;&lt;img src=\"{{110699014__media__items[]photo__photo_img_og}}\" alt=\"{{110699014__beer__beer_name}}\" /&gt;&lt;figcaption&gt;{{110699014__beer__beer_name}}&lt;/figcaption&gt;&lt;/figure&gt;&lt;/p&gt;\n\n\n</code></pre>\n<ul><li>Leave the rest of the inputs alone, and click Continue.</li>\n<li>Click the \u201cSend Test\u2026\u201d-button, and your sample Untappd post should appear on your micro.blog timeline.</li>\n</ul><p>You can see examples of this in my <a href=\"https://khurt.blog/categories/beer\">beer category. page</a> on micro.blog.</p>",
        "text": "Carl Rustung wrote his original post, Zapping Instagram pics to micro.blog on Wed. January 30th, 2019. I wanted my Untappd check-ins automatically posted to my micro.blog. With some trial and error, I was able to tweak his Zap to do it for me.\nHere\u2019s how:\nSet up a new access token for Zapier in your micro.blog account settings.\nMake a new Zap. Choose Untappd for your Trigger App and trigger the zap on \u201cNew Check-In\u201d.\nConnect your Untappd account.\nSelect a sample post.\nAdd \u201cWebhooks\u201d for your Action step, and select the POST request.\nAdd \u201cWebhooks\u201d for your Action step, and select the POST request.Use micro.blog/micropub as the URL and \u201cForm\u201d as the Payload Type\nUnder Data, you\u2019re going to need 4 key-value pairs:\n\nh: entry (literally, write \u201centry\u201d)\n\n\naccess_token: [your access token from step 1]\n\nUse the Zapier tokens to create the content you wantcontent: Use the Zapier tokens to create the content you want. I used the following.\n\n<p><a href=\"https://untappd.com/user/khurtwilliams/checkin/{{110699014__checkin_id}}\">{{110699014__beer__beer_name}}</a> ({{110699014__beer__beer_abv}}% ABV {{110699014__beer__beer_style}}) by <a href=\"https://untappd.com/{{110699014__brewery__brewery_page_url}}\" />{{110699014__brewery__brewery_name}}</a> ({{110699014__brewery__location__brewery_city}}, {{110699014__brewery__location__brewery_state}}). Rating:{{110699014__rating_score}}/5</p>\n\n\n<p>{{110699014__checkin_comment}}</p>\n\n\n<p><figure><img src=\"{{110699014__media__items[]photo__photo_img_og}}\" alt=\"{{110699014__beer__beer_name}}\" /><figcaption>{{110699014__beer__beer_name}}</figcaption></figure></p>\n\n\n\nLeave the rest of the inputs alone, and click Continue.\nClick the \u201cSend Test\u2026\u201d-button, and your sample Untappd post should appear on your micro.blog timeline.\nYou can see examples of this in my beer category. page on micro.blog."
    },
    "name": "Publish untappd check-ins to micro.blog",
    "post-type": "article",
    "_id": "20072444",
    "_source": "242",
    "_is_read": true
}

Chris Aldrich stream.boffosocko.com/profile/chrisaldrich

{
    "type": "entry",
    "published": "2021-04-27T16:41:24+00:00",
    "url": "http://stream.boffosocko.com/2021/biswassholanki-ive-wanted-to-try-out-ghost-but-this-part",
    "syndication": [
        "https://twitter.com/ChrisAldrich/status/1387084741657178115"
    ],
    "in-reply-to": [
        "https://twitter.com/BiswasSholanki/status/1386937046468419584",
        "https://shobiz.hashnode.dev/webmentions-in-ghost-and-the-challenges-that-i-faced"
    ],
    "content": {
        "text": "@BiswasSholanki I've wanted to try out Ghost, but this part has been a blocker. https://indieweb.org/webmention.js might be a place to look for some inspiration. I'd invite you to join us for this upcoming event which will certainly touch on your topic: https://events.indieweb.org/2021/05/webmentions-beyond-webmention-io-zG4JpHhZShVA",
        "html": "@BiswasSholanki I've wanted to try out Ghost, but this part has been a blocker. <a href=\"https://indieweb.org/webmention.js\">https://indieweb.org/webmention.js</a> might be a place to look for some inspiration. I'd invite you to join us for this upcoming event which will certainly touch on your topic: <a href=\"https://events.indieweb.org/2021/05/webmentions-beyond-webmention-io-zG4JpHhZShVA\">https://events.indieweb.org/2021/05/webmentions-beyond-webmention-io-zG4JpHhZShVA</a>"
    },
    "author": {
        "type": "card",
        "name": "Chris Aldrich",
        "url": "http://stream.boffosocko.com/profile/chrisaldrich",
        "photo": "http://stream.boffosocko.com/file/600427b81f7785e704eadfe511a9270f/thumb.jpg"
    },
    "post-type": "reply",
    "_id": "20069366",
    "_source": "192",
    "_is_read": true
}

Chris Aldrich stream.boffosocko.com/profile/chrisaldrich

{
    "type": "entry",
    "published": "2021-04-25T22:35:55+00:00",
    "url": "http://stream.boffosocko.com/2021/sillygwailo-until-there-are-consuming-use-cases-for-it-its",
    "syndication": [
        "https://twitter.com/ChrisAldrich/status/1386449077072711680"
    ],
    "in-reply-to": [
        "https://twitter.com/sillygwailo/status/1386416291502645249"
    ],
    "content": {
        "text": "@sillygwailo Until there are consuming use cases for it, it's not relevant, but basic text with `h-product` and a `dt-published` for first dose datetime and `dt-updated` for subsequent boosters might make sense based on existing work? See: https://microformats.org/wiki/process",
        "html": "<a href=\"https://twitter.com/sillygwailo\">@sillygwailo</a> Until there are consuming use cases for it, it's not relevant, but basic text with `h-product` and a `dt-published` for first dose datetime and `dt-updated` for subsequent boosters might make sense based on existing work? See: <a href=\"https://microformats.org/wiki/process\">https://microformats.org/wiki/process</a>"
    },
    "author": {
        "type": "card",
        "name": "Chris Aldrich",
        "url": "http://stream.boffosocko.com/profile/chrisaldrich",
        "photo": "http://stream.boffosocko.com/file/600427b81f7785e704eadfe511a9270f/thumb.jpg"
    },
    "post-type": "reply",
    "_id": "20030535",
    "_source": "192",
    "_is_read": true
}

Chris Aldrich stream.boffosocko.com/profile/chrisaldrich

{
    "type": "entry",
    "published": "2021-04-24T18:38:31+00:00",
    "url": "http://stream.boffosocko.com/2021/andrejaenisch-sonke-ahrens-book-how-to-take-smart-notes-about",
    "syndication": [
        "https://twitter.com/ChrisAldrich/status/1386027365738762242"
    ],
    "in-reply-to": [
        "https://twitter.com/AndreJaenisch/status/1385861818975981569"
    ],
    "content": {
        "text": "@AndreJaenisch Sonke Ahrens' book How to Take Smart Notes about Luhmann's method is very solid (https://bookshop.org/a/17195/9781542866507). Lots of systems out there to implement it. I like @obsdmd, but other platforms listed here: https://indieweb.org/commonplace_book",
        "html": "<a href=\"https://twitter.com/AndreJaenisch\">@AndreJaenisch</a> Sonke Ahrens' book How to Take Smart Notes about Luhmann's method is very solid (<a href=\"https://bookshop.org/a/17195/9781542866507\">https://bookshop.org/a/17195/9781542866507</a>). Lots of systems out there to implement it. I like <a href=\"https://twitter.com/obsdmd\">@obsdmd</a>, but other platforms listed here: <a href=\"https://indieweb.org/commonplace_book\">https://indieweb.org/commonplace_book</a>"
    },
    "author": {
        "type": "card",
        "name": "Chris Aldrich",
        "url": "http://stream.boffosocko.com/profile/chrisaldrich",
        "photo": "http://stream.boffosocko.com/file/600427b81f7785e704eadfe511a9270f/thumb.jpg"
    },
    "post-type": "reply",
    "_id": "20007548",
    "_source": "192",
    "_is_read": true
}

Jeremy Keith adactio.com

{
    "type": "entry",
    "published": "2021-04-23T10:09:33Z",
    "url": "https://adactio.com/links/18059",
    "category": [
        "indieweb",
        "personal",
        "publishing",
        "words",
        "writing",
        "sharing",
        "music",
        "piano"
    ],
    "bookmark-of": [
        "https://matthiasott.com/notes/no-wrong-notes"
    ],
    "content": {
        "text": "No Wrong Notes \u00b7 Matthias Ott \u2013 User Experience Designer\n\n\n\n\n  A personal website ain\u2019t got no wrong words.",
        "html": "<h3>\n<a class=\"p-name u-bookmark-of\" href=\"https://matthiasott.com/notes/no-wrong-notes\">\nNo Wrong Notes \u00b7 Matthias Ott \u2013 User Experience Designer\n</a>\n</h3>\n\n<blockquote>\n  <p>A personal website ain\u2019t got no wrong words.</p>\n</blockquote>"
    },
    "author": {
        "type": "card",
        "name": "Jeremy Keith",
        "url": "https://adactio.com/",
        "photo": "https://adactio.com/images/photo-150.jpg"
    },
    "post-type": "bookmark",
    "_id": "19971897",
    "_source": "2",
    "_is_read": true
}

Marty McGuire martymcgui.re

{
    "type": "entry",
    "published": "2021-04-19T11:39:07-0400",
    "rsvp": "yes",
    "url": "https://martymcgui.re/2021/04/19/113907/",
    "in-reply-to": [
        "https://events.indieweb.org/2021/05/webmentions-beyond-webmention-io-zG4JpHhZShVA"
    ],
    "content": {
        "text": "I'm going!Looking forward to this IndieWeb Popup! Despite my occasional salty-sounding post about Webmention I am very optimistic about their power as a tool for the web.",
        "html": "I'm going!<p>Looking forward to this IndieWeb Popup! Despite my occasional <a href=\"https://martymcgui.re/2020/07/15/what-we-talk-about-when-were-talking-about-webmentions/\">salty-sounding post about Webmention</a> I am very optimistic about their power as a tool for the web.</p>"
    },
    "author": {
        "type": "card",
        "name": "Marty McGuire",
        "url": "https://martymcgui.re/",
        "photo": "https://martymcgui.re/images/logo.jpg"
    },
    "post-type": "rsvp",
    "refs": {
        "https://events.indieweb.org/2021/05/webmentions-beyond-webmention-io-zG4JpHhZShVA": {
            "type": "entry",
            "summary": "Webmentions haven't really been revisited in some time (and with the advent of people leaning to Webmention.io). This is a chance to see what's been really wanted, what hasn't worked and where we can go with it.",
            "url": "https://events.indieweb.org/2021/05/webmentions-beyond-webmention-io-zG4JpHhZShVA",
            "name": "Webmentions Beyond Webmention.io",
            "author": {
                "type": "card",
                "name": "events.indieweb.org",
                "url": "http://events.indieweb.org",
                "photo": null
            },
            "post-type": "article"
        }
    },
    "_id": "19894123",
    "_source": "175",
    "_is_read": true
}

Manton Reece www.manton.org

How does Micro.blog even work?

{
    "type": "entry",
    "author": {
        "name": "Manton Reece",
        "url": "https://www.manton.org/",
        "photo": "https://micro.blog/manton/avatar.jpg"
    },
    "url": "https://www.manton.org/2021/04/19/how-does-microblog.html",
    "name": "How does Micro.blog even work?",
    "content": {
        "html": "<p>I\u2019ve been upgrading servers and improving performance in Micro.blog lately, a theme which will continue throughout the year to make everything as stable as possible. Sometimes this introduces new bugs or weird behavior that makes people scratch their heads. What is Micro.blog even doing? So let\u2019s look a little at the architecture.</p>\n\n<p>When you write a new post, Micro.blog saves it into a MySQL database. We currently run 2 database servers, so that we can spread some queries between them and to make backups easier. But unlike many web apps, we do not serve blogs from this database. Blogs are published to a separate server as static HTML and images, served directly by Nginx with few or no dependencies on the rest of Micro.blog. This makes your blog very fast, and means that major parts of Micro.blog can go down without affecting your blog.</p>\n\n<p>This has been a key design goal from the very beginning of Micro.blog. We host a blog for you, but it can have its own domain name and is only loosely tied to the rest of Micro.blog. This goal meant discarding some common architectures such as dynamically generating the blog when pages are requested.</p>\n\n<p>Micro.blog is really 3 separate systems combined into a single platform: a blog admin interface, a blog hosting service, and a Twitter-like timeline.</p>\n\n<p>To achieve this, Micro.blog has to translate the blog posts from Markdown to HTML. It runs all the text through <a href=\"https://gohugo.io\">Hugo</a>. It also has to put photos and podcasts in the right place. When you upload a file, Micro.blog copies it to an object storage server at the same time that it syncs the file to your blog.</p>\n\n<p>Timeline web requests and background tasks are run across a few servers, so that we can balance load and deal with outages. While Hugo wants all your Markdown and photos in a specific structure in the file system, Micro.blog maintains content in separate databases and then writes it out to the format that Hugo wants for processing.</p>\n\n<p>Any given server could have part of your content or none of it yet, so Micro.blog will have to sync everything up. It does this in multiple phases to make publishing as fast as possible, and this is the area that I\u2019ve been spending a lot of time tweaking.</p>\n\n<p>First, Micro.blog attempts to quickly publish your latest post, so that it\u2019s available at the permalink URL and included in the blog feed. If you have thousands of posts, it ignores most of them during this phase. It just wants to get your post up on the web as quickly as possible and added to the Micro.blog timeline.</p>\n\n<p>Whenever Micro.blog is processing posts, it also applies any custom themes for your blog. It never skips the Hugo step, even if your blog post content is so simple that it could be previewed with a separate Markdown filter. Every post is run through Hugo, added to the RSS or JSON Feed, and only then processed into the Micro.blog timeline.</p>\n\n<p>This round-trip journey your content takes is an important part of how Micro.blog works with external blog feeds like WordPress. We aren\u2019t interested in building a proprietary social network that is not rooted in blogs. The timeline works with blogs no matter where they are hosted.</p>\n\n<p>Next, Micro.blog will do a full publish of your blog, with the entire site, categories, photo pages, and archive. In some cases, it will combine the Markdown with any uploaded photos before processing them, but usually the uploads are already on your blog. It also keeps a copy of all the Markdown files, independent on any of the web servers, so that if possible it can update those versions without writing out potentially thousands of posts to the file system.</p>\n\n<p>This phase of publishing is the longest, although it\u2019s faster now than it has ever been. During this phase, your latest post should already be live and the timeline updated, so it\u2019s not as annoying to wait around for the archive or category pages to update.</p>\n\n<p>I\u2019m exposing more of what Micro.blog is doing behind the scenes in the <a href=\"https://micro.blog/account/logs\">logs for your account</a>. Here\u2019s a snippet from my log recently, although I\u2019ve flipped it so that it reads in chronology order instead of newest at top:</p>\n\n<pre>\n2021-04-11 16:54:25: Publish: Not queued, publishing manton\n<i>2021-04-11 16:54:25: Publish: Initial prepare for manton</i>\n2021-04-11 16:54:25: Publish: Preparing pages for manton\n2021-04-11 16:54:25: Publish: Persistent folder exists, updating for manton\n<i>2021-04-11 16:54:25: Publish: Initial posts for manton</i>\n2021-04-11 16:54:26: Publish: Linking shared content files for manton\n2021-04-11 16:54:26: Publish: Running Hugo for manton\n<i>2021-04-11 16:54:26: Publish: Initial Hugo run for manton</i>\n<i>2021-04-11 16:54:26: Publish: Initial sync for manton</i>\n<i>2021-04-11 16:54:26: Publish: Pinging manton, progress: 0.866 seconds</i>\n</pre>\n\n<p>Here, there are actually 2 overlapping background tasks. The lines with \u201cInitial\u201d (italicized above) are part of this first phase of quickly publishing your post. In this case, the round-trip from saving the content, publishing the feed, and then updating the timeline was about 1 second. Under a few seconds is kind of the gold standard we\u2019re aiming for.</p>\n\n<p>Finally, Micro.blog assembles the timeline so that it can be served quickly no matter how many people you are following. We have a Redis server that keeps the timeline for each user in a sorted set, and use that from the Micro.blog API to page between posts. Micro.blog also processes posts for @-mentions, sending Webmentions, auto-linking URLs, and other details that are beyond what I wanted to write about here.</p>\n\n<p>Could this be even better? Yes. But while I\u2019m sometimes tempted to change the architecture to something closer to WordPress\u2019s model, I know there\u2019s always more performance we can squeeze out of our current setup.</p>",
        "text": "I\u2019ve been upgrading servers and improving performance in Micro.blog lately, a theme which will continue throughout the year to make everything as stable as possible. Sometimes this introduces new bugs or weird behavior that makes people scratch their heads. What is Micro.blog even doing? So let\u2019s look a little at the architecture.\n\nWhen you write a new post, Micro.blog saves it into a MySQL database. We currently run 2 database servers, so that we can spread some queries between them and to make backups easier. But unlike many web apps, we do not serve blogs from this database. Blogs are published to a separate server as static HTML and images, served directly by Nginx with few or no dependencies on the rest of Micro.blog. This makes your blog very fast, and means that major parts of Micro.blog can go down without affecting your blog.\n\nThis has been a key design goal from the very beginning of Micro.blog. We host a blog for you, but it can have its own domain name and is only loosely tied to the rest of Micro.blog. This goal meant discarding some common architectures such as dynamically generating the blog when pages are requested.\n\nMicro.blog is really 3 separate systems combined into a single platform: a blog admin interface, a blog hosting service, and a Twitter-like timeline.\n\nTo achieve this, Micro.blog has to translate the blog posts from Markdown to HTML. It runs all the text through Hugo. It also has to put photos and podcasts in the right place. When you upload a file, Micro.blog copies it to an object storage server at the same time that it syncs the file to your blog.\n\nTimeline web requests and background tasks are run across a few servers, so that we can balance load and deal with outages. While Hugo wants all your Markdown and photos in a specific structure in the file system, Micro.blog maintains content in separate databases and then writes it out to the format that Hugo wants for processing.\n\nAny given server could have part of your content or none of it yet, so Micro.blog will have to sync everything up. It does this in multiple phases to make publishing as fast as possible, and this is the area that I\u2019ve been spending a lot of time tweaking.\n\nFirst, Micro.blog attempts to quickly publish your latest post, so that it\u2019s available at the permalink URL and included in the blog feed. If you have thousands of posts, it ignores most of them during this phase. It just wants to get your post up on the web as quickly as possible and added to the Micro.blog timeline.\n\nWhenever Micro.blog is processing posts, it also applies any custom themes for your blog. It never skips the Hugo step, even if your blog post content is so simple that it could be previewed with a separate Markdown filter. Every post is run through Hugo, added to the RSS or JSON Feed, and only then processed into the Micro.blog timeline.\n\nThis round-trip journey your content takes is an important part of how Micro.blog works with external blog feeds like WordPress. We aren\u2019t interested in building a proprietary social network that is not rooted in blogs. The timeline works with blogs no matter where they are hosted.\n\nNext, Micro.blog will do a full publish of your blog, with the entire site, categories, photo pages, and archive. In some cases, it will combine the Markdown with any uploaded photos before processing them, but usually the uploads are already on your blog. It also keeps a copy of all the Markdown files, independent on any of the web servers, so that if possible it can update those versions without writing out potentially thousands of posts to the file system.\n\nThis phase of publishing is the longest, although it\u2019s faster now than it has ever been. During this phase, your latest post should already be live and the timeline updated, so it\u2019s not as annoying to wait around for the archive or category pages to update.\n\nI\u2019m exposing more of what Micro.blog is doing behind the scenes in the logs for your account. Here\u2019s a snippet from my log recently, although I\u2019ve flipped it so that it reads in chronology order instead of newest at top:\n\n\n2021-04-11 16:54:25: Publish: Not queued, publishing manton\n2021-04-11 16:54:25: Publish: Initial prepare for manton\n2021-04-11 16:54:25: Publish: Preparing pages for manton\n2021-04-11 16:54:25: Publish: Persistent folder exists, updating for manton\n2021-04-11 16:54:25: Publish: Initial posts for manton\n2021-04-11 16:54:26: Publish: Linking shared content files for manton\n2021-04-11 16:54:26: Publish: Running Hugo for manton\n2021-04-11 16:54:26: Publish: Initial Hugo run for manton\n2021-04-11 16:54:26: Publish: Initial sync for manton\n2021-04-11 16:54:26: Publish: Pinging manton, progress: 0.866 seconds\n\n\nHere, there are actually 2 overlapping background tasks. The lines with \u201cInitial\u201d (italicized above) are part of this first phase of quickly publishing your post. In this case, the round-trip from saving the content, publishing the feed, and then updating the timeline was about 1 second. Under a few seconds is kind of the gold standard we\u2019re aiming for.\n\nFinally, Micro.blog assembles the timeline so that it can be served quickly no matter how many people you are following. We have a Redis server that keeps the timeline for each user in a sorted set, and use that from the Micro.blog API to page between posts. Micro.blog also processes posts for @-mentions, sending Webmentions, auto-linking URLs, and other details that are beyond what I wanted to write about here.\n\nCould this be even better? Yes. But while I\u2019m sometimes tempted to change the architecture to something closer to WordPress\u2019s model, I know there\u2019s always more performance we can squeeze out of our current setup."
    },
    "published": "2021-04-19T09:57:09-05:00",
    "category": [
        "Essays"
    ],
    "post-type": "article",
    "_id": "19892290",
    "_source": "12",
    "_is_read": true
}

Jeremy Keith adactio.com

{
    "type": "entry",
    "published": "2021-04-19T09:53:59Z",
    "url": "https://adactio.com/links/18034",
    "category": [
        "css",
        "custom",
        "properties",
        "theming",
        "naming",
        "webcomponents",
        "conventions",
        "styling",
        "frontend",
        "development"
    ],
    "bookmark-of": [
        "https://github.com/castastrophe/wc-theming-standards/wiki"
    ],
    "content": {
        "text": "Home \u00b7 castastrophe/wc-theming-standards Wiki\n\n\n\nI really like the idea of a shared convention for styling web components with custom properties\u2014feels like BEM meets microformats.",
        "html": "<h3>\n<a class=\"p-name u-bookmark-of\" href=\"https://github.com/castastrophe/wc-theming-standards/wiki\">\nHome \u00b7 castastrophe/wc-theming-standards Wiki\n</a>\n</h3>\n\n<p>I really like the idea of a shared convention for styling web components with custom properties\u2014feels like BEM meets microformats.</p>"
    },
    "author": {
        "type": "card",
        "name": "Jeremy Keith",
        "url": "https://adactio.com/",
        "photo": "https://adactio.com/images/photo-150.jpg"
    },
    "post-type": "bookmark",
    "_id": "19886084",
    "_source": "2",
    "_is_read": true
}

fluffy rambles: Shoulder, unpacking, gardening, etc.

{
    "type": "entry",
    "author": {
        "name": "fluffy",
        "url": "http://beesbuzz.biz/",
        "photo": null
    },
    "url": "http://beesbuzz.biz/blog/9665-Shoulder-unpacking-gardening-etc",
    "published": "2021-04-16T21:28:23-07:00",
    "content": {
        "html": "<p>Wellp, I managed to screw up my shoulder again. <a href=\"http://beesbuzz.biz/blog/6013-Another-pain-another-frustration\">Last time</a> was probably from me using my cane on a fairly long walk, and this time was probably due to me overdoing it with my <a href=\"https://amzn.to/2Qxv65U\">weed puller</a> (which requires a snapping motion that does similar things to my cane). Bleah. At least this time I know stretches and things that might help, and I found <a href=\"https://www.youtube.com/watch?v=q5SsM9PWWYc\">a bunch more</a> which feel like they\u2019re helping. Hopefully I\u2019ll still feel well enough to get my second shot of vaccine tomorrow. (Which will probably have me feeling pretty much immobile for a few days anyway.)</p>\n\n\n<p>I\u2019ve sort of stalled on unpacking, and I haven\u2019t found my Wacom tablet yet. I really want to work on comics though. Maybe I\u2019ll give <a href=\"https://www.macrumors.com/guide/sidecar/\">Sidecar</a> another shot. Although with my shoulder pain I don\u2019t think holding a stylus is a good idea at all right now.</p><p>I\u2019ve also been pretty unmotivated to work on music. I\u2019ve had my usual every-day-a-new-song-scrap thing happen but I\u2019m in a sort of quiescent period when it comes to actually doing more. Mostly because all of my music stuff is down in the basement and I don\u2019t feel like going through the hassle of setting up a recording environment right now and I feel like just like\u2026 waiting until the condo sells and I can build a proper studio.</p><p>And on that note, the condo is off the market temporarily, for Reasons not worth getting into. It\u2019ll hopefully be relisted sometime next week, probably at a lower price (i.e. where I wanted to list it in the first place), so maybe there\u2019ll be a better chance of it selling soon.</p><p>In happier news, we\u2019ve finally managed to hire a manager for my team. She doesn\u2019t start until June, though. But still, having some actual direction will be nice.</p><p>Also at work I gave a talk on IndieWeb which went over really well. I hope I can get more folks interested in it, and maybe I can eventually parlay this into becoming an IndieWeb advocate/developer/whatever. I can dream, anyway.</p><p>Oh and the weed puller arrived on the same day as my <a href=\"https://amzn.to/3ssdN3s\">composter</a>, which is now full of weeds and kitchen scraps and hopefully in a few weeks I\u2019ll have come nice compost to fill my <a href=\"https://www.homedepot.com/p/Greenes-Fence-2-ft-x-4-ft-x-10-5-in-Original-Pine-Raised-Garden-Bed-RCP24484T/315634141\">raised beds</a> with! I feel like playing hundreds of hours of Animal Crossing has prepared me for this. (And also with the random interactions with my neighbors, who continue to be people I\u2019m glad to live near.)</p><p>The raised beds arrive next week, and I\u2019m going to try the <a href=\"https://dengarden.com/gardening/How-to-Make-a-Raised-Bed-Lasagna-Garden\">lasagna method</a> to fill them. Fortunately I still have a lot of paper and cardboard left over from the move!</p>\n\n<p><a href=\"http://beesbuzz.biz/blog/9665-Shoulder-unpacking-gardening-etc#comments\">comments</a></p>",
        "text": "Wellp, I managed to screw up my shoulder again. Last time was probably from me using my cane on a fairly long walk, and this time was probably due to me overdoing it with my weed puller (which requires a snapping motion that does similar things to my cane). Bleah. At least this time I know stretches and things that might help, and I found a bunch more which feel like they\u2019re helping. Hopefully I\u2019ll still feel well enough to get my second shot of vaccine tomorrow. (Which will probably have me feeling pretty much immobile for a few days anyway.)\n\n\nI\u2019ve sort of stalled on unpacking, and I haven\u2019t found my Wacom tablet yet. I really want to work on comics though. Maybe I\u2019ll give Sidecar another shot. Although with my shoulder pain I don\u2019t think holding a stylus is a good idea at all right now.I\u2019ve also been pretty unmotivated to work on music. I\u2019ve had my usual every-day-a-new-song-scrap thing happen but I\u2019m in a sort of quiescent period when it comes to actually doing more. Mostly because all of my music stuff is down in the basement and I don\u2019t feel like going through the hassle of setting up a recording environment right now and I feel like just like\u2026 waiting until the condo sells and I can build a proper studio.And on that note, the condo is off the market temporarily, for Reasons not worth getting into. It\u2019ll hopefully be relisted sometime next week, probably at a lower price (i.e. where I wanted to list it in the first place), so maybe there\u2019ll be a better chance of it selling soon.In happier news, we\u2019ve finally managed to hire a manager for my team. She doesn\u2019t start until June, though. But still, having some actual direction will be nice.Also at work I gave a talk on IndieWeb which went over really well. I hope I can get more folks interested in it, and maybe I can eventually parlay this into becoming an IndieWeb advocate/developer/whatever. I can dream, anyway.Oh and the weed puller arrived on the same day as my composter, which is now full of weeds and kitchen scraps and hopefully in a few weeks I\u2019ll have come nice compost to fill my raised beds with! I feel like playing hundreds of hours of Animal Crossing has prepared me for this. (And also with the random interactions with my neighbors, who continue to be people I\u2019m glad to live near.)The raised beds arrive next week, and I\u2019m going to try the lasagna method to fill them. Fortunately I still have a lot of paper and cardboard left over from the move!\n\ncomments"
    },
    "name": "fluffy rambles: Shoulder, unpacking, gardening, etc.",
    "post-type": "article",
    "_id": "19840606",
    "_source": "3782",
    "_is_read": true
}

Chris Aldrich stream.boffosocko.com/profile/chrisaldrich

{
    "type": "entry",
    "published": "2021-04-16T06:15:06+00:00",
    "url": "http://stream.boffosocko.com/2021/jaybearca-the-webmention-plugin-only-does-notifications-you-also-need",
    "syndication": [
        "https://twitter.com/ChrisAldrich/status/1382941111975620610"
    ],
    "in-reply-to": [
        "https://jaybear.ca/14670/",
        "https://twitter.com/jaybearca/status/1382924534819393536"
    ],
    "content": {
        "text": "@jaybearca The Webmention plugin only does notifications. You also need the semantic linkbacks plugin for the parser which will give you the richer data you're looking for. \nhttps://wordpress.org/plugins/semantic-linkbacks/",
        "html": "@jaybearca The Webmention plugin only does notifications. You also need the semantic linkbacks plugin for the parser which will give you the richer data you're looking for. <br /><a href=\"https://wordpress.org/plugins/semantic-linkbacks/\">https://wordpress.org/plugins/semantic-linkbacks/</a><br /><br />"
    },
    "author": {
        "type": "card",
        "name": "Chris Aldrich",
        "url": "http://stream.boffosocko.com/profile/chrisaldrich",
        "photo": "http://stream.boffosocko.com/file/600427b81f7785e704eadfe511a9270f/thumb.jpg"
    },
    "post-type": "reply",
    "_id": "19815531",
    "_source": "192",
    "_is_read": true
}

Manton Reece www.manton.org

Micro.blog RSVPs with Webmention

{
    "type": "entry",
    "author": {
        "name": "Manton Reece",
        "url": "https://www.manton.org/",
        "photo": "https://micro.blog/manton/avatar.jpg"
    },
    "url": "https://www.manton.org/2021/04/15/microblog-rsvps-with.html",
    "name": "Micro.blog RSVPs with Webmention",
    "content": {
        "html": "<p>Micro.blog sends Webmentions to external blogs when you \u201creply\u201d to a post inside Micro.blog. It marks up your reply with Microformats, discovers the Webmention endpoint for the post you\u2019re replying to, and sends the Webmention. This allows your Micro.blog replies to be included as comments on blogs hosted by other platforms, like WordPress.</p>\n\n<p><a href=\"https://indieweb.org/rsvp\">An RSVP</a> is a special type of reply used to indicate whether you\u2019re attending an event. By posting RSVPs to your own blog, you can attach them to existing posts or just have your own copy of the data. As more bloggers use RSVPs, we could eventually have a more distributed, IndieWeb-friendly system instead of relying on Facebook or Evite.</p>\n\n<p>How to create an RSVP on Micro.blog? We don\u2019t currently have an RSVP button in Micro.blog, because Webmention-enabled events are still rare enough that it would take up a lot of the Micro.blog UI, potentially cluttering the interface.</p>\n\n<p>You\u2019ll need a little bit of HTML to create an RSVP. First, add a link to where you want to send the Webmention. Instead of using Markdown for the link, use HTML and add the Microformats <code>class=\"u-in-reply-to\"</code> to mark the link as a reply to another URL:</p>\n\n<pre><code>Looking forward to this &lt;a href=\"...\" class=\"u-in-reply-to\"&gt;Webmentions pop-up session&lt;/a&gt; next month.\n</code></pre>\n\n<p>Then, to make this an RSVP, add a <code>data</code> tag somewhere in the post with \u201cyes\u201d, \u201cmaybe\u201d, or \u201cno\u201d:</p>\n\n<pre><code>&lt;data class=\"p-rsvp\" value=\"yes\" /&gt;\n</code></pre>\n\n<p>I like to use <code>data</code> because it\u2019s invisible when displayed in a web browser, but it could be a <code>span</code> or other HTML tag. You can see a full example of this if you view the HTML source of <a href=\"https://www.manton.org/2021/04/13/looking-forward-to.html\">my post here</a>, RSVP-ing to an IndieWeb online event.</p>\n\n<p>When you publish the post, Micro.blog will automatically notice the <code>u-in-reply-to</code>, find the Webmention endpoint for the post you\u2019re linking to, and send the Webmention for you. Micro.blog themes also handle the other details, like including your name and profile photo.</p>",
        "text": "Micro.blog sends Webmentions to external blogs when you \u201creply\u201d to a post inside Micro.blog. It marks up your reply with Microformats, discovers the Webmention endpoint for the post you\u2019re replying to, and sends the Webmention. This allows your Micro.blog replies to be included as comments on blogs hosted by other platforms, like WordPress.\n\nAn RSVP is a special type of reply used to indicate whether you\u2019re attending an event. By posting RSVPs to your own blog, you can attach them to existing posts or just have your own copy of the data. As more bloggers use RSVPs, we could eventually have a more distributed, IndieWeb-friendly system instead of relying on Facebook or Evite.\n\nHow to create an RSVP on Micro.blog? We don\u2019t currently have an RSVP button in Micro.blog, because Webmention-enabled events are still rare enough that it would take up a lot of the Micro.blog UI, potentially cluttering the interface.\n\nYou\u2019ll need a little bit of HTML to create an RSVP. First, add a link to where you want to send the Webmention. Instead of using Markdown for the link, use HTML and add the Microformats class=\"u-in-reply-to\" to mark the link as a reply to another URL:\n\nLooking forward to this <a href=\"...\" class=\"u-in-reply-to\">Webmentions pop-up session</a> next month.\n\n\nThen, to make this an RSVP, add a data tag somewhere in the post with \u201cyes\u201d, \u201cmaybe\u201d, or \u201cno\u201d:\n\n<data class=\"p-rsvp\" value=\"yes\" />\n\n\nI like to use data because it\u2019s invisible when displayed in a web browser, but it could be a span or other HTML tag. You can see a full example of this if you view the HTML source of my post here, RSVP-ing to an IndieWeb online event.\n\nWhen you publish the post, Micro.blog will automatically notice the u-in-reply-to, find the Webmention endpoint for the post you\u2019re linking to, and send the Webmention for you. Micro.blog themes also handle the other details, like including your name and profile photo."
    },
    "published": "2021-04-15T16:37:14-05:00",
    "category": [
        "Essays"
    ],
    "post-type": "article",
    "_id": "19810307",
    "_source": "12",
    "_is_read": true
}

Aaron Parecki aaronparecki.com

How to Sign Users In with IndieAuth

{
    "type": "entry",
    "published": "2021-04-13T21:15:45-07:00",
    "summary": "This post will show you step by step how you can let people log in to your website with their own IndieAuth website so you don't need to worry about user accounts or passwords.",
    "url": "https://aaronparecki.com/2021/04/13/26/indieauth",
    "category": [
        "indieauth",
        "indieweb",
        "oauth"
    ],
    "syndication": [
        "https://micro.blog/aaronpk/11319738",
        "https://news.indieweb.org/en"
    ],
    "name": "How to Sign Users In with IndieAuth",
    "author": {
        "type": "card",
        "name": "Aaron Parecki",
        "url": "https://aaronparecki.com/",
        "photo": "https://aperture-media.p3k.io/aaronparecki.com/41061f9de825966faa22e9c42830e1d4a614a321213b4575b9488aa93f89817a.jpg"
    },
    "post-type": "article",
    "_id": "19758665",
    "_source": "16",
    "_is_read": true
}

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/2021/04/13/looking-forward-to.html",
    "content": {
        "html": "<p>Looking forward to this <a href=\"https://events.indieweb.org/2021/05/webmentions-beyond-webmention-io-zG4JpHhZShVA\" class=\"u-in-reply-to\">Webmentions pop-up session</a> next month. </p>",
        "text": "Looking forward to this Webmentions pop-up session next month."
    },
    "published": "2021-04-13T17:03:51-05:00",
    "post-type": "note",
    "_id": "19753877",
    "_source": "12",
    "_is_read": true
}

{
    "type": "entry",
    "url": "https://v2.jacky.wtf/post/5832bbcb-b152-49d8-bff2-d41997719210",
    "content": {
        "text": "In the midst of a re-write of how my site works and in passing conversation in the IndieWeb chat, I think about how to 'show' the IndieWeb as something people can invest in versus a collection of things that...",
        "html": "<p>In the midst of a re-write of how my site works and <a href=\"https://chat.indieweb.org/meta/2021-04-09#t1617992930428800\">in passing conversation in the IndieWeb chat</a>, I think about how to 'show' the IndieWeb as something people can invest in versus a collection of things that...</p>"
    },
    "post-type": "note",
    "_id": "19663685",
    "_source": "1886",
    "_is_read": true
}

{
    "type": "entry",
    "url": "https://v2.jacky.wtf/post/11e8c6f0-d513-4623-b167-502d764a9896",
    "content": {
        "text": "In the midst of a re-write of how my site works and in passing conversation in the IndieWeb chat, I think about how to 'show' the IndieWeb as something people can invest in versus a collection of things that...",
        "html": "<p>In the midst of a re-write of how my site works and <a href=\"https://chat.indieweb.org/meta/2021-04-09#t1617992930428800\">in passing conversation in the IndieWeb chat</a>, I think about how to 'show' the IndieWeb as something people can invest in versus a collection of things that...</p>"
    },
    "post-type": "note",
    "_id": "19663686",
    "_source": "1886",
    "_is_read": true
}

Ben Werdmüller werd.io/profile/benwerd

{
    "type": "entry",
    "published": "2021-04-09T16:21:07+00:00",
    "url": "https://werd.io/2021/turning-off-syndication-to-twitter-at-least",
    "content": {
        "text": "Turning off syndication to Twitter, at least for today. If you're reading this, it's via my indieweb feed on my Known site, or on Micro.blog."
    },
    "author": {
        "type": "card",
        "name": "Ben Werdm\u00fcller",
        "url": "https://werd.io/profile/benwerd",
        "photo": "https://werd.io/file/5d388c5fb16ea14aac640912/thumb.jpg"
    },
    "post-type": "note",
    "_id": "19658557",
    "_source": "191",
    "_is_read": true
}

Christopher Chelpka christopherchelpka.com

{
    "type": "entry",
    "author": {
        "name": "Christopher Chelpka",
        "url": "https://christopherchelpka.com",
        "photo": "https://www.gravatar.com/avatar/6298c8cd5b76684bd44569eadc18838c?s=96&d=https%3A%2F%2Fmicro.blog%2Fimages%2Fblank_avatar.png"
    },
    "url": "https://www.christopherchelpka.com/2021/04/06/now-that-you.html",
    "content": {
        "html": "<p>Now that you know why posting for \u201cfree\u201d on MySpaceBook isn\u2019t a good idea. Check out Micro.blog. I just paid for another year, again. Totally worth it. Micro.blog is the easy way to #indieweb.</p>",
        "text": "Now that you know why posting for \u201cfree\u201d on MySpaceBook isn\u2019t a good idea. Check out Micro.blog. I just paid for another year, again. Totally worth it. Micro.blog is the easy way to #indieweb."
    },
    "published": "2021-04-07T05:00:07+00:00",
    "post-type": "note",
    "_id": "33380025",
    "_source": "7224",
    "_is_read": true
}