@AndreJaenisch Sonke Ahrens' book How to Take Smart Notes about Luhmann's method is very solid (https://bookshop.org/a/17195/9781542866507). Lots of systems out there to implement it. I like @obsdmd, but other platforms listed here: https://indieweb.org/commonplace_book
{
"type": "entry",
"published": "2021-04-24T18:38:31+00:00",
"url": "http://stream.boffosocko.com/2021/andrejaenisch-sonke-ahrens-book-how-to-take-smart-notes-about",
"syndication": [
"https://twitter.com/ChrisAldrich/status/1386027365738762242"
],
"in-reply-to": [
"https://twitter.com/AndreJaenisch/status/1385861818975981569"
],
"content": {
"text": "@AndreJaenisch Sonke Ahrens' book How to Take Smart Notes about Luhmann's method is very solid (https://bookshop.org/a/17195/9781542866507). Lots of systems out there to implement it. I like @obsdmd, but other platforms listed here: https://indieweb.org/commonplace_book",
"html": "<a href=\"https://twitter.com/AndreJaenisch\">@AndreJaenisch</a> Sonke Ahrens' book How to Take Smart Notes about Luhmann's method is very solid (<a href=\"https://bookshop.org/a/17195/9781542866507\">https://bookshop.org/a/17195/9781542866507</a>). Lots of systems out there to implement it. I like <a href=\"https://twitter.com/obsdmd\">@obsdmd</a>, but other platforms listed here: <a href=\"https://indieweb.org/commonplace_book\">https://indieweb.org/commonplace_book</a>"
},
"author": {
"type": "card",
"name": "Chris Aldrich",
"url": "http://stream.boffosocko.com/profile/chrisaldrich",
"photo": "http://stream.boffosocko.com/file/600427b81f7785e704eadfe511a9270f/thumb.jpg"
},
"post-type": "reply",
"_id": "20007548",
"_source": "192",
"_is_read": true
}
A personal website ain’t got no wrong words.
{
"type": "entry",
"published": "2021-04-23T10:09:33Z",
"url": "https://adactio.com/links/18059",
"category": [
"indieweb",
"personal",
"publishing",
"words",
"writing",
"sharing",
"music",
"piano"
],
"bookmark-of": [
"https://matthiasott.com/notes/no-wrong-notes"
],
"content": {
"text": "No Wrong Notes \u00b7 Matthias Ott \u2013 User Experience Designer\n\n\n\n\n A personal website ain\u2019t got no wrong words.",
"html": "<h3>\n<a class=\"p-name u-bookmark-of\" href=\"https://matthiasott.com/notes/no-wrong-notes\">\nNo Wrong Notes \u00b7 Matthias Ott \u2013 User Experience Designer\n</a>\n</h3>\n\n<blockquote>\n <p>A personal website ain\u2019t got no wrong words.</p>\n</blockquote>"
},
"author": {
"type": "card",
"name": "Jeremy Keith",
"url": "https://adactio.com/",
"photo": "https://adactio.com/images/photo-150.jpg"
},
"post-type": "bookmark",
"_id": "19971897",
"_source": "2",
"_is_read": true
}
I'm going!Looking forward to this IndieWeb Popup! Despite my occasional salty-sounding post about Webmention I am very optimistic about their power as a tool for the web.
{
"type": "entry",
"published": "2021-04-19T11:39:07-0400",
"rsvp": "yes",
"url": "https://martymcgui.re/2021/04/19/113907/",
"in-reply-to": [
"https://events.indieweb.org/2021/05/webmentions-beyond-webmention-io-zG4JpHhZShVA"
],
"content": {
"text": "I'm going!Looking forward to this IndieWeb Popup! Despite my occasional salty-sounding post about Webmention I am very optimistic about their power as a tool for the web.",
"html": "I'm going!<p>Looking forward to this IndieWeb Popup! Despite my occasional <a href=\"https://martymcgui.re/2020/07/15/what-we-talk-about-when-were-talking-about-webmentions/\">salty-sounding post about Webmention</a> I am very optimistic about their power as a tool for the web.</p>"
},
"author": {
"type": "card",
"name": "Marty McGuire",
"url": "https://martymcgui.re/",
"photo": "https://martymcgui.re/images/logo.jpg"
},
"post-type": "rsvp",
"refs": {
"https://events.indieweb.org/2021/05/webmentions-beyond-webmention-io-zG4JpHhZShVA": {
"type": "entry",
"summary": "Webmentions haven't really been revisited in some time (and with the advent of people leaning to Webmention.io). This is a chance to see what's been really wanted, what hasn't worked and where we can go with it.",
"url": "https://events.indieweb.org/2021/05/webmentions-beyond-webmention-io-zG4JpHhZShVA",
"name": "Webmentions Beyond Webmention.io",
"author": {
"type": "card",
"name": "events.indieweb.org",
"url": "http://events.indieweb.org",
"photo": null
},
"post-type": "article"
}
},
"_id": "19894123",
"_source": "175",
"_is_read": true
}
{
"type": "entry",
"author": {
"name": "Manton Reece",
"url": "https://www.manton.org/",
"photo": "https://micro.blog/manton/avatar.jpg"
},
"url": "https://www.manton.org/2021/04/19/how-does-microblog.html",
"name": "How does Micro.blog even work?",
"content": {
"html": "<p>I\u2019ve been upgrading servers and improving performance in Micro.blog lately, a theme which will continue throughout the year to make everything as stable as possible. Sometimes this introduces new bugs or weird behavior that makes people scratch their heads. What is Micro.blog even doing? So let\u2019s look a little at the architecture.</p>\n\n<p>When you write a new post, Micro.blog saves it into a MySQL database. We currently run 2 database servers, so that we can spread some queries between them and to make backups easier. But unlike many web apps, we do not serve blogs from this database. Blogs are published to a separate server as static HTML and images, served directly by Nginx with few or no dependencies on the rest of Micro.blog. This makes your blog very fast, and means that major parts of Micro.blog can go down without affecting your blog.</p>\n\n<p>This has been a key design goal from the very beginning of Micro.blog. We host a blog for you, but it can have its own domain name and is only loosely tied to the rest of Micro.blog. This goal meant discarding some common architectures such as dynamically generating the blog when pages are requested.</p>\n\n<p>Micro.blog is really 3 separate systems combined into a single platform: a blog admin interface, a blog hosting service, and a Twitter-like timeline.</p>\n\n<p>To achieve this, Micro.blog has to translate the blog posts from Markdown to HTML. It runs all the text through <a href=\"https://gohugo.io\">Hugo</a>. It also has to put photos and podcasts in the right place. When you upload a file, Micro.blog copies it to an object storage server at the same time that it syncs the file to your blog.</p>\n\n<p>Timeline web requests and background tasks are run across a few servers, so that we can balance load and deal with outages. While Hugo wants all your Markdown and photos in a specific structure in the file system, Micro.blog maintains content in separate databases and then writes it out to the format that Hugo wants for processing.</p>\n\n<p>Any given server could have part of your content or none of it yet, so Micro.blog will have to sync everything up. It does this in multiple phases to make publishing as fast as possible, and this is the area that I\u2019ve been spending a lot of time tweaking.</p>\n\n<p>First, Micro.blog attempts to quickly publish your latest post, so that it\u2019s available at the permalink URL and included in the blog feed. If you have thousands of posts, it ignores most of them during this phase. It just wants to get your post up on the web as quickly as possible and added to the Micro.blog timeline.</p>\n\n<p>Whenever Micro.blog is processing posts, it also applies any custom themes for your blog. It never skips the Hugo step, even if your blog post content is so simple that it could be previewed with a separate Markdown filter. Every post is run through Hugo, added to the RSS or JSON Feed, and only then processed into the Micro.blog timeline.</p>\n\n<p>This round-trip journey your content takes is an important part of how Micro.blog works with external blog feeds like WordPress. We aren\u2019t interested in building a proprietary social network that is not rooted in blogs. The timeline works with blogs no matter where they are hosted.</p>\n\n<p>Next, Micro.blog will do a full publish of your blog, with the entire site, categories, photo pages, and archive. In some cases, it will combine the Markdown with any uploaded photos before processing them, but usually the uploads are already on your blog. It also keeps a copy of all the Markdown files, independent on any of the web servers, so that if possible it can update those versions without writing out potentially thousands of posts to the file system.</p>\n\n<p>This phase of publishing is the longest, although it\u2019s faster now than it has ever been. During this phase, your latest post should already be live and the timeline updated, so it\u2019s not as annoying to wait around for the archive or category pages to update.</p>\n\n<p>I\u2019m exposing more of what Micro.blog is doing behind the scenes in the <a href=\"https://micro.blog/account/logs\">logs for your account</a>. Here\u2019s a snippet from my log recently, although I\u2019ve flipped it so that it reads in chronology order instead of newest at top:</p>\n\n<pre>\n2021-04-11 16:54:25: Publish: Not queued, publishing manton\n<i>2021-04-11 16:54:25: Publish: Initial prepare for manton</i>\n2021-04-11 16:54:25: Publish: Preparing pages for manton\n2021-04-11 16:54:25: Publish: Persistent folder exists, updating for manton\n<i>2021-04-11 16:54:25: Publish: Initial posts for manton</i>\n2021-04-11 16:54:26: Publish: Linking shared content files for manton\n2021-04-11 16:54:26: Publish: Running Hugo for manton\n<i>2021-04-11 16:54:26: Publish: Initial Hugo run for manton</i>\n<i>2021-04-11 16:54:26: Publish: Initial sync for manton</i>\n<i>2021-04-11 16:54:26: Publish: Pinging manton, progress: 0.866 seconds</i>\n</pre>\n\n<p>Here, there are actually 2 overlapping background tasks. The lines with \u201cInitial\u201d (italicized above) are part of this first phase of quickly publishing your post. In this case, the round-trip from saving the content, publishing the feed, and then updating the timeline was about 1 second. Under a few seconds is kind of the gold standard we\u2019re aiming for.</p>\n\n<p>Finally, Micro.blog assembles the timeline so that it can be served quickly no matter how many people you are following. We have a Redis server that keeps the timeline for each user in a sorted set, and use that from the Micro.blog API to page between posts. Micro.blog also processes posts for @-mentions, sending Webmentions, auto-linking URLs, and other details that are beyond what I wanted to write about here.</p>\n\n<p>Could this be even better? Yes. But while I\u2019m sometimes tempted to change the architecture to something closer to WordPress\u2019s model, I know there\u2019s always more performance we can squeeze out of our current setup.</p>",
"text": "I\u2019ve been upgrading servers and improving performance in Micro.blog lately, a theme which will continue throughout the year to make everything as stable as possible. Sometimes this introduces new bugs or weird behavior that makes people scratch their heads. What is Micro.blog even doing? So let\u2019s look a little at the architecture.\n\nWhen you write a new post, Micro.blog saves it into a MySQL database. We currently run 2 database servers, so that we can spread some queries between them and to make backups easier. But unlike many web apps, we do not serve blogs from this database. Blogs are published to a separate server as static HTML and images, served directly by Nginx with few or no dependencies on the rest of Micro.blog. This makes your blog very fast, and means that major parts of Micro.blog can go down without affecting your blog.\n\nThis has been a key design goal from the very beginning of Micro.blog. We host a blog for you, but it can have its own domain name and is only loosely tied to the rest of Micro.blog. This goal meant discarding some common architectures such as dynamically generating the blog when pages are requested.\n\nMicro.blog is really 3 separate systems combined into a single platform: a blog admin interface, a blog hosting service, and a Twitter-like timeline.\n\nTo achieve this, Micro.blog has to translate the blog posts from Markdown to HTML. It runs all the text through Hugo. It also has to put photos and podcasts in the right place. When you upload a file, Micro.blog copies it to an object storage server at the same time that it syncs the file to your blog.\n\nTimeline web requests and background tasks are run across a few servers, so that we can balance load and deal with outages. While Hugo wants all your Markdown and photos in a specific structure in the file system, Micro.blog maintains content in separate databases and then writes it out to the format that Hugo wants for processing.\n\nAny given server could have part of your content or none of it yet, so Micro.blog will have to sync everything up. It does this in multiple phases to make publishing as fast as possible, and this is the area that I\u2019ve been spending a lot of time tweaking.\n\nFirst, Micro.blog attempts to quickly publish your latest post, so that it\u2019s available at the permalink URL and included in the blog feed. If you have thousands of posts, it ignores most of them during this phase. It just wants to get your post up on the web as quickly as possible and added to the Micro.blog timeline.\n\nWhenever Micro.blog is processing posts, it also applies any custom themes for your blog. It never skips the Hugo step, even if your blog post content is so simple that it could be previewed with a separate Markdown filter. Every post is run through Hugo, added to the RSS or JSON Feed, and only then processed into the Micro.blog timeline.\n\nThis round-trip journey your content takes is an important part of how Micro.blog works with external blog feeds like WordPress. We aren\u2019t interested in building a proprietary social network that is not rooted in blogs. The timeline works with blogs no matter where they are hosted.\n\nNext, Micro.blog will do a full publish of your blog, with the entire site, categories, photo pages, and archive. In some cases, it will combine the Markdown with any uploaded photos before processing them, but usually the uploads are already on your blog. It also keeps a copy of all the Markdown files, independent on any of the web servers, so that if possible it can update those versions without writing out potentially thousands of posts to the file system.\n\nThis phase of publishing is the longest, although it\u2019s faster now than it has ever been. During this phase, your latest post should already be live and the timeline updated, so it\u2019s not as annoying to wait around for the archive or category pages to update.\n\nI\u2019m exposing more of what Micro.blog is doing behind the scenes in the logs for your account. Here\u2019s a snippet from my log recently, although I\u2019ve flipped it so that it reads in chronology order instead of newest at top:\n\n\n2021-04-11 16:54:25: Publish: Not queued, publishing manton\n2021-04-11 16:54:25: Publish: Initial prepare for manton\n2021-04-11 16:54:25: Publish: Preparing pages for manton\n2021-04-11 16:54:25: Publish: Persistent folder exists, updating for manton\n2021-04-11 16:54:25: Publish: Initial posts for manton\n2021-04-11 16:54:26: Publish: Linking shared content files for manton\n2021-04-11 16:54:26: Publish: Running Hugo for manton\n2021-04-11 16:54:26: Publish: Initial Hugo run for manton\n2021-04-11 16:54:26: Publish: Initial sync for manton\n2021-04-11 16:54:26: Publish: Pinging manton, progress: 0.866 seconds\n\n\nHere, there are actually 2 overlapping background tasks. The lines with \u201cInitial\u201d (italicized above) are part of this first phase of quickly publishing your post. In this case, the round-trip from saving the content, publishing the feed, and then updating the timeline was about 1 second. Under a few seconds is kind of the gold standard we\u2019re aiming for.\n\nFinally, Micro.blog assembles the timeline so that it can be served quickly no matter how many people you are following. We have a Redis server that keeps the timeline for each user in a sorted set, and use that from the Micro.blog API to page between posts. Micro.blog also processes posts for @-mentions, sending Webmentions, auto-linking URLs, and other details that are beyond what I wanted to write about here.\n\nCould this be even better? Yes. But while I\u2019m sometimes tempted to change the architecture to something closer to WordPress\u2019s model, I know there\u2019s always more performance we can squeeze out of our current setup."
},
"published": "2021-04-19T09:57:09-05:00",
"category": [
"Essays"
],
"post-type": "article",
"_id": "19892290",
"_source": "12",
"_is_read": true
}
I really like the idea of a shared convention for styling web components with custom properties—feels like BEM meets microformats.
{
"type": "entry",
"published": "2021-04-19T09:53:59Z",
"url": "https://adactio.com/links/18034",
"category": [
"css",
"custom",
"properties",
"theming",
"naming",
"webcomponents",
"conventions",
"styling",
"frontend",
"development"
],
"bookmark-of": [
"https://github.com/castastrophe/wc-theming-standards/wiki"
],
"content": {
"text": "Home \u00b7 castastrophe/wc-theming-standards Wiki\n\n\n\nI really like the idea of a shared convention for styling web components with custom properties\u2014feels like BEM meets microformats.",
"html": "<h3>\n<a class=\"p-name u-bookmark-of\" href=\"https://github.com/castastrophe/wc-theming-standards/wiki\">\nHome \u00b7 castastrophe/wc-theming-standards Wiki\n</a>\n</h3>\n\n<p>I really like the idea of a shared convention for styling web components with custom properties\u2014feels like BEM meets microformats.</p>"
},
"author": {
"type": "card",
"name": "Jeremy Keith",
"url": "https://adactio.com/",
"photo": "https://adactio.com/images/photo-150.jpg"
},
"post-type": "bookmark",
"_id": "19886084",
"_source": "2",
"_is_read": true
}
{
"type": "entry",
"author": {
"name": "fluffy",
"url": "http://beesbuzz.biz/",
"photo": null
},
"url": "http://beesbuzz.biz/blog/9665-Shoulder-unpacking-gardening-etc",
"published": "2021-04-16T21:28:23-07:00",
"content": {
"html": "<p>Wellp, I managed to screw up my shoulder again. <a href=\"http://beesbuzz.biz/blog/6013-Another-pain-another-frustration\">Last time</a> was probably from me using my cane on a fairly long walk, and this time was probably due to me overdoing it with my <a href=\"https://amzn.to/2Qxv65U\">weed puller</a> (which requires a snapping motion that does similar things to my cane). Bleah. At least this time I know stretches and things that might help, and I found <a href=\"https://www.youtube.com/watch?v=q5SsM9PWWYc\">a bunch more</a> which feel like they\u2019re helping. Hopefully I\u2019ll still feel well enough to get my second shot of vaccine tomorrow. (Which will probably have me feeling pretty much immobile for a few days anyway.)</p>\n\n\n<p>I\u2019ve sort of stalled on unpacking, and I haven\u2019t found my Wacom tablet yet. I really want to work on comics though. Maybe I\u2019ll give <a href=\"https://www.macrumors.com/guide/sidecar/\">Sidecar</a> another shot. Although with my shoulder pain I don\u2019t think holding a stylus is a good idea at all right now.</p><p>I\u2019ve also been pretty unmotivated to work on music. I\u2019ve had my usual every-day-a-new-song-scrap thing happen but I\u2019m in a sort of quiescent period when it comes to actually doing more. Mostly because all of my music stuff is down in the basement and I don\u2019t feel like going through the hassle of setting up a recording environment right now and I feel like just like\u2026 waiting until the condo sells and I can build a proper studio.</p><p>And on that note, the condo is off the market temporarily, for Reasons not worth getting into. It\u2019ll hopefully be relisted sometime next week, probably at a lower price (i.e. where I wanted to list it in the first place), so maybe there\u2019ll be a better chance of it selling soon.</p><p>In happier news, we\u2019ve finally managed to hire a manager for my team. She doesn\u2019t start until June, though. But still, having some actual direction will be nice.</p><p>Also at work I gave a talk on IndieWeb which went over really well. I hope I can get more folks interested in it, and maybe I can eventually parlay this into becoming an IndieWeb advocate/developer/whatever. I can dream, anyway.</p><p>Oh and the weed puller arrived on the same day as my <a href=\"https://amzn.to/3ssdN3s\">composter</a>, which is now full of weeds and kitchen scraps and hopefully in a few weeks I\u2019ll have come nice compost to fill my <a href=\"https://www.homedepot.com/p/Greenes-Fence-2-ft-x-4-ft-x-10-5-in-Original-Pine-Raised-Garden-Bed-RCP24484T/315634141\">raised beds</a> with! I feel like playing hundreds of hours of Animal Crossing has prepared me for this. (And also with the random interactions with my neighbors, who continue to be people I\u2019m glad to live near.)</p><p>The raised beds arrive next week, and I\u2019m going to try the <a href=\"https://dengarden.com/gardening/How-to-Make-a-Raised-Bed-Lasagna-Garden\">lasagna method</a> to fill them. Fortunately I still have a lot of paper and cardboard left over from the move!</p>\n\n<p><a href=\"http://beesbuzz.biz/blog/9665-Shoulder-unpacking-gardening-etc#comments\">comments</a></p>",
"text": "Wellp, I managed to screw up my shoulder again. Last time was probably from me using my cane on a fairly long walk, and this time was probably due to me overdoing it with my weed puller (which requires a snapping motion that does similar things to my cane). Bleah. At least this time I know stretches and things that might help, and I found a bunch more which feel like they\u2019re helping. Hopefully I\u2019ll still feel well enough to get my second shot of vaccine tomorrow. (Which will probably have me feeling pretty much immobile for a few days anyway.)\n\n\nI\u2019ve sort of stalled on unpacking, and I haven\u2019t found my Wacom tablet yet. I really want to work on comics though. Maybe I\u2019ll give Sidecar another shot. Although with my shoulder pain I don\u2019t think holding a stylus is a good idea at all right now.I\u2019ve also been pretty unmotivated to work on music. I\u2019ve had my usual every-day-a-new-song-scrap thing happen but I\u2019m in a sort of quiescent period when it comes to actually doing more. Mostly because all of my music stuff is down in the basement and I don\u2019t feel like going through the hassle of setting up a recording environment right now and I feel like just like\u2026 waiting until the condo sells and I can build a proper studio.And on that note, the condo is off the market temporarily, for Reasons not worth getting into. It\u2019ll hopefully be relisted sometime next week, probably at a lower price (i.e. where I wanted to list it in the first place), so maybe there\u2019ll be a better chance of it selling soon.In happier news, we\u2019ve finally managed to hire a manager for my team. She doesn\u2019t start until June, though. But still, having some actual direction will be nice.Also at work I gave a talk on IndieWeb which went over really well. I hope I can get more folks interested in it, and maybe I can eventually parlay this into becoming an IndieWeb advocate/developer/whatever. I can dream, anyway.Oh and the weed puller arrived on the same day as my composter, which is now full of weeds and kitchen scraps and hopefully in a few weeks I\u2019ll have come nice compost to fill my raised beds with! I feel like playing hundreds of hours of Animal Crossing has prepared me for this. (And also with the random interactions with my neighbors, who continue to be people I\u2019m glad to live near.)The raised beds arrive next week, and I\u2019m going to try the lasagna method to fill them. Fortunately I still have a lot of paper and cardboard left over from the move!\n\ncomments"
},
"name": "fluffy rambles: Shoulder, unpacking, gardening, etc.",
"post-type": "article",
"_id": "19840606",
"_source": "3782",
"_is_read": true
}
@jaybearca The Webmention plugin only does notifications. You also need the semantic linkbacks plugin for the parser which will give you the richer data you're looking for.
https://wordpress.org/plugins/semantic-linkbacks/
{
"type": "entry",
"published": "2021-04-16T06:15:06+00:00",
"url": "http://stream.boffosocko.com/2021/jaybearca-the-webmention-plugin-only-does-notifications-you-also-need",
"syndication": [
"https://twitter.com/ChrisAldrich/status/1382941111975620610"
],
"in-reply-to": [
"https://jaybear.ca/14670/",
"https://twitter.com/jaybearca/status/1382924534819393536"
],
"content": {
"text": "@jaybearca The Webmention plugin only does notifications. You also need the semantic linkbacks plugin for the parser which will give you the richer data you're looking for. \nhttps://wordpress.org/plugins/semantic-linkbacks/",
"html": "@jaybearca The Webmention plugin only does notifications. You also need the semantic linkbacks plugin for the parser which will give you the richer data you're looking for. <br /><a href=\"https://wordpress.org/plugins/semantic-linkbacks/\">https://wordpress.org/plugins/semantic-linkbacks/</a><br /><br />"
},
"author": {
"type": "card",
"name": "Chris Aldrich",
"url": "http://stream.boffosocko.com/profile/chrisaldrich",
"photo": "http://stream.boffosocko.com/file/600427b81f7785e704eadfe511a9270f/thumb.jpg"
},
"post-type": "reply",
"_id": "19815531",
"_source": "192",
"_is_read": true
}
{
"type": "entry",
"author": {
"name": "Manton Reece",
"url": "https://www.manton.org/",
"photo": "https://micro.blog/manton/avatar.jpg"
},
"url": "https://www.manton.org/2021/04/15/microblog-rsvps-with.html",
"name": "Micro.blog RSVPs with Webmention",
"content": {
"html": "<p>Micro.blog sends Webmentions to external blogs when you \u201creply\u201d to a post inside Micro.blog. It marks up your reply with Microformats, discovers the Webmention endpoint for the post you\u2019re replying to, and sends the Webmention. This allows your Micro.blog replies to be included as comments on blogs hosted by other platforms, like WordPress.</p>\n\n<p><a href=\"https://indieweb.org/rsvp\">An RSVP</a> is a special type of reply used to indicate whether you\u2019re attending an event. By posting RSVPs to your own blog, you can attach them to existing posts or just have your own copy of the data. As more bloggers use RSVPs, we could eventually have a more distributed, IndieWeb-friendly system instead of relying on Facebook or Evite.</p>\n\n<p>How to create an RSVP on Micro.blog? We don\u2019t currently have an RSVP button in Micro.blog, because Webmention-enabled events are still rare enough that it would take up a lot of the Micro.blog UI, potentially cluttering the interface.</p>\n\n<p>You\u2019ll need a little bit of HTML to create an RSVP. First, add a link to where you want to send the Webmention. Instead of using Markdown for the link, use HTML and add the Microformats <code>class=\"u-in-reply-to\"</code> to mark the link as a reply to another URL:</p>\n\n<pre><code>Looking forward to this <a href=\"...\" class=\"u-in-reply-to\">Webmentions pop-up session</a> next month.\n</code></pre>\n\n<p>Then, to make this an RSVP, add a <code>data</code> tag somewhere in the post with \u201cyes\u201d, \u201cmaybe\u201d, or \u201cno\u201d:</p>\n\n<pre><code><data class=\"p-rsvp\" value=\"yes\" />\n</code></pre>\n\n<p>I like to use <code>data</code> because it\u2019s invisible when displayed in a web browser, but it could be a <code>span</code> or other HTML tag. You can see a full example of this if you view the HTML source of <a href=\"https://www.manton.org/2021/04/13/looking-forward-to.html\">my post here</a>, RSVP-ing to an IndieWeb online event.</p>\n\n<p>When you publish the post, Micro.blog will automatically notice the <code>u-in-reply-to</code>, find the Webmention endpoint for the post you\u2019re linking to, and send the Webmention for you. Micro.blog themes also handle the other details, like including your name and profile photo.</p>",
"text": "Micro.blog sends Webmentions to external blogs when you \u201creply\u201d to a post inside Micro.blog. It marks up your reply with Microformats, discovers the Webmention endpoint for the post you\u2019re replying to, and sends the Webmention. This allows your Micro.blog replies to be included as comments on blogs hosted by other platforms, like WordPress.\n\nAn RSVP is a special type of reply used to indicate whether you\u2019re attending an event. By posting RSVPs to your own blog, you can attach them to existing posts or just have your own copy of the data. As more bloggers use RSVPs, we could eventually have a more distributed, IndieWeb-friendly system instead of relying on Facebook or Evite.\n\nHow to create an RSVP on Micro.blog? We don\u2019t currently have an RSVP button in Micro.blog, because Webmention-enabled events are still rare enough that it would take up a lot of the Micro.blog UI, potentially cluttering the interface.\n\nYou\u2019ll need a little bit of HTML to create an RSVP. First, add a link to where you want to send the Webmention. Instead of using Markdown for the link, use HTML and add the Microformats class=\"u-in-reply-to\" to mark the link as a reply to another URL:\n\nLooking forward to this <a href=\"...\" class=\"u-in-reply-to\">Webmentions pop-up session</a> next month.\n\n\nThen, to make this an RSVP, add a data tag somewhere in the post with \u201cyes\u201d, \u201cmaybe\u201d, or \u201cno\u201d:\n\n<data class=\"p-rsvp\" value=\"yes\" />\n\n\nI like to use data because it\u2019s invisible when displayed in a web browser, but it could be a span or other HTML tag. You can see a full example of this if you view the HTML source of my post here, RSVP-ing to an IndieWeb online event.\n\nWhen you publish the post, Micro.blog will automatically notice the u-in-reply-to, find the Webmention endpoint for the post you\u2019re linking to, and send the Webmention for you. Micro.blog themes also handle the other details, like including your name and profile photo."
},
"published": "2021-04-15T16:37:14-05:00",
"category": [
"Essays"
],
"post-type": "article",
"_id": "19810307",
"_source": "12",
"_is_read": true
}
Reminder that it's #HomebrewWebsiteClub Nottingham tonight! I hope to see you there at 1730 for some website stuff, and maybe playing around with some of the stuff I mentioned at #TechNott! https://events.indieweb.org/2021/04/homebrew-website-club-nottingham-7uyCl6f2j0vV
{
"type": "entry",
"published": "2021-04-14T07:48:24.258Z",
"url": "https://www.jvt.me/mf2/2021/04/vcxah/",
"category": [
"homebrew-website-club",
"tech-nottingham"
],
"content": {
"text": "Reminder that it's #HomebrewWebsiteClub Nottingham tonight! I hope to see you there at 1730 for some website stuff, and maybe playing around with some of the stuff I mentioned at #TechNott! https://events.indieweb.org/2021/04/homebrew-website-club-nottingham-7uyCl6f2j0vV",
"html": "<p>Reminder that it's <a href=\"https://www.jvt.me/tags/homebrew-website-club/\">#HomebrewWebsiteClub</a> Nottingham tonight! I hope to see you there at 1730 for some website stuff, and maybe playing around with some of the stuff I mentioned at <a href=\"https://www.jvt.me/tags/tech-nottingham/\">#TechNott</a>! <a href=\"https://events.indieweb.org/2021/04/homebrew-website-club-nottingham-7uyCl6f2j0vV\">https://events.indieweb.org/2021/04/homebrew-website-club-nottingham-7uyCl6f2j0vV</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": "19761490",
"_source": "2169",
"_is_read": true
}
This post will show you step by step how you can let people log in to your website with their own IndieAuth website so you don't need to worry about user accounts or passwords.
{
"type": "entry",
"published": "2021-04-13T21:15:45-07:00",
"summary": "This post will show you step by step how you can let people log in to your website with their own IndieAuth website so you don't need to worry about user accounts or passwords.",
"url": "https://aaronparecki.com/2021/04/13/26/indieauth",
"category": [
"indieauth",
"indieweb",
"oauth"
],
"syndication": [
"https://micro.blog/aaronpk/11319738",
"https://news.indieweb.org/en"
],
"name": "How to Sign Users In with IndieAuth",
"author": {
"type": "card",
"name": "Aaron Parecki",
"url": "https://aaronparecki.com/",
"photo": "https://aperture-media.p3k.io/aaronparecki.com/41061f9de825966faa22e9c42830e1d4a614a321213b4575b9488aa93f89817a.jpg"
},
"post-type": "article",
"_id": "19758665",
"_source": "16",
"_is_read": true
}
Looking forward to this Webmentions pop-up session next month.
{
"type": "entry",
"author": {
"name": "Manton Reece",
"url": "https://www.manton.org/",
"photo": "https://micro.blog/manton/avatar.jpg"
},
"url": "https://www.manton.org/2021/04/13/looking-forward-to.html",
"content": {
"html": "<p>Looking forward to this <a href=\"https://events.indieweb.org/2021/05/webmentions-beyond-webmention-io-zG4JpHhZShVA\" class=\"u-in-reply-to\">Webmentions pop-up session</a> next month. </p>",
"text": "Looking forward to this Webmentions pop-up session next month."
},
"published": "2021-04-13T17:03:51-05:00",
"post-type": "note",
"_id": "19753877",
"_source": "12",
"_is_read": true
}
Thanks to everyone who joined me last night at #TechNott for my talk about the #IndieWeb - you can find the recording of the video at https://www.youtube.com/watch?v=qFXOZww5mmE - I'll also look at getting it uploaded to Archive.org for longevity!
{
"type": "entry",
"published": "2021-04-13T12:02:42Z",
"url": "https://www.jvt.me/mf2/2021/04/lzuc6/",
"category": [
"public-speaking",
"tech-nottingham",
"indieweb"
],
"content": {
"text": "Thanks to everyone who joined me last night at #TechNott for my talk about the #IndieWeb - you can find the recording of the video at https://www.youtube.com/watch?v=qFXOZww5mmE - I'll also look at getting it uploaded to Archive.org for longevity!",
"html": "<p>Thanks to everyone who joined me last night at <a href=\"https://www.jvt.me/tags/tech-nottingham/\">#TechNott</a> for my talk about the <a href=\"https://www.jvt.me/tags/indieweb/\">#IndieWeb</a> - you can find the recording of the video at <a href=\"https://www.youtube.com/watch?v=qFXOZww5mmE\">https://www.youtube.com/watch?v=qFXOZww5mmE</a> - I'll also look at getting it uploaded to Archive.org for longevity!</p>"
},
"author": {
"type": "card",
"name": "Jamie Tanna",
"url": "https://www.jvt.me",
"photo": "https://www.jvt.me/img/profile.png"
},
"post-type": "note",
"_id": "19737830",
"_source": "2169",
"_is_read": true
}
Not long now till you'll be able to hear me talking about the #IndieWeb at tonight's #TechNott - hope to see some of you there to learn what it is, why some of us want to own our data and be our own platforms, and more!
🚨 TONIGHT 🚨
We have @JamieTanna talking all about the #indieWeb and owning your data plus we'll be asking you to share your personal sites in the second half!
⏰ O...
{
"type": "entry",
"published": "2021-04-12T18:05:00+0100",
"url": "https://www.jvt.me/mf2/2021/04/49fni/",
"category": [
"indieweb",
"tech-nottingham"
],
"quotation-of": "https://twitter.com/technottingham/status/1381571321344196616",
"content": {
"text": "Not long now till you'll be able to hear me talking about the #IndieWeb at tonight's #TechNott - hope to see some of you there to learn what it is, why some of us want to own our data and be our own platforms, and more!",
"html": "<p>Not long now till you'll be able to hear me talking about the <a href=\"https://www.jvt.me/tags/indieweb/\">#IndieWeb</a> at tonight's <a href=\"https://www.jvt.me/tags/tech-nottingham/\">#TechNott</a> - hope to see some of you there to learn what it is, why some of us want to own our data and be our own platforms, and more!</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/technottingham/status/1381571321344196616": {
"type": "entry",
"url": "https://twitter.com/technottingham/status/1381571321344196616",
"photo": [
"https://www.jvt.me/"
],
"content": {
"text": "\ud83d\udea8 TONIGHT \ud83d\udea8\nWe have @JamieTanna talking all about the #indieWeb and owning your data plus we'll be asking you to share your personal sites in the second half!\n\u23f0 Online from 18.30 nott.tech/tn-apr-2021",
"html": "\ud83d\udea8 TONIGHT \ud83d\udea8\nWe have <a href=\"https://twitter.com/JamieTanna\">@JamieTanna</a> talking all about the <a href=\"https://twitter.com/search?q=%23indieWeb\">#indieWeb</a> and owning your data plus we'll be asking you to share your personal sites in the second half!\n\u23f0 Online from 18.30 <a href=\"http://nott.tech/tn-apr-2021\">nott.tech/tn-apr-2021</a>"
},
"post-type": "photo"
}
},
"_id": "19722852",
"_source": "2169",
"_is_read": true
}
Happy #TechNott day all! Looking forward to seeing you later to hear a bit more about what the #IndieWeb is, and the ways you can get involved owning your data and building cool things for yourself https://www.technottingham.com/events/tech-nottingham-april-2021
{
"type": "entry",
"published": "2021-04-12T08:23:00+0100",
"url": "https://www.jvt.me/mf2/2021/04/t4vph/",
"category": [
"public-speaking",
"tech-nottingham",
"indieweb"
],
"content": {
"text": "Happy #TechNott day all! Looking forward to seeing you later to hear a bit more about what the #IndieWeb is, and the ways you can get involved owning your data and building cool things for yourself https://www.technottingham.com/events/tech-nottingham-april-2021",
"html": "<p>Happy <a href=\"https://www.jvt.me/tags/tech-nottingham/\">#TechNott</a> day all! Looking forward to seeing you later to hear a bit more about what the <a href=\"https://www.jvt.me/tags/indieweb/\">#IndieWeb</a> is, and the ways you can get involved owning your data and building cool things for yourself <a href=\"https://www.technottingham.com/events/tech-nottingham-april-2021\">https://www.technottingham.com/events/tech-nottingham-april-2021</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": "19708058",
"_source": "2169",
"_is_read": true
}
In the midst of a re-write of how my site works and in passing conversation in the IndieWeb chat, I think about how to 'show' the IndieWeb as something people can invest in versus a collection of things that...
{
"type": "entry",
"url": "https://v2.jacky.wtf/post/5832bbcb-b152-49d8-bff2-d41997719210",
"content": {
"text": "In the midst of a re-write of how my site works and in passing conversation in the IndieWeb chat, I think about how to 'show' the IndieWeb as something people can invest in versus a collection of things that...",
"html": "<p>In the midst of a re-write of how my site works and <a href=\"https://chat.indieweb.org/meta/2021-04-09#t1617992930428800\">in passing conversation in the IndieWeb chat</a>, I think about how to 'show' the IndieWeb as something people can invest in versus a collection of things that...</p>"
},
"post-type": "note",
"_id": "19663685",
"_source": "1886",
"_is_read": true
}
In the midst of a re-write of how my site works and in passing conversation in the IndieWeb chat, I think about how to 'show' the IndieWeb as something people can invest in versus a collection of things that...
{
"type": "entry",
"url": "https://v2.jacky.wtf/post/11e8c6f0-d513-4623-b167-502d764a9896",
"content": {
"text": "In the midst of a re-write of how my site works and in passing conversation in the IndieWeb chat, I think about how to 'show' the IndieWeb as something people can invest in versus a collection of things that...",
"html": "<p>In the midst of a re-write of how my site works and <a href=\"https://chat.indieweb.org/meta/2021-04-09#t1617992930428800\">in passing conversation in the IndieWeb chat</a>, I think about how to 'show' the IndieWeb as something people can invest in versus a collection of things that...</p>"
},
"post-type": "note",
"_id": "19663686",
"_source": "1886",
"_is_read": true
}
Turning off syndication to Twitter, at least for today. If you're reading this, it's via my indieweb feed on my Known site, or on Micro.blog.
{
"type": "entry",
"published": "2021-04-09T16:21:07+00:00",
"url": "https://werd.io/2021/turning-off-syndication-to-twitter-at-least",
"content": {
"text": "Turning off syndication to Twitter, at least for today. If you're reading this, it's via my indieweb feed on my Known site, or on Micro.blog."
},
"author": {
"type": "card",
"name": "Ben Werdm\u00fcller",
"url": "https://werd.io/profile/benwerd",
"photo": "https://werd.io/file/5d388c5fb16ea14aac640912/thumb.jpg"
},
"post-type": "note",
"_id": "19658557",
"_source": "191",
"_is_read": true
}
Now that you know why posting for “free” on MySpaceBook isn’t a good idea. Check out Micro.blog. I just paid for another year, again. Totally worth it. Micro.blog is the easy way to #indieweb.
{
"type": "entry",
"author": {
"name": "Christopher Chelpka",
"url": "https://christopherchelpka.com",
"photo": "https://www.gravatar.com/avatar/6298c8cd5b76684bd44569eadc18838c?s=96&d=https%3A%2F%2Fmicro.blog%2Fimages%2Fblank_avatar.png"
},
"url": "https://www.christopherchelpka.com/2021/04/06/now-that-you.html",
"content": {
"html": "<p>Now that you know why posting for \u201cfree\u201d on MySpaceBook isn\u2019t a good idea. Check out Micro.blog. I just paid for another year, again. Totally worth it. Micro.blog is the easy way to #indieweb.</p>",
"text": "Now that you know why posting for \u201cfree\u201d on MySpaceBook isn\u2019t a good idea. Check out Micro.blog. I just paid for another year, again. Totally worth it. Micro.blog is the easy way to #indieweb."
},
"published": "2021-04-07T05:00:07+00:00",
"post-type": "note",
"_id": "33380025",
"_source": "7224",
"_is_read": true
}
I can very much relate to what Craig is saying here.
{
"type": "entry",
"published": "2021-04-06T18:33:36Z",
"url": "https://adactio.com/links/18009",
"category": [
"code",
"coding",
"indieweb",
"maintenance",
"personal",
"websites",
"tinkering",
"covid-19",
"coronavirus",
"hacking",
"wired"
],
"bookmark-of": [
"https://www.wired.com/story/healing-power-javascript-code-programming/"
],
"content": {
"text": "The Healing Power of Javascript | WIRED\n\n\n\nI can very much relate to what Craig is saying here.",
"html": "<h3>\n<a class=\"p-name u-bookmark-of\" href=\"https://www.wired.com/story/healing-power-javascript-code-programming/\">\nThe Healing Power of Javascript | WIRED\n</a>\n</h3>\n\n<p><a href=\"https://adactio.com/journal/16585\">I can very much relate</a> to what Craig is saying here.</p>"
},
"author": {
"type": "card",
"name": "Jeremy Keith",
"url": "https://adactio.com/",
"photo": "https://adactio.com/images/photo-150.jpg"
},
"post-type": "bookmark",
"_id": "19579521",
"_source": "2",
"_is_read": true
}
Woop woop! Very excited for this 🎉 looking forward to sharing a bit more about what the #IndieWeb is, why you may be interested and what folks can do to get involved!
Next week we've got @JamieTanna talking all about the #IndieWeb and owning your own data!
Join us Monday 12th April 18.30 online 📅
All the deets ➡️ nott.tech/tn-ap...
{
"type": "entry",
"published": "2021-04-06T09:28:00+0100",
"url": "https://www.jvt.me/mf2/2021/04/6ekfo/",
"category": [
"public-speaking",
"indieweb"
],
"quotation-of": "https://twitter.com/technottingham/status/1379341256032198660",
"content": {
"text": "Woop woop! Very excited for this \ud83c\udf89 looking forward to sharing a bit more about what the #IndieWeb is, why you may be interested and what folks can do to get involved!",
"html": "<p>Woop woop! Very excited for this \ud83c\udf89 looking forward to sharing a bit more about what the <a href=\"https://www.jvt.me/tags/indieweb/\">#IndieWeb</a> is, why you may be interested and what folks can do to get involved!</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/technottingham/status/1379341256032198660": {
"type": "entry",
"url": "https://twitter.com/technottingham/status/1379341256032198660",
"photo": [
"https://www.jvt.me/"
],
"content": {
"text": "Next week we've got @JamieTanna talking all about the #IndieWeb and owning your own data!\nJoin us Monday 12th April 18.30 online \ud83d\udcc5\nAll the deets \u27a1\ufe0f nott.tech/tn-apr-2021",
"html": "Next week we've got <a href=\"https://twitter.com/JamieTanna\">@JamieTanna</a> talking all about the <a href=\"https://twitter.com/search?q=%23IndieWeb\">#IndieWeb</a> and owning your own data!\nJoin us Monday 12th April 18.30 online \ud83d\udcc5\nAll the deets \u27a1\ufe0f <a href=\"http://nott.tech/tn-apr-2021\">nott.tech/tn-apr-2021</a>"
},
"post-type": "photo"
}
},
"_id": "19569651",
"_source": "2169",
"_is_read": true
}