IndieWeb

I've been thinking about how I want my site to work (and additionally how I'd like to share it with other people so they can get it running for their own use cases) over the last few weeks as I had my head down working on [Fortress](https://indieweb.org/Fortress). It's been some time (it'll be 5 years this October 17th!) since I've joined the IndieWeb - and began exploring more people-centric social networking systems in general so it's about time.

I’ve went from a Jekyll site to working on my newer site project. This is what cloc shows for the site currently:

     595 text files.
     583 unique files.
      55 files ignored.


github.com/AlDanial/cloc v 1.74  T=1.35 s (410.3 files/s, 48459.7 lines/s)
--------------------------------------------------------------------------------
Language                      files          blank        comment           code
--------------------------------------------------------------------------------
Elixir                          336           4509            552          22526
HTML                              2           6009              0          13872
JSON                             43              0              0          13300
EEx                              44              3              3           1265
liquid                           78             16              8           1166
Sass                             12            144             17            727
Vuejs Component                   5             12              7            264
YAML                              3             23             45            257
Bourne Shell                     17             82             19            225
JavaScript                        4             32              7            185
Cucumber                          4             20              0            107
PO File                           1             21             19             57
make                              4              8              0             32
Bourne Again Shell                1              1              0              2
CSS                               1              0              1              1
--------------------------------------------------------------------------------
SUM:                            555          10880            678          53986
--------------------------------------------------------------------------------

And now, to be honest, I’m thinking about blowing all of it away!

Hear me out - I’ve learned a lot about the IndieWeb by working on this and even more so about the general space of things and now I want to try out something different. Koype works as a ‘monolith’, it has the support for things like Webmentions, IndieAuth and what not. But currently, I haven’t given myself a lot of room to consider other things like templating or making it easy to extend. This is potentially an issue with the framework I chose to work on this project with but blaming the tools doesn’t really fix the problem.

As I’ve continued to work on my site, I’ve seen other projects from people grow and flourish. I envy the flexibility that others have as I kept rushing to cobble more features into my site without taking other parts of it seriously enough. I do have a plan though!

I want to see if I can refactor my site down to a point where it’s truly just a set of “parts”:

a flexible Micropub server
something like silo.pub to handle syndication
finishing up Lwa to act as a Webmention hub (as well as a WebSub hub, contacts manager, and mention feeds)
getting Fortress ready with AutoAuth and provisioning protected content (feeds, posts, etc)

I think that once the basis of the above is in place, I can think more on how I want to handle other things like actually showing the site. I really don’t want to go back to static site generation because the build times for Jekyll really frustrated me and was only justified when I was only writing like blog posts. Since I plan to have my website be my identity, place and hub on the Web, that doesn’t work for me anymore. By refactoring Koype down to just the Micropub server (with some extra kicks, of course), I can go and use the same file storage for content as the backing for a very thin server that can act as the ‘front-end’ for my site. Having two apps running to work as my site is a bit weird but it gives me a bit of power in decoupling how I work on my presentation layer of my site without worrying about breaking how things in the background.

I can imagine this sounding so complex but oddly enough, it’s a lot simpler than the general state of Web development (React! ‘Serverless’! Service Workers! oh my! Offload-all-of-the-work-on-client-devices-because-why-not!). I am excited to start working on this too because it’ll be a lot easier to make progress with things too.

v2.jacky.wtf/post/2186c978-eccc-4b80-b41f-c901aefe1640

{
    "type": "entry",
    "summary": "I've been thinking about how I want my site to work (and additionally how I'd like to share it with other people so they can get it running for their own use cases) over the last few weeks as I had my head down working on [Fortress](https://indieweb.org/Fortress). It's been some time (it'll be 5 years this October 17th!) since I've joined the IndieWeb - and began exploring more people-centric social networking systems in general so it's about time.",
    "url": "https://v2.jacky.wtf/post/2186c978-eccc-4b80-b41f-c901aefe1640",
    "content": {
        "text": "I've been thinking about how I want my site to work (and additionally how I'd like to share it with other people so they can get it running for their own use cases) over the last few weeks as I had my head down working on [Fortress](https://indieweb.org/Fortress). It's been some time (it'll be 5 years this October 17th!) since I've joined the IndieWeb - and began exploring more people-centric social networking systems in general so it's about time.I\u2019ve went from a Jekyll site to working on my newer site project. This is what cloc shows for the site currently:     595 text files.\n     583 unique files.\n      55 files ignored.\n\n\ngithub.com/AlDanial/cloc v 1.74  T=1.35 s (410.3 files/s, 48459.7 lines/s)\n--------------------------------------------------------------------------------\nLanguage                      files          blank        comment           code\n--------------------------------------------------------------------------------\nElixir                          336           4509            552          22526\nHTML                              2           6009              0          13872\nJSON                             43              0              0          13300\nEEx                              44              3              3           1265\nliquid                           78             16              8           1166\nSass                             12            144             17            727\nVuejs Component                   5             12              7            264\nYAML                              3             23             45            257\nBourne Shell                     17             82             19            225\nJavaScript                        4             32              7            185\nCucumber                          4             20              0            107\nPO File                           1             21             19             57\nmake                              4              8              0             32\nBourne Again Shell                1              1              0              2\nCSS                               1              0              1              1\n--------------------------------------------------------------------------------\nSUM:                            555          10880            678          53986\n--------------------------------------------------------------------------------\nAnd now, to be honest, I\u2019m thinking about blowing all of it away!\nHear me out - I\u2019ve learned a lot about the IndieWeb by working on this and even more so about the general space of things and now I want to try out something different. Koype works as a \u2018monolith\u2019, it has the support for things like Webmentions, IndieAuth and what not. But currently, I haven\u2019t given myself a lot of room to consider other things like templating or making it easy to extend. This is potentially an issue with the framework I chose to work on this project with but blaming the tools doesn\u2019t really fix the problem.\nAs I\u2019ve continued to work on my site, I\u2019ve seen other projects from people grow and flourish. I envy the flexibility that others have as I kept rushing to cobble more features into my site without taking other parts of it seriously enough. I do have a plan though!\nI want to see if I can refactor my site down to a point where it\u2019s truly just a set of \u201cparts\u201d:\na flexible Micropub server\n\nsomething like silo.pub to handle syndication\n\nfinishing up Lwa to act as a Webmention hub (as well as a WebSub hub, contacts manager, and mention feeds)\n\ngetting Fortress ready with AutoAuth and provisioning protected content (feeds, posts, etc)\n\nI think that once the basis of the above is in place, I can think more on how I want to handle other things like actually showing the site. I really don\u2019t want to go back to static site generation because the build times for Jekyll really frustrated me and was only justified when I was only writing like blog posts. Since I plan to have my website be my identity, place and hub on the Web, that doesn\u2019t work for me anymore. By refactoring Koype down to just the Micropub server (with some extra kicks, of course), I can go and use the same file storage for content as the backing for a very thin server that can act as the \u2018front-end\u2019 for my site. Having two apps running to work as my site is a bit weird but it gives me a bit of power in decoupling how I work on my presentation layer of my site without worrying about breaking how things in the background.\nI can imagine this sounding so complex but oddly enough, it\u2019s a lot simpler than the general state of Web development (React! \u2018Serverless\u2019! Service Workers! oh my! Offload-all-of-the-work-on-client-devices-because-why-not!). I am excited to start working on this too because it\u2019ll be a lot easier to make progress with things too.",
        "html": "<p class=\"p-summary\">I've been thinking about how I want my site to work (and additionally how I'd like to share it with other people so they can get it running for their own use cases) over the last few weeks as I had my head down working on [Fortress](https://indieweb.org/Fortress). It's been some time (it'll be 5 years this October 17th!) since I've joined the IndieWeb - and began exploring more people-centric social networking systems in general so it's about time.</p><p>I\u2019ve went from a Jekyll site to working on my <a href=\"https://koype.net\">newer site project</a>. This is what <a href=\"https://github.com/AlDanial/cloc\"><code>cloc</code></a> shows for the site currently:</p><pre><code>     595 text files.\n     583 unique files.\n      55 files ignored.\n\n\ngithub.com/AlDanial/cloc v 1.74  T=1.35 s (410.3 files/s, 48459.7 lines/s)\n--------------------------------------------------------------------------------\nLanguage                      files          blank        comment           code\n--------------------------------------------------------------------------------\nElixir                          336           4509            552          22526\nHTML                              2           6009              0          13872\nJSON                             43              0              0          13300\nEEx                              44              3              3           1265\nliquid                           78             16              8           1166\nSass                             12            144             17            727\nVuejs Component                   5             12              7            264\nYAML                              3             23             45            257\nBourne Shell                     17             82             19            225\nJavaScript                        4             32              7            185\nCucumber                          4             20              0            107\nPO File                           1             21             19             57\nmake                              4              8              0             32\nBourne Again Shell                1              1              0              2\nCSS                               1              0              1              1\n--------------------------------------------------------------------------------\nSUM:                            555          10880            678          53986\n--------------------------------------------------------------------------------</code></pre>\n<p>And now, to be honest, I\u2019m thinking about blowing all of it away!</p>\n<p>Hear me out - I\u2019ve learned a <em>lot</em> about the IndieWeb by working on this and even more so about the general space of things and now I want to try out something different. Koype works as a \u2018monolith\u2019, it has the support for things like <a href=\"https://www.w3.org/TR/webmention/\">Webmentions</a>, <a href=\"https://indieauth.spec.indieweb.org/\">IndieAuth</a> and what not. But currently, I haven\u2019t given myself a lot of room to consider other things like templating or making it easy to extend. This is potentially an issue with the framework I chose to work on this project with but blaming the tools doesn\u2019t really fix the problem.</p>\n<p>As I\u2019ve continued to work on my site, I\u2019ve seen other projects from people grow and flourish. I envy the flexibility that others have as I kept rushing to cobble more features into my site without taking other parts of it seriously enough. I do have a plan though!</p>\n<p>I want to see if I can refactor my site down to a point where it\u2019s truly just a set of \u201cparts\u201d:</p>\n<ul><li>a flexible Micropub server\n</li>\n<li>something like <code>silo.pub</code> to handle syndication\n</li>\n<li>finishing up Lwa to act as a Webmention hub (as well as a WebSub hub, contacts manager, and mention feeds)\n</li>\n<li>getting Fortress ready with AutoAuth and provisioning protected content (feeds, posts, etc)\n</li>\n</ul><p>I think that once the basis of the above is in place, I can think more on how I want to handle other things like <em>actually</em> showing the site. I <em>really</em> don\u2019t want to go back to static site generation because the build times for Jekyll really frustrated me and was only justified when I was only writing like blog posts. Since I plan to have my website be <em>my</em> identity, place and hub on the Web, that doesn\u2019t work for me anymore. By refactoring Koype down to just the Micropub server (with some extra kicks, of course), I can go and use the <em>same</em> file storage for content as the backing for a very thin server that can act as the \u2018front-end\u2019 for my site. Having two apps running to work as my site is a bit weird but it gives me a bit of power in decoupling how I work on my presentation layer of my site without worrying about breaking how things in the background.</p>\n<p>I can imagine this sounding so complex but oddly enough, it\u2019s <em>a lot</em> simpler than the general state of Web development (React! \u2018Serverless\u2019! Service Workers! oh my! Offload-all-of-the-work-on-client-devices-because-why-not!). I am excited to start working on this too because it\u2019ll be a lot easier to make progress with things too.</p>"
    },
    "post-type": "note",
    "_id": "19066685",
    "_source": "1886",
    "_is_read": true
}

I've been thinking about how I want my site to work (and additionally how I'd like to share it with other people so they can get it running for their own use cases) over the last few weeks as I had my head down working on [Fortress](https://indieweb.org/Fortress). It's been some time (it'll be 5 years this October 17th!) since I've joined the IndieWeb - and began exploring more people-centric social networking systems in general so it's about time.

I’ve went from a Jekyll site to working on my newer site project. This is what cloc shows for the site currently:

     595 text files.
     583 unique files.
      55 files ignored.


github.com/AlDanial/cloc v 1.74  T=1.35 s (410.3 files/s, 48459.7 lines/s)
--------------------------------------------------------------------------------
Language                      files          blank        comment           code
--------------------------------------------------------------------------------
Elixir                          336           4509            552          22526
HTML                              2           6009              0          13872
JSON                             43              0              0          13300
EEx                              44              3              3           1265
liquid                           78             16              8           1166
Sass                             12            144             17            727
Vuejs Component                   5             12              7            264
YAML                              3             23             45            257
Bourne Shell                     17             82             19            225
JavaScript                        4             32              7            185
Cucumber                          4             20              0            107
PO File                           1             21             19             57
make                              4              8              0             32
Bourne Again Shell                1              1              0              2
CSS                               1              0              1              1
--------------------------------------------------------------------------------
SUM:                            555          10880            678          53986
--------------------------------------------------------------------------------

And now, to be honest, I’m thinking about blowing all of it away!

Hear me out - I’ve learned a lot about the IndieWeb by working on this and even more so about the general space of things and now I want to try out something different. Koype works as a ‘monolith’, it has the support for things like Webmentions, IndieAuth and what not. But currently, I haven’t given myself a lot of room to consider other things like templating or making it easy to extend. This is potentially an issue with the framework I chose to work on this project with but blaming the tools doesn’t really fix the problem.

As I’ve continued to work on my site, I’ve seen other projects from people grow and flourish. I envy the flexibility that others have as I kept rushing to cobble more features into my site without taking other parts of it seriously enough. I do have a plan though!

I want to see if I can refactor my site down to a point where it’s truly just a set of “parts”:

a flexible Micropub server
something like silo.pub to handle syndication
finishing up Lwa to act as a Webmention hub (as well as a WebSub hub, contacts manager, and mention feeds)
getting Fortress ready with AutoAuth and provisioning protected content (feeds, posts, etc)

I think that once the basis of the above is in place, I can think more on how I want to handle other things like actually showing the site. I really don’t want to go back to static site generation because the build times for Jekyll really frustrated me and was only justified when I was only writing like blog posts. Since I plan to have my website be my identity, place and hub on the Web, that doesn’t work for me anymore. By refactoring Koype down to just the Micropub server (with some extra kicks, of course), I can go and use the same file storage for content as the backing for a very thin server that can act as the ‘front-end’ for my site. Having two apps running to work as my site is a bit weird but it gives me a bit of power in decoupling how I work on my presentation layer of my site without worrying about breaking how things in the background.

I can imagine this sounding so complex but oddly enough, it’s a lot simpler than the general state of Web development (React! ‘Serverless’! Service Workers! oh my! Offload-all-of-the-work-on-client-devices-because-why-not!). I am excited to start working on this too because it’ll be a lot easier to make progress with things too.

v2.jacky.wtf/post/a9c0526d-9b37-4559-acd9-3db2814da4db

{
    "type": "entry",
    "summary": "I've been thinking about how I want my site to work (and additionally how I'd like to share it with other people so they can get it running for their own use cases) over the last few weeks as I had my head down working on [Fortress](https://indieweb.org/Fortress). It's been some time (it'll be 5 years this October 17th!) since I've joined the IndieWeb - and began exploring more people-centric social networking systems in general so it's about time.",
    "url": "https://v2.jacky.wtf/post/a9c0526d-9b37-4559-acd9-3db2814da4db",
    "content": {
        "text": "I've been thinking about how I want my site to work (and additionally how I'd like to share it with other people so they can get it running for their own use cases) over the last few weeks as I had my head down working on [Fortress](https://indieweb.org/Fortress). It's been some time (it'll be 5 years this October 17th!) since I've joined the IndieWeb - and began exploring more people-centric social networking systems in general so it's about time.I\u2019ve went from a Jekyll site to working on my newer site project. This is what cloc shows for the site currently:     595 text files.\n     583 unique files.\n      55 files ignored.\n\n\ngithub.com/AlDanial/cloc v 1.74  T=1.35 s (410.3 files/s, 48459.7 lines/s)\n--------------------------------------------------------------------------------\nLanguage                      files          blank        comment           code\n--------------------------------------------------------------------------------\nElixir                          336           4509            552          22526\nHTML                              2           6009              0          13872\nJSON                             43              0              0          13300\nEEx                              44              3              3           1265\nliquid                           78             16              8           1166\nSass                             12            144             17            727\nVuejs Component                   5             12              7            264\nYAML                              3             23             45            257\nBourne Shell                     17             82             19            225\nJavaScript                        4             32              7            185\nCucumber                          4             20              0            107\nPO File                           1             21             19             57\nmake                              4              8              0             32\nBourne Again Shell                1              1              0              2\nCSS                               1              0              1              1\n--------------------------------------------------------------------------------\nSUM:                            555          10880            678          53986\n--------------------------------------------------------------------------------\nAnd now, to be honest, I\u2019m thinking about blowing all of it away!\nHear me out - I\u2019ve learned a lot about the IndieWeb by working on this and even more so about the general space of things and now I want to try out something different. Koype works as a \u2018monolith\u2019, it has the support for things like Webmentions, IndieAuth and what not. But currently, I haven\u2019t given myself a lot of room to consider other things like templating or making it easy to extend. This is potentially an issue with the framework I chose to work on this project with but blaming the tools doesn\u2019t really fix the problem.\nAs I\u2019ve continued to work on my site, I\u2019ve seen other projects from people grow and flourish. I envy the flexibility that others have as I kept rushing to cobble more features into my site without taking other parts of it seriously enough. I do have a plan though!\nI want to see if I can refactor my site down to a point where it\u2019s truly just a set of \u201cparts\u201d:\na flexible Micropub server\n\nsomething like silo.pub to handle syndication\n\nfinishing up Lwa to act as a Webmention hub (as well as a WebSub hub, contacts manager, and mention feeds)\n\ngetting Fortress ready with AutoAuth and provisioning protected content (feeds, posts, etc)\n\nI think that once the basis of the above is in place, I can think more on how I want to handle other things like actually showing the site. I really don\u2019t want to go back to static site generation because the build times for Jekyll really frustrated me and was only justified when I was only writing like blog posts. Since I plan to have my website be my identity, place and hub on the Web, that doesn\u2019t work for me anymore. By refactoring Koype down to just the Micropub server (with some extra kicks, of course), I can go and use the same file storage for content as the backing for a very thin server that can act as the \u2018front-end\u2019 for my site. Having two apps running to work as my site is a bit weird but it gives me a bit of power in decoupling how I work on my presentation layer of my site without worrying about breaking how things in the background.\nI can imagine this sounding so complex but oddly enough, it\u2019s a lot simpler than the general state of Web development (React! \u2018Serverless\u2019! Service Workers! oh my! Offload-all-of-the-work-on-client-devices-because-why-not!). I am excited to start working on this too because it\u2019ll be a lot easier to make progress with things too.",
        "html": "<p class=\"p-summary\">I've been thinking about how I want my site to work (and additionally how I'd like to share it with other people so they can get it running for their own use cases) over the last few weeks as I had my head down working on [Fortress](https://indieweb.org/Fortress). It's been some time (it'll be 5 years this October 17th!) since I've joined the IndieWeb - and began exploring more people-centric social networking systems in general so it's about time.</p><p>I\u2019ve went from a Jekyll site to working on my <a href=\"https://koype.net\">newer site project</a>. This is what <a href=\"https://github.com/AlDanial/cloc\"><code>cloc</code></a> shows for the site currently:</p><pre><code>     595 text files.\n     583 unique files.\n      55 files ignored.\n\n\ngithub.com/AlDanial/cloc v 1.74  T=1.35 s (410.3 files/s, 48459.7 lines/s)\n--------------------------------------------------------------------------------\nLanguage                      files          blank        comment           code\n--------------------------------------------------------------------------------\nElixir                          336           4509            552          22526\nHTML                              2           6009              0          13872\nJSON                             43              0              0          13300\nEEx                              44              3              3           1265\nliquid                           78             16              8           1166\nSass                             12            144             17            727\nVuejs Component                   5             12              7            264\nYAML                              3             23             45            257\nBourne Shell                     17             82             19            225\nJavaScript                        4             32              7            185\nCucumber                          4             20              0            107\nPO File                           1             21             19             57\nmake                              4              8              0             32\nBourne Again Shell                1              1              0              2\nCSS                               1              0              1              1\n--------------------------------------------------------------------------------\nSUM:                            555          10880            678          53986\n--------------------------------------------------------------------------------</code></pre>\n<p>And now, to be honest, I\u2019m thinking about blowing all of it away!</p>\n<p>Hear me out - I\u2019ve learned a <em>lot</em> about the IndieWeb by working on this and even more so about the general space of things and now I want to try out something different. Koype works as a \u2018monolith\u2019, it has the support for things like <a href=\"https://www.w3.org/TR/webmention/\">Webmentions</a>, <a href=\"https://indieauth.spec.indieweb.org/\">IndieAuth</a> and what not. But currently, I haven\u2019t given myself a lot of room to consider other things like templating or making it easy to extend. This is potentially an issue with the framework I chose to work on this project with but blaming the tools doesn\u2019t really fix the problem.</p>\n<p>As I\u2019ve continued to work on my site, I\u2019ve seen other projects from people grow and flourish. I envy the flexibility that others have as I kept rushing to cobble more features into my site without taking other parts of it seriously enough. I do have a plan though!</p>\n<p>I want to see if I can refactor my site down to a point where it\u2019s truly just a set of \u201cparts\u201d:</p>\n<ul><li>a flexible Micropub server\n</li>\n<li>something like <code>silo.pub</code> to handle syndication\n</li>\n<li>finishing up Lwa to act as a Webmention hub (as well as a WebSub hub, contacts manager, and mention feeds)\n</li>\n<li>getting Fortress ready with AutoAuth and provisioning protected content (feeds, posts, etc)\n</li>\n</ul><p>I think that once the basis of the above is in place, I can think more on how I want to handle other things like <em>actually</em> showing the site. I <em>really</em> don\u2019t want to go back to static site generation because the build times for Jekyll really frustrated me and was only justified when I was only writing like blog posts. Since I plan to have my website be <em>my</em> identity, place and hub on the Web, that doesn\u2019t work for me anymore. By refactoring Koype down to just the Micropub server (with some extra kicks, of course), I can go and use the <em>same</em> file storage for content as the backing for a very thin server that can act as the \u2018front-end\u2019 for my site. Having two apps running to work as my site is a bit weird but it gives me a bit of power in decoupling how I work on my presentation layer of my site without worrying about breaking how things in the background.</p>\n<p>I can imagine this sounding so complex but oddly enough, it\u2019s <em>a lot</em> simpler than the general state of Web development (React! \u2018Serverless\u2019! Service Workers! oh my! Offload-all-of-the-work-on-client-devices-because-why-not!). I am excited to start working on this too because it\u2019ll be a lot easier to make progress with things too.</p>"
    },
    "post-type": "note",
    "_id": "19066686",
    "_source": "1886",
    "_is_read": true
}

brainbaking.com/post/2021/03/the-indieweb-mixed-bag/

Jamie Tanna www.jvt.me

#indieweb #decentralisation #webmention #microformats

March 15, 2021 12:42pm +00:00

{
    "type": "entry",
    "published": "2021-03-15T12:42:00+0000",
    "url": "https://www.jvt.me/mf2/2021/03/1bkre/",
    "category": [
        "indieweb",
        "decentralisation",
        "webmention",
        "microformats"
    ],
    "bookmark-of": [
        "https://brainbaking.com/post/2021/03/the-indieweb-mixed-bag/"
    ],
    "author": {
        "type": "card",
        "name": "Jamie Tanna",
        "url": "https://www.jvt.me",
        "photo": "https://www.jvt.me/img/profile.png"
    },
    "post-type": "bookmark",
    "_id": "19054062",
    "_source": "2169",
    "_is_read": true
}

Vika fireburn.ru

Роскомпозор замедляет твиттер? а зачем нужен твиттер если есть собственный блог, в который можно постить как в твиттер только лучше? #IndieWeb #ownyourdata

#IndieWeb #ownyourdata

March 12, 2021 5:13pm +00:00

{
    "type": "entry",
    "published": "2021-03-12T17:13:26+00:00",
    "url": "https://fireburn.ru/posts/1615569206",
    "category": [
        "IndieWeb",
        "ownyourdata"
    ],
    "syndication": [
        "https://twitter.com/kisik21/status/1370422712926093313"
    ],
    "content": {
        "text": "\u0420\u043e\u0441\u043a\u043e\u043c\u043f\u043e\u0437\u043e\u0440 \u0437\u0430\u043c\u0435\u0434\u043b\u044f\u0435\u0442 \u0442\u0432\u0438\u0442\u0442\u0435\u0440? \u0430 \u0437\u0430\u0447\u0435\u043c \u043d\u0443\u0436\u0435\u043d \u0442\u0432\u0438\u0442\u0442\u0435\u0440 \u0435\u0441\u043b\u0438 \u0435\u0441\u0442\u044c \u0441\u043e\u0431\u0441\u0442\u0432\u0435\u043d\u043d\u044b\u0439 \u0431\u043b\u043e\u0433, \u0432 \u043a\u043e\u0442\u043e\u0440\u044b\u0439 \u043c\u043e\u0436\u043d\u043e \u043f\u043e\u0441\u0442\u0438\u0442\u044c \u043a\u0430\u043a \u0432 \u0442\u0432\u0438\u0442\u0442\u0435\u0440 \u0442\u043e\u043b\u044c\u043a\u043e \u043b\u0443\u0447\u0448\u0435? #IndieWeb #ownyourdata",
        "html": "<p>\u0420\u043e\u0441\u043a\u043e\u043c\u043f\u043e\u0437\u043e\u0440 \u0437\u0430\u043c\u0435\u0434\u043b\u044f\u0435\u0442 \u0442\u0432\u0438\u0442\u0442\u0435\u0440? \u0430 \u0437\u0430\u0447\u0435\u043c \u043d\u0443\u0436\u0435\u043d \u0442\u0432\u0438\u0442\u0442\u0435\u0440 \u0435\u0441\u043b\u0438 \u0435\u0441\u0442\u044c \u0441\u043e\u0431\u0441\u0442\u0432\u0435\u043d\u043d\u044b\u0439 \u0431\u043b\u043e\u0433, \u0432 \u043a\u043e\u0442\u043e\u0440\u044b\u0439 \u043c\u043e\u0436\u043d\u043e \u043f\u043e\u0441\u0442\u0438\u0442\u044c \u043a\u0430\u043a \u0432 \u0442\u0432\u0438\u0442\u0442\u0435\u0440 \u0442\u043e\u043b\u044c\u043a\u043e \u043b\u0443\u0447\u0448\u0435? #IndieWeb #ownyourdata</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": "19001673",
    "_source": "1371",
    "_is_read": true
}

twitter.com/arcatech/status/1370191316852826118

Oh that was the same for me. I had a static site using Jekyll some time ago but then ended up writing my own blog as well. Frankly, if I had to do it all over again, I’d opt for a light system that makes it easier for me to plug in my own bits for Webmentions and other IndieWeb stuff

v2.jacky.wtf/post/ba3238de-8371-4175-80a0-e7e60c385bfc

{
    "type": "entry",
    "url": "https://v2.jacky.wtf/post/ba3238de-8371-4175-80a0-e7e60c385bfc",
    "in-reply-to": [
        "https://twitter.com/arcatech/status/1370191316852826118"
    ],
    "content": {
        "text": "Oh that was the same for me. I had a static site using Jekyll some time ago but then ended up writing my own blog as well. Frankly, if I had to do it all over again, I\u2019d opt for a light system that makes it easier for me to plug in my own bits for Webmentions and other IndieWeb stuff",
        "html": "<p>Oh that was the same for me. I had a static site using Jekyll some time ago but then ended up writing my own blog as well. Frankly, if I had to do it all over again, I\u2019d opt for a light system that makes it easier for me to plug in my own bits for Webmentions and other IndieWeb stuff</p>"
    },
    "post-type": "reply",
    "refs": {
        "https://twitter.com/arcatech/status/1370191316852826118": {
            "type": "entry",
            "url": "https://twitter.com/arcatech/status/1370191316852826118",
            "name": "Replied to a article by a remote entity",
            "post-type": "article"
        }
    },
    "_id": "18997474",
    "_source": "1886",
    "_is_read": true
}

twitter.com/arcatech/status/1370110429758947335

aye! lemme know if you need help with that! or pop into https://chat.indieweb.org/dev/!

v2.jacky.wtf/post/3c811ecc-0b2a-4079-9b84-242e94befa73

{
    "type": "entry",
    "url": "https://v2.jacky.wtf/post/3c811ecc-0b2a-4079-9b84-242e94befa73",
    "in-reply-to": [
        "https://twitter.com/arcatech/status/1370110429758947335"
    ],
    "content": {
        "text": "aye! lemme know if you need help with that! or pop into https://chat.indieweb.org/dev/!",
        "html": "<p>aye! lemme know if you need help with that! or pop into <a href=\"https://chat.indieweb.org/dev/\">https://chat.indieweb.org/dev/</a>!</p>"
    },
    "post-type": "reply",
    "refs": {
        "https://twitter.com/arcatech/status/1370110429758947335": {
            "type": "entry",
            "url": "https://twitter.com/arcatech/status/1370110429758947335",
            "name": "Replied to a article by a remote entity",
            "post-type": "article"
        }
    },
    "_id": "18975880",
    "_source": "1886",
    "_is_read": true
}

Colin Walker colinwalker.blog

# I'm three weeks in to my journalling streak and it feels good to have kept it going, not that there's really been anything earth-shattering written there. It definitely helps having a little reminder at the top of the blog page that is also a direct link to the journal page.

# Non-WordPress blog status update:

RSS feeds (live & daily) - done
inline editing - done
image uploads - done

Everything I wanted to achieve for a version 1.0 has been completed. It's been relatively easy as it's all based on the custom layer that I created on top of WordPress. I have just had to transpose the code over and replace WordPress specific function with normal PHP and JavaScript. The only thing that hasn't translated has been treating each day as a single post. For now.

I've been thinking about how I could implement a comment system but that's not a priority right now. I also looked at sending/receiving webmentions but that's still a bit beyond me at present, maybe I'll work out how to do it in future but, again, it's not a priority.

The real question is do I make the switch to this system? There's no way I'm going to (be able to) migrate existing content over so the WordPress blog would still have to exist as an archive. I also wouldn't migrate the Garden as that would be too much work. The Journal could be fair game, however.

In the meantime, I'll run the non-wp blog in the background to give it a thorough test before making any decisions as I'm sure there are bugs that will need to be ironed out. Irrespective of any issues I'm really happy with what I've been able to create thus far.

# I appear to have broken the RSS feed generator on the WordPress blog so the decision may be getting made for me.

# Look like I've managed to fix it so an enforced change isn't on the cards just yet.

# And there we have it, Lockdown 3 in England until further notice due to continued increases in Covid cases. The easing of restrictions is tied to the vaccination program so we could be in to March before anything changes.

January 4, 2021 9:05am +00:00

{
    "type": "entry",
    "author": {
        "name": "Colin Walker",
        "url": "https://colinwalker.blog/",
        "photo": null
    },
    "url": "https://colinwalker.blog/04-01-2021-0905/",
    "published": "2021-01-04T09:05:00+00:00",
    "content": {
        "html": "<p><a href=\"https://colinwalker.blog/04-01-2021-0905/\">#</a> I'm three weeks in to my journalling streak and it feels good to have kept it going, not that there's really been anything earth-shattering written there. It definitely helps having a little reminder at the top of the blog page that is also a direct link to the journal page.</p>\n<p><a href=\"https://colinwalker.blog/04-01-2021-0905/#p1\">#</a> Non-WordPress blog status update:</p>\n<ul><li>RSS feeds (live &amp; daily) - done</li>\n<li>inline editing - done</li>\n<li>image uploads - done</li>\n</ul><p>Everything I wanted to achieve for a version 1.0 has been completed. It's been relatively easy as it's all based on the custom layer that I created on top of WordPress. I have just had to transpose the code over and replace WordPress specific function with normal PHP and JavaScript. The only thing that hasn't translated has been treating each day as a single post. For now.</p>\n<p>I've been thinking about how I could implement a comment system but that's not a priority right now. I also looked at sending/receiving webmentions but that's still a bit beyond me at present, maybe I'll work out how to do it in future but, again, it's not a priority.</p>\n<p>The real question is do I make the switch to this system? There's no way I'm going to (be able to) migrate existing content over so the WordPress blog would still have to exist as an archive. I also wouldn't migrate the Garden as that would be too much work. The Journal could be fair game, however.</p>\n<p>In the meantime, I'll run the non-wp blog in the background to give it a thorough test before making any decisions as I'm sure there are bugs that will need to be ironed out. Irrespective of any issues I'm really happy with what I've been able to create thus far.</p>\n<p><a href=\"https://colinwalker.blog/04-01-2021-0905/#p2\">#</a> I appear to have broken the RSS feed generator on the WordPress blog so the decision may be getting made for me.</p>\n<p><a href=\"https://colinwalker.blog/04-01-2021-0905/#p3\">#</a> Look like I've managed to fix it so an enforced change isn't on the cards just yet.</p>\n<p><a href=\"https://colinwalker.blog/04-01-2021-0905/#p4\">#</a> And there we have it, Lockdown 3 in England until further notice due to continued increases in Covid cases. The easing of restrictions is tied to the vaccination program so we could be in to March before anything changes.</p>",
        "text": "# I'm three weeks in to my journalling streak and it feels good to have kept it going, not that there's really been anything earth-shattering written there. It definitely helps having a little reminder at the top of the blog page that is also a direct link to the journal page.\n# Non-WordPress blog status update:\nRSS feeds (live & daily) - done\ninline editing - done\nimage uploads - done\nEverything I wanted to achieve for a version 1.0 has been completed. It's been relatively easy as it's all based on the custom layer that I created on top of WordPress. I have just had to transpose the code over and replace WordPress specific function with normal PHP and JavaScript. The only thing that hasn't translated has been treating each day as a single post. For now.\nI've been thinking about how I could implement a comment system but that's not a priority right now. I also looked at sending/receiving webmentions but that's still a bit beyond me at present, maybe I'll work out how to do it in future but, again, it's not a priority.\nThe real question is do I make the switch to this system? There's no way I'm going to (be able to) migrate existing content over so the WordPress blog would still have to exist as an archive. I also wouldn't migrate the Garden as that would be too much work. The Journal could be fair game, however.\nIn the meantime, I'll run the non-wp blog in the background to give it a thorough test before making any decisions as I'm sure there are bugs that will need to be ironed out. Irrespective of any issues I'm really happy with what I've been able to create thus far.\n# I appear to have broken the RSS feed generator on the WordPress blog so the decision may be getting made for me.\n# Look like I've managed to fix it so an enforced change isn't on the cards just yet.\n# And there we have it, Lockdown 3 in England until further notice due to continued increases in Covid cases. The easing of restrictions is tied to the vaccination program so we could be in to March before anything changes."
    },
    "post-type": "note",
    "_id": "18946849",
    "_source": "237",
    "_is_read": true
}

Parts completed in Fortress:

Drop-in support as a IndieAuth provider (it still requires setup)

Things that I’m planning to complete:

Audit log of each token use
Revoke tokens from Web
Add information on dashboard about supported providers
Add flow for adding devices

v2.jacky.wtf/post/479afb27-d468-4d12-9725-e4c715a0ba57

{
    "type": "entry",
    "url": "https://v2.jacky.wtf/post/479afb27-d468-4d12-9725-e4c715a0ba57",
    "content": {
        "text": "Parts completed in Fortress:Drop-in support as a IndieAuth provider (it still requires setup)\n\nThings that I\u2019m planning to complete:Audit log of each token use\n\nRevoke tokens from Web\n\nAdd information on dashboard about supported providers\n\nAdd flow for adding devices",
        "html": "<p>Parts completed in <a href=\"https://app.fortress.black.af\">Fortress</a>:</p><ul><li>Drop-in support as a IndieAuth provider (it still requires setup)\n</li>\n</ul><p>Things that I\u2019m planning to complete:</p><ul><li>Audit log of each token use\n</li>\n<li>Revoke tokens from Web\n</li>\n<li>Add information on dashboard about supported providers\n</li>\n<li>Add flow for adding devices\n</li>\n</ul>"
    },
    "post-type": "note",
    "_id": "18931435",
    "_source": "1886",
    "_is_read": true
}

tantek.com/2021/064/b1/one-year-since-homebrew-website-club

Jeremy Keith adactio.com

One Year Since The #IndieWeb Homebrew Website Club Met In Person And Other Last Times - Tantek

Expect more poignant one-year anniversary memories this March.

We reached our disembarkation stop and stepped off. I put my mask away. We hugged and said our goodbyes. Didn’t think it would be the last time I’d ride MUNI light rail. Or hug a friend without a second thought.

#covid-19 #coronavirus #pandemic #lockdown #anniversary #memory

March 7, 2021 12:48pm +00:00

{
    "type": "entry",
    "published": "2021-03-07T12:48:29Z",
    "url": "https://adactio.com/links/17893",
    "category": [
        "covid-19",
        "coronavirus",
        "pandemic",
        "lockdown",
        "anniversary",
        "memory"
    ],
    "bookmark-of": [
        "https://tantek.com/2021/064/b1/one-year-since-homebrew-website-club"
    ],
    "content": {
        "text": "One Year Since The #IndieWeb Homebrew Website Club Met In Person And Other Last Times - Tantek\n\n\n\nExpect more poignant one-year anniversary memories this March.\n\n\n  We reached our disembarkation stop and stepped off. I put my mask away. We hugged and said our goodbyes. Didn\u2019t think it would be the last time I\u2019d ride MUNI light rail. Or hug a friend without a second thought.",
        "html": "<h3>\n<a class=\"p-name u-bookmark-of\" href=\"https://tantek.com/2021/064/b1/one-year-since-homebrew-website-club\">\nOne Year Since The #IndieWeb Homebrew Website Club Met In Person And Other Last Times - Tantek\n</a>\n</h3>\n\n<p>Expect more poignant one-year anniversary memories this March.</p>\n\n<blockquote>\n  <p>We reached our disembarkation stop and stepped off. I put my mask away. We hugged and said our goodbyes. Didn\u2019t think it would be the last time I\u2019d ride MUNI light rail. Or hug a friend without a second thought.</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": "18865591",
    "_source": "2",
    "_is_read": true
}

Jamie Tanna www.jvt.me

Introducing tokens-pls, a Web Application to Test OAuth2 Code Flows

Announcing my new project, tokens-pls, which allows for easier manual testing with the OAuth2 code flow for Public Clients.

#indieauth #oauth2 #token-pls

March 6, 2021 1:42pm +00:00

{
    "type": "entry",
    "published": "2021-03-06 13:42:20 +0000 +0000",
    "summary": "Announcing my new project, tokens-pls, which allows for easier manual testing with the OAuth2 code flow for Public Clients.",
    "url": "https://www.jvt.me/posts/2021/03/06/tokens-pls/",
    "category": [
        "indieauth",
        "oauth2",
        "token-pls"
    ],
    "name": "Introducing tokens-pls, a Web Application to Test OAuth2 Code Flows",
    "author": {
        "type": "card",
        "name": "Jamie Tanna",
        "url": "https://www.jvt.me",
        "photo": "https://www.jvt.me/img/profile.png"
    },
    "post-type": "article",
    "_id": "18851134",
    "_source": "2169",
    "_is_read": true
}

atthis.link/blog/2021/rss.html

Jeremy Keith adactio.com

Why I Still Use RSS | atthislink

Having only the content I want to see only be shown when I want to see it with the freedom to jump between readers as I please, all with no ads? For me, no other service comes close to the flexibility, robustness, and overall ease-of-use that RSS offers.

#rss #syndication #wellbeing #social #indieweb #reading #readers #freedom

March 6, 2021 2:45pm +00:00

{
    "type": "entry",
    "published": "2021-03-06T14:45:01Z",
    "url": "https://adactio.com/links/17888",
    "category": [
        "rss",
        "syndication",
        "wellbeing",
        "social",
        "indieweb",
        "reading",
        "readers",
        "freedom"
    ],
    "bookmark-of": [
        "https://atthis.link/blog/2021/rss.html"
    ],
    "content": {
        "text": "Why I Still Use RSS | atthislink\n\n\n\n\n  Having only the content I want to see only be shown when I want to see it with the freedom to jump between readers as I please, all with no ads? For me, no other service comes close to the flexibility, robustness, and overall ease-of-use that RSS offers.",
        "html": "<h3>\n<a class=\"p-name u-bookmark-of\" href=\"https://atthis.link/blog/2021/rss.html\">\nWhy I Still Use RSS | atthislink\n</a>\n</h3>\n\n<blockquote>\n  <p>Having only the content I want to see only be shown when I want to see it with the freedom to jump between readers as I please, all with no ads? For me, no other service comes close to the flexibility, robustness, and overall ease-of-use that RSS offers.</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": "18850072",
    "_source": "2",
    "_is_read": true
}

Neil Mather doubleloop.net

Liked Why The IndieWeb? (briefs.video)

A brief video about the web from Webbed Briefs

March 3, 2021 9:36pm +00:00

{
    "type": "entry",
    "author": {
        "name": "Neil Mather",
        "url": "https://doubleloop.net/",
        "photo": null
    },
    "url": "https://doubleloop.net/2021/03/03/7406/",
    "published": "2021-03-03T21:36:47+00:00",
    "content": {
        "html": "Liked <a href=\"https://briefs.video/videos/why-the-indieweb/\">Why The IndieWeb?</a> <em>(briefs.video)</em>\n<blockquote>A brief video about the web from Webbed Briefs</blockquote>",
        "text": "Liked Why The IndieWeb? (briefs.video)\nA brief video about the web from Webbed Briefs"
    },
    "post-type": "note",
    "_id": "18790185",
    "_source": "1895",
    "_is_read": true
}

airbagindustries.com/there-s-a-voice-inside-your-heads-that-prevents-you-from-adding-your-voice-to-the-room-punch-it-in-the-face/

Jeremy Keith adactio.com

There’s a voice inside your head that prevents you from sharing ideas—punch it in the face. - Airbag Industries

Violence is never the answer, unless you’re dealing with nazis or your inner critic.

The excuses—or, I’m sorry, reasons—I hear folks say they can’t write include: I’m not very good at writing (you can’t improve if you don’t write often), my website isn’t finished (classic, and also guilty so shut up), and I don’t know what to write about, there’s nothing new for me to add (oh boy).

#writing #sharing #innercritic #personal #publishing #indieweb #blogging #ideas

March 2, 2021 9:43am +00:00

{
    "type": "entry",
    "published": "2021-03-02T09:43:23Z",
    "url": "https://adactio.com/links/17877",
    "category": [
        "writing",
        "sharing",
        "innercritic",
        "personal",
        "publishing",
        "indieweb",
        "blogging",
        "ideas"
    ],
    "bookmark-of": [
        "https://airbagindustries.com/there-s-a-voice-inside-your-heads-that-prevents-you-from-adding-your-voice-to-the-room-punch-it-in-the-face/"
    ],
    "content": {
        "text": "There\u2019s a voice inside your head that prevents you from sharing ideas\u2014punch it in the face. - Airbag Industries\n\n\n\nViolence is never the answer, unless you\u2019re dealing with nazis or your inner critic.\n\n\n  The excuses\u2014or, I\u2019m sorry, reasons\u2014I hear folks say they can\u2019t write include: I\u2019m not very good at writing (you can\u2019t improve if you don\u2019t write often), my website isn\u2019t finished (classic, and also guilty so shut up), and I don\u2019t know what to write about, there\u2019s nothing new for me to add (oh boy).",
        "html": "<h3>\n<a class=\"p-name u-bookmark-of\" href=\"https://airbagindustries.com/there-s-a-voice-inside-your-heads-that-prevents-you-from-adding-your-voice-to-the-room-punch-it-in-the-face/\">\nThere\u2019s a voice inside your head that prevents you from sharing ideas\u2014punch it in the face. - Airbag Industries\n</a>\n</h3>\n\n<p>Violence is never the answer, unless you\u2019re dealing with nazis or your inner critic.</p>\n\n<blockquote>\n  <p>The excuses\u2014or, I\u2019m sorry, reasons\u2014I hear folks say they can\u2019t write include: I\u2019m not very good at writing (you can\u2019t improve if you don\u2019t write often), my website isn\u2019t finished (classic, and also guilty so shut up), and I don\u2019t know what to write about, there\u2019s nothing new for me to add (oh boy).</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": "18747607",
    "_source": "2",
    "_is_read": true
}

Jamie Tanna www.jvt.me

Reminder that it's #HomebrewWebsiteClub Nottingham tomorrow! I hope to see you there at 1730 for some website stuff! https://events.indieweb.org/2021/03/homebrew-website-club-nottingham-zpkxpaQ4wCgD

#homebrew-website-club

March 2, 2021 9:40am +00:00

{
    "type": "entry",
    "published": "2021-03-02T09:40:32.248Z",
    "url": "https://www.jvt.me/mf2/2021/03/g4qai/",
    "category": [
        "homebrew-website-club"
    ],
    "content": {
        "text": "Reminder that it's #HomebrewWebsiteClub Nottingham tomorrow! I hope to see you there at 1730 for some website stuff! https://events.indieweb.org/2021/03/homebrew-website-club-nottingham-zpkxpaQ4wCgD",
        "html": "<p>Reminder that it's <a href=\"https://www.jvt.me/tags/homebrew-website-club/\">#HomebrewWebsiteClub</a> Nottingham tomorrow! I hope to see you there at 1730 for some website stuff! <a href=\"https://events.indieweb.org/2021/03/homebrew-website-club-nottingham-zpkxpaQ4wCgD\">https://events.indieweb.org/2021/03/homebrew-website-club-nottingham-zpkxpaQ4wCgD</a></p>"
    },
    "author": {
        "type": "card",
        "name": "Jamie Tanna",
        "url": "https://www.jvt.me",
        "photo": "https://www.jvt.me/img/profile.png"
    },
    "post-type": "note",
    "_id": "18747265",
    "_source": "2169",
    "_is_read": true
}

Jamie Tanna www.jvt.me

Welp, backlog of webmentions from telegraph.p3k.io means you may see some poorly timed interactions from me - sorry 🙃

March 1, 2021 4:31pm +00:00

{
    "type": "entry",
    "published": "2021-03-01T16:31:00+0000",
    "url": "https://www.jvt.me/mf2/2021/03/rlwgr/",
    "content": {
        "text": "Welp, backlog of webmentions from telegraph.p3k.io means you may see some poorly timed interactions from me - sorry \ud83d\ude43",
        "html": "<p>Welp, backlog of webmentions from telegraph.p3k.io means you may see some poorly timed interactions from me - sorry \ud83d\ude43</p>"
    },
    "author": {
        "type": "card",
        "name": "Jamie Tanna",
        "url": "https://www.jvt.me",
        "photo": "https://www.jvt.me/img/profile.png"
    },
    "post-type": "note",
    "_id": "18732524",
    "_source": "2169",
    "_is_read": true
}

twitter.com/Cambridgeport90/status/1365748410469523464

stream.boffosocko.com/2021/roberthaisfield-i-agree-wholeheartedly-and-have-written-a-bit-about

Chris Aldrich stream.boffosocko.com/profile/chrisaldrich

@Cambridgeport90 I don't worry about them stepping on each other, I simply make sure they're cross-linked so that if I go looking for something, I'll be able to find it. Webmention definitely helps in this respect.

As an example you'll notice that my earlier response (http://stream.boffosocko.com/2021/roberthaisfield-i-agree-wholeheartedly-and-have-written-a-bit-about) links to part of the related commentary on my main site, so there will be a webmention in the comments there that ties it all together.

February 27, 2021 7:50pm +00:00

{
    "type": "entry",
    "published": "2021-02-27T19:50:42+00:00",
    "url": "http://stream.boffosocko.com/2021/cambridgeport90-i-dont-worry-about-them-stepping-on-each-other",
    "syndication": [
        "https://twitter.com/ChrisAldrich/status/1365751334381760514"
    ],
    "in-reply-to": [
        "https://twitter.com/Cambridgeport90/status/1365748410469523464",
        "http://stream.boffosocko.com/2021/roberthaisfield-i-agree-wholeheartedly-and-have-written-a-bit-about"
    ],
    "content": {
        "text": "@Cambridgeport90 I don't worry about them stepping on each other, I simply make sure they're cross-linked so that if I go looking for something, I'll be able to find it. Webmention definitely helps in this respect.\n\n\nAs an example you'll notice that my earlier response (http://stream.boffosocko.com/2021/roberthaisfield-i-agree-wholeheartedly-and-have-written-a-bit-about) links to part of the related commentary on my main site, so there will be a webmention in the comments there that ties it all together.",
        "html": "@Cambridgeport90 I don't worry about them stepping on each other, I simply make sure they're cross-linked so that if I go looking for something, I'll be able to find it. Webmention definitely helps in this respect.<br /><br />\nAs an example you'll notice that my earlier response (<a href=\"http://stream.boffosocko.com/2021/roberthaisfield-i-agree-wholeheartedly-and-have-written-a-bit-about\">http://stream.boffosocko.com/2021/roberthaisfield-i-agree-wholeheartedly-and-have-written-a-bit-about</a>) links to part of the related commentary on my main site, so there will be a webmention in the comments there that ties it all together."
    },
    "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": "18696082",
    "_source": "192",
    "_is_read": true
}

Manton Reece www.manton.org

How to blog about books

#Books #Essays

February 25, 2021 1:43pm -06:00

{
    "type": "entry",
    "author": {
        "name": "Manton Reece",
        "url": "https://www.manton.org/",
        "photo": "https://micro.blog/manton/avatar.jpg"
    },
    "url": "https://www.manton.org/2021/02/25/how-to-blog.html",
    "name": "How to blog about books",
    "content": {
        "html": "<p>First, there is no right way! Just type something about what you\u2019ve read or want to read, hit post, and you\u2019re good. However, we have built a few book-specific features in to Micro.blog that aren\u2019t obvious on first glance.</p>\n\n<p>My favorite is <a href=\"https://micro.blog/books/search\">the book search</a>. Enter an ISBN-13 or a book title and author, and Micro.blog will return a list of books it finds using <a href=\"https://openlibrary.org\">Open Library</a> and <a href=\"https://www.isbndb.com\">ISBNdb</a>. From there, you can click to automatically draft a post with the book title, link, and author. You can then add some commentary or just publish it as-is.</p>\n\n<p>Blog posts that contain the books emoji \ud83d\udcda will get collected in our Discover \u2192 Books collection. If the post includes a link to Micro.blog with the ISBN (<code>micro.blog/books/isbn-here</code>, added for you by the book search), then Micro.blog will also show the blog post on our <a href=\"https://micro.blog/discover/books/grid\">book covers grid</a>, which is another fun way to discover what people on Micro.blog are reading.</p>\n\n<p>A nice bonus with including \ud83d\udcda in your posts is that it\u2019s easy to tell Micro.blog to add all your book-related posts to a category on your blog. Click on Categories \u2192 Edit Filters and make a filter that assigns the Books category whenever a post contains that emoji.</p>\n\n<p>Micro.blog also supports <a href=\"https://indiebookclub.biz\">indiebookclub</a>. It uses the Micropub API to publish blog posts, and Micro.blog will format them so they are also included in the book covers and Discover collection.</p>\n\n<p>Personally, I\u2019ve been reading a lot the last few months. I\u2019ve also started to use Goodreads more, in addition to blogging about books I finish <a href=\"https://www.manton.org/categories/books/\">on my own site</a>, to better understand what additional features we could build around books for Micro.blog.</p>",
        "text": "First, there is no right way! Just type something about what you\u2019ve read or want to read, hit post, and you\u2019re good. However, we have built a few book-specific features in to Micro.blog that aren\u2019t obvious on first glance.\n\nMy favorite is the book search. Enter an ISBN-13 or a book title and author, and Micro.blog will return a list of books it finds using Open Library and ISBNdb. From there, you can click to automatically draft a post with the book title, link, and author. You can then add some commentary or just publish it as-is.\n\nBlog posts that contain the books emoji \ud83d\udcda will get collected in our Discover \u2192 Books collection. If the post includes a link to Micro.blog with the ISBN (micro.blog/books/isbn-here, added for you by the book search), then Micro.blog will also show the blog post on our book covers grid, which is another fun way to discover what people on Micro.blog are reading.\n\nA nice bonus with including \ud83d\udcda in your posts is that it\u2019s easy to tell Micro.blog to add all your book-related posts to a category on your blog. Click on Categories \u2192 Edit Filters and make a filter that assigns the Books category whenever a post contains that emoji.\n\nMicro.blog also supports indiebookclub. It uses the Micropub API to publish blog posts, and Micro.blog will format them so they are also included in the book covers and Discover collection.\n\nPersonally, I\u2019ve been reading a lot the last few months. I\u2019ve also started to use Goodreads more, in addition to blogging about books I finish on my own site, to better understand what additional features we could build around books for Micro.blog."
    },
    "published": "2021-02-25T13:43:20-06:00",
    "category": [
        "Books",
        "Essays"
    ],
    "post-type": "article",
    "_id": "18651689",
    "_source": "12",
    "_is_read": true
}

Manton Reece www.manton.org

Thinking back to IndieWebCamp

#Essays

February 25, 2021 11:46am -06:00

{
    "type": "entry",
    "author": {
        "name": "Manton Reece",
        "url": "https://www.manton.org/",
        "photo": "https://micro.blog/manton/avatar.jpg"
    },
    "url": "https://www.manton.org/2021/02/25/thinking-back-to.html",
    "name": "Thinking back to IndieWebCamp",
    "content": {
        "html": "<p><a href=\"https://micro.welltempered.net\">Jean</a> and I were talking this week about how it\u2019s been 1 year since IndieWebCamp Austin. That was the 3rd IndieWebCamp here, and after it wrapped up we were already talking about plans for 2021, excited to look at potential new spaces for the conference in Austin.</p>\n\n<p>Little did we know last year that IndieWebCamp Austin would be the last in-person IndieWeb event all year, for any city, with everything else cancelled or moved online because of COVID. If the Austin event had been even a couple weeks later, we probably would have cancelled it too, as the scope of COVID was just starting to be understood.</p>\n\n<p>Now a year later, a tragic 500,000 dead in the United States, vaccines are rolling out, and we are starting to see the light at the end of the tunnel. I think 2021 is going to be largely the same as 2020 in terms of events. WWDC will no doubt be online again too. But I can start to imagine that some in-person events and meetups will come back next year, although surely reimagined around safety. In the meantime there have been a number of <a href=\"https://events.indieweb.org\">online IndieWeb events</a>, both informal meetups and pop-up sessions around specific topics, like improving APIs.</p>\n\n<p>We are also thinking about what a Micro.blog-focused online conference might look like. It has been wonderful to watch the community grow, and there\u2019s so much we could do this year.</p>",
        "text": "Jean and I were talking this week about how it\u2019s been 1 year since IndieWebCamp Austin. That was the 3rd IndieWebCamp here, and after it wrapped up we were already talking about plans for 2021, excited to look at potential new spaces for the conference in Austin.\n\nLittle did we know last year that IndieWebCamp Austin would be the last in-person IndieWeb event all year, for any city, with everything else cancelled or moved online because of COVID. If the Austin event had been even a couple weeks later, we probably would have cancelled it too, as the scope of COVID was just starting to be understood.\n\nNow a year later, a tragic 500,000 dead in the United States, vaccines are rolling out, and we are starting to see the light at the end of the tunnel. I think 2021 is going to be largely the same as 2020 in terms of events. WWDC will no doubt be online again too. But I can start to imagine that some in-person events and meetups will come back next year, although surely reimagined around safety. In the meantime there have been a number of online IndieWeb events, both informal meetups and pop-up sessions around specific topics, like improving APIs.\n\nWe are also thinking about what a Micro.blog-focused online conference might look like. It has been wonderful to watch the community grow, and there\u2019s so much we could do this year."
    },
    "published": "2021-02-25T11:46:14-06:00",
    "category": [
        "Essays"
    ],
    "post-type": "article",
    "_id": "18646524",
    "_source": "12",
    "_is_read": true
}

Matthias Pfefferle notiz.blog/author/matthias-pfefferle/

Inventur

January 29, 2021 11:46am +01:00

{
    "type": "entry",
    "published": "2021-01-29T11:46:00+01:00",
    "url": "https://notiz.blog/2021/01/29/inventur/",
    "featured": "https://notiz.blog/wp-content/uploads/2021/02/wordpress-plugins-900x271.png",
    "name": "Inventur",
    "content": {
        "text": "Mein erstes WordPress Plugin hab ich vor mehr als 14 Jahren ver\u00f6ffentlicht und \u00fcber die Jahre sind eine ganze Menge, mehr oder weniger erfolgreiche, Plugins dazu gekommen\u2026 Zeit f\u00fcr eine Inventur \ud83d\ude42\n\n\n\nViele der Plugins schreibe ich in erster Linie f\u00fcr mich selbst (eat your own dogfood), weshalb ich in den wenigesten F\u00e4llen \u00fcber die Plugins spreche oder sie bewerbe. Das, in Verbindung mit meinen eher sp\u00e4rlichen Beschreibungen, sorgt oft f\u00fcr eher zweistellige, maximal dreistellige Download-Zahlen. Wo die Zahlen h\u00f6her sind, habe ich das Plugin meistens von Anderen \u00fcbernommen (um die Weiterentwicklung zu gew\u00e4hrleisten) oder ich bin einfach \u201enur\u201c Contributor.\n\n\n\nAber Schluss mit der falschen Bescheidenheit!\n\n\n\nSelbst wenn ich die Plugins f\u00fcr mich baue, ist die Motivation nat\u00fcrlich gr\u00f6\u00dfer, wenn sie auch von anderen benutzt werden. Also m\u00f6chte ich euch hier ein paar meiner Plugins vorstellen.\n\n\n\nActivityPub\n\n\n\nActivityPub ist ein, vom W3C ver\u00f6ffentlichtes, offenes, dezentrales Protokoll f\u00fcr soziale Netzwerke.\n\n\n\n\nThe ActivityPub protocol is a decentralized social networking protocol based upon the [ActivityStreams] 2.0 data format. It provides a client to server API for creating, updating and deleting content, as well as a federated server to server API for delivering notifications and content.\nhttps://www.w3.org/TR/activitypub/\n\n\n\n\nEs erm\u00f6glicht das dezentrale kommunizieren \u00fcber Text, Bild, Video und Audio \u00fcber ein simples Inbox/Outbox Prinzip.\n\n\n\nWebFinger Plugin\n\n\n\nWebFinger ist kein fester Bestandteil von ActivityPub, wird aber von allen gro\u00dfen Netzwerken unterst\u00fctzt und von Mastodon sogar verlangt. WebFinger ist eine Art Meta-Data System f\u00fcr alle m\u00f6glichen URIs. Der g\u00e4ngige Identifier im Fediverse ist @username@domain.tld, das Plugin erlaubt aber auch die Author URL oder die Instant-Messaging Accounts eines Users, wenn diese unter der gleichen Domain erreichbar sind.\n\n\n\nMein Identifier ist Beispielsweise pfefferle@notiz.blog und die Meta-Daten k\u00f6nnen \u00fcber folgenden API-Endpunkt abgerufen werden: https://notiz.blog/.well-known/webfinger?resource=acct%3Apfefferle%40notiz.blog\n\n\n\nWebFinger auf WordPress.org\nWebFinger auf GitHub\nNodeInfo Plugin\n\n\n\nNodeInfo (2) ist auch kein fester Bestandteil von ActivityPub, wird aber auch von den Meisten Netzwerken unterst\u00fctzt. NodeInfo stellt, wie der Name schon sagt, Infos \u00fcber einen \u201eNode\u201c (Server) bereit. Dank NodeInfo gibt es eine ganze Reihe an Statistik-Seiten wie the-federation.info, die bei der Auswahl der richtigen Plattform bzw. des richtigen Servers helfen.\n\n\n\nNodeInfo auf WordPress.org\nNodeInfo auf GitHub\nActivityPub Plugin\n\n\n\nDas eigentliche ActivityPub Plugin macht WordPress zu einem (kleinen) Teil des Fediverse. User von Mastodon, Pleroma, Friendi.ca oder Pixelfed k\u00f6nnen dem Blog \u201efolgen\u201c und sehen ab dann alle neuen Blog-Posts in ihrer Timeline und k\u00f6nnen diese kommentieren. Das Plugin ist immernoch in einem fr\u00fchen Stadium und bekommt sicherlich noch das ein oder andere Feature, im Fokus soll aber das Bloggen stehen. Wer ein vollwertiges, dezentrales, soziales Netzwerk m\u00f6chte, sollte sich erstmal f\u00fcr eine der oben genannten Plattformen entscheiden.\n\n\n\nActivityPub auf WordPress.org\nActivityPub auf GitHub\nIndieWeb\n\n\n\nDas IndieWeb ist eine Grassroots Bewegung mit dem Ziel, die eigene Webseite als zentralen Kommunikations-Hub zu nutzen.\n\n\n\n\nThe IndieWeb is a community of individual personal websites, connected by simple standards, based on the principles of owning your domain, using it as your primary identity, to publish on your own site (optionally syndicate elsewhere), and own your data.\nhttps://indieweb.org/IndieWeb\n\n\n\n\nMehr zum IndieWeb findet ihr hier oder unter dem Tag \u201eindieweb\u201c hier im Blog.\n\n\n\nIndieWeb Plugin\n\n\n\nDas IndieWeb Plugin hat nahezu keine Funktionalit\u00e4t, es ist vielmehr eine Art Installer um die IndieWeb Plugins \u00fcber eine zentrale Stelle verwalten zu k\u00f6nnen. \n\n\n\nEs gibt immer wieder Kritik am Aufbau des Plugins, bzw. kommt immer wieder die Frage auf, warum das Plugin nicht einfach die komplette Funktionalit\u00e4t der einzelnen Plugins beinhaltet. Meine Antwort darauf: Das IndieWeb ist mehr eine Idee als eine Spezifikation und es gibt verschiedene M\u00f6glichkeiten diese Idee mit WordPress umzusetzen. F\u00fcr einen Usecase gibt es also oft verschiedene L\u00f6sungen, die von verschiedenen Personen entwickelt werden. Ein IndieWeb Plugin im Stil von ActivityPub ist in meinen Augen nicht m\u00f6glich. Ich lasse mich aber gerne eines besseren belehren \ud83d\ude09\n\n\n\nIndieWeb auf WordPress.org\nIndieWeb auf GitHub\nWebmention Plugin\n\n\n\nWebmentions sind eine moderne Alternative zu Pingbacks und Trackbacks. Im Gegensatz zu der eher ungl\u00fccklichen Darstellung von Pingbacks ([...] super, wie war nochmal der kontext, oder [...]) versucht das IndieWeb (\u00fcber Webmentions und Microformats), den Sinn und die Art einer Verlinkung heraus zu bekommen um die Reaktion dann als Like, Bookmark oder vollwertiges Kommentar anzuzeigen.\n\n\n\nDas Webmention Plugin implementiert aktuell nur den Kommunikations-Teil, f\u00fcr das Interpretieren der Websemantiken ben\u00f6tigt ihr zus\u00e4tzlich das \u201eSemantic Linkbacks\u201c Plugin.\n\n\n\nMehr \u00fcber Webmentions hier oder unter dem \u201ewebmention\u201c Tag hier im Blog.\n\n\n\nWebmention auf WordPress.org\nWebmention auf GitHub\nSemantic Linkbacks Plugin\n\n\n\nWie oben beschrieben sorgt das Semantic Linkbacks Plugin f\u00fcr die h\u00fcbsche Darstellung der Webmentions, Pingbacks und Trackbacks. Wir sind gerade dabei, die Funktionalit\u00e4t in das Webmention Plugin zu \u00fcbertragen, deshalb hat das Plugin aber nur noch tempor\u00e4r Bedeutung.\n\n\n\nSemantic Linkbacks auf WordPress.org\nSemantic Linkbacks auf GitHub\nWebSub Plugin\n\n\n\nWebSub (formerly known as: PubSubHubbub) ist ein simples PubSub Protokoll f\u00fcr das Web. Es wurde urspr\u00fcnglich entwickelt um updates von RSS und Atom Feeds in \u201eechtzeit\u201c zu konsumieren. Push statt pull. Die Restriktion auf RSS und Atom, wurde mit der aktuellen Version aufgehoben.\n\n\n\n\nWebSub provides a common mechanism for communication between publishers of any kind of Web content and their subscribers, based on HTTP web hooks. Subscription requests are relayed through hubs, which validate and verify the request. Hubs then distribute new and updated content to subscribers when it becomes available. WebSub was previously known as PubSubHubbub.\nhttps://www.w3.org/TR/websub/\n\n\n\n\n\u00dcber das WebSub Plugin (urspr\u00fcnglich entwickelt von Josh Fraser) kann man die Standard-Feeds von WordPress abonnieren. Das Plugin kann aber auch \u00fcber andere Plugins und Themes erweitert werden.\n\n\n\nWebSub auf WordPress.org\nWebSub auf GitHub\nMF2 Feed Plugin\n\n\n\nDas IndieWeb setzt im, Gegensatz zum Fediverse, nicht auf APIs, sondern auf Semantisches HTML:\n\n\n\n\nThe idea is rather than publishing something twice (repeating yourself) with (x)HTML for browsers and XML for aggregators \u2013 you simply publish once using (x)HTML and allow the tools to take care of the rest.\nhttp://microformats.org/wiki/dry\n\n\n\n\nIn einer Welt in der jeder WordPress Theme Developer Wert auf Microformats, Schema.org oder \u00c4hnliches achtet, funktioniert das Konzept super. Die Erfahrung zeigt aber, dass nur wenige Themes (seit fast 9 Jahren eigentlich sogar nur ein Theme) im WordPress.org Repo Microformats2 unterst\u00fctzt.\n\n\n\nIch habe viel herum experimentiert um Themes \u00fcber ein Plugin mit den n\u00f6tigen Semantiken zu erweitern, was aber, durch Output Escaping, zu komischen Nebeneffekten gef\u00fchrt hat (das alles aber nur der Vollst\u00e4ndigkeit halber, das Thema ist eigentlich einen ganzen Artikel wert).\n\n\n\nLetztendlich haben wir f\u00fcr WordPress ein Plugin gebaut, das einen Feed bereit stellt, der genau dem JSON Format entspricht, welches auch die Microformats Parser ausspucken. Das Webmention Plugin sucht also erst den pre-parsed Feed und versucht erst im zweiten Schritt, die Seite selbst zu parsen.\n\n\n\nIhr versteht die Ironie? Microformats(2) sind geschaffen worden um XML/JSON APIs abzul\u00f6sen und weil das bei WordPress nicht wirklich dolle funktioniert bieten wir die Infos als JSON API an! \ud83d\ude00\n\n\n\nMF2 feed auf WordPress.org\nMF2 feed auf GitHub\nDecisions, not Options\n\n\n\nIch bin ein Freund von kleinen Plugins die nur einen spezifischen Anwendungsfall abdecken und im besten Fall auch vollkommen ohne Settings aus kommen. Frei nach dem Motto von WordPress:\n\n\n\n\nWhen making decisions these are the users we consider first. A great example of this consideration is software options. Every time you give a user an option, you are asking them to make a decision. When a user doesn\u2019t care or understand the option this ultimately leads to frustration.\nhttps://wordpress.org/about/philosophy/#decisions\n\n\n\n\n(Ironischerweise f\u00fchrt aber gerade das Fehlen von Settings oft f\u00fcr Verwirrung \ud83d\ude09 )\n\n\n\nOpenGraph Plugin\n\n\n\nDas Open Graph Protokoll wurde von Facebook entwickelt und hat einen \u00e4hnlichen Nutzen wie oEmbed:\n\n\n\n\nThe Open Graph protocol enables any web page to become a rich object in a social graph. For instance, this is used on Facebook to allow any web page to have the same functionality as any other object on Facebook.\nhttps://ogp.me\n\n\n\n\nEs wird aktuell von fast jedem gro\u00dfen Netzwerk oder fast jeder Messaging App benutzt und sorgt daf\u00fcr, dass ihr die kleinen h\u00fcbschen Vorschausnippets seht, wenn ihr einen Link mit euren Freunden teilt.\n\n\n\nDas OpenGraph Plugin wurde urspr\u00fcnglich von Will Norris geschrieben und generiert alle notwendigen Meta-Tag Header. Keine Settings, keine Entscheidungen, aber mit wohl definierten Filtern zum erweitern.\n\n\n\nOpenGraph auf WordPress.org\nOpenGraph auf GitHub\nHum Plugin\n\n\n\nHum generiert sch\u00f6ne, semantische Short-URLs f\u00fcr WordPress Posts und Pages. Das Plugin ist urspr\u00fcnglich auch von Will Norris, integriert sich in die WordPress Core-Funktionen und kommt auch komplett ohne Settings aus.\n\n\n\nHum basiert auf Whistle\u2026\n\n\n\n\nWhistle is an open source, algorithmically reversible, personal URL shortener.\nhttp://tantek.pbworks.com/w/page/21743973/Whistle\n\n\n\n\n\u2026und New Base 60\u2026\n\n\n\n\nA base 60 numbering system using only ASCII numbers and letters.\nor\na side effect of building a personal URL shortener\nhttp://tantek.pbworks.com/w/page/19402946/NewBase60\n\n\n\n\n\u2026zwei Specs von Tantek \u00c7elik.\n\n\n\nHum auf WordPress.org\nHum auf GitHub\nOpen Search Document Plugin\n\n\n\nDie OpenSearch Spezifikation bietet M\u00f6glichkeiten um die lokale Blog-Suche f\u00fcr Browser oder Suchmaschinen zug\u00e4nglich zu machen.\n\n\n\n\nOpenSearch is a collection of simple formats for the sharing of search results.\nhttps://github.com/dewitt/opensearch\n\n\n\n\nEs gibt Integrationen f\u00fcr alle bekannten Browser wie z.B. Chrome, Safari, Firefox und Microsoft Edge.\n\n\n\nDas Plugin wurde urspr\u00fcnglich von johnnoone Entwickelt, es stellt eine XML Beschreibung der Suche und einen Endpunkt f\u00fcr Such-Vorschl\u00e4ge basierend auf Tags bereit.\n\n\n\nDas wars auch schon \ud83d\ude42\n\n\n\nOpen Search Document auf WordPress.org\n\nOpen Search Document auf GitHub\nMehr?\n\n\n\nNat\u00fcrlich gibt es noch mehr, das w\u00fcrde aber den Rahmen sprengen. Ich nutze WordPress gerne um neue Specs und Ideen auszuprobieren und daraus entstehen meist kleine Plugins, die es oft nicht wert sind, auf WordPress.org ver\u00f6ffentlichen zu werden.\n\n\n\nIhr k\u00f6nnt aber gerne:\n\n\n\neinen Blick auf mein WordPress.org Profil werfen\noder auf GitHub suchen.\nIhr k\u00f6nnt fast alle Plugins auch bequem \u00fcber Composer installieren und updaten.\n\n\n\nIch freue mich IMMER \u00fcber Hilfe, also feel free to contribute!",
        "html": "<p>Mein erstes WordPress Plugin hab ich vor mehr als <a href=\"https://plugins.trac.wordpress.org/browser/simple-cocomments/trunk/simple_coco.php?rev=9246\">14 Jahren ver\u00f6ffentlicht</a> und \u00fcber die Jahre sind <a href=\"https://profiles.wordpress.org/pfefferle/#content-plugins\">eine ganze Menge, mehr oder weniger erfolgreiche, Plugins</a> dazu gekommen\u2026 Zeit f\u00fcr eine Inventur \ud83d\ude42</p>\n\n\n\n<p>Viele der Plugins schreibe ich in erster Linie f\u00fcr mich selbst (<a href=\"https://indieweb.org/selfdogfood\">eat your own dogfood</a>), weshalb ich in den wenigesten F\u00e4llen \u00fcber die Plugins spreche oder sie bewerbe. Das, in Verbindung mit meinen eher sp\u00e4rlichen Beschreibungen, sorgt oft f\u00fcr eher zweistellige, maximal dreistellige Download-Zahlen. Wo die Zahlen h\u00f6her sind, habe ich das Plugin meistens von Anderen \u00fcbernommen (um die Weiterentwicklung zu gew\u00e4hrleisten) oder ich bin einfach \u201enur\u201c Contributor.</p>\n\n\n\n<p>Aber Schluss mit der falschen Bescheidenheit!</p>\n\n\n\n<p>Selbst wenn ich die Plugins f\u00fcr mich baue, ist die Motivation nat\u00fcrlich gr\u00f6\u00dfer, wenn sie auch von anderen benutzt werden. Also m\u00f6chte ich euch hier ein paar meiner Plugins vorstellen.</p>\n\n\n\n<h2>ActivityPub</h2>\n\n\n\n<p><a href=\"https://www.w3.org/TR/activitypub/\">ActivityPub</a> ist ein, vom <a href=\"https://www.w3.org/\">W3C</a> ver\u00f6ffentlichtes, offenes, dezentrales Protokoll f\u00fcr soziale Netzwerke.</p>\n\n\n\n<blockquote>\n<p>The ActivityPub protocol is a decentralized social networking protocol based upon the [<a href=\"https://www.w3.org/TR/activitypub/#bib-ActivityStreams\">ActivityStreams</a>] 2.0 data format. It provides a client to server API for creating, updating and deleting content, as well as a federated server to server API for delivering notifications and content.</p>\nhttps://www.w3.org/TR/activitypub/\n</blockquote>\n\n\n\n<img width=\"765\" height=\"360\" src=\"https://notiz.blog/wp-content/uploads/2019/01/activitypub-flow.png\" alt=\"\" /><p>Es erm\u00f6glicht das dezentrale kommunizieren \u00fcber Text, Bild, Video und Audio \u00fcber ein simples Inbox/Outbox Prinzip.</p>\n\n\n\n<h3>WebFinger Plugin</h3>\n\n\n\n<p><a href=\"https://webfinger.net/\">WebFinger</a> ist kein fester Bestandteil von ActivityPub, wird aber von allen gro\u00dfen Netzwerken unterst\u00fctzt und von Mastodon sogar verlangt. WebFinger ist eine Art Meta-Data System f\u00fcr alle m\u00f6glichen URIs. Der g\u00e4ngige Identifier im Fediverse ist <code>@username@domain.tld</code>, das Plugin erlaubt aber auch die Author URL oder die Instant-Messaging Accounts eines Users, wenn diese unter der gleichen Domain erreichbar sind.</p>\n\n\n\n<p>Mein Identifier ist Beispielsweise <code>pfefferle@notiz.blog</code> und die Meta-Daten k\u00f6nnen \u00fcber folgenden API-Endpunkt abgerufen werden: <a href=\"https://notiz.blog/.well-known/webfinger?resource=acct%3Apfefferle%40notiz.blog\">https://notiz.blog/.well-known/webfinger?resource=acct%3Apfefferle%40notiz.blog</a></p>\n\n\n\n<ul><li><a href=\"https://wordpress.org/plugins/webfinger/\">WebFinger auf WordPress.org</a></li>\n<li><a href=\"https://github.com/pfefferle/wordpress-webfinger\">WebFinger auf GitHub</a></li>\n</ul><h3>NodeInfo Plugin</h3>\n\n\n\n<p><a href=\"https://nodeinfo.diaspora.software/\">NodeInfo</a> (<a href=\"https://git.feneas.org/jaywink/nodeinfo2\">2</a>) ist auch kein fester Bestandteil von ActivityPub, wird aber auch von den Meisten Netzwerken unterst\u00fctzt. NodeInfo stellt, wie der Name schon sagt, Infos \u00fcber einen \u201eNode\u201c (Server) bereit. Dank NodeInfo gibt es eine ganze Reihe an Statistik-Seiten wie <a href=\"https://the-federation.info\">the-federation.info</a>, die bei der Auswahl der <strong>richtigen</strong> Plattform bzw. des <strong>richtigen</strong> Servers helfen.</p>\n\n\n\n<ul><li><a href=\"https://wordpress.org/plugins/nodeinfo/\">NodeInfo auf WordPress.org</a></li>\n<li><a href=\"https://github.com/pfefferle/wordpress-nodeinfo\">NodeInfo auf GitHub</a></li>\n</ul><h3>ActivityPub Plugin</h3>\n\n\n\n<p>Das eigentliche ActivityPub Plugin macht WordPress zu einem (kleinen) Teil des <a href=\"https://en.wikipedia.org/wiki/Fediverse\">Fediverse</a>. User von <a href=\"https://notiz.blog/2020/12/31/activitypub-fuer-wordpress/\">Mastodon, Pleroma, Friendi.ca oder Pixelfed</a> k\u00f6nnen dem Blog \u201efolgen\u201c und sehen ab dann alle neuen Blog-Posts in ihrer Timeline und k\u00f6nnen diese kommentieren. Das Plugin ist immernoch in einem fr\u00fchen Stadium und bekommt sicherlich noch das ein oder andere Feature, im Fokus soll aber das Bloggen stehen. Wer ein vollwertiges, dezentrales, soziales Netzwerk m\u00f6chte, sollte sich erstmal f\u00fcr eine der oben genannten Plattformen entscheiden.</p>\n\n\n\n<ul><li><a href=\"https://wordpress.org/plugins/activitypub/\">ActivityPub auf WordPress.org</a></li>\n<li><a href=\"https://github.com/pfefferle/wordpress-activitypub\">ActivityPub auf GitHub</a></li>\n</ul><h2>IndieWeb</h2>\n\n\n\n<img src=\"https://notiz.blog/wp-content/uploads/2021/02/indie-wapuu-with-text-598x660-1.png\" alt=\"\" width=\"299\" height=\"330\" />\n\n\n\n<p>Das <a href=\"https://indieweb.org/\">IndieWeb</a> ist eine <a href=\"https://de.wikipedia.org/wiki/Graswurzelbewegung\">Grassroots</a> Bewegung mit dem Ziel, die eigene Webseite als zentralen Kommunikations-Hub zu nutzen.</p>\n\n\n\n<blockquote>\n<p>The <strong>IndieWeb</strong> is a community of individual personal websites, connected by simple standards, based on the <strong><a href=\"https://indieweb.org/principles\">principles</a></strong> of <strong><a href=\"https://indieweb.org/personal-domain\">owning your domain</a></strong>, using it as <strong><a href=\"https://indieweb.org/How_to_set_up_web_sign-in_on_your_own_domain\">your primary identity</a></strong>, to <strong><a href=\"https://indieweb.org/POSSE\">publish on your own site</a></strong> (optionally syndicate elsewhere), and <strong><a href=\"https://indieweb.org/ownyourdata\">own your data</a></strong>.</p>\nhttps://indieweb.org/IndieWeb\n</blockquote>\n\n\n\n<p>Mehr zum IndieWeb findet ihr <a href=\"https://notiz.blog/2013/06/18/the-rise-of-the-indieweb/\">hier</a> oder unter dem Tag \u201e<a href=\"https://notiz.blog/tag/indieweb/\">indieweb</a>\u201c hier im Blog.</p>\n\n\n\n<h3>IndieWeb Plugin</h3>\n\n\n\n<p>Das IndieWeb Plugin hat nahezu keine Funktionalit\u00e4t, es ist vielmehr eine Art <em>Installer</em> um die IndieWeb Plugins \u00fcber eine zentrale Stelle verwalten zu k\u00f6nnen. </p>\n\n\n\n<p>Es gibt immer wieder Kritik am Aufbau des Plugins, bzw. kommt immer wieder die Frage auf, warum das Plugin nicht einfach die komplette Funktionalit\u00e4t der einzelnen Plugins beinhaltet. Meine Antwort darauf: Das IndieWeb ist mehr eine Idee als eine Spezifikation und es gibt verschiedene M\u00f6glichkeiten diese Idee mit WordPress umzusetzen. F\u00fcr einen Usecase gibt es also oft verschiedene L\u00f6sungen, die von verschiedenen Personen entwickelt werden. Ein IndieWeb Plugin im Stil von ActivityPub ist in meinen Augen nicht m\u00f6glich. Ich lasse mich aber gerne eines besseren belehren \ud83d\ude09</p>\n\n\n\n<ul><li><a href=\"https://wordpress.org/plugins/indieweb/\">IndieWeb auf WordPress.org</a></li>\n<li><a href=\"https://github.com/indieweb/wordpress-indieweb\">IndieWeb auf GitHub</a></li>\n</ul><h3>Webmention Plugin</h3>\n\n\n\n<p>Webmentions sind eine moderne Alternative zu Pingbacks und Trackbacks. Im Gegensatz zu der eher ungl\u00fccklichen Darstellung von Pingbacks (<code><code>[...] super, wie war nochmal der kontext, oder [...]</code></code>) versucht das IndieWeb (\u00fcber Webmentions und <a href=\"https://notiz.blog/tag/microformats\">Microformats</a>), den Sinn und die Art einer Verlinkung heraus zu bekommen um die Reaktion dann als Like, Bookmark oder vollwertiges Kommentar anzuzeigen.</p>\n\n\n\n<p>Das Webmention Plugin implementiert <strong>aktuell</strong> nur den Kommunikations-Teil, f\u00fcr das Interpretieren der Websemantiken ben\u00f6tigt ihr zus\u00e4tzlich das \u201eSemantic Linkbacks\u201c Plugin.</p>\n\n\n\n<p>Mehr \u00fcber Webmentions <a href=\"https://notiz.blog/2013/07/08/die-renaissance-des-pingbacks/\">hier</a> oder unter dem \u201e<a href=\"https://notiz.blog/tag/webmention/\">webmention</a>\u201c Tag hier im Blog.</p>\n\n\n\n<ul><li><a href=\"https://wordpress.org/plugins/webmention/\">Webmention auf WordPress.org</a></li>\n<li><a href=\"https://github.com/pfefferle/wordpress-webmention\">Webmention auf GitHub</a></li>\n</ul><h3>Semantic Linkbacks Plugin</h3>\n\n\n\n<p>Wie oben beschrieben sorgt das <em>Semantic Linkbacks</em> Plugin f\u00fcr die h\u00fcbsche Darstellung der Webmentions, Pingbacks und Trackbacks. Wir sind gerade dabei, die Funktionalit\u00e4t in das Webmention Plugin zu \u00fcbertragen, deshalb hat das Plugin aber nur noch tempor\u00e4r Bedeutung.</p>\n\n\n\n<ul><li><a href=\"https://wordpress.org/plugins/semantic-linkbacks/\">Semantic Linkbacks auf WordPress.org</a></li>\n<li><a href=\"https://github.com/pfefferle/wordpress-semantic-linkbacks\">Semantic Linkbacks auf GitHub</a></li>\n</ul><h3>WebSub Plugin</h3>\n\n\n\n<p><a href=\"https://www.w3.org/TR/websub/\">WebSub</a> (formerly known as: <a href=\"https://notiz.blog/2010/01/13/are-we-there-yet/\">PubSubHubbub</a>) ist ein simples PubSub Protokoll f\u00fcr das Web. Es wurde urspr\u00fcnglich entwickelt um updates von RSS und Atom Feeds in \u201eechtzeit\u201c zu konsumieren. Push statt pull. Die Restriktion auf RSS und Atom, wurde mit der aktuellen Version aufgehoben.</p>\n\n\n\n<blockquote>\n<p>WebSub provides a common mechanism for communication between publishers of any kind of Web content and their subscribers, based on HTTP web hooks. Subscription requests are relayed through hubs, which validate and verify the request. Hubs then distribute new and updated content to subscribers when it becomes available. WebSub was previously known as PubSubHubbub.</p>\nhttps://www.w3.org/TR/websub/\n</blockquote>\n\n\n\n<p>\u00dcber das WebSub Plugin (urspr\u00fcnglich entwickelt von <a href=\"https://twitter.com/joshfraz\">Josh Fraser</a>) kann man die Standard-Feeds von WordPress abonnieren. Das Plugin kann aber auch \u00fcber andere Plugins und Themes erweitert werden.</p>\n\n\n\n<ul><li><a href=\"https://wordpress.org/plugins/pubsubhubbub/\">WebSub auf WordPress.org</a></li>\n<li><a href=\"https://github.com/pubsubhubbub/wordpress-pubsubhubbub\">WebSub auf GitHub</a></li>\n</ul><h3>MF2 Feed Plugin</h3>\n\n\n\n<p>Das IndieWeb setzt im, Gegensatz zum Fediverse, nicht auf APIs, sondern auf Semantisches HTML:</p>\n\n\n\n<blockquote>\n<p>The idea is rather than publishing something twice (repeating yourself) with (x)HTML for browsers and XML for aggregators \u2013 you simply publish once using (x)HTML and allow the tools to take care of the rest.</p>\n<a href=\"http://microformats.org/wiki/dry\">http://microformats.org/wiki/dry</a>\n</blockquote>\n\n\n\n<img src=\"https://notiz.blog/wp-content/uploads/2006/11/microformats.jpg\" alt=\"\" />\n\n\n\n<p>In einer Welt in der jeder <em>WordPress Theme Developer</em> Wert auf Microformats, Schema.org oder \u00c4hnliches achtet, funktioniert das Konzept super. Die Erfahrung zeigt aber, dass nur wenige Themes (<a href=\"https://notiz.blog/2019/08/16/the-first-microformats2-wp-theme/\">seit fast 9 Jahren eigentlich sogar nur ein Theme</a>) im <a href=\"https://wordpress.org/themes/search/microformats+v2/\">WordPress.org Repo Microformats2</a> unterst\u00fctzt.</p>\n\n\n\n<p>Ich habe viel herum experimentiert um Themes \u00fcber ein <a href=\"https://wordpress.org/plugins/wp-uf2/\">Plugin</a> mit den n\u00f6tigen Semantiken zu erweitern, was aber, durch Output Escaping, zu <a href=\"https://github.com/indieweb/wordpress-uf2/issues/41\">komischen Nebeneffekten</a> gef\u00fchrt hat (das alles aber nur der Vollst\u00e4ndigkeit halber, das Thema ist eigentlich einen ganzen Artikel wert).</p>\n\n\n\n<p>Letztendlich haben wir f\u00fcr WordPress ein Plugin gebaut, das einen Feed bereit stellt, der genau dem JSON Format entspricht, welches auch die Microformats Parser ausspucken. Das Webmention Plugin sucht also erst den pre-parsed Feed und versucht erst im zweiten Schritt, die Seite selbst zu parsen.</p>\n\n\n\n<p>Ihr versteht die Ironie? Microformats(2) sind geschaffen worden um XML/JSON APIs abzul\u00f6sen und weil das bei WordPress nicht wirklich dolle funktioniert bieten wir die Infos als JSON API an! \ud83d\ude00</p>\n\n\n\n<ul><li><a href=\"https://wordpress.org/plugins/mf2-feed/\">MF2 feed auf WordPress.org</a></li>\n<li><a href=\"https://github.com/indieweb/wordpress-mf2-feed\">MF2 feed auf GitHub</a></li>\n</ul><h2>Decisions, not Options</h2>\n\n\n\n<p>Ich bin ein Freund von kleinen Plugins die nur einen spezifischen Anwendungsfall abdecken und im besten Fall auch vollkommen ohne Settings aus kommen. Frei nach dem Motto von WordPress:</p>\n\n\n\n<blockquote>\n<p>When making decisions these are the users we consider first. A great example of this consideration is software options. Every time you give a user an option, you are asking them to make a decision. When a user doesn\u2019t care or understand the option this ultimately leads to frustration.</p>\n<a href=\"https://wordpress.org/about/philosophy/#decisions\">https://wordpress.org/about/philosophy/#decisions</a>\n</blockquote>\n\n\n\n<p>(<a href=\"https://wordpress.org/support/topic/it-does-absolutely-nothing/\">Ironischerweise f\u00fchrt aber gerade das Fehlen von Settings oft f\u00fcr Verwirrung</a> \ud83d\ude09 )</p>\n\n\n\n<h3>OpenGraph Plugin</h3>\n\n\n\n<p>Das <a href=\"https://ogp.me/\">Open Graph Protokoll</a> wurde von Facebook entwickelt und hat einen \u00e4hnlichen Nutzen wie <a href=\"https://oembed.com/\">oEmbed</a>:</p>\n\n\n\n<blockquote>\n<p>The <a href=\"https://ogp.me/\">Open Graph protocol</a> enables any web page to become a rich object in a social graph. For instance, this is used on Facebook to allow any web page to have the same functionality as any other object on Facebook.</p>\n<a href=\"https://ogp.me\">https://ogp.me</a>\n</blockquote>\n\n\n\n<p>Es wird aktuell von fast jedem gro\u00dfen Netzwerk oder fast jeder Messaging App benutzt und sorgt daf\u00fcr, dass ihr die kleinen h\u00fcbschen Vorschausnippets seht, wenn ihr einen Link mit euren Freunden teilt.</p>\n\n\n\n<p>Das OpenGraph Plugin wurde urspr\u00fcnglich von <a href=\"https://willnorris.com/\">Will Norris</a> geschrieben und generiert alle notwendigen Meta-Tag Header. Keine Settings, keine Entscheidungen, aber mit wohl definierten Filtern zum erweitern.</p>\n\n\n\n<ul><li><a href=\"https://wordpress.org/plugins/opengraph/\">OpenGraph auf WordPress.org</a></li>\n<li><a href=\"https://github.com/willnorris/wordpress-opengraph\">OpenGraph auf GitHub</a></li>\n</ul><h3>Hum Plugin</h3>\n\n\n\n<p>Hum generiert sch\u00f6ne, semantische Short-URLs f\u00fcr WordPress Posts und Pages. Das Plugin ist urspr\u00fcnglich auch von Will Norris, integriert sich in die WordPress Core-Funktionen und kommt auch komplett ohne Settings aus.</p>\n\n\n\n<p>Hum basiert auf <a href=\"http://tantek.pbworks.com/w/page/21743973/Whistle\">Whistle</a>\u2026</p>\n\n\n\n<blockquote>\n<p>Whistle is an open source, <em><strong>algorithmically reversible, personal URL</strong></em> shortener.</p>\n<a href=\"http://tantek.pbworks.com/w/page/21743973/Whistle\">http://tantek.pbworks.com/w/page/21743973/Whistle</a>\n</blockquote>\n\n\n\n<p>\u2026und <a href=\"http://tantek.pbworks.com/w/page/19402946/NewBase60\">New Base 60</a>\u2026</p>\n\n\n\n<blockquote>\n<p>A base 60 numbering system using only ASCII numbers and letters.<br />or<br />a side effect of building a personal URL shortener</p>\n<a href=\"http://tantek.pbworks.com/w/page/19402946/NewBase60\">http://tantek.pbworks.com/w/page/19402946/NewBase60</a>\n</blockquote>\n\n\n\n<p>\u2026zwei Specs von <a href=\"https://tantek.com/\">Tantek \u00c7elik</a>.</p>\n\n\n\n<ul><li><a href=\"https://wordpress.org/plugins/hum/\">Hum auf WordPress.org</a></li>\n<li><a href=\"https://github.com/willnorris/wordpress-hum\">Hum auf GitHub</a></li>\n</ul><h3>Open Search Document Plugin</h3>\n\n\n\n<p>Die OpenSearch Spezifikation bietet M\u00f6glichkeiten um die lokale Blog-Suche f\u00fcr Browser oder Suchmaschinen zug\u00e4nglich zu machen.</p>\n\n\n\n<blockquote>\n<p>OpenSearch is a collection of simple formats for the sharing of search results.</p>\n<a href=\"https://github.com/dewitt/opensearch\">https://github.com/dewitt/opensearch</a>\n</blockquote>\n\n\n\n<p>Es gibt Integrationen f\u00fcr alle bekannten Browser wie z.B. <a href=\"https://www.chromium.org/tab-to-search\">Chrome</a>, <a href=\"https://developer.apple.com/library/archive/releasenotes/General/WhatsNewInSafari/Articles/Safari_8_0.html\">Safari</a>, <a href=\"https://developer.mozilla.org/de/docs/OpenSearch_Plugin_f%C3%BCr_Firefox_erstellen\">Firefox</a> und <a href=\"https://support.microsoft.com/de-de/microsoft-edge/%C3%A4ndern-der-standardsuchmaschine-f863c519-5994-a8ed-6859-00fbc123b782\">Microsoft Edge</a>.</p>\n\n\n\n<p>Das Plugin wurde urspr\u00fcnglich von <a href=\"https://profiles.wordpress.org/johnnoone/\">johnnoone</a> Entwickelt, es stellt eine XML Beschreibung der Suche und einen Endpunkt f\u00fcr Such-Vorschl\u00e4ge basierend auf Tags bereit.</p>\n\n\n\n<p>Das wars auch schon \ud83d\ude42</p>\n\n\n\n<ul><li><a href=\"https://wordpress.org/plugins/open-search-document/\">Open Search Document auf WordPress.org</a></li>\n<li>\n<a href=\"https://github.com/pfefferle/wordpress-open-search-document\"></a><a href=\"https://wordpress.org/plugins/open-search-document/\">Open Search Document</a> auf GitHub</li>\n</ul><h2>Mehr?</h2>\n\n\n\n<p>Nat\u00fcrlich gibt es noch mehr, das w\u00fcrde aber den Rahmen sprengen. Ich nutze WordPress gerne um neue <a href=\"https://github.com/pfefferle/wordpress-twtxt\">Specs</a> und <a href=\"https://github.com/pfefferle/wordpress-hashtags\">Ideen</a> auszuprobieren und daraus entstehen meist kleine Plugins, die es oft nicht wert sind, auf WordPress.org ver\u00f6ffentlichen zu werden.</p>\n\n\n\n<p>Ihr k\u00f6nnt aber gerne:</p>\n\n\n\n<ul><li>einen Blick auf mein <a href=\"https://profiles.wordpress.org/pfefferle/\">WordPress.org Profil</a> werfen</li>\n<li>oder auf <a href=\"https://github.com/search?q=topic%3Awordpress-plugin+user%3Apfefferle+org%3Aindieweb+org%3Aapml+org%3Adiso+org%3Apubsubhubbub&amp;type=Repositories&amp;ref=advsearch&amp;l=&amp;l=\">GitHub suchen</a>.</li>\n</ul><p>Ihr k\u00f6nnt fast alle Plugins auch bequem \u00fcber Composer installieren und updaten.</p>\n\n\n\n<p>Ich freue mich IMMER \u00fcber Hilfe, also <strong>feel free to contribute</strong>!</p>"
    },
    "author": {
        "type": "card",
        "name": "Matthias Pfefferle",
        "url": "https://notiz.blog/author/matthias-pfefferle/",
        "photo": "https://secure.gravatar.com/avatar/75512bb584bbceae57dfc503692b16b2?s=40&d=mm&r=g"
    },
    "post-type": "note",
    "_id": "18578934",
    "_source": "206",
    "_is_read": true
}

fluffy beesbuzz.biz

fluffy rambles: Where I'm at right now

February 22, 2021 12:35am -08:00

{
"type": "entry",
"author": {
"name": "fluffy",
"url": "http://beesbuzz.biz/",
"photo": null
},
"url": "http://beesbuzz.biz/blog/8515-Where-Im-at-right-now",
"published": "2021-02-22T00:35:46-08:00",
"content": {
"html": "What are some of the things going on in my life? Ugh, where to start.\n\n\nFirst off, I\u2019ve been having a pretty bad fibro flare for the last couple of weeks. This has been intertwined with job stress. And just like\u2026 stress in general. This has really gotten in the way of me being productive at work, or being able to work on comics, or music (including the music I was going to do for some folks' game jam games), or any of my IndieWeb things, and I\u2019m just in pain a lot of the time. And as usual it has a feedback loop where things just get worse and worse.I\u2019ve also been house hunting. I need a calmer environment to be in. My condo has gotten pretty noisy since everyone\u2019s home all the time and always having progressively-louder Zoom meetings, and I\u2019d really like a space to do more physical things in, like woodworking and gardening. None of those are doable when living in an enclosed shoebox in the urban core of Seattle.But I\u2019m not the only one doing this house hunt, and so the housing market is absolutely ridiculous right now. Things will go on the market and then get snatched up for higher than asking price within days, or sometimes even hours. And the market is flooded with poorly-considered flips, or places which are almost great except for one critical flaw.For example, I put an offer on a place in Renton, before realizing that the kitchen had only a tiny refrigerator, and nowhere to put a bigger one. Fortunately, I was able to get out of the contract thanks to the inspection contingency. Then someone else bought it half an hour later. Good for the seller.There was also a fantastic place in Bothell that was seemingly perfect, but my Realtor\u2122 convinced me to go back today and check out how things were during high airplane traffic. Because it is directly under the flight path of both SeaTac and Boeing Field. Yeah, that would have driven me bonkers pretty quickly. (But otherwise, the house was exactly what I was looking for. Such a shame.)My mom has been trying to convince me to move back to New Mexico but oh my god that is such a terrible idea. Yeah, I can do my work from anywhere (and a big part of why I\u2019m considering the suburbs is because it\u2019s not like I need to commute anymore) but Seattle is where all my friends are, and I still want to be here when the pandemic eases up! Plus, I\u2019m way too used to living near sea level and having at least some amount of humidity.My other reason for trying to move to the suburbs is to just reduce my monthly living expenses, and get more capital to have stuff to do with in case the worst things happen and I have to go \u201cself-employed\u201d again. Right now most of my money is tied up in my condo. Selling my condo gives me way more breathing room.As much as I enjoyed my trip to Port Angeles last November I don\u2019t think I\u2019d want to move there. I\u2019d go stir-crazy with isolation, and it\u2019s quite the endeavor to get back to Seattle from there. If I have to expand my housing search out to, say, Federal Way or Tacoma, that still feels doable, and would also make it way easier to access Portland, but that\u2019s starting to feel so far away from everything and everyone I care about.Anyway. In happier news, at work we\u2019re working on finally hiring a manager for my team, which is something that\u2019s been promised for the past six months while I\u2019ve been here (holy heck has it already been that long?!) and hopefully that\u2019ll help to get things more manageable there.Also, Werner, who is now around 19 years old, has gotten much more kitten-like and has gotten yet another burst of playfulness. The little old man just isn\u2019t gonna give up, is he. And Fiona\u2019s still got boundless energy too, even though she\u2019s around 10 years old now.But, holy cow I\u2019m in so much pain. I have so many things I want to do but just\u2026 can\u2019t, right now. I feel like I\u2019m being hit by many simultaneous cases of <a href=\"https://tantek.com/2021/051/b1/life-happens\">life happening</a> and it\u2019s all I can do to even tread water.It also really doesn\u2019t help that now that everything\u2019s online, every single platform has doubled down on trying to completely monopolize my entire attention all the time. When gatherings were in person it was easy for me to choose the one to go to and decline everything else. But now I\u2019m constantly inundated with things from Meetup and Discord and Slack and Zoom, and since everything is \u201cjust online\u201d it\u2019s so easy for everyone to expect everyone to come to everything. And everything tries to grab my attention constantly through email and a deluge of in-app notifications, which has now made it pretty much impossible for me to keep up with things.Back when the pandemic first hit I thought, oh hey, great, now people will be more willing to do things in a more accessible way that doesn\u2019t require physical travel. And then the monkey\u2019s paw curled another finger.Everything\u2019s just so much right now and I have no idea how to cope. I could really use a break from everything.\n\n<a href=\"http://beesbuzz.biz/blog/8515-Where-Im-at-right-now#comments\">comments</a>",
"text": "What are some of the things going on in my life? Ugh, where to start.\n\n\nFirst off, I\u2019ve been having a pretty bad fibro flare for the last couple of weeks. This has been intertwined with job stress. And just like\u2026 stress in general. This has really gotten in the way of me being productive at work, or being able to work on comics, or music (including the music I was going to do for some folks' game jam games), or any of my IndieWeb things, and I\u2019m just in pain a lot of the time. And as usual it has a feedback loop where things just get worse and worse.I\u2019ve also been house hunting. I need a calmer environment to be in. My condo has gotten pretty noisy since everyone\u2019s home all the time and always having progressively-louder Zoom meetings, and I\u2019d really like a space to do more physical things in, like woodworking and gardening. None of those are doable when living in an enclosed shoebox in the urban core of Seattle.But I\u2019m not the only one doing this house hunt, and so the housing market is absolutely ridiculous right now. Things will go on the market and then get snatched up for higher than asking price within days, or sometimes even hours. And the market is flooded with poorly-considered flips, or places which are almost great except for one critical flaw.For example, I put an offer on a place in Renton, before realizing that the kitchen had only a tiny refrigerator, and nowhere to put a bigger one. Fortunately, I was able to get out of the contract thanks to the inspection contingency. Then someone else bought it half an hour later. Good for the seller.There was also a fantastic place in Bothell that was seemingly perfect, but my Realtor\u2122 convinced me to go back today and check out how things were during high airplane traffic. Because it is directly under the flight path of both SeaTac and Boeing Field. Yeah, that would have driven me bonkers pretty quickly. (But otherwise, the house was exactly what I was looking for. Such a shame.)My mom has been trying to convince me to move back to New Mexico but oh my god that is such a terrible idea. Yeah, I can do my work from anywhere (and a big part of why I\u2019m considering the suburbs is because it\u2019s not like I need to commute anymore) but Seattle is where all my friends are, and I still want to be here when the pandemic eases up! Plus, I\u2019m way too used to living near sea level and having at least some amount of humidity.My other reason for trying to move to the suburbs is to just reduce my monthly living expenses, and get more capital to have stuff to do with in case the worst things happen and I have to go \u201cself-employed\u201d again. Right now most of my money is tied up in my condo. Selling my condo gives me way more breathing room.As much as I enjoyed my trip to Port Angeles last November I don\u2019t think I\u2019d want to move there. I\u2019d go stir-crazy with isolation, and it\u2019s quite the endeavor to get back to Seattle from there. If I have to expand my housing search out to, say, Federal Way or Tacoma, that still feels doable, and would also make it way easier to access Portland, but that\u2019s starting to feel so far away from everything and everyone I care about.Anyway. In happier news, at work we\u2019re working on finally hiring a manager for my team, which is something that\u2019s been promised for the past six months while I\u2019ve been here (holy heck has it already been that long?!) and hopefully that\u2019ll help to get things more manageable there.Also, Werner, who is now around 19 years old, has gotten much more kitten-like and has gotten yet another burst of playfulness. The little old man just isn\u2019t gonna give up, is he. And Fiona\u2019s still got boundless energy too, even though she\u2019s around 10 years old now.But, holy cow I\u2019m in so much pain. I have so many things I want to do but just\u2026 can\u2019t, right now. I feel like I\u2019m being hit by many simultaneous cases of life happening and it\u2019s all I can do to even tread water.It also really doesn\u2019t help that now that everything\u2019s online, every single platform has doubled down on trying to completely monopolize my entire attention all the time. When gatherings were in person it was easy for me to choose the one to go to and decline everything else. But now I\u2019m constantly inundated with things from Meetup and Discord and Slack and Zoom, and since everything is \u201cjust online\u201d it\u2019s so easy for everyone to expect everyone to come to everything. And everything tries to grab my attention constantly through email and a deluge of in-app notifications, which has now made it pretty much impossible for me to keep up with things.Back when the pandemic first hit I thought, oh hey, great, now people will be more willing to do things in a more accessible way that doesn\u2019t require physical travel. And then the monkey\u2019s paw curled another finger.Everything\u2019s just so much right now and I have no idea how to cope. I could really use a break from everything.\n\ncomments"
},
"name": "fluffy rambles: Where I'm at right now",
"post-type": "article",
"_id": "18567253",
"_source": "3782",
"_is_read": true
}