This is what happens when you accidentally feed incorrect post data to #Blogblaze and the h-entry template rendering fails. #webdevelopment #frontend #Deno #webdesign #IndieWeb
{
"type": "entry",
"published": "2020-07-03T18:02:27+00:00",
"url": "https://fireburn.ru/posts/1593799347",
"category": [
"Blogblaze",
"webdevelopment",
"frontend",
"Deno",
"webdesign",
"IndieWeb"
],
"photo": [
"https://fireburn.ru/media/c5/ea/e7/07/6ff1e054cd8aa0a7e8e04b9ee1f095805c7f9394eccbf9e04713e8f3.png"
],
"syndication": [
"https://twitter.com/kisik21/status/1279113315222986753"
],
"content": {
"text": "This is what happens when you accidentally feed incorrect post data to #Blogblaze and the h-entry template rendering fails. #webdevelopment #frontend #Deno #webdesign #IndieWeb",
"html": "<p>This is what happens when you accidentally feed incorrect post data to #Blogblaze and the h-entry template rendering fails. #webdevelopment #frontend #Deno #webdesign #IndieWeb</p>"
},
"author": {
"type": "card",
"name": "Vika",
"url": "https://fireburn.ru/",
"photo": "https://fireburn.ru/media/f1/5a/fb/9b/081efafb97b4ad59f5025cf2fd0678b8f3e20e4c292489107d52be09.png"
},
"post-type": "photo",
"_id": "12930314",
"_source": "1371",
"_is_read": true
}
{
"type": "entry",
"published": "2020-07-03T13:27:37Z",
"url": "https://adactio.com/journal/17086",
"category": [
"",
"css",
"colours",
"schemes",
"styles",
"switcher",
"toggle",
"light",
"dark",
"modes",
"indiewebcamp",
"styling",
"images",
"frontend",
"development",
"design"
],
"syndication": [
"https://medium.com/@adactio/194630f97c43"
],
"name": "Dark mode revisited",
"content": {
"text": "I added a dark mode to my website a while back. It was a fun thing to do during Indie Web Camp Amsterdam last year.\n\nI tied the colour scheme to the operating system level. If you choose a dark mode in your OS, my website will adjust automatically thanks to the prefers-color-scheme: dark media query.\n\nBut I\u2019ve seen notes from a few friends, not about my site specifically, but about how they like having an explicit toggle for dark mode (as well as the media query). Whenever I read those remarks, I\u2019d think \u201cI\u2019m really not sure I\u2019ve got time to deal with adding that kind of toggle to my site.\u201d\n\nBut then I realised, \u201cJeremy, you absolute muffin! You\u2019ve had a theme switcher on your website for almost two decades now!\u201d\n\nDoh! I had forgotten about that theme switcher. It dates back to the early days of CSS. I wanted my site to be a demonstration of how you could apply different styles to the same underlying markup (this was before the CSS Zen Garden came along). Those themes are very dated now, but if you like you can view my site with a Zeldman theme or a sci-fi theme.\n\nTo offer a dark-mode theme for my site, all I had to do was take the default stylesheet, pull out the custom properties from the prefers-color-scheme: dark media query, and done. It took less than five minutes.\n\nSo if you want to view my site in dark mode, it\u2019s one of the options in the \u201cCustomise\u201d dropdown on every page of the website.",
"html": "<p><a href=\"https://adactio.com/journal/15941\">I added a dark mode to my website a while back</a>. It was a fun thing to do during Indie Web Camp Amsterdam last year.</p>\n\n<p>I tied the colour scheme to the operating system level. If you choose a dark mode in your OS, my website will adjust automatically thanks to the <code>prefers-color-scheme: dark</code> media query.</p>\n\n<p>But I\u2019ve seen notes from a few friends, not about my site specifically, but about how they like having an explicit toggle for dark mode (as well as the media query). Whenever I read those remarks, I\u2019d think \u201cI\u2019m really not sure I\u2019ve got time to deal with adding that kind of toggle to my site.\u201d</p>\n\n<p>But then I realised, \u201cJeremy, you absolute muffin! You\u2019ve had a theme switcher on your website for almost two decades now!\u201d</p>\n\n<p>Doh! I had forgotten about that theme switcher. It dates back to the early days of CSS. I wanted my site to be a demonstration of how you could apply different styles to the same underlying markup (this was before the CSS Zen Garden came along). Those themes are very dated now, but if you like you can view my site with <a href=\"https://adactio.com/?skin=zeldman\">a Zeldman theme</a> or <a href=\"https://adactio.com/?skin=sci-fi\">a sci-fi theme</a>.</p>\n\n<p>To offer a dark-mode theme for my site, all I had to do was take the default stylesheet, pull out the custom properties from the <code>prefers-color-scheme: dark</code> media query, and done. It took less than five minutes.</p>\n\n<p>So if you want to view my site <a href=\"https://adactio.com/?skin=dark\">in dark mode</a>, it\u2019s one of the options in the \u201cCustomise\u201d dropdown on every page of the website.</p>"
},
"author": {
"type": "card",
"name": "Jeremy Keith",
"url": "https://adactio.com/",
"photo": "https://adactio.com/images/photo-150.jpg"
},
"post-type": "article",
"_id": "12923943",
"_source": "2",
"_is_read": true
}
Catching up on a couple of the sessions I missed at IndieWebCamp West. All the videos are linked on the schedule page here.
{
"type": "entry",
"author": {
"name": "Manton Reece",
"url": "https://www.manton.org/",
"photo": "https://micro.blog/manton/avatar.jpg"
},
"url": "https://www.manton.org/2020/07/02/catching-up-on.html",
"content": {
"html": "<p>Catching up on a couple of the sessions I missed at IndieWebCamp West. All the videos are linked <a href=\"https://indieweb.org/2020/West/Schedule\">on the schedule page here</a>.</p>",
"text": "Catching up on a couple of the sessions I missed at IndieWebCamp West. All the videos are linked on the schedule page here."
},
"published": "2020-07-02T15:03:22-05:00",
"post-type": "note",
"_id": "12908389",
"_source": "12",
"_is_read": true
}
{
"type": "entry",
"published": "2020-07-01 18:00-0700",
"rsvp": "yes",
"url": "http://tantek.com/2020/183/t1/homebrew-website-club-west-coast",
"in-reply-to": [
"https://events.indieweb.org/2020/07/homebrew-website-club-west-coast-gIN0wgZCOdeP"
],
"content": {
"text": "hosting Homebrew Website Club West Coast NOW!\n\ud83d\uddd3 started at 18:00, seven of us here, hop on Zoom and say hi!\nhttps://events.indieweb.org/2020/07/homebrew-website-club-west-coast-gIN0wgZCOdeP\n@brb_irl @Kongaloosh @AllAboutGeorge @JackyAlcine @AndiGalpern @indirect @generativist @BenWerd @pvh @aaronpk",
"html": "hosting Homebrew Website Club West Coast NOW!<br />\ud83d\uddd3 started at 18:00, seven of us here, hop on Zoom and say hi!<br /><a href=\"https://events.indieweb.org/2020/07/homebrew-website-club-west-coast-gIN0wgZCOdeP\">https://events.indieweb.org/2020/07/homebrew-website-club-west-coast-gIN0wgZCOdeP</a><br /><a class=\"h-cassis-username\" href=\"https://twitter.com/brb_irl\">@brb_irl</a> <a class=\"h-cassis-username\" href=\"https://twitter.com/Kongaloosh\">@Kongaloosh</a> <a class=\"h-cassis-username\" href=\"https://twitter.com/AllAboutGeorge\">@AllAboutGeorge</a> <a class=\"h-cassis-username\" href=\"https://twitter.com/JackyAlcine\">@JackyAlcine</a> <a class=\"h-cassis-username\" href=\"https://twitter.com/AndiGalpern\">@AndiGalpern</a> <a class=\"h-cassis-username\" href=\"https://twitter.com/indirect\">@indirect</a> <a class=\"h-cassis-username\" href=\"https://twitter.com/generativist\">@generativist</a> <a class=\"h-cassis-username\" href=\"https://twitter.com/BenWerd\">@BenWerd</a> <a class=\"h-cassis-username\" href=\"https://twitter.com/pvh\">@pvh</a> <a class=\"h-cassis-username\" href=\"https://twitter.com/aaronpk\">@aaronpk</a>"
},
"author": {
"type": "card",
"name": "Tantek \u00c7elik",
"url": "http://tantek.com/",
"photo": "https://aperture-media.p3k.io/tantek.com/acfddd7d8b2c8cf8aa163651432cc1ec7eb8ec2f881942dca963d305eeaaa6b8.jpg"
},
"post-type": "rsvp",
"refs": {
"https://events.indieweb.org/2020/07/homebrew-website-club-west-coast-gIN0wgZCOdeP": {
"type": "entry",
"url": "https://events.indieweb.org/2020/07/homebrew-website-club-west-coast-gIN0wgZCOdeP",
"name": "an IndieWeb event",
"post-type": "article"
}
},
"_id": "12887511",
"_source": "1",
"_is_read": true
}
For all of y’all who make Twitter threads, now you can do that and then publish it BACK to your site using a standard in publishing content on the Web: Micropub! https://twitter.com/threadreaderapp/status/1276635958708862976
{
"type": "entry",
"published": "2020-07-01T16:30:26.78885-07:00",
"url": "https://v2.jacky.wtf/post/f141c646-507a-431b-8984-7443a03b60f5",
"content": {
"text": "For all of y\u2019all who make Twitter threads, now you can do that and then publish it BACK to your site using a standard in publishing content on the Web: Micropub! https://twitter.com/threadreaderapp/status/1276635958708862976",
"html": "<p>For all of y\u2019all who make Twitter threads, now you can do that and then publish it BACK to your site using a standard in publishing content on the Web: Micropub! <a href=\"https://twitter.com/threadreaderapp/status/1276635958708862976\">https://twitter.com/threadreaderapp/status/1276635958708862976</a></p>"
},
"author": {
"type": "card",
"name": "",
"url": "https://v2.jacky.wtf",
"photo": null
},
"post-type": "note",
"_id": "12883589",
"_source": "1886",
"_is_read": true
}
{
"type": "entry",
"author": {
"name": "Neil Mather",
"url": "https://doubleloop.net/",
"photo": null
},
"url": "https://doubleloop.net/2020/07/01/control-of-computing-infrastructure/",
"published": "2020-07-01T20:48:01+00:00",
"content": {
"html": "<p>I had not really thought much about the tech firms in this light before \u2013 of the undue control they have on computing infrastructure. (I think the author here including both hardware and software platforms in \u2018infrastructure\u2019).</p>\n<blockquote><p>In all the global crises, pandemics and social upheavals that may yet come, those in control of the computers, not those with the largest datasets, have the best visibility and the best \u2013 and perhaps the scariest \u2014 ability to change the world.</p>\n<p>\u2013 <a href=\"https://www.theguardian.com/commentisfree/2020/jul/01/apple-google-contact-tracing-app-tech-giant-digital-rights\">Privacy is not the problem with the Apple-Google contact-tracing toolkit</a></p></blockquote>\n<p>I don\u2019t know if it\u2019s a bigger problem or not than <a href=\"https://commonplace.doubleloop.net/surveillance-capitalism.html\">surveillance capitalism</a> though. They both seem like big problems, in tandem.</p>\n<p>The distinction between harvesting data and running the platform seems pretty neglible, too. Unless maybe he\u2019s talking about things like Amazon Web Services more than things like Facebook?</p>\n<p>Dunno. Regardless, cool to see both <a href=\"https://commonplace.doubleloop.net/20200308230733-right_to_repair.html\">right to repair</a> and <a href=\"https://commonplace.doubleloop.net/indieweb.html\">IndieWeb</a>-adjacent stuff mentioned together as modes of resistance against big tech.</p>",
"text": "I had not really thought much about the tech firms in this light before \u2013 of the undue control they have on computing infrastructure. (I think the author here including both hardware and software platforms in \u2018infrastructure\u2019).\nIn all the global crises, pandemics and social upheavals that may yet come, those in control of the computers, not those with the largest datasets, have the best visibility and the best \u2013 and perhaps the scariest \u2014 ability to change the world.\n\u2013 Privacy is not the problem with the Apple-Google contact-tracing toolkit\nI don\u2019t know if it\u2019s a bigger problem or not than surveillance capitalism though. They both seem like big problems, in tandem.\nThe distinction between harvesting data and running the platform seems pretty neglible, too. Unless maybe he\u2019s talking about things like Amazon Web Services more than things like Facebook?\nDunno. Regardless, cool to see both right to repair and IndieWeb-adjacent stuff mentioned together as modes of resistance against big tech."
},
"name": "Control of computing infrastructure",
"post-type": "article",
"_id": "12882091",
"_source": "1895",
"_is_read": true
}
#100days 60 - Made a small but long overdue change to my site, so that it only sends me notifications about new webmentions. My notifications were filling up with duplicate mentions because of people sending them every time they build their site (which is totally fine)
{
"type": "entry",
"published": "2020-07-01T08:55:00.550Z",
"url": "https://grant.codes/2020/07/01/08-55-00",
"category": [
"100days"
],
"syndication": [
"https://t.me/Telegram/261"
],
"content": {
"text": "#100days 60 - Made a small but long overdue change to my site, so that it only sends me notifications about new webmentions. My notifications were filling up with duplicate mentions because of people sending them every time they build their site (which is totally fine)",
"html": "<p>#100days 60 - Made a small but long overdue change to my site, so that it only sends me notifications about new webmentions. My notifications were filling up with duplicate mentions because of people sending them every time they build their site (which is totally fine)</p>"
},
"author": {
"type": "card",
"name": "Grant Richmond",
"url": "https://grant.codes/",
"photo": "https://images.weserv.nl/?url=grant.codes%2Fimg%2Fme.jpg&errorredirect=grant.codes%2Fimg%2Fme.jpg&w=20&h=20&fit=contain&dpr=2"
},
"post-type": "note",
"_id": "12864706",
"_source": "11",
"_is_read": true
}
Hm, advice is interesting. I want this to signify that it’s a tag of sorts; something that can be indexed (for a negative filter search of sorts). This is making me want to lean into something like this format:
<span class="p-content-category p-category">gore</span>
<span class="p-content-category p-category">blood</span>
Leaning into what we have for tagging already would allow us to build a common way of filtering things out (or in). This is something that would have to be pushed up into the Microformats spec, IMO.
Also, I took some time to see how our friends in ActivityPub took this: https://github.com/w3c/activitypub/issues/232, some important notes there regarding overloading. One downside is that they relied on Mastodon to be the defacto representative of AP, in Microformats; the format is the leader!
{
"type": "entry",
"published": "2020-06-30T19:36:17.56587-07:00",
"url": "https://v2.jacky.wtf/post/d7187860-6d7a-4cc9-9465-792daaab2b30",
"in-reply-to": [
"https://github.com/snarfed/bridgy/issues/952#issuecomment-652084336"
],
"content": {
"text": "Hm, advice is interesting. I want this to signify that it\u2019s a tag of sorts; something that can be indexed (for a negative filter search of sorts). This is making me want to lean into something like this format:<span class=\"p-content-category p-category\">gore</span>\n<span class=\"p-content-category p-category\">blood</span>\nLeaning into what we have for tagging already would allow us to build a common way of filtering things out (or in). This is something that would have to be pushed up into the Microformats spec, IMO.\nAlso, I took some time to see how our friends in ActivityPub took this: https://github.com/w3c/activitypub/issues/232, some important notes there regarding overloading. One downside is that they relied on Mastodon to be the defacto representative of AP, in Microformats; the format is the leader!",
"html": "<p>Hm, <code>advice</code> is interesting. I want this to signify that it\u2019s a tag of sorts; something that can be indexed (for a negative filter search of sorts). This is making me want to lean into something like this format:</p><pre><code><span class=\"p-content-category p-category\">gore</span>\n<span class=\"p-content-category p-category\">blood</span></code></pre>\n<p>Leaning into what we have for tagging already would allow us to build a common way of filtering things out (or in). This is something that would have to be pushed up into the Microformats spec, IMO.</p>\n<p>Also, I took some time to see how our friends in ActivityPub took this: <a href=\"https://github.com/w3c/activitypub/issues/232\">https://github.com/w3c/activitypub/issues/232</a>, some important notes there regarding overloading. One downside is that they relied on Mastodon to be the defacto representative of AP, in Microformats; the format is the leader!</p>"
},
"author": {
"type": "card",
"name": "",
"url": "https://v2.jacky.wtf",
"photo": null
},
"post-type": "reply",
"refs": {
"https://github.com/snarfed/bridgy/issues/952#issuecomment-652084336": {
"type": "entry",
"url": "https://github.com/snarfed/bridgy/issues/952#issuecomment-652084336",
"content": {
"text": "OK, thanks! will have a think and try to see if I can gain some traction towards consensus.\n\nThis is something I'm into and didn't know what kind of name I wanted to use in the property naming.\n\nStill thinking about how to word this, mainly due to my novice status in the world of indieweb.. but, Jacky how does p-content-advice sound\\feel?",
"html": "<blockquote>\n<blockquote>\n<p>OK, thanks! will have a think and try to see if I can gain some traction towards consensus.</p>\n</blockquote>\n<p>This is something I'm into and didn't know what kind of name I wanted to use in the property naming.</p>\n</blockquote>\n<p>Still thinking about how to word this, mainly due to my novice status in the world of indieweb.. but, Jacky how does p-content-advice sound\\feel? </p>"
},
"author": {
"type": "card",
"name": "jk-na",
"url": "https://github.com/jk-na",
"photo": null
},
"post-type": "note"
}
},
"_id": "12859166",
"_source": "1886",
"_is_read": true
}
{
"type": "entry",
"published": "2020-06-30T19:48:13Z",
"url": "https://adactio.com/links/17076",
"category": [
"weird",
"webring",
"indieweb",
"personal",
"websites",
"design",
"whimsical",
"fun",
"delight",
"personality"
],
"bookmark-of": [
"https://weirdwidewebring.net/"
],
"content": {
"text": "Weird Wide Webring\n\n\n\nMore of the whimsical web!",
"html": "<h3>\n<a class=\"p-name u-bookmark-of\" href=\"https://weirdwidewebring.net/\">\nWeird Wide Webring\n</a>\n</h3>\n\n<p>More of <a href=\"https://adactio.com/links/17075\">the whimsical web</a>!</p>"
},
"author": {
"type": "card",
"name": "Jeremy Keith",
"url": "https://adactio.com/",
"photo": "https://adactio.com/images/photo-150.jpg"
},
"post-type": "bookmark",
"_id": "12851309",
"_source": "2",
"_is_read": true
}
A collection of truly personal sites.
This site is meant to showcase how a more personal web could look like, and hopefully give you some inspiration to make your own corner of the web a bit weirder.
Of course Cassie’s site is included!
{
"type": "entry",
"published": "2020-06-30T19:45:46Z",
"url": "https://adactio.com/links/17075",
"category": [
"indieweb",
"personal",
"websites",
"design",
"whimsical",
"fun",
"delight",
"personality"
],
"bookmark-of": [
"https://whimsical.club/"
],
"content": {
"text": "The Whimsical Web\n\n\n\nA collection of truly personal sites.\n\n\n This site is meant to showcase how a more personal web could look like, and hopefully give you some inspiration to make your own corner of the web a bit weirder.\n\n\nOf course Cassie\u2019s site is included!",
"html": "<h3>\n<a class=\"p-name u-bookmark-of\" href=\"https://whimsical.club/\">\nThe Whimsical Web\n</a>\n</h3>\n\n<p>A collection of truly personal sites.</p>\n\n<blockquote>\n <p>This site is meant to showcase how a more personal web could look like, and hopefully give you some inspiration to make your own corner of the web a bit weirder.</p>\n</blockquote>\n\n<p>Of <em>course</em> <a href=\"https://www.cassie.codes/\">Cassie\u2019s site</a> is included!</p>"
},
"author": {
"type": "card",
"name": "Jeremy Keith",
"url": "https://adactio.com/",
"photo": "https://adactio.com/images/photo-150.jpg"
},
"post-type": "bookmark",
"_id": "12851310",
"_source": "2",
"_is_read": true
}
As soon as I confirm that Webmentions work well with Lighthouse, I think I’m going to draft my backfill of content from my old Twitter account and Instagram
{
"type": "entry",
"published": "2020-06-30T10:54:00.00000-07:00",
"url": "https://v2.jacky.wtf/post/620c58f0-d746-4bc0-b5b1-42add609bb66",
"content": {
"text": "As soon as I confirm that Webmentions work well with Lighthouse, I think I\u2019m going to draft my backfill of content from my old Twitter account and Instagram",
"html": "<p>As soon as I confirm that Webmentions work well with Lighthouse, I think I\u2019m going to draft my backfill of content from my old Twitter account and Instagram</p>"
},
"author": {
"type": "card",
"name": "",
"url": "https://v2.jacky.wtf",
"photo": null
},
"post-type": "note",
"_id": "12848260",
"_source": "1886",
"_is_read": true
}
sad that IndieWeb summit isn't happening this year, but enjoying catching up on all the recordings from the online event over the weekend! Thanks to everyone for the great discussions and the organisers for making the content available.
{
"type": "entry",
"published": "2020-06-30T21:50:36+10:00",
"url": "https://mblaney.xyz/2020-06-30-sad_that_IndieWeb_summit_isnt_happening_this_",
"syndication": [
"https://twitter.com/malcolmblaney/status/1277932564683112448"
],
"content": {
"text": "sad that IndieWeb summit isn't happening this year, but enjoying catching up on all the recordings from the online event over the weekend! Thanks to everyone for the great discussions and the organisers for making the content available.",
"html": "sad that IndieWeb summit isn't happening this year, but enjoying catching up on all the recordings from the online event over the weekend! Thanks to everyone for the great discussions and the organisers for making the content available.<a href=\"https://brid.gy/publish/twitter?bridgy_omit_link=true\"></a><a href=\"https://twitter.com/malcolmblaney/status/1277932564683112448\" class=\"u-syndication\"></a>"
},
"author": {
"type": "card",
"name": "Malcolm Blaney",
"url": "https://mblaney.xyz",
"photo": "https://mblaney.xyz/public/profile_thumb.png"
},
"post-type": "note",
"_id": "12839709",
"_source": "3708",
"_is_read": true
}
I recently had a chat with a couple of friends about style; it inspired me to take a project off the back-burner and turn it into code.
{
"type": "entry",
"published": "2020-06-29 23:40:28.756219",
"summary": "I recently had a chat with a couple of friends about style; it inspired me to take a project off the back-burner and turn it into code.",
"url": "https://kongaloosh.com/e/2020/6/29/aether-a-p",
"syndication": [
"https://twitter.com/kongaloosh/status/1277813401025118208"
],
"name": "Aether: A Personal Board For Inspiration",
"content": {
"text": "I recently had a chat with a couple of friends about style; it inspired me to take a project off the back-burner and turn it into code.\n \n \n \n \n\n \n\n\n \n \n A couple of friends posed a question: is artistic style something that is innate, or cultivated? We spent a few hours digging into art we had created throughout adolescence and into adulthood, picking apart what remained consistent throughout. We sifted through sketchbooks thinking about what may have influenced changes. \nTo some degree, each of us kept track of inspiration. Katryna went as far as to keep collages and document each of them. I've always admired collages: there's something about collecting, organising, and drawing inspiration from unexpected places.\nWhen I travel, I often take pictures of scenes I find interesting: details that catch my eye. A memorable example: to shelter from the rain in Vienna, I ducked into a chapel. The dreary light diffused through the windows to create a high-contrast baroque scene. Typically overwhelming colours and ornamentation became subdued. I collected the moment for later.\n\nIt's not just scenes that I collect. Occasionally I'll find a striking design element or detail and save it for later. A bar I was dining at during a layover in the Houston airport was tiled with mahjong pieces.\n\nIn spite of my aesthetic hoarding, I don't really have a method for collecting these images in a sensible way. They sit on my phone, my computer, and my desktop: apocalyptically poor organisation. I'm always on the hunt for inspiration, but don't have a place to enjoy the fruits of this collecting. \nSo I made an indie-pinboard.\naether is a small flask-app with hints of javascript that take a folder on your server and transform it into an infinite scroll of images that are slowly loaded as you cruise by. In my head, these scenes and images were being collected to make some wild reference art-book collage. By making a tiled album, I'm conveying the sense of purpose that I originally intended.\n\nYou can find the code in a repo here.\nThese images are displayed in a haphazard way: the only unifying trait is that each represents something that I liked. In the future I hope to add a more contentful display. I'm thinking that by employing some simple computer vision, I can partition the images by theme and sort them by feel.\n \n\n \n \n \n \n \n \n\n\n \n\n\n \n \n \n \n \n tech\n \n article\n \n dev\n \n indie\n \n indieweb\n \n art\n \n inspiration\n \n hack",
"html": "<p>\n <i>\n I recently had a chat with a couple of friends about style; it inspired me to take a project off the back-burner and turn it into code.\n </i>\n </p>\n \n \n\n \n\n\n \n \n <p>A couple of friends posed a question: is artistic style something that is innate, or cultivated? We spent a few hours digging into art we had created throughout adolescence and into adulthood, picking apart what remained consistent throughout. We sifted through sketchbooks thinking about what may have influenced changes. </p>\n<p>To some degree, each of us kept track of inspiration. Katryna went as far as to keep collages and document each of them. I've always admired collages: there's something about collecting, organising, and drawing inspiration from unexpected places.</p>\n<p>When I travel, I often take pictures of scenes I find interesting: details that catch my eye. A memorable example: to shelter from the rain in Vienna, I ducked into a chapel. The dreary light diffused through the windows to create a high-contrast baroque scene. Typically overwhelming colours and ornamentation became subdued. I collected the moment for later.</p>\n<p><img alt=\"\" src=\"http://aether.kongaloosh.com/images/IMG_2734.JPG\" /></p>\n<p>It's not just scenes that I collect. Occasionally I'll find a striking design element or detail and save it for later. A bar I was dining at during a layover in the Houston airport was tiled with <em>mahjong pieces</em>.</p>\n<p><img alt=\"\" src=\"http://aether.kongaloosh.com/images/IMG_5044.jpeg\" /></p>\n<p>In spite of my aesthetic hoarding, I don't really have a method for collecting these images in a sensible way. They sit on my phone, my computer, and my desktop: apocalyptically poor organisation. I'm always on the hunt for inspiration, but don't have a place to enjoy the fruits of this collecting. </p>\n<p><a href=\"http://aether.kongaloosh.com\">So I made an indie-pinboard.</a></p>\n<p><em>aether</em> is a small flask-app with hints of javascript that take a folder on your server and transform it into an infinite scroll of images that are slowly loaded as you cruise by. In my head, these scenes and images were being collected to make some wild reference art-book collage. By making a tiled album, I'm conveying the sense of purpose that I originally intended.</p>\n<p><img alt=\"\" src=\"https://github.com/Kongaloosh/aether/raw/master/demo.gif?raw=true\" /></p>\n<p>You can find the code in a repo <a href=\"https://github.com/Kongaloosh/aether\">here</a>.</p>\n<p>These images are displayed in a haphazard way: the only unifying trait is that each represents <em>something</em> that I liked. In the future I hope to add a more contentful display. I'm thinking that by employing some simple computer vision, I can partition the images by theme and sort them by feel.</p>\n \n\n \n \n <p></p>\n \n \n \n\n\n \n\n\n \n \n \n <i></i>\n \n <a href=\"https://kongaloosh.com/t/tech\">tech</a>\n \n <a href=\"https://kongaloosh.com/t/article\">article</a>\n \n <a href=\"https://kongaloosh.com/t/dev\">dev</a>\n \n <a href=\"https://kongaloosh.com/t/indie\">indie</a>\n \n <a href=\"https://kongaloosh.com/t/indieweb\">indieweb</a>\n \n <a href=\"https://kongaloosh.com/t/art\">art</a>\n \n <a href=\"https://kongaloosh.com/t/inspiration\">inspiration</a>\n \n <a href=\"https://kongaloosh.com/t/hack\">hack</a>"
},
"author": {
"type": "card",
"name": "Alex Kearney",
"url": "http://kongaloosh.com",
"photo": null
},
"post-type": "article",
"_id": "12835411",
"_source": "228",
"_is_read": true
}
The more time I read and check things, the more I realize that protocols are only half of the problem. Heh, we need people working on really solid content creation tools that can match or rival what we see out there. It’s easy to publish text or an image. Video gets a bit tricky and even more dynamic content like polling, RSVPs or protected content gets more difficult.
But those are just touching the surface. I’m starting to see why the idea of being able to push a “component” of information is very attractive - by design, it can provide the necessary means for rendering things if it’s not yet supported and perhaps give users a chance to choose if they’d want to see it anyway. This is part of my hope as I begin toying with the mobile client I have in mind to be a companion to Lwa. By default, none of the post types outside of a note would be supported. It’d have to ask a Microsub server for information / tools / data on how to render it. This adds complexity to the server but it makes clients very thin.
{
"type": "entry",
"published": "2020-06-29T17:40:44.98974-07:00",
"url": "https://v2.jacky.wtf/post/55426f1d-b4d8-457e-a418-8dba46902641",
"category": [
"indieweb",
"thoughts",
"social web"
],
"content": {
"text": "The more time I read and check things, the more I realize that protocols are only half of the problem. Heh, we need people working on really solid content creation tools that can match or rival what we see out there. It\u2019s easy to publish text or an image. Video gets a bit tricky and even more dynamic content like polling, RSVPs or protected content gets more difficult.But those are just touching the surface. I\u2019m starting to see why the idea of being able to push a \u201ccomponent\u201d of information is very attractive - by design, it can provide the necessary means for rendering things if it\u2019s not yet supported and perhaps give users a chance to choose if they\u2019d want to see it anyway. This is part of my hope as I begin toying with the mobile client I have in mind to be a companion to Lwa. By default, none of the post types outside of a note would be supported. It\u2019d have to ask a Microsub server for information / tools / data on how to render it. This adds complexity to the server but it makes clients very thin.",
"html": "<p>The more time I read and check things, the more I realize that protocols are only <em>half</em> of the problem. Heh, we need people working on really solid content creation tools that can match or rival what we see out there. It\u2019s easy to publish text or an image. Video gets a bit tricky and even more dynamic content like polling, RSVPs or protected content gets more difficult.</p><p>But those are just touching the surface. I\u2019m starting to see why the idea of being able to push a \u201ccomponent\u201d of information is very attractive - by design, it can provide the necessary means for rendering things if it\u2019s not yet supported and perhaps give users a chance to choose <em>if</em> they\u2019d want to see it anyway. This is part of my hope as I begin toying with the mobile client I have in mind to be a companion to Lwa. By default, none of the post types outside of a note would be supported. It\u2019d have to ask a Microsub server for information / tools / data on how to render it. This adds complexity to the server but it makes clients very thin.</p>"
},
"author": {
"type": "card",
"name": "",
"url": "https://v2.jacky.wtf",
"photo": null
},
"post-type": "note",
"_id": "12829494",
"_source": "1886",
"_is_read": true
}
So it’s both Lighthouse not sending the callback when it’s successful and Koype not waiting until the Webmention callback is called to then update the syndication result. Both are fine and easy to fix.
{
"type": "entry",
"published": "2020-06-29T14:23:08.42587-07:00",
"url": "https://v2.jacky.wtf/post/6b95afe0-c350-4a39-8169-ecf0590d1275",
"category": [
"lighthouse"
],
"content": {
"text": "So it\u2019s both Lighthouse not sending the callback when it\u2019s successful and Koype not waiting until the Webmention callback is called to then update the syndication result. Both are fine and easy to fix.",
"html": "<p>So it\u2019s both Lighthouse not sending the callback when it\u2019s successful and Koype not waiting until the Webmention callback is called to then update the syndication result. Both are fine and easy to fix.</p>"
},
"author": {
"type": "card",
"name": "",
"url": "https://v2.jacky.wtf",
"photo": null
},
"post-type": "note",
"_id": "12825579",
"_source": "1886",
"_is_read": true
}
Interesting. It doesn’t look like Lighthouse is actually sending out Webmentions. Ugh.
{
"type": "entry",
"published": "2020-06-29T14:00:00.00000-07:00",
"url": "https://v2.jacky.wtf/post/7588b56f-b16b-4bbc-95e4-0909b3ad60cd",
"content": {
"text": "Interesting. It doesn\u2019t look like Lighthouse is actually sending out Webmentions. Ugh.",
"html": "<p>Interesting. It doesn\u2019t look like Lighthouse is actually sending out Webmentions. Ugh.</p>"
},
"author": {
"type": "card",
"name": "",
"url": "https://v2.jacky.wtf",
"photo": null
},
"post-type": "note",
"_id": "12825308",
"_source": "1886",
"_is_read": true
}
I think I’ve successfully introduced the concept of asynchronous Webmentions to my site and Lighthouse. It does look like that’s the only kind Lighthouse might be able to accept. It relies on the sender providing a callback URL that’s sent a post of the same target and source whenever it notices a change. Usually, this shouldn’t be often but I do it to allow for slower services or passive retries.
That said, Lighthouse is successfully handling this and I think I’ll begin working on the extraction of a feed to place into a reader soon. That and having a facility to render Webmentions on one’s site will be key! Lighthouse does have a hard requirement that people leverage IndieAuth and that’s largely to reduce the number of domains / sites that one can have monitored. But I’ll have to eventually refactor that because I do want to have a per-site experience for myself (giving each of my projects their own site will be better for me to separate into my reader).
{
"type": "entry",
"published": "2020-06-29T06:21:00.00000-07:00",
"url": "https://v2.jacky.wtf/post/9920e3ce-b6c5-4fc1-a7df-8c53cd00a321",
"category": [
"itches",
"side projects",
"lighthouse"
],
"content": {
"text": "I think I\u2019ve successfully introduced the concept of asynchronous Webmentions to my site and Lighthouse. It does look like that\u2019s the only kind Lighthouse might be able to accept. It relies on the sender providing a callback URL that\u2019s sent a post of the same target and source whenever it notices a change. Usually, this shouldn\u2019t be often but I do it to allow for slower services or passive retries.That said, Lighthouse is successfully handling this and I think I\u2019ll begin working on the extraction of a feed to place into a reader soon. That and having a facility to render Webmentions on one\u2019s site will be key! Lighthouse does have a hard requirement that people leverage IndieAuth and that\u2019s largely to reduce the number of domains / sites that one can have monitored. But I\u2019ll have to eventually refactor that because I do want to have a per-site experience for myself (giving each of my projects their own site will be better for me to separate into my reader).",
"html": "<p>I think I\u2019ve successfully introduced the concept of asynchronous Webmentions to my site and Lighthouse. It does look like that\u2019s the only kind Lighthouse might be able to accept. It relies on the sender providing a callback URL that\u2019s sent a post of the same target and source whenever it notices a change. Usually, this shouldn\u2019t be often but I do it to allow for slower services or passive retries.</p><p>That said, Lighthouse is successfully handling this and I think I\u2019ll begin working on the extraction of a feed to place into a reader soon. That and having a facility to render Webmentions on one\u2019s site will be key! Lighthouse does have a hard requirement that people leverage IndieAuth and that\u2019s largely to reduce the number of domains / sites that one can have monitored. But I\u2019ll have to eventually refactor that because I do want to have a per-site experience for myself (giving each of my projects their own site will be better for me to separate into my reader).</p>"
},
"author": {
"type": "card",
"name": "",
"url": "https://v2.jacky.wtf",
"photo": null
},
"post-type": "note",
"_id": "12814161",
"_source": "1886",
"_is_read": true
}
This is me testing if Webmention-based syndication works for my site. This relies on using the code in https://git.jacky.wtf/indieweb/koype/issues/202 to get that working.
{
"type": "entry",
"published": "2020-06-29T03:15:37.55497-07:00",
"url": "https://v2.jacky.wtf/post/514ec949-2316-4e98-8060-746783d5b9a8",
"content": {
"text": "This is me testing if Webmention-based syndication works for my site. This relies on using the code in https://git.jacky.wtf/indieweb/koype/issues/202 to get that working.",
"html": "<p>This is me testing if Webmention-based syndication works for my site. This relies on using the code in <a href=\"https://git.jacky.wtf/indieweb/koype/issues/202\">https://git.jacky.wtf/indieweb/koype/issues/202</a> to get that working.</p>"
},
"author": {
"type": "card",
"name": "",
"url": "https://v2.jacky.wtf",
"photo": null
},
"post-type": "note",
"_id": "12811176",
"_source": "1886",
"_is_read": true
}
{
"type": "entry",
"author": {
"name": "fluffy",
"url": "http://beesbuzz.biz/",
"photo": null
},
"url": "http://beesbuzz.biz/blog/5711-Access-token-grants-for-feed-readers",
"published": "2020-06-28T17:02:36-07:00",
"content": {
"html": "<p>This year <a href=\"https://2020.indieweb.org/summit\">IndieWeb Summit</a> was canceled<a href=\"http://beesbuzz.biz/blog/5711-Access-token-grants-for-feed-readers#d_e5711_fn1\">1</a>, and some pretty good conversations took place. As usual my biggest interest was in doing authenticated, secure sharing of private posts, which has been a huge focus in how I\u2019ve been building Publ.</p><p>I wasn\u2019t really able to participate in any of the development stuff (as I\u2019m still in quite a lot of pain due to whatever the hell is going on with my chronic pain stuff interacting with whatever the hell has been going on with my shoulder for the past <em>month</em>), but I did join in on the ending of a discussion/dev session about <a href=\"https://indieweb.org/AutoAuth\">AutoAuth</a>.</p>\n\n\n<p>My understanding about what happened before I joined in is that a few folks did end up implementing an end-to-end version of AutoAuth flow, but they decided that there were still too many parts to deal with for the entire implementation and wanted to separate out parts of the protocol to capture what we actually want out of this mechanism, which is absolutely fair.</p><p>What I liked about the idea of AutoAuth was that people could subscribe to any arbitrary feed in their social reader and opt into (securely) sharing their identity with the publisher, and then the publisher could opt into (securely) adding their private posts into the feed. But the protocol behind that is rather complex and not necessarily what\u2019s needed for the flow, and we eventually reached a consensus that the subscription part could be designed and implemented separately from the access grant.</p><p><a href=\"https://aaronpk.com/\">Aaron</a> had a sketch of a protocol up on his screen, but I didn\u2019t quite understand the flow based on the text notes and his verbal explanation, and I\u2019m hoping that he\u2019ll be able to document it on <a href=\"https://indieweb.org/\">the wiki</a> at some point, but in the meantime, my takeaway of how things could possibly work:</p>\n<ol><li>A feed with a privacy upgrade available can respond with a <code>WWW-Authenticate:</code> header (per AutoAuth)</li>\n<li>The reader UX indicates that authentication might be an option</li>\n<li>Somehow the following relationship is established between the reader and the publisher, and the publisher provides a bearer token to the reader</li>\n<li>The reader makes future requests with the appropriate <code>Authorization: Bearer xxxxx</code> header</li>\n</ol><p>For what it\u2019s worth, Publ already supports steps 1 and 4, and so I want to propose a mechanism for step 3 (which would be fairly easy for me to implement into Publ and possibly into <a href=\"https://github.com/fluffy-critter/Feed-on-Feeds\">Feed On Feeds</a>): If a user is logged in to a site, the site will provide the bearer token. Specifically, it would do so in one or more of the following ways:</p>\n<ul><li>A response header, e.g. <code>Access-Token: Bearer xxxxx</code></li>\n<li>An HTML header, e.g. <code><meta http-equiv=\"Access-Token\" content=\"Bearer xxxxx\"></code></li>\n<li>Displayed UX, such as a display to the end user with reasonable messaging regarding the value of the <code>Authorization: Bearer xxxxx</code> header to add to their reader manually</li>\n</ul><p>The first two could work alongside a future AutoAuth-type flow in the reader, or a user extension for the browser to show some flow for adding the access token to their compatible reader or whatever. The third one would cover a manual flow.</p><p>This does lead to some questions, like how do we handle things like token expiration (both from timeouts and from revocation). I think that this can still be covered by a simple flow; first, we\u2019d suggest that any token expiration be fairly long-lived (like, on the order of months, if not permanent). Next, if a token has expired, then the retrieval of the resource should raise a <code>401 Unauthorized</code> header, which would indicate to the reader that the token needs to be updated.<a href=\"http://beesbuzz.biz/blog/5711-Access-token-grants-for-feed-readers#d_e5711_fn2\">2</a></p><p>I\u2019m tempted to try hacking this into Feed On Feeds, but I think what I really want to do going forward is to use this as an excuse to finally start writing <a href=\"http://beesbuzz.biz/blog/8118-So-what-is-Subl-anyway\">Subl</a>, as just a very basic social reader that provides subscription and manual-flow authentication UX. Automation-flow can come later.</p><p>Anyway, I\u2019m hoping that the following folks will have feedback on this proposal: <a href=\"https://aaronpk.com/\">Aaron</a>, <a href=\"https://tantek.com/\">Tantek</a>, <a href=\"https://www.svenknebel.de/posts/\">Sven</a>, and <a href=\"https://www.jacky.wtf/\">Jackie</a>.</p>\n\n<ol><li><p>In the \u201cwe had a pandemic and had to call it off\u201d sense and not in the \u201cwe have too many cishet white guys\u201d sense. <a href=\"http://beesbuzz.biz/blog/5711-Access-token-grants-for-feed-readers#r_e5711_fn1\">\u21a9</a></p></li><li><p>Incidentally, this is also how Publ already implements it, so of course I\u2019m biased towards it. :) <a href=\"http://beesbuzz.biz/blog/5711-Access-token-grants-for-feed-readers#r_e5711_fn2\">\u21a9</a></p></li></ol><p><a href=\"http://beesbuzz.biz/blog/5711-Access-token-grants-for-feed-readers#comments\">comments</a></p>",
"text": "This year IndieWeb Summit was canceled1, and some pretty good conversations took place. As usual my biggest interest was in doing authenticated, secure sharing of private posts, which has been a huge focus in how I\u2019ve been building Publ.I wasn\u2019t really able to participate in any of the development stuff (as I\u2019m still in quite a lot of pain due to whatever the hell is going on with my chronic pain stuff interacting with whatever the hell has been going on with my shoulder for the past month), but I did join in on the ending of a discussion/dev session about AutoAuth.\n\n\nMy understanding about what happened before I joined in is that a few folks did end up implementing an end-to-end version of AutoAuth flow, but they decided that there were still too many parts to deal with for the entire implementation and wanted to separate out parts of the protocol to capture what we actually want out of this mechanism, which is absolutely fair.What I liked about the idea of AutoAuth was that people could subscribe to any arbitrary feed in their social reader and opt into (securely) sharing their identity with the publisher, and then the publisher could opt into (securely) adding their private posts into the feed. But the protocol behind that is rather complex and not necessarily what\u2019s needed for the flow, and we eventually reached a consensus that the subscription part could be designed and implemented separately from the access grant.Aaron had a sketch of a protocol up on his screen, but I didn\u2019t quite understand the flow based on the text notes and his verbal explanation, and I\u2019m hoping that he\u2019ll be able to document it on the wiki at some point, but in the meantime, my takeaway of how things could possibly work:\nA feed with a privacy upgrade available can respond with a WWW-Authenticate: header (per AutoAuth)\nThe reader UX indicates that authentication might be an option\nSomehow the following relationship is established between the reader and the publisher, and the publisher provides a bearer token to the reader\nThe reader makes future requests with the appropriate Authorization: Bearer xxxxx header\nFor what it\u2019s worth, Publ already supports steps 1 and 4, and so I want to propose a mechanism for step 3 (which would be fairly easy for me to implement into Publ and possibly into Feed On Feeds): If a user is logged in to a site, the site will provide the bearer token. Specifically, it would do so in one or more of the following ways:\nA response header, e.g. Access-Token: Bearer xxxxx\nAn HTML header, e.g. <meta http-equiv=\"Access-Token\" content=\"Bearer xxxxx\">\nDisplayed UX, such as a display to the end user with reasonable messaging regarding the value of the Authorization: Bearer xxxxx header to add to their reader manually\nThe first two could work alongside a future AutoAuth-type flow in the reader, or a user extension for the browser to show some flow for adding the access token to their compatible reader or whatever. The third one would cover a manual flow.This does lead to some questions, like how do we handle things like token expiration (both from timeouts and from revocation). I think that this can still be covered by a simple flow; first, we\u2019d suggest that any token expiration be fairly long-lived (like, on the order of months, if not permanent). Next, if a token has expired, then the retrieval of the resource should raise a 401 Unauthorized header, which would indicate to the reader that the token needs to be updated.2I\u2019m tempted to try hacking this into Feed On Feeds, but I think what I really want to do going forward is to use this as an excuse to finally start writing Subl, as just a very basic social reader that provides subscription and manual-flow authentication UX. Automation-flow can come later.Anyway, I\u2019m hoping that the following folks will have feedback on this proposal: Aaron, Tantek, Sven, and Jackie.\n\nIn the \u201cwe had a pandemic and had to call it off\u201d sense and not in the \u201cwe have too many cishet white guys\u201d sense. \u21a9Incidentally, this is also how Publ already implements it, so of course I\u2019m biased towards it. :) \u21a9comments"
},
"name": "Plaidophile: Access token grants for feed readers",
"post-type": "article",
"_id": "12803371",
"_source": "3782",
"_is_read": true
}
Announcing my own personal Micropub client to publish content that is very specific to my workflows.
{
"type": "entry",
"published": "2020-06-28 21:08:04 +0100 +0100",
"summary": "Announcing my own personal Micropub client to publish content that is very specific to my workflows.",
"url": "https://www.jvt.me/posts/2020/06/28/personal-micropub-client/",
"category": [
"www.jvt.me",
"micropub"
],
"name": "Creating My Own Personal Micropub Client",
"author": {
"type": "card",
"name": "Jamie Tanna",
"url": "https://www.jvt.me",
"photo": "https://www.jvt.me/img/profile.png"
},
"post-type": "article",
"_id": "12801271",
"_source": "2169",
"_is_read": true
}
