It’s increasingly clear that WordPress (steered by Automattic) isn’t particularly interested in blogging anymore. I agree that a solid, open source, turnkey solution for IndieWeb compatible personal websites is important. I also think Eddie is right that having several would be even better.
We have a great start in Known, which is what I use on my website, but we badly need more contributors. If you’re looking for a place to dive in and help solve this problem, I would highly encourage you to take a look at Known!
{
"type": "entry",
"published": "2018-12-13T19:47:26+00:00",
"url": "https://cleverdevil.io/2018/its-increasingly-clear-that-wordpress-steered-by",
"in-reply-to": [
"https://ramblinggit.com/2018/12/blog-engines-and-indieweb-controlling-upstream/"
],
"content": {
"text": "It\u2019s increasingly clear that WordPress (steered by Automattic) isn\u2019t particularly interested in blogging anymore. I agree that a solid, open source, turnkey solution for IndieWeb compatible personal websites is important. I also think Eddie is right that having several would be even better.\n\n\nWe have a great start in Known, which is what I use on my website, but we badly need more contributors. If you\u2019re looking for a place to dive in and help solve this problem, I would highly encourage you to take a look at Known!",
"html": "It\u2019s increasingly clear that WordPress (steered by Automattic) isn\u2019t particularly interested in blogging anymore. I agree that a solid, open source, turnkey solution for IndieWeb compatible personal websites is important. I also think Eddie is right that having several would be even better.<br /><br />\nWe have a great start in Known, which is what I use on my website, but we badly need more contributors. If you\u2019re looking for a place to dive in and help solve this problem, I would highly encourage you to take a look at Known!"
},
"author": {
"type": "card",
"name": "Jonathan LaCour",
"url": "https://cleverdevil.io/profile/cleverdevil",
"photo": "https://aperture-proxy.p3k.io/77e5d6e5871324c43aebf2e3e7a5553e14578f66/68747470733a2f2f636c65766572646576696c2e696f2f66696c652f66646263373639366135663733383634656131316138323863383631653133382f7468756d622e6a7067"
},
"post-type": "reply",
"_id": "1607228",
"_is_read": true
}
After discussing the finer points of multitags in the IndieWeb chat today, I decided to add support for it to my site. Thanks to my recent re-architecture in November, it was actually really quick and easy. Took less than 30 minutes!
{
"type": "entry",
"published": "2018-12-12T23:47:52-05:00",
"url": "https://eddiehinkle.com/2018/12/12/28/note/",
"category": [
"tech",
"indieweb"
],
"syndication": [
"https://micro.blog/EddieHinkle",
"https://news.indieweb.org/en",
"https://twitter.com/eddiehinkle"
],
"content": {
"text": "After discussing the finer points of multitags in the IndieWeb chat today, I decided to add support for it to my site. Thanks to my recent re-architecture in November, it was actually really quick and easy. Took less than 30 minutes!",
"html": "After discussing the finer points of <a href=\"https://indieweb.org/multitag\">multitags</a> in the IndieWeb chat today, I decided to add support for it to my site. Thanks to my recent re-architecture in November, it was actually really quick and easy. Took less than 30 minutes!"
},
"author": {
"type": "card",
"name": "Eddie Hinkle",
"url": "https://eddiehinkle.com/",
"photo": "https://aperture-proxy.p3k.io/cc9591b69c2c835fa2c6e23745b224db4b4b431f/68747470733a2f2f656464696568696e6b6c652e636f6d2f696d616765732f70726f66696c652e6a7067"
},
"post-type": "note",
"_id": "1602963",
"_is_read": true
}
Marty McGuire
My 2019-01-01 Commitment
2018 is drawing to a close and wow, what a year. It feels like it has, by turns, both crawled and raced by on its way. Tonight I'm at my final Homebrew Website Club as an organizer before the moving truck comes tomorrow and we begin our transfer to NYC. If all goes well we should be living our lives there by this time next week!
Even amidst this turmoil, the IndieWeb community, and Homebrew Website Club in general, has been helping me periodically bring my focus back to the things I want to work on for my personal site. Each year, community members challenge themselves to deliver something new to their site by the end of the year, and there are a lot of commitments already up.
My site is currently built with the static site generator Jekyll. As I'd added posts and features, Jekyll builds started taking 1 to 2 minutes or more. This became excruciating for simple edits or wanting to quickly syndicate a post from my site to Twitter or Facebook. So, in the last year (or more!) I've been refactoring my site and porting over my templates to Hugo, a very fast static site generator written in Go.
I think the last piece I am missing before launching is some updates to my Micropub endpoint to create and edit posts in Hugo-specific locations and with Hugo-specific metadata (seriously, why can't Go parse ISO 8601 dates without a seconds field?).
So, I am committed to finish putting the pieces together and relaunch my site on Hugo before 2019-01-01.
How will you know that I've finished it? I'll have to tell you! Because, ideally, the site should look and work the same as before, with a few improvements in markup and a couple of non-obvious new archive pages.
{
"type": "entry",
"published": "2018-12-11T20:00:54-05:00",
"url": "https://martymcgui.re/2018/12/11/200054/",
"category": [
"newwwyear"
],
"name": "My 2019-01-01 Commitment",
"content": {
"text": "2018 is drawing to a close and wow, what a year. It feels like it has, by turns, both crawled and raced by on its way. Tonight I'm at my final Homebrew Website Club as an organizer before the moving truck comes tomorrow and we begin our transfer to NYC. If all goes well we should be living our lives there by this time next week!\nEven amidst this turmoil, the IndieWeb community, and Homebrew Website Club in general, has been helping me periodically bring my focus back to the things I want to work on for my personal site. Each year, community members challenge themselves to deliver something new to their site by the end of the year, and there are a lot of commitments already up.\nMy site is currently built with the static site generator Jekyll. As I'd added posts and features, Jekyll builds started taking 1 to 2 minutes or more. This became excruciating for simple edits or wanting to quickly syndicate a post from my site to Twitter or Facebook.\u00a0 So, in the last year (or more!) I've been refactoring my site and porting over my templates to Hugo, a very fast static site generator written in Go.\n\n I think the last piece I am missing before launching is some updates to my Micropub endpoint to create and edit posts in Hugo-specific locations and with Hugo-specific metadata (seriously, why can't Go parse ISO 8601 dates without a seconds field?).\n \n\nSo, I am committed to finish putting the pieces together and relaunch my site on Hugo before 2019-01-01.\nHow will you know that I've finished it? I'll have to tell you! Because, ideally, the site should look and work the same as before, with a few improvements in markup and a couple of non-obvious new archive pages.\n\n Trust me, I'll let y'all know here on this site!",
"html": "<p>2018 is drawing to a close and wow, what a year. It feels like it has, by turns, both crawled and raced by on its way. Tonight I'm at my final <a href=\"https://indieweb.org/events/2018-12-11-homebrew-website-club-baltimore\">Homebrew Website Club</a> as an organizer before the moving truck comes tomorrow and we begin our transfer to NYC. If all goes well we should be living our lives there by this time next week!</p>\n<p>Even amidst this turmoil, the <a href=\"https://indieweb.org/\">IndieWeb</a> community, and Homebrew Website Club in general, has been helping me periodically bring my focus back to the things I want to work on for my personal site. Each year, community members challenge themselves to deliver something new to their site by the end of the year, and there are a <a href=\"https://indieweb.org/2019-01-01-commitments\">lot of commitments already up</a>.</p>\n<p>My site is currently built with the static site generator <a href=\"https://jekyllrb.com/\">Jekyll</a>. As I'd added posts and features, Jekyll builds started taking 1 to 2 minutes or more. This became excruciating for simple edits or wanting to quickly syndicate a post from my site to Twitter or Facebook.\u00a0 So, in the last year (or more!) I've been refactoring my site and porting over my templates to <a href=\"https://gohugo.io/\">Hugo</a>, a very fast static site generator written in Go.</p>\n<p>\n I think the last piece I am missing before launching is some updates to my Micropub endpoint to create and edit posts in Hugo-specific locations and with Hugo-specific metadata (seriously, why can't Go parse ISO 8601 dates without a seconds field?).\n <br /></p>\n<p>So, I am committed to finish putting the pieces together and relaunch my site on Hugo before 2019-01-01.</p>\n<p>How will you know that I've finished it? I'll have to tell you! Because, ideally, the site should look and work the same as before, with a few improvements in markup and a couple of non-obvious new archive pages.</p>\n<p>\n Trust me, I'll let y'all know here on this site!\n <br /></p>"
},
"author": {
"type": "card",
"name": "Marty McGuire",
"url": false,
"photo": "https://aperture-proxy.p3k.io/8275f85e3a389bd0ae69f209683436fc53d8bad9/68747470733a2f2f6d617274796d636775692e72652f696d616765732f6c6f676f2e6a7067"
},
"post-type": "article",
"_id": "1595509",
"_is_read": true
}
....fun to figure out everything I wanted to do with my website,....gained a sense of voice...,...I’m so tired of all the endless perfection I see on social media......my relationship with technology changed....
After my initial posting on this yesterday, Greg shares a few more quotesfromhisstudents. It reminds me of the things both teachers and students said at the end of my 2008 project at Rotterdam university for applied sciences. There, a group of teachers explored how to use digital technology, blogs and the myriad of social web tools, to both support their own learning and change their teaching. The sentiments expressed are similar, if you look at the quotes in the last two sections (change yourself, change your students) of my 2009 posting about it. What jumps out most for me, is the sense of agency, the power that comes from discovering that agency.
{
"type": "entry",
"author": {
"name": "Ton Zijlstra",
"url": "https://www.zylstra.org/blog",
"photo": null
},
"url": "https://www.zylstra.org/blog/2018/12/more-edu106-quotes/",
"published": "2018-12-11T13:02:33+00:00",
"content": {
"html": "Replied to <a href=\"https://quickthoughts.jgregorymcverry.com/2018/12/11/some-quick-quotes-on-edu106-and-the-power-of-indieweb\">Some quick quotes on #edu106 and the power of #IndieWeb #creativity #edtechchat #mb</a> by <img src=\"https://aperture-proxy.p3k.io/69e89036892b6e902cdcc0efccca43644c5c6b38/68747470733a2f2f717569636b74686f75676874732e6a677265676f72796d6376657272792e636f6d2f66696c652f36383032666263646433666164613863623631666662373938393738663732662f7468756d622e6a7067\" alt=\"Greg McVerry\" />Greg McVerry\n<blockquote>....fun to figure out everything I wanted to do with my website,....gained a sense of voice...,...I\u2019m so tired of all the endless perfection I see on social media......my relationship with technology changed....</blockquote>\n\n<p>After my initial <a href=\"https://www.zylstra.org/blog/2018/12/why-go-indie-on-the-web-cause-its-a-beatiful-thing/\">posting on this yesterday</a>, <a href=\"https://quickthoughts.jgregorymcverry.com/2018/12/11/some-quick-quotes-on-edu106-and-the-power-of-indieweb\">Greg shares a few more quotes</a> <a href=\"https://lindseymaesblog.wordpress.com/2018/12/10/brief-reflection/\">from</a> <a href=\"https://tatianiabond2017.wordpress.com/portfolio-2/\">his</a> <a href=\"https://julianicolexx.wordpress.com/porfolio/\">students</a>. It reminds me of the things both teachers and students said at the end of my 2008 project at Rotterdam university for applied sciences. There, a group of teachers explored how to use digital technology, blogs and the myriad of social web tools, to both support their own learning and change their teaching. The sentiments expressed are similar, if you <a href=\"https://www.zylstra.org/blog/2009/06/rotterdam_unive/\">look at the quotes in the last two sections</a> (change yourself, change your students) of my 2009 posting about it. What jumps out most for me, is the sense of agency, the power that comes from discovering that agency. </p>",
"text": "Replied to Some quick quotes on #edu106 and the power of #IndieWeb #creativity #edtechchat #mb by Greg McVerry\n....fun to figure out everything I wanted to do with my website,....gained a sense of voice...,...I\u2019m so tired of all the endless perfection I see on social media......my relationship with technology changed....\n\nAfter my initial posting on this yesterday, Greg shares a few more quotes from his students. It reminds me of the things both teachers and students said at the end of my 2008 project at Rotterdam university for applied sciences. There, a group of teachers explored how to use digital technology, blogs and the myriad of social web tools, to both support their own learning and change their teaching. The sentiments expressed are similar, if you look at the quotes in the last two sections (change yourself, change your students) of my 2009 posting about it. What jumps out most for me, is the sense of agency, the power that comes from discovering that agency."
},
"post-type": "note",
"_id": "1590257",
"_is_read": true
}
This morning I gave a brief talk about IndieAuth at the @W3C Strong Authentication and Identity workshop. I just finished transcribing the recording and published the slides and video! https://www.youtube.com/watch?v=EeCNlB7v08I
{
"type": "entry",
"published": "2018-12-10T22:44:15-08:00",
"url": "https://aaronparecki.com/2018/12/10/28/indieauth",
"category": [
"w3c",
"indieauth"
],
"syndication": [
"https://twitter.com/aaronpk/status/1072381543941844993"
],
"content": {
"text": "This morning I gave a brief talk about IndieAuth at the @W3C Strong Authentication and Identity workshop. I just finished transcribing the recording and published the slides and video! https://www.youtube.com/watch?v=EeCNlB7v08I",
"html": "This morning I gave a brief talk about IndieAuth at the <a href=\"https://twitter.com/W3C\">@W3C</a> Strong Authentication and Identity workshop. I just finished transcribing the recording and published the slides and video! <a href=\"https://www.youtube.com/watch?v=EeCNlB7v08I\"><span>https://</span>www.youtube.com/watch?v=EeCNlB7v08I</a>"
},
"author": {
"type": "card",
"name": "Aaron Parecki",
"url": "https://aaronparecki.com/",
"photo": "https://aperture-media.p3k.io/aaronparecki.com/2b8e1668dcd9cfa6a170b3724df740695f73a15c2a825962fd0a0967ec11ecdc.jpg"
},
"post-type": "note",
"_id": "1588981",
"_is_read": true
}
Ik volg met interesse het blog van Elja Daae, die in 3 weken tijd een concept voor haar boek af wil schrijven. Omdat de uitgever het dan verwacht. Elke dag schrijft ze over haar voortgang en afwegingen. Inmiddels zijn we een week onderweg, met een eerste posting over het niet bestaan van Writers block, en de laatste over schrijven is schrappen in Refocus.
Mijn interesse zit hem vooral in hoe je dat nou aanpakt, tot een boek concept komen. En eigenlijk ben ik ook wel nieuwsgierig naar hoe ze dan straks van een concept naar een boek komt. Is dan niet immers alles al gezegd? Waarom meer woorden er tegenaan gooien als je de boodschap al op papier hebt? Dat is ook meteen waarom ik haar proces volg. Het verschil tussen schrijvers en lezers lijkt vooral te zijn dat iedereen stiekem wel een boek wil schrijven, maar dat schrijvers het uiteindelijk ook doen. Mij wordt ook wel regelmatig de suggestie aan de hand gedaan, “schrijf daar nou eens een boek over!“. En ik heb bij vlagen ook wel die wensgedachte. Maar doen is iets anders. Veel van de boeken die me als voorbeeld worden voorgehouden komen op me over als veel wol om de ruimte tussen de kaften te vullen. Nog maar weer vijf anecdotes en voorbeelden om het punt nogmaals te maken. Waar een handjevol blogposts, of zelfs een rijtje bullet points, waarschijnlijk ook had volstaan.
Elja komt in ieder geval tot actie, en ze laat iedereen meekijken. Frank Meeuwsen schreef ooit ook een boek, Bloghelden, over de vroege Nederlandstalige blog-wereld. Zou hij het proces van Elja herkennen? Frank en ik hadden het laatst over een boek over het IndieWeb, om het vrije en open web uit te leggen aan nieuw publiek. Materiaal genoeg op zich. Maar ook nog veel te onderzoeken. Schrijft Elja alleen uit ervaring, of doet ze ook extra onderzoek tijdens het maken van haar boek?
(Ik ontmoette Elja aan de keukentafel van Ewout, voor een goed gesprek over de toekomst van het internet. Frank was daar ook bij. Hij en ik kennen elkaar uit de Nederlandse blog-oertijd. Zowel Elja (blogpost) als Frank (blogpost) waren aanwezig op onze STM18 unconference op Elmine’s verjaardag.)
{
"type": "entry",
"author": {
"name": "Ton Zijlstra",
"url": "https://www.zylstra.org/blog",
"photo": null
},
"url": "https://www.zylstra.org/blog/2018/12/een-boek-concept-schrijven-in-3-weken/",
"published": "2018-12-10T08:01:53+00:00",
"content": {
"html": "<p>Ik volg met interesse het <a href=\"https://www.eljadaae.nl/\">blog van Elja Daae</a>, die in 3 weken tijd een concept voor haar boek af wil schrijven. Omdat de uitgever het dan verwacht. Elke dag schrijft ze over haar voortgang en afwegingen. Inmiddels zijn we een week onderweg, met een eerste posting over het niet bestaan van <a href=\"https://www.eljadaae.nl/boekaftelblog-1-22-theres-no-such-thing-as-writers-block/\">Writers block</a>, en de laatste over schrijven is schrappen in <a href=\"https://www.eljadaae.nl/refocus/\">Refocus</a>.</p>\n<p>Mijn interesse zit hem vooral in hoe je dat nou aanpakt, tot een boek concept komen. En eigenlijk ben ik ook wel nieuwsgierig naar hoe ze dan straks van een concept naar een boek komt. Is dan niet immers alles al gezegd? Waarom meer woorden er tegenaan gooien als je de boodschap al op papier hebt? Dat is ook meteen waarom ik haar proces volg. Het verschil tussen schrijvers en lezers lijkt vooral te zijn dat iedereen stiekem wel een boek wil schrijven, maar dat schrijvers het uiteindelijk ook doen. Mij wordt ook wel regelmatig de suggestie aan de hand gedaan, \u201c<em>schrijf daar nou eens een boek over!</em>\u201c. En ik heb bij vlagen ook wel die wensgedachte. Maar doen is iets anders. Veel van de boeken die me als voorbeeld worden voorgehouden komen op me over als veel wol om de ruimte tussen de kaften te vullen. Nog maar weer vijf anecdotes en voorbeelden om het punt nogmaals te maken. Waar een handjevol blogposts, of zelfs een rijtje bullet points, waarschijnlijk ook had volstaan.</p>\n<p>Elja komt in ieder geval tot actie, en ze laat iedereen meekijken. <a href=\"https://diggingthedigital.com/\">Frank Meeuwsen</a> schreef ooit ook een boek, <a href=\"https://diggingthedigital.com/Bloghelden-te-koop/\">Bloghelden</a>, over de vroege Nederlandstalige blog-wereld. Zou hij het proces van Elja herkennen? Frank en ik hadden het laatst over een boek over het IndieWeb, om het vrije en open web uit te leggen aan nieuw publiek. Materiaal genoeg op zich. Maar ook nog veel te onderzoeken. Schrijft Elja alleen uit ervaring, of doet ze ook extra onderzoek tijdens het maken van haar boek?</p>\n<p>(Ik ontmoette Elja aan de <a href=\"https://www.zylstra.org/blog/2018/06/4131/\">keukentafel van Ewout</a>, voor een goed gesprek over de toekomst van het internet. Frank was daar ook bij. Hij en ik kennen elkaar uit de Nederlandse blog-oertijd. Zowel Elja (<a href=\"https://www.eljadaae.nl/het-oh-shit-moment-en-waarom-wij-afwijzing-vermijden/\">blogpost</a>) als Frank (<a href=\"https://diggingthedigital.com/Smart-Stuff-Unconference-2018/\">blogpost</a>) waren aanwezig op onze <a href=\"https://www.zylstra.org/blog/2018/09/do-you-have-any-diodes/\">STM18 unconference</a> op <a href=\"http://storymin.es/en/2018/09/another-epic-birthday-party/\">Elmine\u2019s verjaardag</a>.)</p>",
"text": "Ik volg met interesse het blog van Elja Daae, die in 3 weken tijd een concept voor haar boek af wil schrijven. Omdat de uitgever het dan verwacht. Elke dag schrijft ze over haar voortgang en afwegingen. Inmiddels zijn we een week onderweg, met een eerste posting over het niet bestaan van Writers block, en de laatste over schrijven is schrappen in Refocus.\nMijn interesse zit hem vooral in hoe je dat nou aanpakt, tot een boek concept komen. En eigenlijk ben ik ook wel nieuwsgierig naar hoe ze dan straks van een concept naar een boek komt. Is dan niet immers alles al gezegd? Waarom meer woorden er tegenaan gooien als je de boodschap al op papier hebt? Dat is ook meteen waarom ik haar proces volg. Het verschil tussen schrijvers en lezers lijkt vooral te zijn dat iedereen stiekem wel een boek wil schrijven, maar dat schrijvers het uiteindelijk ook doen. Mij wordt ook wel regelmatig de suggestie aan de hand gedaan, \u201cschrijf daar nou eens een boek over!\u201c. En ik heb bij vlagen ook wel die wensgedachte. Maar doen is iets anders. Veel van de boeken die me als voorbeeld worden voorgehouden komen op me over als veel wol om de ruimte tussen de kaften te vullen. Nog maar weer vijf anecdotes en voorbeelden om het punt nogmaals te maken. Waar een handjevol blogposts, of zelfs een rijtje bullet points, waarschijnlijk ook had volstaan.\nElja komt in ieder geval tot actie, en ze laat iedereen meekijken. Frank Meeuwsen schreef ooit ook een boek, Bloghelden, over de vroege Nederlandstalige blog-wereld. Zou hij het proces van Elja herkennen? Frank en ik hadden het laatst over een boek over het IndieWeb, om het vrije en open web uit te leggen aan nieuw publiek. Materiaal genoeg op zich. Maar ook nog veel te onderzoeken. Schrijft Elja alleen uit ervaring, of doet ze ook extra onderzoek tijdens het maken van haar boek?\n(Ik ontmoette Elja aan de keukentafel van Ewout, voor een goed gesprek over de toekomst van het internet. Frank was daar ook bij. Hij en ik kennen elkaar uit de Nederlandse blog-oertijd. Zowel Elja (blogpost) als Frank (blogpost) waren aanwezig op onze STM18 unconference op Elmine\u2019s verjaardag.)"
},
"name": "Een boek concept schrijven in 3 weken",
"post-type": "article",
"_id": "1581924",
"_is_read": true
}
I am concerned that the block structure of Gutenberg will break all the IndieWeb WordPress plugins. I’ve installed the Classic Editor plugin. Hopefully, this will all be sorted out by 2021. Transitioning to an alternative platform would be challenging.
{
"type": "entry",
"author": {
"name": "<span class='p-author h-card'>Kh\u00fcrt Williams</span>",
"url": "https://islandinthenet.com/",
"photo": null
},
"url": "https://islandinthenet.com/2018-12-09-08-43-13/",
"published": "2018-12-09T13:43:13+00:00",
"content": {
"html": "<p>I am concerned that the block structure of Gutenberg will break all the IndieWeb WordPress plugins. I\u2019ve installed the Classic Editor plugin. Hopefully, this will all be sorted out by 2021. Transitioning to an alternative platform would be challenging.</p>",
"text": "I am concerned that the block structure of Gutenberg will break all the IndieWeb WordPress plugins. I\u2019ve installed the Classic Editor plugin. Hopefully, this will all be sorted out by 2021. Transitioning to an alternative platform would be challenging."
},
"name": "2018-12-09 08.43.13",
"post-type": "article",
"_id": "1576733",
"_is_read": true
}
@manton@danielpunkass@cheesemaker Is it common to do many small Frameworks or a single large one? In a WWDC Session they said you shouldn't have more than 6 frameworks in an app? I'm packing my IndieWeb code and trying to decide if they should be 3 or 1. Any thoughts?
{
"type": "entry",
"published": "2018-12-05T12:44:01-05:00",
"url": "https://eddiehinkle.com/2018/12/05/13/note/",
"syndication": [
"https://micro.blog/EddieHinkle"
],
"content": {
"text": "@manton @danielpunkass @cheesemaker Is it common to do many small Frameworks or a single large one? In a WWDC Session they said you shouldn't have more than 6 frameworks in an app? I'm packing my IndieWeb code and trying to decide if they should be 3 or 1. Any thoughts?",
"html": "<a href=\"https://micro.blog/manton\">@manton</a> <a href=\"https://micro.blog/danielpunkass\">@danielpunkass</a> <a href=\"https://micro.blog/cheesemaker\">@cheesemaker</a> Is it common to do many small Frameworks or a single large one? In a WWDC Session they said you shouldn't have more than 6 frameworks in an app? I'm packing my IndieWeb code and trying to decide if they should be 3 or 1. Any thoughts?"
},
"author": {
"type": "card",
"name": "Eddie Hinkle",
"url": "https://eddiehinkle.com/",
"photo": "https://aperture-proxy.p3k.io/cc9591b69c2c835fa2c6e23745b224db4b4b431f/68747470733a2f2f656464696568696e6b6c652e636f6d2f696d616765732f70726f66696c652e6a7067"
},
"post-type": "note",
"_id": "1551997",
"_is_read": true
}
I misspoke at the beginning about the founding of the IndieWeb, incorrectly saying “Distributed Web Summit” when I meant “Federated Social Web Summit”. I actually interviewed Tantek and Aaron about those early days of the IndieWeb when I was in Portland this year, for my upcoming book Indie Microblogging. I’d love to get part of that transcript out soon since there’s a lot of good history in it.
{
"type": "entry",
"author": {
"name": "Manton Reece",
"url": "https://www.manton.org/",
"photo": "https://aperture-proxy.p3k.io/907926e361383204bd1bc913c143c23e70ae69bb/68747470733a2f2f6d6963726f2e626c6f672f6d616e746f6e2f6176617461722e6a7067"
},
"url": "https://www.manton.org/2018/12/05/interview-on-plutopia.html",
"name": "Interview on Plutopia podcast",
"content": {
"html": "<p>Speaking of <a href=\"https://manton.org/2018/12/05/good-morning-austin.html\">tonight\u2019s Homebrew Website Club</a>, Tom Brown and I were guests on <a href=\"https://www.plutopia.io/2018/12/02/tom-brown-and-manton-reece-an-introduction-to-indieweb/\">the Plutopia podcast that just posted this week</a>, talking about the IndieWeb, posting to your own blog, and Micro.blog.</p>\n\n<p>I misspoke at the beginning about the founding of the IndieWeb, incorrectly saying \u201cDistributed Web Summit\u201d when I meant \u201cFederated Social Web Summit\u201d. I actually interviewed Tantek and Aaron about those early days of the IndieWeb when I was in Portland this year, for my upcoming book Indie Microblogging. I\u2019d love to get part of that transcript out soon since there\u2019s a lot of good history in it.</p>",
"text": "Speaking of tonight\u2019s Homebrew Website Club, Tom Brown and I were guests on the Plutopia podcast that just posted this week, talking about the IndieWeb, posting to your own blog, and Micro.blog.\n\nI misspoke at the beginning about the founding of the IndieWeb, incorrectly saying \u201cDistributed Web Summit\u201d when I meant \u201cFederated Social Web Summit\u201d. I actually interviewed Tantek and Aaron about those early days of the IndieWeb when I was in Portland this year, for my upcoming book Indie Microblogging. I\u2019d love to get part of that transcript out soon since there\u2019s a lot of good history in it."
},
"published": "2018-12-05T11:22:41-06:00",
"post-type": "article",
"_id": "1551467",
"_is_read": true
}
Good morning, Austin! Tonight is Homebrew Website Club, 6:30pm at Mozart’s Coffee. We’ll meet at a table outside to talk about the IndieWeb, plan for the upcoming IndieWebCamp Austin, or work on your own web site.
{
"type": "entry",
"author": {
"name": "Manton Reece",
"url": "https://www.manton.org/",
"photo": "https://aperture-proxy.p3k.io/907926e361383204bd1bc913c143c23e70ae69bb/68747470733a2f2f6d6963726f2e626c6f672f6d616e746f6e2f6176617461722e6a7067"
},
"url": "https://www.manton.org/2018/12/05/good-morning-austin.html",
"content": {
"html": "<p>Good morning, Austin! Tonight is Homebrew Website Club, 6:30pm at Mozart\u2019s Coffee. We\u2019ll meet at a table outside to talk about the IndieWeb, plan for the upcoming IndieWebCamp Austin, or work on your own web site.</p>",
"text": "Good morning, Austin! Tonight is Homebrew Website Club, 6:30pm at Mozart\u2019s Coffee. We\u2019ll meet at a table outside to talk about the IndieWeb, plan for the upcoming IndieWebCamp Austin, or work on your own web site."
},
"published": "2018-12-05T07:57:23-06:00",
"post-type": "note",
"_id": "1550340",
"_is_read": true
}
Yesterday we started the 12 days of microblogging blog post series to mark the 1-year anniversary of the public launch of Micro.blog. I posted about making it easier for people to share their stories in audio form with microcasting. Today I want to highlight photoblogging.
Sharing photos is an important part of Micro.blog. I put a custom photo picker and filters in the original Micro.blog iOS app to encourage everyone to post photos to their blog, so that you end up with a great collection of your best photos at your own domain name. Because photos are square by default, they look great in the Micro.blog timeline, and with cross-posting Micro.blog can attach photos to your tweets or send posts to other social networks.
We also have a companion iOS app just for photos called Sunlit. It has an Instagram-like timeline for browsing photos from your Micro.blog timeline, with the focus around blogs that I wrote about in my preview post as we were relaunching Sunlit 2.0:
To play nicely with microblogs, we introduced a new post type in the app for single photos. For longer posts, you can still collect multiple photos together, add text, and post them as a story directly to your blog.
Some people on Micro.blog focus almost exclusively on posting photos, like Robert Brook. Some people have even created separate blogs just for their photos at their own domain name hosted on Micro.blog, like burk.photos. There’s a special section of Discover that features photos from more Micro.blog users.
One of the most common questions we get is how to migrate photos from Instagram to Micro.blog. I think we have 2 really good options for this:
Micro.blog for macOS has a built-in Instagram importer. It will take the archive you get from Instagram and allow you to batch import your Instagram photos to Micro.blog, preserving the original dates and text from Instagram.
OwnYourGram is a web-based app that connects to your Instagram account to automatically copy new Instagram posts to your own blog. Because it’s based on IndieWeb standards, it can also post directly to Micro.blog-hosted sites.
I hope you enjoy posting and browsing photos on Micro.blog! Tomorrow I’ll have the next post in the 12 days of microblogging series.
{
"type": "entry",
"author": {
"name": "Manton Reece",
"url": "https://www.manton.org/",
"photo": "https://aperture-proxy.p3k.io/907926e361383204bd1bc913c143c23e70ae69bb/68747470733a2f2f6d6963726f2e626c6f672f6d616e746f6e2f6176617461722e6a7067"
},
"url": "https://www.manton.org/2018/12/04/days-of-microblogging.html",
"name": "12 days of microblogging: photos",
"content": {
"html": "<p>Yesterday we started the <em>12 days of microblogging</em> blog post series to mark the 1-year anniversary of the public launch of Micro.blog. <a href=\"https://manton.org/2018/12/03/microblog-milestone-first.html\">I posted about</a> making it easier for people to share their stories in audio form with microcasting. Today I want to highlight photoblogging.</p>\n\n<p>Sharing photos is an important part of Micro.blog. I put a custom photo picker and filters in the original Micro.blog iOS app to encourage everyone to post photos to their blog, so that you end up with a great collection of your best photos at your own domain name. Because photos are square by default, they look great in the Micro.blog timeline, and <a href=\"http://help.micro.blog/2016/cross-posting-twitter/\">with cross-posting</a> Micro.blog can attach photos to your tweets or send posts to other social networks.</p>\n\n<p>We also have a companion iOS app just for photos called <a href=\"https://sunlit.io/\">Sunlit</a>. It has an Instagram-like timeline for browsing photos from your Micro.blog timeline, with the focus around blogs that I wrote about <a href=\"https://www.manton.org/2017/06/27/preview-of-sunlit.html\">in my preview post</a> as we were relaunching Sunlit 2.0:</p>\n\n<blockquote>\n <p>To play nicely with microblogs, we introduced a new post type in the app for single photos. For longer posts, you can still collect multiple photos together, add text, and post them as a story directly to your blog.</p>\n</blockquote>\n\n<p>Some people on Micro.blog focus almost exclusively on posting photos, like <a href=\"https://micro.blog/robertbrook\">Robert Brook</a>. Some people have even created separate blogs just for their photos at their own domain name hosted on Micro.blog, like <a href=\"http://burk.photos/\">burk.photos</a>. There\u2019s <a href=\"https://micro.blog/discover/photos\">a special section of Discover</a> that features photos from more Micro.blog users.</p>\n\n<p>A couple of weeks ago, <a href=\"https://micro.blog/cleverdevil\">Jonathan LaCour</a> on Micro.blog <a href=\"https://github.com/microdotblog/issues/issues/112\">submitted a feature request</a> for a photos JSON Feed. He used this feed to build <a href=\"https://github.com/cleverdevil/microgram\">Microgram</a>, a snippet of HTML that you can paste into your blog to provide a grid of photo thumbnails. You can see <a href=\"https://manton.org/photos/\">my photos page at manton.org</a> using Microgram in this screenshot:</p>\n\n<p><img src=\"https://aperture-proxy.p3k.io/638a2d006a9978aec563959b586f198ff94a5926/68747470733a2f2f7777772e6d616e746f6e2e6f72672f75706c6f6164732f323031382f363236383030636366332e6a7067\" width=\"500\" height=\"495\" alt=\"Screenshot of photos grid\" /></p>\n\n<p>One of the most common questions we get is how to migrate photos from Instagram to Micro.blog. I think we have 2 really good options for this:</p>\n\n<ul><li>Micro.blog for macOS has <a href=\"https://manton.org/2018/05/03/instagram-import-in.html\">a built-in Instagram importer</a>. It will take the archive you get from Instagram and allow you to batch import your Instagram photos to Micro.blog, preserving the original dates and text from Instagram.</li>\n <li><a href=\"https://ownyourgram.com\">OwnYourGram</a> is a web-based app that connects to your Instagram account to automatically copy new Instagram posts to your own blog. Because it\u2019s based on IndieWeb standards, it can also post directly to Micro.blog-hosted sites.</li>\n</ul><p>I hope you enjoy posting and browsing photos on Micro.blog! Tomorrow I\u2019ll have the next post in the <em>12 days of microblogging</em> series.</p>",
"text": "Yesterday we started the 12 days of microblogging blog post series to mark the 1-year anniversary of the public launch of Micro.blog. I posted about making it easier for people to share their stories in audio form with microcasting. Today I want to highlight photoblogging.\n\nSharing photos is an important part of Micro.blog. I put a custom photo picker and filters in the original Micro.blog iOS app to encourage everyone to post photos to their blog, so that you end up with a great collection of your best photos at your own domain name. Because photos are square by default, they look great in the Micro.blog timeline, and with cross-posting Micro.blog can attach photos to your tweets or send posts to other social networks.\n\nWe also have a companion iOS app just for photos called Sunlit. It has an Instagram-like timeline for browsing photos from your Micro.blog timeline, with the focus around blogs that I wrote about in my preview post as we were relaunching Sunlit 2.0:\n\n\n To play nicely with microblogs, we introduced a new post type in the app for single photos. For longer posts, you can still collect multiple photos together, add text, and post them as a story directly to your blog.\n\n\nSome people on Micro.blog focus almost exclusively on posting photos, like Robert Brook. Some people have even created separate blogs just for their photos at their own domain name hosted on Micro.blog, like burk.photos. There\u2019s a special section of Discover that features photos from more Micro.blog users.\n\nA couple of weeks ago, Jonathan LaCour on Micro.blog submitted a feature request for a photos JSON Feed. He used this feed to build Microgram, a snippet of HTML that you can paste into your blog to provide a grid of photo thumbnails. You can see my photos page at manton.org using Microgram in this screenshot:\n\n\n\nOne of the most common questions we get is how to migrate photos from Instagram to Micro.blog. I think we have 2 really good options for this:\n\nMicro.blog for macOS has a built-in Instagram importer. It will take the archive you get from Instagram and allow you to batch import your Instagram photos to Micro.blog, preserving the original dates and text from Instagram.\n OwnYourGram is a web-based app that connects to your Instagram account to automatically copy new Instagram posts to your own blog. Because it\u2019s based on IndieWeb standards, it can also post directly to Micro.blog-hosted sites.\nI hope you enjoy posting and browsing photos on Micro.blog! Tomorrow I\u2019ll have the next post in the 12 days of microblogging series."
},
"published": "2018-12-04T15:40:26-06:00",
"post-type": "article",
"_id": "1545509",
"_is_read": true
}
For the IndieWeb Day 3 challenge, I saw on the To Do list that we needed to clean up the Personal Domains page and the Domain Registrar page and merge them. I took a swing at it, and it can be seen here. If you have further thoughts, please help contribute!
{
"type": "entry",
"published": "2018-12-03T23:59:36-05:00",
"url": "https://eddiehinkle.com/2018/12/03/15/note/",
"category": [
"indieweb"
],
"syndication": [
"https://micro.blog/EddieHinkle",
"https://news.indieweb.org/en"
],
"content": {
"text": "For the IndieWeb Day 3 challenge, I saw on the To Do list that we needed to clean up the Personal Domains page and the Domain Registrar page and merge them. I took a swing at it, and it can be seen here. If you have further thoughts, please help contribute!",
"html": "For the IndieWeb Day 3 challenge, I saw on the <a href=\"https://indieweb.org/to-do\">To Do list</a> that we needed to clean up the Personal Domains page and the Domain Registrar page and merge them. I took a swing at it, and it <a href=\"https://indieweb.org/personal-domain\">can be seen here</a>. If you have further thoughts, please help contribute!"
},
"author": {
"type": "card",
"name": "Eddie Hinkle",
"url": "https://eddiehinkle.com/",
"photo": "https://aperture-proxy.p3k.io/cc9591b69c2c835fa2c6e23745b224db4b4b431f/68747470733a2f2f656464696568696e6b6c652e636f6d2f696d616765732f70726f66696c652e6a7067"
},
"post-type": "note",
"_id": "1541188",
"_is_read": true
}
I decided to work on my website theme for a bit. In order to support it, today I shipped(with a minor bug, sorry), a new Indieweb plugin that adds the ability to add the rel-me links inside the h-card widget instead of by themselves. I’m now using it. In my theme, I added support for a dedicated h-card page. I’ll be turning it on on my site likely in future as I experiment with moving my feed off of my main page.
{
"type": "entry",
"published": "2018-12-03T22:26:47-05:00",
"url": "https://david.shanske.com/2018/12/03/2544/",
"content": {
"text": "I decided to work on my website theme for a bit.\u00a0 In order to support it, today I shipped(with a minor bug, sorry), a new Indieweb plugin that adds the ability to add the rel-me links inside the h-card widget instead of by themselves. I\u2019m now using it. In my theme, I added support for a dedicated h-card page. I\u2019ll be turning it on on my site likely in future as I experiment with moving my feed off of my main page."
},
"author": {
"type": "card",
"name": "David Shanske",
"url": "https://david.shanske.com/",
"photo": "https://david.shanske.com/wp-content/uploads/avatar-privacy/cache/gravatar/2/c/2cb1f8afd9c8d3b646b4071c5ed887c970d81d625eeed87e447706940e2c403d-125.png"
},
"post-type": "note",
"_id": "1540827",
"_is_read": true
}
Adding an SSL to my domain has now presented me with a headache for my #indieweb logins.
One of the many great things about the Indieweb is that I can use my domain URL to log into and use different services. But now changing from http: to https: those services see that as a new URL.
Disabling the redirect in the .htaccess file only works for the root. Once I try to authenticate with the WordPress element we’re right back to using the secure URL.
Most of this problem is of my own creation. I don’t run WordPress for my whole site. Only the /blog part is WP as I wanted to retain a POSH homepage and be able to play around on the non-blog parts.
This means the URL I have to use is https://davidjohnmead.com/blog. Not great as most things are geared around the root.
I think I’m just going to have to discard my old URL login and start anew with the secure one.
{
"type": "entry",
"url": "https://davidjohnmead.com/blog/2018/12/03/ssl-headache-for-my-indieweb-logins/",
"syndication": [
"https://twitter.com/davidmead/status/1069771868356399104"
],
"content": {
"text": "Adding an SSL to my domain has now presented me with a headache for my #indieweb logins.\nOne of the many great things about the Indieweb is that I can use my domain URL to log into and use different services. But now changing from http: to https: those services see that as a new URL.\nDisabling the redirect in the .htaccess file only works for the root. Once I try to authenticate with the WordPress element we\u2019re right back to using the secure URL.\nMost of this problem is of my own creation. I don\u2019t run WordPress for my whole site. Only the /blog part is WP as I wanted to retain a POSH homepage and be able to play around on the non-blog parts.\nThis means the URL I have to use is https://davidjohnmead.com/blog. Not great as most things are geared around the root.\nI think I\u2019m just going to have to discard my old URL login and start anew with the secure one.",
"html": "Adding an SSL to my domain has now presented me with a headache for my #indieweb logins.\n<p>One of the many great things about the <a href=\"https://indieweb.org/\">Indieweb</a> is that I can use my domain URL to log into and use different services. But now changing from <code>http:</code> to <code>https:</code> those services see that as a new URL.</p>\n<p>Disabling the redirect in the <code>.htaccess</code> file only works for the root. Once I try to authenticate with the WordPress element we\u2019re right back to using the secure URL.</p>\n<p>Most of this problem is of my own creation. I don\u2019t run WordPress for my whole site. Only the <code>/blog</code> part is WP as I wanted to retain a <abbr title=\"Plain Old Semantic HTML\">POSH</abbr> homepage and be able to play around on the non-blog parts.</p>\n<p>This means the URL I have to use is <code>https://davidjohnmead.com/blog</code>. Not great as most things are geared around the root.</p>\n<p>I think I\u2019m just going to have to discard my old URL login and start anew with the secure one.</p>"
},
"post-type": "note",
"_id": "1539975",
"_is_read": true
}
Going through my Twitter archive from 2007-12. So many dead shortened URL’s and defunct #silos I never received an export from, like the food app Nosh.
#indieweb
{
"type": "entry",
"url": "https://davidjohnmead.com/blog/2018/12/03/so-many-dead-links/",
"syndication": [
"https://twitter.com/davidmead/status/1069672918714589185"
],
"content": {
"text": "Going through my Twitter archive from 2007-12. So many dead shortened URL\u2019s and defunct #silos I never received an export from, like the food app Nosh.\n\n#indieweb",
"html": "Going through <a title=\"self-hosted Twitter posts\" href=\"https://davidjohnmead.com/archive/twitter/\">my Twitter archive from 2007-12</a>. So many dead shortened URL\u2019s and defunct #silos I never received an export from, like the food app Nosh.<br />\n#indieweb"
},
"post-type": "note",
"_id": "1537460",
"_is_read": true
}
{
"type": "entry",
"published": "2018-12-03T10:36:40Z",
"url": "https://adactio.com/links/14572",
"category": [
"youtube",
"video",
"indieweb",
"voxxeddays",
"thessaloniki",
"publishing",
"technology",
"webmention",
"micropub",
"relme",
"microformats",
"presentation",
"talk",
"keynote"
],
"bookmark-of": [
"https://www.youtube.com/watch?v=loASnMsGyvY"
],
"content": {
"text": "Voxxed Thessaloniki 2018 - Opening Keynote - Taking Back The Web - YouTube\n\n\n\nHere\u2019s the talk I gave recently about indie web building blocks.\n\nThere\u2019s fifteen minutes of Q&A starting around the 35 minute mark. People asked some great questions!",
"html": "<h3>\n<a class=\"p-name u-bookmark-of\" href=\"https://www.youtube.com/watch?v=loASnMsGyvY\">\nVoxxed Thessaloniki 2018 - Opening Keynote - Taking Back The Web - YouTube\n</a>\n</h3>\n\n<p>Here\u2019s the talk I gave recently about indie web building blocks.</p>\n\n<p>There\u2019s fifteen minutes of Q&A starting <a href=\"https://youtu.be/loASnMsGyvY?t=2087\">around the 35 minute mark</a>. People asked some great questions!</p>"
},
"author": {
"type": "card",
"name": "Jeremy Keith",
"url": "https://adactio.com/",
"photo": "https://aperture-proxy.p3k.io/bbbacdf0a064621004f2ce9026a1202a5f3433e0/68747470733a2f2f6164616374696f2e636f6d2f696d616765732f70686f746f2d3135302e6a7067"
},
"post-type": "bookmark",
"_id": "1534995",
"_is_read": true
}
{
"type": "entry",
"published": "2018-12-02T20:57:32-05:00",
"url": "https://eddiehinkle.com/2018/12/02/11/note/",
"category": [
"indieweb"
],
"syndication": [
"https://micro.blog/EddieHinkle",
"https://news.indieweb.org/en"
],
"content": {
"text": "Every day in December, the IndieWeb is trying to collectively ship an update. Today, I created a stub for the 2019 Austin IWC page, and Aaron Parecki published it live on the server! So that's day 2! It's missing the schedule and sponsors because I didn't have that info, but it'll be added soon enough \ud83d\ude42",
"html": "<a href=\"https://indieweb.org/2018-12-indieweb-challenge\">Every day in December, the IndieWeb is trying to collectively ship an update</a>. Today, I created a stub for the <a href=\"https://2019.indieweb.org/austin\">2019 Austin IWC page</a>, and <a href=\"https://aaronparecki.com\">Aaron Parecki</a> published it live on the server! So that's day 2! It's missing the schedule and sponsors because I didn't have that info, but it'll be added soon enough \ud83d\ude42"
},
"author": {
"type": "card",
"name": "Eddie Hinkle",
"url": "https://eddiehinkle.com/",
"photo": "https://aperture-proxy.p3k.io/cc9591b69c2c835fa2c6e23745b224db4b4b431f/68747470733a2f2f656464696568696e6b6c652e636f6d2f696d616765732f70726f66696c652e6a7067"
},
"post-type": "note",
"_id": "1533602",
"_is_read": true
}
{
"type": "entry",
"author": {
"name": null,
"url": "https://herestomwiththeweather.com/",
"photo": null
},
"url": "https://herestomwiththeweather.com/2018/12/02/plutopia.io-podcast-on-the-indieweb/",
"published": "2018-12-02T15:53:17+00:00",
"content": {
"html": "<p>I had fun participating in the <a href=\"https://www.plutopia.io/2018/12/02/tom-brown-and-manton-reece-an-introduction-to-indieweb/\">Introduction to Indieweb</a> podcast with Manton, Jon and Scoop where we talk about some of the latest <a href=\"https://indieweb.org/\">Indieweb</a> progress.</p>\n\n<p>Also mentioned is the upcoming <a href=\"https://indieweb.org/2019/Austin\">IndieWebCamp Austin</a> (February 23-24) as well as the monthly <a href=\"https://indieweb.org/Homebrew_Website_Club\">Homebrew Website Club</a> meetings (first Wednesday of the month) at <a href=\"http://mozartscoffee.com/\">Mozart\u2019s Coffee</a>.</p>",
"text": "I had fun participating in the Introduction to Indieweb podcast with Manton, Jon and Scoop where we talk about some of the latest Indieweb progress.\n\nAlso mentioned is the upcoming IndieWebCamp Austin (February 23-24) as well as the monthly Homebrew Website Club meetings (first Wednesday of the month) at Mozart\u2019s Coffee."
},
"name": "Plutopia.io podcast on the Indieweb",
"post-type": "article",
"_id": "1532814",
"_is_read": true
}
A search engine for the whole IndieWeb has been a hot conversation topic, on and off, for many years now. Many of us offer search on our own individual sites, and more ambitious projects like cweiske‘s phinde can search our IRC archives, but building a full fledged search engine to crawl and index all IndieWeb sites has always been a bit too big of a project to tackle. (Not to mention the question of which sites we should include in the first place.)
As usual, my first instinct is always software prevention. Whatever the task at hand is, someone has else has usually already tried to do it. Often they’ve even succeeded, to some degree. Search is certainly no exception. Google has offered custom search engines for individual sites for a long time, so I threw together one that searches all of the sites in Indie Map, plus lots more that have joined the IndieWeb since then. It seems to work ok so far. Try it out and let me know what you think!
Continue reading →
{
"type": "entry",
"published": "2018-11-30T11:15:39-08:00",
"url": "https://snarfed.org/2018-11-30_indieweb-google-custom-search-engine",
"syndication": [
"https://news.indieweb.org/en/snarfed.org/2018-11-30_indieweb-google-custom-search-engine"
],
"name": "IndieWeb Google Custom Search Engine",
"content": {
"text": "TL;DR: it exists! Try it below, or here.\n\n\n\n\n A search engine for the whole IndieWeb has been a hot conversation topic, on and off, for many years now. Many of us offer search on our own individual sites, and more ambitious projects like cweiske\u2018s phinde can search our IRC archives, but building a full fledged search engine to crawl and index all IndieWeb sites has always been a bit too big of a project to tackle. (Not to mention the question of which sites we should include in the first place.)\nAs usual, my first instinct is always software prevention. Whatever the task at hand is, someone has else has usually already tried to do it. Often they\u2019ve even succeeded, to some degree. Search is certainly no exception. Google has offered custom search engines for individual sites for a long time, so I threw together one that searches all of the sites in Indie Map, plus lots more that have joined the IndieWeb since then. It seems to work ok so far. Try it out and let me know what you think!\n Continue reading \u2192",
"html": "<em>TL;DR: it exists! Try it below, <a href=\"https://cse.google.com/cse?cx=001473925626342383772:izm-5gxypp4\">or here</a>.</em>\n<p></p>\n<p></p>\n<p></p>\n<p>\n <img src=\"https://aperture-proxy.p3k.io/3f73cab69d2a5a859e37f9d4afe4e8f9c115eb46/68747470733a2f2f736e61726665642e6f72672f6d61676e696679696e675f676c6173732e6a7067\" alt=\"magnifying_glass.jpg\" /></p><img src=\"https://aperture-proxy.p3k.io/3f73cab69d2a5a859e37f9d4afe4e8f9c115eb46/68747470733a2f2f736e61726665642e6f72672f6d61676e696679696e675f676c6173732e6a7067\" alt=\"magnifying_glass.jpg\" />\n<p>A search engine for the whole <a href=\"https://indieweb.org/\">IndieWeb</a> has been a <a href=\"https://quickthoughts.jgregorymcverry.com/2018/11/25/scoping-out-basics-of-indieweb-search\">hot conversation topic</a>, on and off, for many years now. Many of us offer <a href=\"https://indieweb.org/search\">search</a> on our own individual sites, and more ambitious projects like <a href=\"https://cweiske.de/\">cweiske</a>\u2018s <a href=\"https://cweiske.de/tagebuch/phinde.htm\">phinde</a> can <a href=\"http://indiechat.search.cweiske.de/\">search our IRC archives</a>, but building a full fledged search engine to crawl and index <em>all</em> IndieWeb sites has always been a bit too big of a project to tackle. (Not to mention the question of <a href=\"https://indiemap.org/docs.html#sites\">which sites we should include</a> in the first place.)</p>\n<p>As usual, my first instinct is always <a href=\"https://snarfed.org/2017-01-23_23351\">software prevention</a>. Whatever the task at hand is, someone has else has usually already tried to do it. Often they\u2019ve even succeeded, to some degree. Search is certainly no exception. Google has offered <a href=\"https://developers.google.com/custom-search/\">custom search engines</a> for individual sites for a long time, so I threw together one that searches all of the sites in <a href=\"https://indiemap.org/\">Indie Map</a>, plus lots more that have joined the IndieWeb since then. It seems to work ok so far. <a href=\"https://cse.google.com/cse?cx=001473925626342383772:izm-5gxypp4\">Try it out</a> and let me know what you think!\n <a href=\"https://snarfed.org/2018-11-30_indieweb-google-custom-search-engine#more-30513\">Continue reading <span>\u2192</span></a></p>"
},
"author": {
"type": "card",
"name": "Ryan Barrett",
"url": "https://snarfed.org/",
"photo": "https://aperture-proxy.p3k.io/7e644a0ecb0339b875f998fc405c685591d80cd7/68747470733a2f2f7365637572652e67726176617461722e636f6d2f6176617461722f39343762356633663332336461306566373835623666303264396332363564363f733d393626643d626c616e6b26723d67"
},
"post-type": "article",
"_id": "1520188",
"_is_read": true
}
{
"type": "event",
"name": "Homebrew Website Club SF!",
"summary": "17:30: Optional writing hour and quiet socializing\n18:30: IndieWeb demos and hack night!\n\nHomebrew Website Club retro 1980s-style logo\nTopics for this week: Year-end hack projects 2018 IndieWeb Challenge starts Saturday! Demos of personal website breakthroughs Create or update your personal web site!\nJoin a community with like-minded interests. Bring friends that want a personal site, or are interested in a healthy, independent web!\nAny questions? Ask in #indieweb Slack or IRC\nMore information: IndieWeb Wiki Event Page\nRSVP: post an indie RSVP on your own site!",
"published": "2018-11-29 20:05-0800",
"start": "2018-12-12 17:30-0800",
"end": "2018-12-12 19:30-0800",
"url": "http://tantek.com/2018/346/e1/homebrew-website-club-sf",
"location": [
"https://wiki.mozilla.org/SF"
],
"content": {
"text": "When: 2018-12-12 17:30\u202619:30\nWhere: Mozilla San Francisco\n\nHost: Tantek \u00c7elik\n\n\n\n17:30: Optional writing hour and quiet socializing\n\n18:30: IndieWeb demos and hack night!\n\n\nTopics for this week:\nYear-end hack projects\n\n2018 IndieWeb Challenge starts Saturday!\nDemos of personal website breakthroughs\nCreate or update your personal web site!\n\nJoin a community with like-minded interests. Bring friends that want a personal site, or are interested in a healthy, independent web!\n\n\nAny questions? Ask in \n#indieweb Slack or IRC\n\n\nMore information: \nIndieWeb Wiki Event Page\n\n\nRSVP: post an indie RSVP on your own site!",
"html": "<p>\nWhen: <time class=\"dt-start\">2018-12-12 17:30</time>\u2026<time class=\"dt-end\">19:30</time><span>\nWhere: <a class=\"u-location h-card\" href=\"https://wiki.mozilla.org/SF\">Mozilla San Francisco</a>\n</span>\nHost: <a class=\"u-organizer h-card\" href=\"http://tantek.com/\">Tantek \u00c7elik</a>\n</p>\n\n<p>\n17:30: Optional writing hour and quiet socializing<br />\n18:30: IndieWeb demos and hack night!<br /></p>\n<p><img class=\"u-featured\" style=\"height:300px;\" src=\"https://aperture-media.p3k.io/indieweb.org/c24f7b1e711955ef818bde12e2a3e79708ecc9b106d95b460a9fefe93b0be723.jpg\" alt=\"Homebrew Website Club retro 1980s-style logo\" /></p>\n<p>Topics for this week:</p>\n<ul><li><a href=\"https://indieweb.org/2019-01-01-commitments\">Year-end hack projects</a></li>\n<li>\n<a href=\"https://indieweb.org/2018-12-indieweb-challenge\">2018 IndieWeb Challenge</a> starts Saturday!</li>\n<li>Demos of personal website breakthroughs</li>\n<li>Create or update your personal web site!</li>\n</ul><p>\nJoin a community with like-minded interests. Bring friends that want a personal site, or are interested in a healthy, independent web!\n</p>\n<p>\nAny questions? Ask in \n<a href=\"https://indieweb.org/discuss\">#indieweb Slack or IRC</a>\n</p>\n<p>\nMore information: \n<a class=\"u-url\" href=\"https://indieweb.org/events/2018-12-12-homebrew-website-club\">IndieWeb Wiki Event Page</a>\n</p>\n<p>\nRSVP: post an <a href=\"https://indieweb.org/rsvp\">indie RSVP</a> on your own site!\n</p>"
},
"post-type": "event",
"refs": {
"https://wiki.mozilla.org/SF": {
"type": "card",
"name": "Mozilla San Francisco",
"url": "https://wiki.mozilla.org/SF",
"photo": null
}
},
"_id": "1516294",
"_is_read": true
}
