Time to traumatize myself by implementing the entire IndieAuth spec by hand. The newest version that seems to be twice as complex as the one from three years ago.
I’m not sure if I should draft a will first, it seems overwhelming to me... (but I’m sure that in the event that I succeed, I will reap major rewards from it)
{
"type": "entry",
"published": "2022-07-10T15:00:33.009962176+03:00",
"url": "https://fireburn.ru/posts/indieauth-woes-part-0",
"category": [
"IndieAuth",
"kittybox"
],
"content": {
"text": "Time to traumatize myself by implementing the entire IndieAuth spec by hand. The newest version that seems to be twice as complex as the one from three years ago.\n\nI\u2019m not sure if I should draft a will first, it seems overwhelming to me... (but I\u2019m sure that in the event that I succeed, I will reap major rewards from it)",
"html": "<p>Time to traumatize myself by implementing <a href=\"https://indieauth.spec.indieweb.org/\">the entire IndieAuth spec</a> by hand. The newest version that seems to be twice as complex as the one from three years ago.</p>\n\n<p>I\u2019m not sure if I should draft a will first, it seems overwhelming to me... (but I\u2019m sure that in the event that I succeed, I will reap major rewards from it)</p>"
},
"author": {
"type": "card",
"name": "Vika",
"url": "https://fireburn.ru/",
"photo": "https://avatars.githubusercontent.com/u/7953163?v=4"
},
"post-type": "note",
"_id": "30194029",
"_source": "1371",
"_is_read": true
}
{
"type": "entry",
"author": {
"name": "fluffy",
"url": "http://beesbuzz.biz/",
"photo": null
},
"url": "http://beesbuzz.biz/blog/chatter/5125-Why-The-Indieweb",
"published": "2022-07-06T10:20:54-07:00",
"content": {
"html": "<a href=\"http://beesbuzz.biz/blog/chatter/?id=5125&tag=indieweb\">#indieweb</a><a href=\"http://beesbuzz.biz/blog/chatter/?id=5125&tag=humor\">#humor</a>",
"text": "#indieweb#humor"
},
"name": "Notes: Why The Indieweb?",
"post-type": "article",
"_id": "30121693",
"_source": "3782",
"_is_read": true
}
{
"type": "entry",
"author": {
"name": "Manton Reece",
"url": "https://www.manton.org/",
"photo": "https://micro.blog/manton/avatar.jpg"
},
"url": "https://www.manton.org/2022/07/05/importing-checkins-from.html",
"name": "Importing check-ins from Ohai",
"content": {
"html": "<p>I\u2019ve used a few apps over the years for location check-ins. Gowalla, Foursquare, and Ohai, which was built on the App.net API. The Gowalla data was lost after they were acquired by Facebook. I\u2019ve continued to use Foursquare and have imported many of those check-ins to my location site <a href=\"https://manton.coffee\">manton.coffee</a>.</p>\n<p>I have about a year of data from Ohai, from around 2013-2014. Before App.net shut down, I exported the data. I wanted to dust it off and import it into Micro.blog.</p>\n<p>The data is stored in the App.net \u201cmessages\u201d JSON. In some cases, there is annotation data that includes the location information such as place name for the check-in and latitude/longitude.</p>\n<p>Here\u2019s an example of one of the check-ins, cleaned up slightly to remove fields I don\u2019t care about:</p>\n<pre style=\"color:#f8f8f2;background-color:#272822;\"><code>{\n <span style=\"color:#f92672;\">\"annotations\"</span>: [\n {\n <span style=\"color:#f92672;\">\"type\"</span>: <span style=\"color:#e6db74;\">\"net.app.ohai.location\"</span>,\n <span style=\"color:#f92672;\">\"value\"</span>: {\n <span style=\"color:#f92672;\">\"address\"</span>: <span style=\"color:#e6db74;\">\"11521 N Fm 620\"</span>,\n <span style=\"color:#f92672;\">\"country_code\"</span>: <span style=\"color:#e6db74;\">\"us\"</span>,\n <span style=\"color:#f92672;\">\"latitude\"</span>: <span style=\"color:#ae81ff;\">30.45419</span>,\n <span style=\"color:#f92672;\">\"locality\"</span>: <span style=\"color:#e6db74;\">\"Austin\"</span>,\n <span style=\"color:#f92672;\">\"longitude\"</span>: <span style=\"color:#ae81ff;\">-97.8271</span>,\n <span style=\"color:#f92672;\">\"name\"</span>: <span style=\"color:#e6db74;\">\"Starbucks\"</span>,\n <span style=\"color:#f92672;\">\"postcode\"</span>: <span style=\"color:#e6db74;\">\"78726\"</span>,\n <span style=\"color:#f92672;\">\"region\"</span>: <span style=\"color:#e6db74;\">\"TX\"</span>\n }\n }\n ],\n <span style=\"color:#f92672;\">\"created_at\"</span>: <span style=\"color:#e6db74;\">\"2013-11-11T14:44:25Z\"</span>,\n <span style=\"color:#f92672;\">\"id\"</span>: <span style=\"color:#e6db74;\">\"1922259\"</span>,\n <span style=\"color:#f92672;\">\"source\"</span>: {\n <span style=\"color:#f92672;\">\"client_id\"</span>: <span style=\"color:#e6db74;\">\"nymmngm43jnYP2FQ4pCvXjBpT3YyfNDa\"</span>,\n <span style=\"color:#f92672;\">\"link\"</span>: <span style=\"color:#e6db74;\">\"http://ohaiapp.net/\"</span>,\n <span style=\"color:#f92672;\">\"name\"</span>: <span style=\"color:#e6db74;\">\"Ohai\"</span>\n },\n <span style=\"color:#f92672;\">\"text\"</span>: <span style=\"color:#e6db74;\">\"Working after tacos. Hoping to get some coding done with an early start to the week.\"</span>\n}\n</code></pre><p>I had originally used Ohai as a sort of private check-in journal, not intending it to be public in the way that Foursquare check-ins often are. But I\u2019ve found that after nearly 10 years, semi-private data like this can usually be public without the same kind of privacy considerations that I would have worried about at the time it was first written.</p>\n<p>So how do we get this data into Micro.blog? Micro.blog can import from a bunch of platforms, but it doesn\u2019t make sense to add support for this file format directly to Micro.blog. It\u2019s not something that most people would need. I wrote a custom script to handle this for my check-ins blog.</p>\n<p>In the script, we\u2019ll iterate over each message and look for the ones posted from Ohai, ignoring everything else. For some reason \u2014 maybe because I was offline or because of limitations in the App.net places database \u2014 not all of my messages included location information, but I still want to record the post and date because it included text I wrote about the check-in. If there is location information, we\u2019ll pass that to Micro.blog too.</p>\n<p><a href=\"https://gist.github.com/manton/50293c39b6f9c96e5e0ed19ebbff93bf\">Here\u2019s the script</a>. If you want to customize it for your own use, make sure to set the app token and blog URL.</p>\n<p>Micro.blog uses the Micropub API for creating posts. When there\u2019s location information, we\u2019ll pass a <code>checkin</code> field to store that with Micro.blog. We can then access that data from a Micro.blog theme, for example to show a map. See <a href=\"https://book.micro.blog/micropub/\">my book chapter on Micropub</a> for details on the JSON format.</p>\n<p>I had a lot of fun going through this old data and migrating it to Micro.blog so that it can be preserved. Eventually I want to have a Micro.blog-based client solution for new check-ins, starting with Sunlit for iOS, so that I don\u2019t need to keep depending on Foursquare.</p>",
"text": "I\u2019ve used a few apps over the years for location check-ins. Gowalla, Foursquare, and Ohai, which was built on the App.net API. The Gowalla data was lost after they were acquired by Facebook. I\u2019ve continued to use Foursquare and have imported many of those check-ins to my location site manton.coffee.\nI have about a year of data from Ohai, from around 2013-2014. Before App.net shut down, I exported the data. I wanted to dust it off and import it into Micro.blog.\nThe data is stored in the App.net \u201cmessages\u201d JSON. In some cases, there is annotation data that includes the location information such as place name for the check-in and latitude/longitude.\nHere\u2019s an example of one of the check-ins, cleaned up slightly to remove fields I don\u2019t care about:\n{\n \"annotations\": [\n {\n \"type\": \"net.app.ohai.location\",\n \"value\": {\n \"address\": \"11521 N Fm 620\",\n \"country_code\": \"us\",\n \"latitude\": 30.45419,\n \"locality\": \"Austin\",\n \"longitude\": -97.8271,\n \"name\": \"Starbucks\",\n \"postcode\": \"78726\",\n \"region\": \"TX\"\n }\n }\n ],\n \"created_at\": \"2013-11-11T14:44:25Z\",\n \"id\": \"1922259\",\n \"source\": {\n \"client_id\": \"nymmngm43jnYP2FQ4pCvXjBpT3YyfNDa\",\n \"link\": \"http://ohaiapp.net/\",\n \"name\": \"Ohai\"\n },\n \"text\": \"Working after tacos. Hoping to get some coding done with an early start to the week.\"\n}\nI had originally used Ohai as a sort of private check-in journal, not intending it to be public in the way that Foursquare check-ins often are. But I\u2019ve found that after nearly 10 years, semi-private data like this can usually be public without the same kind of privacy considerations that I would have worried about at the time it was first written.\nSo how do we get this data into Micro.blog? Micro.blog can import from a bunch of platforms, but it doesn\u2019t make sense to add support for this file format directly to Micro.blog. It\u2019s not something that most people would need. I wrote a custom script to handle this for my check-ins blog.\nIn the script, we\u2019ll iterate over each message and look for the ones posted from Ohai, ignoring everything else. For some reason \u2014 maybe because I was offline or because of limitations in the App.net places database \u2014 not all of my messages included location information, but I still want to record the post and date because it included text I wrote about the check-in. If there is location information, we\u2019ll pass that to Micro.blog too.\nHere\u2019s the script. If you want to customize it for your own use, make sure to set the app token and blog URL.\nMicro.blog uses the Micropub API for creating posts. When there\u2019s location information, we\u2019ll pass a checkin field to store that with Micro.blog. We can then access that data from a Micro.blog theme, for example to show a map. See my book chapter on Micropub for details on the JSON format.\nI had a lot of fun going through this old data and migrating it to Micro.blog so that it can be preserved. Eventually I want to have a Micro.blog-based client solution for new check-ins, starting with Sunlit for iOS, so that I don\u2019t need to keep depending on Foursquare."
},
"published": "2022-07-05T07:53:04-05:00",
"category": [
"Essays"
],
"post-type": "article",
"_id": "30096712",
"_source": "12",
"_is_read": true
}
{
"type": "entry",
"published": "2022-07-04 15:18-0700",
"url": "https://gregorlove.com/2022/07/indieauth-for-processwire-released/",
"category": [
"indieweb",
"processwire"
],
"syndication": [
"https://news.indieweb.org/en",
"https://processwire.com/talk/topic/26220-module-indieauth-for-processwire/",
"https://twitter.com/gRegorLove/status/1544096341986402304"
],
"name": "IndieAuth for ProcessWire Released",
"content": {
"text": "IndieAuth lets you sign in to applications using your domain name and grant access to read/write to your site. This module adds IndieAuth support to your ProcessWire site, enabling two main things:\n\nAuthentication: When you visit a site like indielogin.com and enter your domain name, you will be taken to your ProcessWire admin area to sign in and approve the request. If you approve the request, you will be returned to the site and logged in as your domain name.\n\tAuthorization: When you visit an application like Quill, it needs to also get your permission to post to your site. You will be taken to your ProcessWire admin area to sign in and approve the request/scopes that the app is requesting (create, update, delete, etc.). If you approve the request, you will be returned to the app, logged in as your domain name, and the app will have an access token for your site.\nFeatures\n\nBrowse the applications you have granted access tokens to. See when each one was granted, last used, and will expire.\n\tRevoke any application\u2019s access tokens\n\tSet the default expiration period for new access tokens. The initial default is 14 days.\n\tAutomatically remove expired tokens\n\tDuring authorization, confirm and change the scopes granted to the application. For example, an app may request \u201ccreate\u201d and \u201cdelete\u201d scopes, but you can grant only \u201ccreate.\u201d\n\tDuring authorization, you can also choose to grant an access token with no expiration\nInstallation from GitHub\n\nThis module is currently pending approval to appear in the Directory of ProcessWire plugin modules. Until it is approved, please follow the instructions on GitHub to install. I will remove this notice once the module is in the directory.\n\nInstallation from Modules Directory\n\nThe recommended method is to use the ProcessWire admin area\u2019s module interface.\n\nNavigate to Modules > New. In the Module Class Name field, enter ProcessIndieAuth\n\n\tCopy the template files from the module\u2019s directory /extras/templates into your site\u2019s /site/templates directory.\n\tVerify that the plugin installed pages:\n\tIndieAuth Metadata Endpoint\n\t\tAuthorization Endpoint\n\t\tToken Endpoint\n\t\tToken Revocation Endpoint\n\t\tIndieAuth page under the admin\u2019s Access menu\n\t\n\tLook up the user(s) that you want to allow to use IndieAuth and assign them the \u201cindieauth\u201d role\n\tUpdate your home page template to add the link elements inside the <head> element:\n<?=$modules->get('ProcessIndieAuth')->getLinkElements();?>\n\nThis should result in three <link> elements in the source HTML:\n\n\n<head>\n <link rel=\"indieauth-metadata\" href=\"/indieauth-metadata-endpoint/\">\n <link rel=\"authorization_endpoint\" href=\"/authorization-endpoint/\">\n <link rel=\"token_endpoint\" href=\"/token-endpoint/\">\n</head>\n\nSign In\n\nTo test signing in with IndieAuth, visit indielogin.com and enter your domain name. Follow the prompts to authenticate and you should end up back on indielogin.com with a success message.\n\nThe authentication prompt when signing in with IndieAuth\nSign In and Authorize\n\nTo authorize an application with IndieAuth, you site will first need a module that uses access tokens. I have a Micropub for ProcessWire module in development that does that. Micropub is a standard that lets you publish to your site using third-party clients. If you\u2019d like to try it out, follow the instructions on GitHub to install it.\n\nAfter installing, visit Quill and enter your domain name. Follow the prompts and note the additional fields for \u201cscope\u201d and \u201cexpiration,\u201d since you are authorizing an application to interact with your site. After successfully authorizing, try to post a short note from Quill. Quill should redirect you to the new post if it was successful.\n\nFor a list of other Micropub clients you can try, see https://indieweb.org/Micropub/Clients.\n\nThe authorization prompt\nAdmin and Options\n\nIn the admin, you can see which applications you have granted access tokens to. You can see when each token was issued, last accessed, and its expiration. You can also manually revoke a token at any time. Navigate to: Access > IndieAuth.\n\nThe admin page displaying access tokens you have granted\nThere are a couple options in the admin at: Modules > Configure > ProcessIndieAuth:\n\nDefault access token lifetime (in seconds): This defaults to 14 days and is what appears in the authorization screenshot above.\n\tAutomatically remove access tokens after expiration (enabled by default): When enabled, the site checks approximately every six hours and removes expired access tokens. Regardless of whether this option is enabled, the module will reject any application attempting to use an expired access token. Since access tokens cannot (currently) have their expiration extended, I recommend keeping this option enabled so the admin list stays tidy and current.\nFinally, this module writes some admin logs. Access those at: Setup > Logs > indieauth\n\nMore About IndieAuth\n\nIf you\u2019re interested in more details about IndieAuth, I recommend the article \u201cOAuth for the Open Web\u201d by Aaron Parecki (or the video presentation). If you are interested in implementing IndieAuth in your project, see the IndieAuth specification.",
"html": "<p>IndieAuth lets you sign in to applications using your domain name and grant access to read/write to your site. This module adds IndieAuth support to your <a href=\"https://processwire.com/\">ProcessWire</a> site, enabling two main things:</p>\n\n<ol><li>Authentication: When you visit a site like <a href=\"https://indielogin.com/\">indielogin.com</a> and enter your domain name, you will be taken to your ProcessWire admin area to sign in and approve the request. If you approve the request, you will be returned to the site and logged in as your domain name.</li>\n\t<li>Authorization: When you visit an application like <a href=\"https://quill.p3k.io/\">Quill</a>, it needs to also get your permission to post to your site. You will be taken to your ProcessWire admin area to sign in and approve the request/scopes that the app is requesting (create, update, delete, etc.). If you approve the request, you will be returned to the app, logged in as your domain name, and the app will have an access token for your site.</li>\n</ol><h2>Features</h2>\n\n<ul><li>Browse the applications you have granted access tokens to. See when each one was granted, last used, and will expire.</li>\n\t<li>Revoke any application\u2019s access tokens</li>\n\t<li>Set the default expiration period for new access tokens. The initial default is 14 days.</li>\n\t<li>Automatically remove expired tokens</li>\n\t<li>During authorization, confirm and change the scopes granted to the application. For example, an app may request \u201ccreate\u201d and \u201cdelete\u201d scopes, but you can grant only \u201ccreate.\u201d</li>\n\t<li>During authorization, you can also choose to grant an access token with no expiration</li>\n</ul><h2>Installation from GitHub</h2>\n\nThis module is currently pending approval to appear in the <a href=\"https://processwire.com/modules/\" style=\"color:#523e02;font-weight:700;\">Directory of ProcessWire plugin modules</a>. Until it is approved, please follow the instructions on <a href=\"https://github.com/gregorlove/Processwire-IndieAuth\" style=\"color:#523e02;font-weight:700;\">GitHub</a> to install. I will remove this notice once the module is in the directory.\n\n<h2>Installation from Modules Directory</h2>\n\n<p>The recommended method is to use the ProcessWire admin area\u2019s module interface.</p>\n\n<ol><li>Navigate to Modules > New. In the <i>Module Class Name</i> field, enter <code>ProcessIndieAuth</code>\n</li>\n\t<li>Copy the template files from the module\u2019s directory <code>/extras/templates</code> into your site\u2019s <code>/site/templates</code> directory.</li>\n\t<li>Verify that the plugin installed pages:\n\t<ul><li>IndieAuth Metadata Endpoint</li>\n\t\t<li>Authorization Endpoint</li>\n\t\t<li>Token Endpoint</li>\n\t\t<li>Token Revocation Endpoint</li>\n\t\t<li>IndieAuth page under the admin\u2019s Access menu</li>\n\t</ul></li>\n\t<li>Look up the user(s) that you want to allow to use IndieAuth and assign them the \u201cindieauth\u201d role</li>\n\t<li>Update your home page template to add the link elements inside the <head> element:<br /><code style=\"font-size:1.6rem;\"><?=$modules->get('ProcessIndieAuth')->getLinkElements();?></code>\n</li>\n</ol><p>This should result in three <link> elements in the source HTML:</p>\n\n<pre>\n<code style=\"font-size:1.6rem;\"><head>\n <link rel=\"indieauth-metadata\" href=\"/indieauth-metadata-endpoint/\">\n <link rel=\"authorization_endpoint\" href=\"/authorization-endpoint/\">\n <link rel=\"token_endpoint\" href=\"/token-endpoint/\">\n</head></code></pre>\n\n<h2>Sign In</h2>\n\n<p>To test signing in with IndieAuth, visit <a href=\"https://indielogin.com\">indielogin.com</a> and enter your domain name. Follow the prompts to authenticate and you should end up back on indielogin.com with a success message.</p>\n\n<img alt=\"screenshot\" src=\"https://gregorlove.com/site/assets/files/6031/indieauth-for-processwire-authentication.1000x0-is.png\" /><p>The authentication prompt when signing in with IndieAuth</p>\n<h2>Sign In and Authorize</h2>\n\n<p>To authorize an application with IndieAuth, you site will first need a module that uses access tokens. I have a <a href=\"https://github.com/gregorlove/ProcessWire-Micropub\">Micropub for ProcessWire</a> module in development that does that. Micropub is a standard that lets you publish to your site using third-party clients. If you\u2019d like to try it out, follow the instructions on GitHub to install it.</p>\n\n<p>After installing, visit <a href=\"https://quill.p3k.io/\">Quill</a> and enter your domain name. Follow the prompts and note the additional fields for \u201cscope\u201d and \u201cexpiration,\u201d since you are authorizing an application to interact with your site. After successfully authorizing, try to post a short note from Quill. Quill should redirect you to the new post if it was successful.</p>\n\n<p>For a list of other Micropub clients you can try, see <a href=\"https://indieweb.org/Micropub/Clients\">https://indieweb.org/Micropub/Clients</a>.</p>\n\n<img alt=\"screenshot\" src=\"https://gregorlove.com/site/assets/files/6031/indieauth-for-processwire-authorization.1000x0-is.png\" /><p>The authorization prompt</p>\n<h2>Admin and Options</h2>\n\n<p>In the admin, you can see which applications you have granted access tokens to. You can see when each token was issued, last accessed, and its expiration. You can also manually revoke a token at any time. Navigate to: Access > IndieAuth.</p>\n\n<img alt=\"screenshot\" src=\"https://gregorlove.com/site/assets/files/6031/indieauth-for-processwire-tokens.1000x0-is.png\" /><p>The admin page displaying access tokens you have granted</p>\n<p>There are a couple options in the admin at: Modules > Configure > ProcessIndieAuth:</p>\n\n<ol><li>Default access token lifetime (in seconds): This defaults to 14 days and is what appears in the authorization screenshot above.</li>\n\t<li>Automatically remove access tokens after expiration (enabled by default): When enabled, the site checks approximately every six hours and removes expired access tokens. Regardless of whether this option is enabled, the module will reject any application attempting to use an expired access token. Since access tokens cannot (currently) have their expiration extended, I recommend keeping this option enabled so the admin list stays tidy and current.</li>\n</ol><p>Finally, this module writes some admin logs. Access those at: Setup > Logs > indieauth</p>\n\n<h2>More About IndieAuth</h2>\n\n<p>If you\u2019re interested in more details about IndieAuth, I recommend the article \u201c<a href=\"https://aaronparecki.com/2018/07/07/7/oauth-for-the-open-web\">OAuth for the Open Web</a>\u201d by Aaron Parecki (or the <a href=\"https://youtu.be/EeCNlB7v08I\">video presentation</a>). If you are interested in implementing IndieAuth in your project, see the <a href=\"https://indieauth.spec.indieweb.org/\">IndieAuth specification</a>.</p>"
},
"author": {
"type": "card",
"name": "gRegor Morrill",
"url": "https://gregorlove.com/",
"photo": "https://gregorlove.com/site/assets/files/3473/profile-2016-med.jpg"
},
"post-type": "article",
"_id": "30086026",
"_source": "179",
"_is_read": true
}
{
"type": "entry",
"published": "2022-07-03T18:32:04+00:00",
"url": "https://werd.io/2022/my-text-editors",
"name": "My text editors",
"content": {
"text": "A text editor is just a text editor, right? Well, not really - and it turns out I use a variety of text editors for different purposes.iA Writer is how I draft and publish my blog posts and short stories. It\u2019s a beautiful, minimalist markdown editor that knows when to get out of my way. And it supports Micropub, which lets me publish pieces directly to my website.BBEdit is a professional text editor. I use it as my scratchpad; features like regular expression search and replace and smart syntax highlighting make it an easy place for me to inspect and adjust text files.Ulysses is a long-form writing app. I\u2019m writing a novel in it, and have a few abandoned starts to other long-form fiction. I haven\u2019t used its grammar checker or editing tools (in general, I hate and distrust grammar checkers), but I know they may come in handy later on.Obsidian is becoming my outboard brain. Some of those thoughts are public; you can find them at werd.cloud. I love that it\u2019s completely cross-platform.VSCode is my Integrated Development Environment of choice; if you\u2019re a programmer, it\u2019s a good chance it\u2019s yours, too. If you\u2019d told the me ten years ago that I\u2019d be regularly using a product with \u201cVisual Studio\u201d in the name, I would have laughed at you - but here we are. It\u2019s a testament to how much Microsoft has grown and changed.Nano is the editor I use inside my terminal window. I prefer it to vi and vim; I just do.Slab is how I write documentation to share with teams. It\u2019s dramatically better than Confluence, which I\u2019d used previously, for this purpose: lightning fast, with features that allow you to ensure documentation is current.Apple Notes (in concert with Reminders) has become my place to keep track of work notes. It\u2019s not perfect, but it\u2019s steadily improving, and it\u2019s always there, across my devices. The Quick Note feature is really neat, and I love that I can write in longhand with my Apple Pencil.Google Docs is how I collaborate on documentation with other people. It\u2019s easy, real-time, and cross-platform.Microsoft Word is how I talk to lawyers and format fiction manuscripts.What are your text editors of choice?",
"html": "<p>A text editor is just a text editor, right? Well, not really - and it turns out I use a variety of text editors for different purposes.</p><p><a href=\"https://ia.net/writer\">iA Writer</a> is how I draft and publish my blog posts and short stories. It\u2019s a beautiful, minimalist markdown editor that knows when to get out of my way. And it supports <a href=\"https://micropub.net/\">Micropub</a>, which lets me publish pieces directly to my website.</p><p><a href=\"https://www.barebones.com/products/bbedit/\">BBEdit</a> is a professional text editor. I use it as my scratchpad; features like regular expression search and replace and smart syntax highlighting make it an easy place for me to inspect and adjust text files.</p><p><a href=\"https://ulysses.app/\">Ulysses</a> is a long-form writing app. I\u2019m writing a novel in it, and have a few abandoned starts to other long-form fiction. I haven\u2019t used its grammar checker or editing tools (in general, I hate and distrust grammar checkers), but I know they may come in handy later on.</p><p><a href=\"https://obsidian.md/\">Obsidian</a> is becoming my outboard brain. Some of those thoughts are public; you can find them at <a href=\"https://werd.cloud\">werd.cloud</a>. I love that it\u2019s completely cross-platform.</p><p><a href=\"https://code.visualstudio.com/\">VSCode</a> is my Integrated Development Environment of choice; if you\u2019re a programmer, it\u2019s a good chance it\u2019s yours, too. If you\u2019d told the me ten years ago that I\u2019d be regularly using a product with \u201cVisual Studio\u201d in the name, I would have laughed at you - but here we are. It\u2019s a testament to how much Microsoft has grown and changed.</p><p><a href=\"https://www.nano-editor.org/\">Nano</a> is the editor I use inside my terminal window. I prefer it to vi and <a href=\"https://www.vim.org/\">vim</a>; I just do.</p><p><a href=\"https://slab.com\">Slab</a> is how I write documentation to share with teams. It\u2019s dramatically better than <a href=\"https://www.atlassian.com/software/confluence\">Confluence</a>, which I\u2019d used previously, for this purpose: lightning fast, with features that allow you to ensure documentation is current.</p><p><a href=\"https://9to5mac.com/2022/06/07/apple-notes-app-new-features/\">Apple Notes</a> (in concert with Reminders) has become my place to keep track of work notes. It\u2019s not perfect, but it\u2019s steadily improving, and it\u2019s always there, across my devices. The Quick Note feature is really neat, and I love that I can write in longhand with my Apple Pencil.</p><p><a href=\"https://docs.google.com\">Google Docs</a> is how I collaborate on documentation with other people. It\u2019s easy, real-time, and cross-platform.</p><p><a href=\"https://www.microsoft.com/en-us/microsoft-365/word\">Microsoft Word</a> is how I talk to lawyers and format fiction manuscripts.</p><p>What are your text editors of choice?</p>"
},
"author": {
"type": "card",
"name": "Ben Werdm\u00fcller",
"url": "https://werd.io/profile/benwerd",
"photo": "https://werd.io/file/5d388c5fb16ea14aac640912/thumb.jpg"
},
"post-type": "article",
"_id": "30065273",
"_source": "191",
"_is_read": true
}
Here's a list of sites within the Fediverse that report supporting Webmention:
https://the-federation.info/protocol/webmention
I'm not sure if Aaron Parecki has a public list of all the sites that are using webmention.io, but that would add a huge number as would all the native sites that are part of micro.blog. I'm not sure if either publishes a list of sites using their services for a variety of reasons.
{
"type": "entry",
"published": "2022-06-25T00:11:33+00:00",
"url": "http://stream.boffosocko.com/2022/heres-a-list-of-sites-within-the-fediverse-that-report",
"in-reply-to": [
"https://lordmatt.co.uk/technology/the-internet/all-the-active-indieweb-sites-i-have-found-so-far-june-2022/",
"https://aaronparecki.com/"
],
"content": {
"text": "Here's a list of sites within the Fediverse that report supporting Webmention:\nhttps://the-federation.info/protocol/webmention\n\n\nI'm not sure if Aaron Parecki has a public list of all the sites that are using webmention.io, but that would add a huge number as would all the native sites that are part of micro.blog. I'm not sure if either publishes a list of sites using their services for a variety of reasons.",
"html": "Here's a list of sites within the Fediverse that report supporting Webmention:<br /><a href=\"https://the-federation.info/protocol/webmention\">https://the-federation.info/protocol/webmention</a><br /><br />\nI'm not sure if Aaron Parecki has a public list of all the sites that are using webmention.io, but that would add a huge number as would all the native sites that are part of micro.blog. I'm not sure if either publishes a list of sites using their services for a variety of reasons."
},
"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": "29906889",
"_source": "192",
"_is_read": true
}
- Each voice is individual and matters
- Slow is ok
- Diversified and independent is good
- Not fitting a pattern is ok
- Not being easily commodified is ok
{
"type": "entry",
"published": "2022-06-20T16:17:31Z",
"url": "https://adactio.com/links/19203",
"category": [
"blogs",
"blogging",
"writing",
"sharing",
"personal",
"publishing",
"indieweb"
],
"bookmark-of": [
"https://blog.jim-nielsen.com/2022/the-message-and-medium-of-the-personal-blog/"
],
"content": {
"text": "The Message Behind the Medium of a Personal Blog - Jim Nielsen\u2019s Blog\n\n\n\n\n Each voice is individual and matters\n Slow is ok\n Diversified and independent is good\n Not fitting a pattern is ok\n Not being easily commodified is ok",
"html": "<h3>\n<a class=\"p-name u-bookmark-of\" href=\"https://blog.jim-nielsen.com/2022/the-message-and-medium-of-the-personal-blog/\">\nThe Message Behind the Medium of a Personal Blog - Jim Nielsen\u2019s Blog\n</a>\n</h3>\n\n<blockquote>\n <ul><li>Each voice is individual and matters</li>\n <li>Slow is ok</li>\n <li>Diversified and independent is good</li>\n <li>Not fitting a pattern is ok</li>\n <li>Not being easily commodified is ok</li>\n </ul></blockquote>"
},
"author": {
"type": "card",
"name": "Jeremy Keith",
"url": "https://adactio.com/",
"photo": "https://adactio.com/images/photo-150.jpg"
},
"post-type": "bookmark",
"_id": "29814445",
"_source": "2",
"_is_read": true
}
I’m honoured to mentioned in the same paragraph as Seth Godin and Chris Coyier (and I too have really been enjoying Chris’s writing).
{
"type": "entry",
"published": "2022-06-20T16:16:04Z",
"url": "https://adactio.com/links/19202",
"category": [
"blogging",
"writing",
"sharing",
"indieweb",
"blogs",
"personal",
"publishing"
],
"bookmark-of": [
"https://matthiasott.com/notes/just-put-stuff-out-there"
],
"content": {
"text": "Just Put Stuff Out There \u00b7 Matthias Ott \u2013 User Experience Designer\n\n\n\nI\u2019m honoured to mentioned in the same paragraph as Seth Godin and Chris Coyier (and I too have really been enjoying Chris\u2019s writing).",
"html": "<h3>\n<a class=\"p-name u-bookmark-of\" href=\"https://matthiasott.com/notes/just-put-stuff-out-there\">\nJust Put Stuff Out There \u00b7 Matthias Ott \u2013 User Experience Designer\n</a>\n</h3>\n\n<p>I\u2019m honoured to mentioned in the same paragraph as <a href=\"https://seths.blog/\">Seth Godin</a> and <a href=\"https://chriscoyier.net/\">Chris Coyier</a> (and I too have really been enjoying Chris\u2019s writing).</p>"
},
"author": {
"type": "card",
"name": "Jeremy Keith",
"url": "https://adactio.com/",
"photo": "https://adactio.com/images/photo-150.jpg"
},
"post-type": "bookmark",
"_id": "29814446",
"_source": "2",
"_is_read": true
}
This is very cool! Looks like I need to implement OpenID Connect for my #IndieAuth server so I can get in on this 👀
The @projectsigstore documentation has a new Gitsign section explaining everything you need to know to start signing your commits with an OpenID identity, such as your Gi...
{
"type": "entry",
"published": "2022-06-17T08:29:00+0100",
"url": "https://www.jvt.me/mf2/2022/06/8tbj9/",
"category": [
"oidc",
"indie-auth"
],
"quotation-of": "https://twitter.com/erikaheidi/status/1537432578298216458",
"content": {
"text": "This is very cool! Looks like I need to implement OpenID Connect for my #IndieAuth server so I can get in on this \ud83d\udc40",
"html": "<p>This is very cool! Looks like I need to implement OpenID Connect for my <a href=\"https://www.jvt.me/tags/indie-auth/\">#IndieAuth</a> server so I can get in on this \ud83d\udc40</p>"
},
"author": {
"type": "card",
"name": "Jamie Tanna",
"url": "https://www.jvt.me",
"photo": "https://www.jvt.me/img/profile.png"
},
"post-type": "note",
"refs": {
"https://twitter.com/erikaheidi/status/1537432578298216458": {
"type": "entry",
"url": "https://twitter.com/erikaheidi/status/1537432578298216458",
"content": {
"text": "The @projectsigstore documentation has a new Gitsign section explaining everything you need to know to start signing your commits with an OpenID identity, such as your GitHub or Google account. No need for dealing with GPG keys!\ndocs.sigstore.dev/gitsign/overvi\u2026",
"html": "The <a href=\"https://twitter.com/projectsigstore\">@projectsigstore</a> documentation has a new Gitsign section explaining everything you need to know to start signing your commits with an OpenID identity, such as your GitHub or Google account. No need for dealing with GPG keys!\n<a href=\"https://docs.sigstore.dev/gitsign/overview\">docs.sigstore.dev/gitsign/overvi\u2026</a>"
},
"post-type": "note"
}
},
"_id": "29755426",
"_source": "2169",
"_is_read": true
}
{
"type": "entry",
"published": "2022-06-14T19:49:02+00:00",
"url": "http://stream.boffosocko.com/2022/qwxleaa-ade_oshineye-houshuang-in-fact-heres-a-good-example-of",
"syndication": [
"https://twitter.com/ChrisAldrich/status/1536798127725891584"
],
"in-reply-to": [
"https://twitter.com/ChrisAldrich/status/1536795123874508800",
"http://stream.boffosocko.com/2022/qwxleaa-ade_oshineye-houshuang-some-have-been-experimenting-with-using-the"
],
"content": {
"text": "@QwxleaA @ade_oshineye @houshuang In fact, here's a good example of one of @andy_matuschak's notes interacting directly via webmention to create bi-directional links (albeit just a notification in this case) with my notes. https://boffosocko.com/2021/07/03/differentiating-online-variations-of-the-commonplace-book-digital-gardens-wikis-zettlekasten-waste-books-florilegia-and-second-brains/#comment-368792\nhttps://notes.andymatuschak.org/z2QvtE9w5zs49x7WUeG8Ut1vywHDLiG2Wkm9p",
"html": "@QwxleaA @ade_oshineye @houshuang In fact, here's a good example of one of @andy_matuschak's notes interacting directly via webmention to create bi-directional links (albeit just a notification in this case) with my notes. <a href=\"https://boffosocko.com/2021/07/03/differentiating-online-variations-of-the-commonplace-book-digital-gardens-wikis-zettlekasten-waste-books-florilegia-and-second-brains/#comment-368792\">https://boffosocko.com/2021/07/03/differentiating-online-variations-of-the-commonplace-book-digital-gardens-wikis-zettlekasten-waste-books-florilegia-and-second-brains/#comment-368792</a><br /><a href=\"https://notes.andymatuschak.org/z2QvtE9w5zs49x7WUeG8Ut1vywHDLiG2Wkm9p\">https://notes.andymatuschak.org/z2QvtE9w5zs49x7WUeG8Ut1vywHDLiG2Wkm9p</a>"
},
"author": {
"type": "card",
"name": "Chris Aldrich",
"url": "http://stream.boffosocko.com/profile/chrisaldrich",
"photo": "http://stream.boffosocko.com/file/600427b81f7785e704eadfe511a9270f/thumb.jpg"
},
"post-type": "reply",
"_id": "29704311",
"_source": "192",
"_is_read": true
}
@QwxleaA @ade_oshineye @houshuang Some have been experimenting with using the Webmention spec to allow one wiki, note, or digital garden space interact with another. It's become quite common in the blogosphere, why not for online notes or zettelkasten?
https://indieweb.org/Webmention
{
"type": "entry",
"published": "2022-06-14T19:37:35+00:00",
"url": "http://stream.boffosocko.com/2022/qwxleaa-ade_oshineye-houshuang-some-have-been-experimenting-with-using-the",
"syndication": [
"https://twitter.com/ChrisAldrich/status/1536795123874508800"
],
"in-reply-to": [
"https://twitter.com/QwxleaA/status/1533489580816666625"
],
"content": {
"text": "@QwxleaA @ade_oshineye @houshuang Some have been experimenting with using the Webmention spec to allow one wiki, note, or digital garden space interact with another. It's become quite common in the blogosphere, why not for online notes or zettelkasten?\nhttps://indieweb.org/Webmention",
"html": "<a href=\"https://twitter.com/QwxleaA\">@QwxleaA</a> <a href=\"https://twitter.com/ade_oshineye\">@ade_oshineye</a> <a href=\"https://twitter.com/houshuang\">@houshuang</a> Some have been experimenting with using the Webmention spec to allow one wiki, note, or digital garden space interact with another. It's become quite common in the blogosphere, why not for online notes or zettelkasten?<br /><a href=\"https://indieweb.org/Webmention\">https://indieweb.org/Webmention</a>"
},
"author": {
"type": "card",
"name": "Chris Aldrich",
"url": "http://stream.boffosocko.com/profile/chrisaldrich",
"photo": "http://stream.boffosocko.com/file/600427b81f7785e704eadfe511a9270f/thumb.jpg"
},
"post-type": "reply",
"_id": "29704312",
"_source": "192",
"_is_read": true
}
I'm sorry you've run into this issue. I can't help but wonder if most of the spam is really pingback spam? Much of what you've gotten likely isn't arriving via webmention as I see the following header in your page:
<link rel="pingback" href="https://webmention.io/www.miriamsuzanne.com/xmlrpc" />
My guess along with some minor sleuthing is that the entirety of the spam you're seeing is of the pingback variety as the mechanism by which webmention works is mean to actively decrease the amount of unwanted spam. Vanishingly little Webmention spam has been seen in the wild.
Removing the pingback link from the header of that particular page (or others that might get linked to with heavily trafficked sites like CSS-Tricks which are often pirated) should solve your immediate problem. Hopefully those who are working on additional anti-spam features will add to these measures to further mitigate this sort of issue for the broader publics' use and adoption. I've personally experienced this sort of "attack" at least once in the pingback space and another using the even older refbacks specification. On my small personal site, I leave them all on however, particularly for the small slice of academic blogging community that still uses pingbacks and the benefits generally outstrip the annoyance. Naturally your mileage may vary and you may consider turning them off.
Of course, you'll probably also realize that the reason the CSS-Tricks notification was caught in spam was because it also came in as a pingback and not by webmetion. (I'm pretty sure that they don't have webmention set up to send them, so their site would have only sent a pingback.)
Many of the older systems, including WordPress which are frequently used by these same sorts of pirates, will still send/trigger pingbacks. Within the IndieWeb space, most sites explicitly sending webmention notifications will include h-cards with author names and timestamps which is part of why Max Böck’s filtering solution works well.
On the positive side, I wonder if this sort of notification behavior might help sites like CSS-Tricks to track these sort of bad actors for help in potential take downs of this sort of piracy?
{
"type": "entry",
"published": "2022-06-14T04:50:05+00:00",
"url": "http://stream.boffosocko.com/2022/im-sorry-youve-run-into-this-issue-i-cant-help",
"in-reply-to": [
"https://www.miriamsuzanne.com/2022/06/09/the-spam/"
],
"content": {
"text": "I'm sorry you've run into this issue. I can't help but wonder if most of the spam is really pingback spam? Much of what you've gotten likely isn't arriving via webmention as I see the following header in your page: \n\n<link rel=\"pingback\" href=\"https://webmention.io/www.miriamsuzanne.com/xmlrpc\" />\n\n\nMy guess along with some minor sleuthing is that the entirety of the spam you're seeing is of the pingback variety as the mechanism by which webmention works is mean to actively decrease the amount of unwanted spam. Vanishingly little Webmention spam has been seen in the wild. \n\n\nRemoving the pingback link from the header of that particular page (or others that might get linked to with heavily trafficked sites like CSS-Tricks which are often pirated) should solve your immediate problem. Hopefully those who are working on additional anti-spam features will add to these measures to further mitigate this sort of issue for the broader publics' use and adoption. I've personally experienced this sort of \"attack\" at least once in the pingback space and another using the even older refbacks specification. On my small personal site, I leave them all on however, particularly for the small slice of academic blogging community that still uses pingbacks and the benefits generally outstrip the annoyance. Naturally your mileage may vary and you may consider turning them off.\n\n\nOf course, you'll probably also realize that the reason the CSS-Tricks notification was caught in spam was because it also came in as a pingback and not by webmetion. (I'm pretty sure that they don't have webmention set up to send them, so their site would have only sent a pingback.) \n\n\nMany of the older systems, including WordPress which are frequently used by these same sorts of pirates, will still send/trigger pingbacks. Within the IndieWeb space, most sites explicitly sending webmention notifications will include h-cards with author names and timestamps which is part of why Max B\u00f6ck\u2019s filtering solution works well.\n\n\nOn the positive side, I wonder if this sort of notification behavior might help sites like CSS-Tricks to track these sort of bad actors for help in potential take downs of this sort of piracy?",
"html": "I'm sorry you've run into this issue. I can't help but wonder if most of the spam is really pingback spam? Much of what you've gotten likely isn't arriving via webmention as I see the following header in your page: <br />\n<link rel=\"pingback\" href=\"https://webmention.io/www.miriamsuzanne.com/xmlrpc\" /><br /><br />\nMy guess along with some minor sleuthing is that the entirety of the spam you're seeing is of the pingback variety as the mechanism by which webmention works is mean to actively decrease the amount of unwanted spam. Vanishingly little Webmention spam has been seen in the wild. <br /><br />\nRemoving the pingback link from the header of that particular page (or others that might get linked to with heavily trafficked sites like CSS-Tricks which are often pirated) should solve your immediate problem. Hopefully those who are working on additional anti-spam features will add to these measures to further mitigate this sort of issue for the broader publics' use and adoption. I've personally experienced this sort of \"attack\" at least once in the pingback space and another using the even older refbacks specification. On my small personal site, I leave them all on however, particularly for the small slice of academic blogging community that still uses pingbacks and the benefits generally outstrip the annoyance. Naturally your mileage may vary and you may consider turning them off.<br /><br />\nOf course, you'll probably also realize that the reason the CSS-Tricks notification was caught in spam was because it also came in as a pingback and not by webmetion. (I'm pretty sure that they don't have webmention set up to send them, so their site would have only sent a pingback.) <br /><br />\nMany of the older systems, including WordPress which are frequently used by these same sorts of pirates, will still send/trigger pingbacks. Within the IndieWeb space, most sites explicitly sending webmention notifications will include h-cards with author names and timestamps which is part of why Max B\u00f6ck\u2019s filtering solution works well.<br /><br />\nOn the positive side, I wonder if this sort of notification behavior might help sites like CSS-Tricks to track these sort of bad actors for help in potential take downs of this sort of piracy?"
},
"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": "29690379",
"_source": "192",
"_is_read": true
}
{
"type": "entry",
"published": "2022-06-12T03:19:26-04:00",
"syndication": [
"https://news.indieweb.org/en/david.shanske.com/2022/06/12/indiewebifying-a-wordpress-site-2022-edition/",
"https://twitter.com/dshanske/status/1535885717653622784",
"https://micro.blog/dshanske/13015162"
],
"name": "Indiewebifying a WordPress Site \u2013 2022 Edition - June 12, 2022",
"author": {
"type": "card",
"name": "David Shanske",
"url": "https://david.shanske.com/",
"photo": "https://david.shanske.com/avatar/dshanske?s=96"
},
"post-type": "article",
"_id": "29651942",
"_source": "5",
"_is_read": true
}
{
"type": "entry",
"published": "2022-06-12T03:19:26-04:00",
"syndication": [
"https://news.indieweb.org/en/david.shanske.com/2022/06/12/indiewebifying-a-wordpress-site-2022-edition/",
"https://twitter.com/dshanske/status/1535885717653622784"
],
"name": "Indiewebifying a WordPress Site \u2013 2022 Edition - June 12, 2022",
"author": {
"type": "card",
"name": "David Shanske",
"url": "https://david.shanske.com/",
"photo": "https://david.shanske.com/avatar/dshanske?s=96"
},
"post-type": "article",
"_id": "29651920",
"_source": "5",
"_is_read": true
}
{
"type": "entry",
"published": "2022-06-12T03:19:26-04:00",
"url": "https://david.shanske.com/2022/06/12/indiewebifying-a-wordpress-site-2022-edition/",
"name": "Indiewebifying a WordPress Site \u2013 2022 Edition - June 12, 2022",
"author": {
"type": "card",
"name": "David Shanske",
"url": "https://david.shanske.com/",
"photo": "https://david.shanske.com/avatar/dshanske?s=96"
},
"post-type": "article",
"_id": "29651900",
"_source": "5",
"_is_read": true
}
Indiewebifying a WordPress Site – 2022 Edition david.shanske.com
{
"type": "entry",
"author": {
"name": "David Shanske",
"url": "https://david.shanske.com",
"photo": "https://www.gravatar.com/avatar/681eba02e72ba1d894097034a8110e61?s=96&d=https%3A%2F%2Fmicro.blog%2Fimages%2Fblank_avatar.png"
},
"url": "https://david.shanske.com/2022/06/12/indiewebifying-a-wordpress-site-2022-edition/",
"content": {
"html": "Indiewebifying a WordPress Site \u2013 2022 Edition <a href=\"https://david.shanske.com/2022/06/12/indiewebifying-a-wordpress-site-2022-edition/\">david.shanske.com</a>",
"text": "Indiewebifying a WordPress Site \u2013 2022 Edition david.shanske.com"
},
"published": "2022-06-12T07:19:26+00:00",
"post-type": "note",
"_id": "33379996",
"_source": "7224",
"_is_read": true
}
When @hacdias.com posted about our conversation about post topics I couldn’t stay behind to also formulate my part of it in a blogpost.
Currently I have various feeds for various post types. I don’t want to link them all here, in case I want to change them around, but I have different feeds that only show my likes, my photos, my replies, etc (you can probably guess the URLs).
These feeds are relatively easy to set up: does it have a photo? Then it’s a photo. Does it have a title? Then it’s an article. This post doesn’t have any, so it’s a note. I have a few of those rules set up and they fill these pages.
But when you scroll through my photo feed, you will also see drawings. When you scroll through my notes, there are various topics represented. It is not that bad right now, but that is mainly because I don’t post as much as I could, because I don’t want to bore my readers with topics they don’t want to follow.
On social media, we live a siloed life, and the people on the IndieWeb are trying to bring that all back to their own site. But, in the siloed life, we can pick the silo for the post. ‘Insta is for friends, Twitter is more business, Reddit is shitposting’, something like that. Sometimes the silo is aimed at a certain kind of post, sometimes it is just the kind of bubble you created for yourself on that silo that makes you post a certain way.
On the IndieWeb, I have only one site. Of course I can get multiple – I have – but I like having all my posts in one place. But I also want to give people options for how to follow me, different persona to share posts with.
I do have tags but most are not that useful. Most of them only contain one post, and also, most of them are very specific. I like the indieweb and vim tags, for they are quite topical, but those are exceptions.
At one point (not now) I would like to divide posts up into probably five rough categories. The homepage might still show a selection of all, and there will also be a place to actually see everything, but I think these categories make sense to me:
-
professional / helpful for all those posts in which I share something about IndieWeb, Vim, something about programming, something I learned
-
personal for stories about what happened in my life, maybe also some tweets, the more human connection
-
too personal for checkins, books I’ve read, food I’ve eaten, movies I’ve watched, still about life but without commentary
-
art for those good pictures, occasional drawings, fiction stories, the things I post too little
I said five and I posted four, because I don’t think this is final. I might also want to add a ‘current obsession’ category, to blog about those things I am deeply into. (There has been posts about keyboards here, you missed Getting Things Done, currently I am into the game of Go again.)
A last category I might also need is ‘thinking out loud’, as this is a post that would fall into that. For what is worth, I’ll post it anyway.
{
"type": "entry",
"published": "2022-06-09T20:42:59+0000",
"url": "https://seblog.nl/2022/06/09/1/post-types-and-post-topics",
"category": [
"indieweb"
],
"content": {
"text": "When @hacdias.com posted about our conversation about post topics I couldn\u2019t stay behind to also formulate my part of it in a blogpost.\nCurrently I have various feeds for various post types. I don\u2019t want to link them all here, in case I want to change them around, but I have different feeds that only show my likes, my photos, my replies, etc (you can probably guess the URLs). \nThese feeds are relatively easy to set up: does it have a photo? Then it\u2019s a photo. Does it have a title? Then it\u2019s an article. This post doesn\u2019t have any, so it\u2019s a note. I have a few of those rules set up and they fill these pages.\nBut when you scroll through my photo feed, you will also see drawings. When you scroll through my notes, there are various topics represented. It is not that bad right now, but that is mainly because I don\u2019t post as much as I could, because I don\u2019t want to bore my readers with topics they don\u2019t want to follow.\nOn social media, we live a siloed life, and the people on the IndieWeb are trying to bring that all back to their own site. But, in the siloed life, we can pick the silo for the post. \u2018Insta is for friends, Twitter is more business, Reddit is shitposting\u2019, something like that. Sometimes the silo is aimed at a certain kind of post, sometimes it is just the kind of bubble you created for yourself on that silo that makes you post a certain way.\nOn the IndieWeb, I have only one site. Of course I can get multiple \u2013 I have \u2013 but I like having all my posts in one place. But I also want to give people options for how to follow me, different persona to share posts with.\nI do have tags but most are not that useful. Most of them only contain one post, and also, most of them are very specific. I like the indieweb and vim tags, for they are quite topical, but those are exceptions.\nAt one point (not now) I would like to divide posts up into probably five rough categories. The homepage might still show a selection of all, and there will also be a place to actually see everything, but I think these categories make sense to me:\n\nprofessional / helpful for all those posts in which I share something about IndieWeb, Vim, something about programming, something I learned\n\npersonal for stories about what happened in my life, maybe also some tweets, the more human connection\n\ntoo personal for checkins, books I\u2019ve read, food I\u2019ve eaten, movies I\u2019ve watched, still about life but without commentary\n\nart for those good pictures, occasional drawings, fiction stories, the things I post too little\nI said five and I posted four, because I don\u2019t think this is final. I might also want to add a \u2018current obsession\u2019 category, to blog about those things I am deeply into. (There has been posts about keyboards here, you missed Getting Things Done, currently I am into the game of Go again.)\nA last category I might also need is \u2018thinking out loud\u2019, as this is a post that would fall into that. For what is worth, I\u2019ll post it anyway.",
"html": "<p>When <a href=\"http://hacdias.com\">@hacdias.com</a> <a href=\"https://hacdias.com/2022/06/09/igackzpsqy\">posted</a> about our conversation about post topics I couldn\u2019t stay behind to also formulate my part of it in a blogpost.</p>\n<p>Currently I have various feeds for various post types. I don\u2019t want to link them all here, in case I want to change them around, but I have different feeds that only show my likes, my photos, my replies, etc (you can probably guess the URLs). </p>\n<p>These feeds are relatively easy to set up: does it have a photo? Then it\u2019s a photo. Does it have a title? Then it\u2019s an article. This post doesn\u2019t have any, so it\u2019s a note. I have a few of those rules set up and they fill these pages.</p>\n<p>But when you scroll through my photo feed, you will also see drawings. When you scroll through my notes, there are various topics represented. It is not that bad right now, but that is mainly because I don\u2019t post as much as I could, because I don\u2019t want to bore my readers with topics they don\u2019t want to follow.</p>\n<p>On social media, we live a siloed life, and the people on the <a href=\"https://indieweb.org\">IndieWeb</a> are trying to bring that all back to their own site. But, in the siloed life, we can pick the silo for the post. \u2018Insta is for friends, Twitter is more business, Reddit is shitposting\u2019, something like that. Sometimes the silo is aimed at a certain kind of post, sometimes it is just the kind of bubble you created for yourself on that silo that makes you post a certain way.</p>\n<p>On the IndieWeb, I have only one site. Of course I can get multiple \u2013 <a href=\"https://sebastiaanandeweg.nl\">I have</a> \u2013 but I like having all my posts in one place. But I also want to give people options for how to follow me, different persona to share posts with.</p>\n<p>I do have tags but most are not that useful. Most of them only contain one post, and also, most of them are very specific. I like the <a href=\"https://seblog.nl/category/indieweb\">indieweb</a> and <a href=\"https://seblog.nl/category/vim\">vim</a> tags, for they are quite topical, but those are exceptions.</p>\n<p>At one point (not now) I would like to divide posts up into probably five rough categories. The homepage might still show a selection of all, and there will also be a place to actually see everything, but I think these categories make sense to me:</p>\n<ul><li>\n<strong>professional / helpful</strong> for all those posts in which I share something about IndieWeb, Vim, something about programming, something I learned</li>\n<li>\n<strong>personal</strong> for stories about what happened in my life, maybe also some tweets, the more human connection</li>\n<li>\n<strong>too personal</strong> for checkins, books I\u2019ve read, food I\u2019ve eaten, movies I\u2019ve watched, still about life but without commentary</li>\n<li>\n<strong>art</strong> for those good pictures, occasional drawings, fiction stories, the things I post too little</li>\n</ul><p>I said five and I posted four, because I don\u2019t think this is final. I might also want to add a \u2018current obsession\u2019 category, to blog about those things I am deeply into. (There has been posts about keyboards here, you missed Getting Things Done, currently I am into the game of Go again.)</p>\n<p>A last category I might also need is \u2018thinking out loud\u2019, as this is a post that would fall into that. For what is worth, I\u2019ll post it anyway.</p>"
},
"author": {
"type": "card",
"name": "Sebastiaan Andeweg",
"url": "https://seblog.nl/",
"photo": "https://seblog.nl/photo.jpg"
},
"post-type": "note",
"_id": "29612308",
"_source": "1366",
"_is_read": true
}
@benwerd @benwerd@mastodon.social It would be cool if they could easily expose numbers of interactions (reads, replies, bookmarks, etc.) as a signal in a way such that social readers could filter using this data along with tags/categories for prioritizing what we might want to read.
Selfishly they could use these signals internally for better measuring engagement with articles and particular writers. Is it high quality engagement (useful comments, reads) versus lower quality engagement (bookmarks which might indicate "I read the headline and might be interested").
Highly enterprising publications, and especially "local" publications/newspapers, might consider offering IndieWeb as a Service to allow their readers the ability to have their "own platform" within the publisher's platform/stack. This could be done on a co-op basis or potentially even bundled into subscription prices. Something along the lines of Kinja perhaps, but with more ownership/control/ability to move. Or perhaps a white-labeled version of something like micro.blog, but run/managed by the NYT, WSJ, other?
A well tummeled version of the Hometown fork of Mastodon with "local only posting" could be an engaging thing for a sophisticated newspaper or magazine to create. The publication could have closer control/moderation of the local posting for article related conversations, but people could still communicate with others outside of that "home" server. Alternately, in the standard Mastodon model, the "public timeline" could be filtered for posts about or commenting on the outlet's own content and all other content goes into the federated timeline.
Publications offering their own microsub social reader interfaces could be fun and clever. It could be an interesting way to have a more streamlined reading experience for paid subscribers among other potential options. This could be an interesting interface for helping people build a truly custom reading experience specifically for them, particularly for larger newspapers with large amounts of content that could be better filtered and personalized to individuals.
{
"type": "entry",
"published": "2022-06-09T03:21:29+00:00",
"url": "http://stream.boffosocko.com/2022/benwerd-benwerdmastodonsocial-it-would-be-cool-if-they-could-easily",
"syndication": [
"https://twitter.com/ChrisAldrich/status/1534737482956296192",
"https://mastodon.social/@chrisaldrich/108445362565602155"
],
"in-reply-to": [
"https://twitter.com/benwerd/status/1534560310979338241",
"https://werd.io/2022/lets-say-a-news-outlet-wants-to",
"https://mastodon.social/web/@benwerd/108442593798977942"
],
"content": {
"text": "@benwerd @benwerd@mastodon.social It would be cool if they could easily expose numbers of interactions (reads, replies, bookmarks, etc.) as a signal in a way such that social readers could filter using this data along with tags/categories for prioritizing what we might want to read. \n\n\nSelfishly they could use these signals internally for better measuring engagement with articles and particular writers. Is it high quality engagement (useful comments, reads) versus lower quality engagement (bookmarks which might indicate \"I read the headline and might be interested\").\n\n\nHighly enterprising publications, and especially \"local\" publications/newspapers, might consider offering IndieWeb as a Service to allow their readers the ability to have their \"own platform\" within the publisher's platform/stack. This could be done on a co-op basis or potentially even bundled into subscription prices. Something along the lines of Kinja perhaps, but with more ownership/control/ability to move. Or perhaps a white-labeled version of something like micro.blog, but run/managed by the NYT, WSJ, other?\n\n\nA well tummeled version of the Hometown fork of Mastodon with \"local only posting\" could be an engaging thing for a sophisticated newspaper or magazine to create. The publication could have closer control/moderation of the local posting for article related conversations, but people could still communicate with others outside of that \"home\" server. Alternately, in the standard Mastodon model, the \"public timeline\" could be filtered for posts about or commenting on the outlet's own content and all other content goes into the federated timeline.\n\n\nPublications offering their own microsub social reader interfaces could be fun and clever. It could be an interesting way to have a more streamlined reading experience for paid subscribers among other potential options. This could be an interesting interface for helping people build a truly custom reading experience specifically for them, particularly for larger newspapers with large amounts of content that could be better filtered and personalized to individuals.",
"html": "@benwerd @benwerd@mastodon.social It would be cool if they could easily expose numbers of interactions (reads, replies, bookmarks, etc.) as a signal in a way such that social readers could filter using this data along with tags/categories for prioritizing what we might want to read. <br /><br />\nSelfishly they could use these signals internally for better measuring engagement with articles and particular writers. Is it high quality engagement (useful comments, reads) versus lower quality engagement (bookmarks which might indicate \"I read the headline and might be interested\").<br /><br />\nHighly enterprising publications, and especially \"local\" publications/newspapers, might consider offering IndieWeb as a Service to allow their readers the ability to have their \"own platform\" within the publisher's platform/stack. This could be done on a co-op basis or potentially even bundled into subscription prices. Something along the lines of Kinja perhaps, but with more ownership/control/ability to move. Or perhaps a white-labeled version of something like micro.blog, but run/managed by the NYT, WSJ, other?<br /><br />\nA well tummeled version of the Hometown fork of Mastodon with \"local only posting\" could be an engaging thing for a sophisticated newspaper or magazine to create. The publication could have closer control/moderation of the local posting for article related conversations, but people could still communicate with others outside of that \"home\" server. Alternately, in the standard Mastodon model, the \"public timeline\" could be filtered for posts about or commenting on the outlet's own content and all other content goes into the federated timeline.<br /><br />\nPublications offering their own microsub social reader interfaces could be fun and clever. It could be an interesting way to have a more streamlined reading experience for paid subscribers among other potential options. This could be an interesting interface for helping people build a truly custom reading experience specifically for them, particularly for larger newspapers with large amounts of content that could be better filtered and personalized to individuals."
},
"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": "29595120",
"_source": "192",
"_is_read": true
}
Let’s say a news outlet wants to fully embrace the open web, indieweb, and maybe even the fediverse. What would your top technical or product asks of them be?
{
"type": "entry",
"published": "2022-06-08T15:37:41+00:00",
"url": "https://werd.io/2022/lets-say-a-news-outlet-wants-to",
"content": {
"text": "Let\u2019s say a news outlet wants to fully embrace the open web, indieweb, and maybe even the fediverse. What would your top technical or product asks of them be?"
},
"author": {
"type": "card",
"name": "Ben Werdm\u00fcller",
"url": "https://werd.io/profile/benwerd",
"photo": "https://werd.io/file/5d388c5fb16ea14aac640912/thumb.jpg"
},
"post-type": "note",
"_id": "29586079",
"_source": "191",
"_is_read": true
}
Miriam has a wishlist for scaling up the indie web approach:
What I would like to see is a tool that helps bring the entire system together in one place. Somewhere that non-technical people can:
- build their own site, with support for feeds/mentions
- see what feeds are available on other sites, and subscribe to them
- easily respond to other sites, and see the resulting threads
(Oh, and by linking to this post, this should show up as a bookmark—I’m also testing Miriam’s webmention setup.)
{
"type": "entry",
"published": "2022-06-07T08:26:25Z",
"url": "https://adactio.com/links/19149",
"category": [
"indieweb",
"personal",
"publishing",
"social",
"networks",
"rss",
"feeds",
"syndication",
"webmentions"
],
"bookmark-of": [
"https://www.miriamsuzanne.com/2022/06/04/indiweb/"
],
"content": {
"text": "Am I on the IndieWeb Yet? | Miriam Eric Suzanne\n\n\n\nMiriam has a wishlist for scaling up the indie web approach:\n\n\n What I would like to see is a tool that helps bring the entire system together in one place. Somewhere that non-technical people can:\n \n build their own site, with support for feeds/mentions\n see what feeds are available on other sites, and subscribe to them\n easily respond to other sites, and see the resulting threads\n \n\n(Oh, and by linking to this post, this should show up as a bookmark\u2014I\u2019m also testing Miriam\u2019s webmention setup.)",
"html": "<h3>\n<a class=\"p-name u-bookmark-of\" href=\"https://www.miriamsuzanne.com/2022/06/04/indiweb/\">\nAm I on the IndieWeb Yet? | Miriam Eric Suzanne\n</a>\n</h3>\n\n<p>Miriam has a wishlist for scaling up the indie web approach:</p>\n\n<blockquote>\n <p>What I would like to see is a tool that helps bring the entire system together in one place. Somewhere that non-technical people can:</p>\n \n <ul><li>build their own site, with support for feeds/mentions</li>\n <li>see what feeds are available on other sites, and subscribe to them</li>\n <li>easily respond to other sites, and see the resulting threads</li>\n </ul></blockquote>\n\n<p>(Oh, and by linking to this post, this should show up as a bookmark\u2014I\u2019m also testing Miriam\u2019s webmention setup.)</p>"
},
"author": {
"type": "card",
"name": "Jeremy Keith",
"url": "https://adactio.com/",
"photo": "https://adactio.com/images/photo-150.jpg"
},
"post-type": "bookmark",
"_id": "29553848",
"_source": "2",
"_is_read": true
}
