Two of my favourite things: indie web and service workers.
This makes me so happy. I remember saying when my book came out, that the best feedback I could possibly get would be readers making their websites work offline. The same can be said for the talk of the book.
{
"type": "entry",
"published": "2019-03-22T11:02:37Z",
"url": "https://adactio.com/links/14978",
"category": [
"serviceworkers",
"goingoffline",
"homebrew",
"website",
"club",
"indieweb",
"clearleft",
"frontend",
"development",
"javascript",
"talk",
"presentation"
],
"bookmark-of": [
"https://benjamin.parry.is/collecting/thoughts/2018/03/going-offline/"
],
"content": {
"text": "Benjamin Parry Offline Homebrewing\n\n\n\nTwo of my favourite things: indie web and service workers.\n\nThis makes me so happy. I remember saying when my book came out, that the best feedback I could possibly get would be readers making their websites work offline. The same can be said for the talk of the book.",
"html": "<h3>\n<a class=\"p-name u-bookmark-of\" href=\"https://benjamin.parry.is/collecting/thoughts/2018/03/going-offline/\">\nBenjamin Parry Offline Homebrewing\n</a>\n</h3>\n\n<p>Two of my favourite things: indie web and service workers.</p>\n\n<p>This makes me so happy. I remember saying when my book came out, that the best feedback I could possibly get would be readers making their websites work offline. The same can be said for <a href=\"https://adactio.com/journal/14911\">the talk of the book</a>.</p>"
},
"author": {
"type": "card",
"name": "Jeremy Keith",
"url": "https://adactio.com/",
"photo": "https://aperture-proxy.p3k.io/bbbacdf0a064621004f2ce9026a1202a5f3433e0/68747470733a2f2f6164616374696f2e636f6d2f696d616765732f70686f746f2d3135302e6a7067"
},
"post-type": "bookmark",
"_id": "2645703",
"_is_read": true
}
Summary: 01:42 suspended per Twitter email: "abusive behavior" and "targeted harassment of someone" 18:36 restored per "account got caught up in one of these spam groups by mistake"
My tweets are pretty boring. Running pics. #IndieWeb #CSS
One comparing Twitter to the Matrix about an abstract “someone”. Does Twitter’s automated system think “harassment of someone” literally means referring to the literal text “someone”? Is one offhand tweet considered “harassment”?
{
"type": "entry",
"published": "2019-03-20 20:49-0700",
"url": "http://tantek.com/2019/079/t3/summary-suspended-restored",
"category": [
"IndieWeb",
"CSS"
],
"in-reply-to": [
"https://tantek.com/2019/079/t2/thanks"
],
"content": {
"text": "Summary:\n01:42 suspended per Twitter email: \"abusive behavior\" and \"targeted harassment of someone\"\n18:36 restored per \"account got caught up in one of these spam groups by mistake\"\n\nMy tweets are pretty boring. Running pics. #IndieWeb #CSS\n\nOne comparing Twitter to the Matrix about an abstract \u201csomeone\u201d. Does Twitter\u2019s automated system think \u201charassment of someone\u201d literally means referring to the literal text \u201csomeone\u201d? Is one offhand tweet considered \u201charassment\u201d?",
"html": "Summary:<br />01:42 suspended per Twitter email: \"abusive behavior\" and \"targeted harassment of someone\"<br />18:36 restored per \"account got caught up in one of these spam groups by mistake\"<br /><br />My tweets are pretty boring. Running pics. #<span class=\"p-category\">IndieWeb</span> #<span class=\"p-category\">CSS</span><br /><br />One comparing Twitter to the Matrix about an abstract \u201csomeone\u201d. Does Twitter\u2019s automated system think \u201charassment of someone\u201d literally means referring to the literal text \u201csomeone\u201d? Is one offhand tweet considered \u201charassment\u201d?"
},
"author": {
"type": "card",
"name": "Tantek \u00c7elik",
"url": "http://tantek.com/",
"photo": "https://aperture-media.p3k.io/tantek.com/acfddd7d8b2c8cf8aa163651432cc1ec7eb8ec2f881942dca963d305eeaaa6b8.jpg"
},
"post-type": "reply",
"refs": {
"https://tantek.com/2019/079/t2/thanks": {
"type": "entry",
"url": "https://tantek.com/2019/079/t2/thanks",
"name": "Tantek\u2019s note",
"post-type": "article"
}
},
"_id": "2626135",
"_is_read": true
}
Here are some notes from the "broadcast" portion of the meetup!
dmitri.shuralyov.com — Working on his notification system, specifically tracking (un)read status of notifications from Gerrit. Today was exploring pieces of the system he'll have to modify to get this to work and now has a list of which pieces need updates. In his previous notification system, any fetch of a notification marked it as read, but that will change because it gives him more control over the system. Also made an update to the Homebrew Website Club main page to make the event description clearer, using text that we include on individual HWC event pages now.
martymcgui.re — Did a lot of digging into what's possible with MediaWiki templates, with the goal of simplifying the creation of Homebrew Website Club event pages on the IndieWeb wiki. He was able to get an "hwcdate" template together that outputs the date portion (2019-03-20) of event pages like events/2019-03-20-homebrew-website-club-nyc. Maybe created some tech debt, given how that locks in our URLs, but hopefully it will save some copy-paste-tweak labor.
rootedfromnature.com — Got stuck on a train and super delayed! 😭
Other discussion:
MediaWiki and its relation to Wikipedia and as an open source project. Many mediawiki installs become stale quickly, for some good reasons! Finding documentation on parts of mediawiki can also be confusing, as the common terms may point to similar but unrelated topics, may be outdated, may refer to plugins or extensions you don't have, or may refer to functionality available in newer versions of mediawiki.
How we learn and modify the tools we use to write and edit code. The trade-offs between using something we're comfortable with versus trying to pick up and become proficient with new tools. Sublime and vim and emacs and VisualStudio Code and all their plugins and ways of integrating with services and supporting different languages.
The Language Server Protocol for standardizing how editors can provide "smart" features like autocomplete for different languages and projects.
Synchronizing work-in-progress code. Is Git too much overhead? Maybe! Dmitri likes using Dropbox.
{
"type": "entry",
"published": "2019-03-20T19:56:40-0400",
"url": "https://martymcgui.re/2019/03/20/hwc-nyc-wrap-up-2019-03-20/",
"featured": "https://res.cloudinary.com/schmarty/image/fetch/w_960,c_fill/https://media.martymcgui.re/2c/d9/90/9b/12900d4a1a5e3027384426efe00d5746fcabc119c9a81a9e5d78db85.jpg",
"category": [
"HWC",
"NYC",
"IndieWeb",
"wrap-up"
],
"name": "HWC NYC Wrap-Up 2019-03-20",
"content": {
"text": "New York City's second Homebrew Website Club of March met at The Bean at Cooper Union on March 20th, with me playing host. \n \n\nHere are some notes from the \"broadcast\" portion of the meetup!\n\n dmitri.shuralyov.com \u2014 Working on his notification system, specifically tracking (un)read status of notifications from Gerrit. Today was exploring pieces of the system he'll have to modify to get this to work and now has a list of which pieces need updates. In his previous notification system, any fetch of a notification marked it as read, but that will change because it gives him more control over the system. Also made an update to the Homebrew Website Club main page to make the event description clearer, using text that we include on individual HWC event pages now.\n \n\n\n martymcgui.re \u2014 Did a lot of digging into what's possible with MediaWiki templates, with the goal of simplifying the creation of Homebrew Website Club event pages on the IndieWeb wiki. He was able to get an \"hwcdate\" template together that outputs the date portion (2019-03-20) of event pages like events/2019-03-20-homebrew-website-club-nyc. Maybe created some tech debt, given how that locks in our URLs, but hopefully it will save some copy-paste-tweak labor.\n \n\nrootedfromnature.com \u2014 Got stuck on a train and super delayed! \ud83d\ude2d\nOther discussion:\nMediaWiki and its relation to Wikipedia and as an open source project. Many mediawiki installs become stale quickly, for some good reasons! Finding documentation on parts of mediawiki can also be confusing, as the common terms may point to similar but unrelated topics, may be outdated, may refer to plugins or extensions you don't have, or may refer to functionality available in newer versions of mediawiki.\n How we learn and modify the tools we use to write and edit code. The trade-offs between using something we're comfortable with versus trying to pick up and become proficient with new tools. Sublime and vim and emacs and VisualStudio Code and all their plugins and ways of integrating with services and supporting different languages.\n The Language Server Protocol for standardizing how editors can provide \"smart\" features like autocomplete for different languages and projects.\n \n Synchronizing work-in-progress code. Is Git too much overhead? Maybe! Dmitri likes using Dropbox.\n \n\nLeft-to-right: martymcgui.re, dmitri.shuryalov.comThanks to everyone who came out! We look forward to seeing you at our next meetup on Wednesday, April 4th at 6:30pm!",
"html": "<p>\n New York City's second <a href=\"https://indieweb.org/events/2019-03-20-homebrew-website-club-nyc\">Homebrew Website Club of March</a> met at <a href=\"https://www.thebeannyc.com/location/the-bean-3rd-ave/\">The Bean at Cooper Union</a> on March 20th, with me playing host. \n <br /></p>\n<p>Here are some notes from the \"broadcast\" portion of the meetup!</p>\n<p>\n dmitri.shuralyov.com \u2014 Working on his notification system, specifically tracking (un)read status of notifications from Gerrit. Today was exploring pieces of the system he'll have to modify to get this to work and now has a list of which pieces need updates. In his previous notification system, any fetch of a notification marked it as read, but that will change because it gives him more control over the system. Also made an update to the <a href=\"https://indieweb.org/Homebrew_Website_Club\">Homebrew Website Club</a> main page to make the event description clearer, using text that we include on individual HWC event pages now.\n <br /></p>\n<p>\n martymcgui.re \u2014 Did a lot of digging into what's possible with MediaWiki templates, with the goal of simplifying the creation of Homebrew Website Club event pages on the IndieWeb wiki. He was able to get <a href=\"https://indieweb.org/wiki/index.php?title=Template:hwcdate\">an \"hwcdate\" template</a> together that outputs the date portion (2019-03-20) of event pages like events/2019-03-20-homebrew-website-club-nyc. Maybe created some tech debt, given how that locks in our URLs, but hopefully it will save some copy-paste-tweak labor.\n <br /></p>\n<p>rootedfromnature.com \u2014 Got stuck on a train and super delayed! \ud83d\ude2d</p>\n<p>Other discussion:</p>\n<ul><li>MediaWiki and its relation to Wikipedia and as an open source project. Many mediawiki installs become stale quickly, for some good reasons! Finding documentation on parts of mediawiki can also be confusing, as the common terms may point to similar but unrelated topics, may be outdated, may refer to plugins or extensions you don't have, or may refer to functionality available in newer versions of mediawiki.</li>\n <li>How we learn and modify the tools we use to write and edit code. The trade-offs between using something we're comfortable with versus trying to pick up and become proficient with new tools. Sublime and vim and emacs and VisualStudio Code and all their plugins and ways of integrating with services and supporting different languages.</li>\n <li>The <a href=\"https://microsoft.github.io/language-server-protocol/\">Language Server Protocol</a> for standardizing how editors can provide \"smart\" features like autocomplete for different languages and projects.</li>\n <li>\n Synchronizing work-in-progress code. Is Git too much overhead? Maybe! Dmitri likes using Dropbox.\n <br /></li>\n</ul><img class=\"u-featured\" src=\"https://res.cloudinary.com/schmarty/image/fetch/w_960,c_fill/https://media.martymcgui.re/2c/d9/90/9b/12900d4a1a5e3027384426efe00d5746fcabc119c9a81a9e5d78db85.jpg\" alt=\"Marty and Dmitri smile at the camera, sitting in front of a brick wall.\" />Left-to-right: martymcgui.re, dmitri.shuryalov.com<p>Thanks to everyone who came out! We look forward to seeing you at our next meetup on Wednesday, April 4th at 6:30pm! </p>"
},
"author": {
"type": "card",
"name": "Marty McGuire",
"url": "https://martymcgui.re/",
"photo": "https://aperture-proxy.p3k.io/8275f85e3a389bd0ae69f209683436fc53d8bad9/68747470733a2f2f6d617274796d636775692e72652f696d616765732f6c6f676f2e6a7067"
},
"post-type": "article",
"_id": "2625168",
"_is_read": true
}
The new version of Sunlit is now available in the App Store. You can download it for free and use it with Micro.blog or to publish photos to an existing blog like WordPress.
Open standards mean interoperability with multiple tools. I can use IndieWeb tools like OwnYourGram to automatically copy Instagram posts to Micro.blog, or use traditional blogging apps like MarsEdit to upload and post photos.
Content ownership gives the flexibility to move photos between hosting providers. You can host on Micro.blog or WordPress or some future blogging platform without URLs breaking.
Smaller social networks get us away from ad-based businesses that sell our data. Because Sunlit is powered by Micro.blog, you can even follow Mastodon or PixelFed users and see their photos in the Sunlit timeline.
I’m very excited about this release and hope you like it. It’s time to move away Instagram. If you need help importing your photos, check out this video I made about batch importing from Instagram to Micro.blog-hosted blogs.
{
"type": "entry",
"author": {
"name": "Manton Reece",
"url": "https://www.manton.org/",
"photo": "https://aperture-proxy.p3k.io/907926e361383204bd1bc913c143c23e70ae69bb/68747470733a2f2f6d6963726f2e626c6f672f6d616e746f6e2f6176617461722e6a7067"
},
"url": "https://www.manton.org/2019/03/20/sunlit-now-available.html",
"name": "Sunlit 2.4 now available",
"content": {
"html": "<p>The new version of Sunlit is <a href=\"https://itunes.apple.com/us/app/sunlit/id1334727769?ls=1&mt=8\">now available in the App Store</a>. You can download it for free and use it with Micro.blog or to publish photos to an existing blog like WordPress.</p>\n\n<p>Why does controlling our own photos matter? As I wrote in <a href=\"https://manton.org/2018/09/07/the-way-out.html\">this post about the way out of the mess created by massive social networks</a>, having posts at our own domain names unlocks a few very important features:</p>\n\n<ul><li><strong>Open standards</strong> mean interoperability with multiple tools. I can use IndieWeb tools like OwnYourGram to automatically copy Instagram posts to Micro.blog, or use traditional blogging apps like MarsEdit to upload and post photos.</li>\n<li><strong>Content ownership</strong> gives the flexibility to move photos between hosting providers. You can host on Micro.blog or WordPress or some future blogging platform without URLs breaking.</li>\n<li><strong>Smaller social networks</strong> get us away from ad-based businesses that sell our data. Because Sunlit is powered by Micro.blog, you can even follow Mastodon or PixelFed users and see their photos in the Sunlit timeline.</li>\n</ul><p>I\u2019m very excited about this release and hope you like it. It\u2019s time to move away Instagram. If you need help importing your photos, <a href=\"https://manton.org/2018/05/03/instagram-import-in.html\">check out this video I made</a> about batch importing from Instagram to Micro.blog-hosted blogs.</p>",
"text": "The new version of Sunlit is now available in the App Store. You can download it for free and use it with Micro.blog or to publish photos to an existing blog like WordPress.\n\nWhy does controlling our own photos matter? As I wrote in this post about the way out of the mess created by massive social networks, having posts at our own domain names unlocks a few very important features:\n\nOpen standards mean interoperability with multiple tools. I can use IndieWeb tools like OwnYourGram to automatically copy Instagram posts to Micro.blog, or use traditional blogging apps like MarsEdit to upload and post photos.\nContent ownership gives the flexibility to move photos between hosting providers. You can host on Micro.blog or WordPress or some future blogging platform without URLs breaking.\nSmaller social networks get us away from ad-based businesses that sell our data. Because Sunlit is powered by Micro.blog, you can even follow Mastodon or PixelFed users and see their photos in the Sunlit timeline.\nI\u2019m very excited about this release and hope you like it. It\u2019s time to move away Instagram. If you need help importing your photos, check out this video I made about batch importing from Instagram to Micro.blog-hosted blogs."
},
"published": "2019-03-20T10:24:51-05:00",
"post-type": "article",
"_id": "2615845",
"_is_read": true
}
{
"type": "entry",
"published": "2019-03-18T15:06:35Z",
"url": "https://adactio.com/notes/14961",
"syndication": [
"https://twitter.com/adactio/status/1107659570787291137"
],
"content": {
"text": "Brightonians with websites: Homebrew Website Club Brighton is now happening every Thursday evening in the @Clearleft studio:\n\nhttps://indieweb.org/HomebrewWebsiteClub#Brighton\n\nShow up from 6pm and we\u2019ll mess about with our websites.",
"html": "<p>Brightonians with websites: Homebrew Website Club Brighton is now happening every <em>Thursday</em> evening in the <a href=\"https://twitter.com/Clearleft\">@Clearleft</a> studio:</p>\n\n<p><a href=\"https://indieweb.org/Homebrew_Website_Club#Brighton\">https://indieweb.org/Homebrew<em>Website</em>Club#Brighton</a></p>\n\n<p>Show up from 6pm and we\u2019ll mess about with our websites.</p>"
},
"author": {
"type": "card",
"name": "Jeremy Keith",
"url": "https://adactio.com/",
"photo": "https://aperture-proxy.p3k.io/bbbacdf0a064621004f2ce9026a1202a5f3433e0/68747470733a2f2f6164616374696f2e636f6d2f696d616765732f70686f746f2d3135302e6a7067"
},
"post-type": "note",
"_id": "2585554",
"_is_read": true
}
Indieweb reader access with Wordpress on shared hosting
An Indieweb reader (like Monocle, Together or Indigenous) authenticates you with your personal website which also tells the indieweb reader where to fetch your feeds. Wordpress is a popular option for a personal website.
Although I’m not an active wordpress user, I’ve helped a few wordpress users interested in adding Indieweb functionality. I haven’t had much of a problem with the indieweb wordpress plugins and themes but from time to time, I’ve needed a little help from the usual suspects on the indieweb-wordpress chat.
I also have very little experience with shared hosting but it seems that with their one-click wordpress installers, this could be a good option to experience the benefits of an indieweb reader while avoiding more complex hosting options. Shared hosting seems to be much more affordable, too.
It turned out that what I thought was a missing piece was already available. Your website needs to declare where you keep your feeds so that your indieweb reader can find them. On wordpress, this can be accomplished with the aperture plugin. So, I added and activated this plugin to my existing indieweb wordpress test site hosted on dreamhost. The plugin automates the creation of an aperture account and adds a microsub link tag to your web page which points to your aperture url so that your indieweb reader can find your feeds. This ability to declare where you are storing your feeds allows you to change the microsub provider that is hosting your feeds. There are already several microsub providers to choose from.
Next, I tried logging into the Monocle indieweb reader and received a “bearer token not supplied” error.
Aaron Parecki who was nearby explained to me that the web server running wordpress was unfortunately stripping out the authorization request header. A quick search revealed a workaround for this issue by adding the following line to your .htaccess file:
At this point, my unfamiliarity with shared hosting bit me as I had purposely avoided looking under the hood of my account. So, I assumed I could just use my normal credentials to upload the needed .htaccess file but my changes were ignored. It did not occur to me that there was another dreamhost user account under which the one-click wordpress was installed and I needed to use those credentials to make the changes.
As I didn’t immediately figure this out, I decided to try Reclaim Hosting as an alternative shared hosting provider and installed wordpress and the appropriate indieweb plugins and an indieweb-friendly theme. I had better luck this time (and much more affordable). Again, I ran into the “bearer token not supplied” error when logging into the indieweb reader, but luckily there was no multiple user account confusion with reclaim hosting. I could easily add the .htaccess file and confirm that it fixed the “bearer token not supplied” issue.
However, somehow I found myself in a coherency problem state as I received a “This token was issued to a different user” error where aperture was saying my microsub url was different than my website was claiming (different aperture user accounts). I was not able to resolve this issue by reinstalling the aperture wordpress plugin but I was able to resolve it by changing the aperture_microsub_url option name in the wp_options database table to match the one aperture was expecting.
{
"type": "entry",
"author": {
"name": null,
"url": "https://herestomwiththeweather.com/",
"photo": null
},
"url": "https://herestomwiththeweather.com/2019/03/17/indieweb-reader-access-with-wordpress-on-shared-hosting/",
"published": "2019-03-17T14:03:31+00:00",
"content": {
"html": "<p>An <a href=\"https://indieweb.org/reader\">Indieweb reader</a> (like <a href=\"https://monocle.p3k.io/\">Monocle</a>, <a href=\"https://alltogethernow.io/\">Together</a> or <a href=\"https://indieweb.org/Indigenous\">Indigenous</a>) authenticates you with your personal website which also tells the indieweb reader where to fetch your feeds. <a href=\"https://wordpress.org/\">Wordpress</a> is a popular option for a personal website.</p>\n\n<p>Although I\u2019m not an active wordpress user, I\u2019ve helped a few wordpress users interested in adding <a href=\"https://indieweb.org/\">Indieweb</a> functionality. I haven\u2019t had much of a problem with the indieweb wordpress <a href=\"https://indieweb.org/WordPress/Plugins\">plugins</a> and <a href=\"https://indieweb.org/WordPress/Themes\">themes</a> but from time to time, I\u2019ve needed a little help from the usual suspects on the <a href=\"https://chat.indieweb.org/wordpress/\">indieweb-wordpress</a> chat.</p>\n\n<p>I also have very little experience with <a href=\"https://indieweb.org/web_hosting#Shared_Hosting\">shared hosting</a> but it seems that with their one-click wordpress installers, this could be a good option to experience the benefits of an indieweb reader while avoiding more complex hosting options. Shared hosting seems to be much more affordable, too.</p>\n\n<p>At <a href=\"https://indieweb.org/2019/Austin\">IndiewebCamp Austin 2019</a>, I investigated <a href=\"https://www.dreamhost.com/\">Dreamhost</a> and <a href=\"https://reclaimhosting.com/\">Reclaim Hosting</a> as two shared hosting options for interoperability with indieweb readers.</p>\n\n<p>It turned out that what I thought was a missing piece was already available. Your website needs to declare where you keep your feeds so that your indieweb reader can find them. On wordpress, this can be accomplished with the <a href=\"https://wordpress.org/plugins/aperture/\">aperture plugin</a>. So, I added and activated this plugin to my existing indieweb wordpress test site hosted on dreamhost. The plugin automates the creation of an <a href=\"https://aperture.p3k.io/\">aperture</a> account and adds a <a href=\"https://indieweb.org/Microsub\">microsub</a> link tag to your web page which points to your aperture url so that your indieweb reader can find your feeds. This ability to declare where you are storing your feeds allows you to change the microsub provider that is hosting your feeds. There are already several microsub providers to choose from.</p>\n\n<p>Next, I tried logging into the Monocle indieweb reader and received a \u201cbearer token not supplied\u201d error.</p>\n\n<p><img src=\"https://aperture-proxy.p3k.io/8fa52fdcf4ff87a985726dafc493700aeab1b218/68747470733a2f2f73332e616d617a6f6e6177732e636f6d2f737461726b2d6d6f6f6e2d34362f696d616765732f6265617265725f746f6b656e5f6e6f745f737570706c6965642e706e67\" alt=\"Bearer token not supplied\" /></p>\n\n<p>Aaron Parecki who was nearby explained to me that the web server running wordpress was unfortunately stripping out the authorization request header. A quick search revealed a <a href=\"https://islandinthenet.com/aperture/#comment-13386\">workaround for this issue</a> by adding the following line to your .htaccess file:</p>\n\n<pre><code>SetEnvIf Authorization \"(.*)\" HTTP_AUTHORIZATION=$1\n</code></pre>\n\n\n<p>At this point, my unfamiliarity with shared hosting bit me as I had purposely avoided looking under the hood of my account. So, I assumed I could just use my normal credentials to upload the needed .htaccess file but my changes were ignored. It did not occur to me that there was another dreamhost user account under which the one-click wordpress was installed and I needed to use those credentials to make the changes.</p>\n\n<p>As I didn\u2019t immediately figure this out, I decided to try <a href=\"https://reclaimhosting.com/\">Reclaim Hosting</a> as an alternative shared hosting provider and installed wordpress and the appropriate indieweb plugins and an indieweb-friendly theme. I had better luck this time (and much more affordable). Again, I ran into the \u201cbearer token not supplied\u201d error when logging into the indieweb reader, but luckily there was no multiple user account confusion with reclaim hosting. I could easily add the .htaccess file and confirm that it fixed the \u201cbearer token not supplied\u201d issue.</p>\n\n<p>However, somehow I found myself in a coherency problem state as I received a \u201cThis token was issued to a different user\u201d error where aperture was saying my microsub url was different than my website was claiming (different aperture user accounts). I was not able to resolve this issue by reinstalling the aperture wordpress plugin but I was able to resolve it by changing the aperture_microsub_url option name in the wp_options database table to match the one aperture was expecting.</p>",
"text": "An Indieweb reader (like Monocle, Together or Indigenous) authenticates you with your personal website which also tells the indieweb reader where to fetch your feeds. Wordpress is a popular option for a personal website.\n\nAlthough I\u2019m not an active wordpress user, I\u2019ve helped a few wordpress users interested in adding Indieweb functionality. I haven\u2019t had much of a problem with the indieweb wordpress plugins and themes but from time to time, I\u2019ve needed a little help from the usual suspects on the indieweb-wordpress chat.\n\nI also have very little experience with shared hosting but it seems that with their one-click wordpress installers, this could be a good option to experience the benefits of an indieweb reader while avoiding more complex hosting options. Shared hosting seems to be much more affordable, too.\n\nAt IndiewebCamp Austin 2019, I investigated Dreamhost and Reclaim Hosting as two shared hosting options for interoperability with indieweb readers.\n\nIt turned out that what I thought was a missing piece was already available. Your website needs to declare where you keep your feeds so that your indieweb reader can find them. On wordpress, this can be accomplished with the aperture plugin. So, I added and activated this plugin to my existing indieweb wordpress test site hosted on dreamhost. The plugin automates the creation of an aperture account and adds a microsub link tag to your web page which points to your aperture url so that your indieweb reader can find your feeds. This ability to declare where you are storing your feeds allows you to change the microsub provider that is hosting your feeds. There are already several microsub providers to choose from.\n\nNext, I tried logging into the Monocle indieweb reader and received a \u201cbearer token not supplied\u201d error.\n\n\n\nAaron Parecki who was nearby explained to me that the web server running wordpress was unfortunately stripping out the authorization request header. A quick search revealed a workaround for this issue by adding the following line to your .htaccess file:\n\nSetEnvIf Authorization \"(.*)\" HTTP_AUTHORIZATION=$1\n\n\n\nAt this point, my unfamiliarity with shared hosting bit me as I had purposely avoided looking under the hood of my account. So, I assumed I could just use my normal credentials to upload the needed .htaccess file but my changes were ignored. It did not occur to me that there was another dreamhost user account under which the one-click wordpress was installed and I needed to use those credentials to make the changes.\n\nAs I didn\u2019t immediately figure this out, I decided to try Reclaim Hosting as an alternative shared hosting provider and installed wordpress and the appropriate indieweb plugins and an indieweb-friendly theme. I had better luck this time (and much more affordable). Again, I ran into the \u201cbearer token not supplied\u201d error when logging into the indieweb reader, but luckily there was no multiple user account confusion with reclaim hosting. I could easily add the .htaccess file and confirm that it fixed the \u201cbearer token not supplied\u201d issue.\n\nHowever, somehow I found myself in a coherency problem state as I received a \u201cThis token was issued to a different user\u201d error where aperture was saying my microsub url was different than my website was claiming (different aperture user accounts). I was not able to resolve this issue by reinstalling the aperture wordpress plugin but I was able to resolve it by changing the aperture_microsub_url option name in the wp_options database table to match the one aperture was expecting."
},
"name": "Indieweb reader access with Wordpress on shared hosting",
"post-type": "article",
"_id": "2578148",
"_is_read": true
}
{
"type": "entry",
"author": {
"name": "Ton Zijlstra",
"url": "https://www.zylstra.org/blog",
"photo": null
},
"url": "https://www.zylstra.org/blog/2019/03/week-notes-1911/",
"published": "2019-03-17T20:12:19+00:00",
"content": {
"html": "<p>A logistically challenging week with the little one at home with a fever.</p>\n<ul><li>Checked the city archives for the building plans of our house</li>\n<li>Worked on a transparency benchmark for provinces</li>\n<li>Had an early confcall with my World Bank colleagues and our Malaysian government client for our upcoming work there</li>\n<li>Worked on an open data project for a province</li>\n<li>Had a meeting with two directors of the National Archives</li>\n<li>Did some planning for IndieWebCamp Utrecht in May</li>\n<li>Agreed a lease for office space for The Green Land in Utrecht</li>\n</ul>",
"text": "A logistically challenging week with the little one at home with a fever.\nChecked the city archives for the building plans of our house\nWorked on a transparency benchmark for provinces\nHad an early confcall with my World Bank colleagues and our Malaysian government client for our upcoming work there\nWorked on an open data project for a province\nHad a meeting with two directors of the National Archives\nDid some planning for IndieWebCamp Utrecht in May\nAgreed a lease for office space for The Green Land in Utrecht"
},
"name": "Week Notes 19#11",
"post-type": "article",
"_id": "2575630",
"_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: IndieWebCamp Austin & IndieWebCamp Online projects & demos! IndieWebCamp New Haven is this March 30-31! Sign-up! IndieWebCamp D\u00fcsseldorf is scheduled May 11-12! Sign-up! 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": "2019-03-14 20:25-0700",
"start": "2019-03-20 17:30-0700",
"end": "2019-03-20 19:30-0700",
"url": "http://tantek.com/2019/079/e1/homebrew-website-club-sf",
"location": [
"https://wiki.mozilla.org/SF"
],
"content": {
"text": "When: 2019-03-20 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:\n\nIndieWebCamp Austin & IndieWebCamp Online projects & demos!\n\nIndieWebCamp New Haven is this March 30-31! Sign-up!\n\n\nIndieWebCamp D\u00fcsseldorf is scheduled May 11-12! Sign-up!\n\n\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\">2019-03-20 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>\n<a href=\"https://indieweb.org/2019/Austin\">IndieWebCamp Austin</a> & <a href=\"https://indieweb.org/2019/Online\">IndieWebCamp Online</a> projects & demos!</li>\n<li>\n<a href=\"https://indieweb.org/2019/New_Haven\">IndieWebCamp New Haven</a> is this March 30-31! <a href=\"https://2019.indieweb.org/newhaven\">Sign-up!</a>\n</li>\n<li>\n<a href=\"https://indieweb.org/2019/D%C3%BCsseldorf\">IndieWebCamp D\u00fcsseldorf</a> is scheduled May 11-12! <a href=\"https://btco.nf/DUS2019indiewebcamp\">Sign-up!</a>\n</li>\n\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/2019-03-20-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": "2539891",
"_is_read": true
}
{
"type": "entry",
"published": "2019-03-14T11:20:52-0400",
"url": "https://martymcgui.re/2019/03/14/112052/",
"category": [
"IndieWeb",
"context",
"UX",
"twitter"
],
"content": {
"text": "Me: [scrolling through posts in Monocle, the IndieWeb reader]\nMonocle:\nMe: I don't want to open up 8 tabs for Twitter. I'll just visit Tantek's homepage where I bet he shows these tweets in full context.\ntantek.com:\n\ud83d\ude02",
"html": "<p>Me: [scrolling through posts in Monocle, the IndieWeb reader]</p>\n<p>Monocle:</p>\n<img src=\"https://aperture-proxy.p3k.io/b50b03c14bf0a4869d4bec122237c9bdfadd3d0b/68747470733a2f2f6d656469612e6d617274796d636775692e72652f61662f62332f31342f33312f31653139623966323561363339303333383033353937613863333530376135636462396331376366393537333933343863636261613031372e706e67\" alt=\"8 nearly-identical posts saying 'Tantek \u00c7elik liked a post on twitter.com'\" /><p>Me: I don't want to open up 8 tabs for Twitter. I'll just visit <a href=\"https://tantek.com/\">Tantek's homepage</a> where I bet he shows these tweets in full context.</p>\n<p>tantek.com:</p>\n<img src=\"https://aperture-proxy.p3k.io/6800499f99fb72411dbae57060eeb1844be4c4e5/68747470733a2f2f6d656469612e6d617274796d636775692e72652f63322f38622f30382f65332f66353739666466353737346466343165613362303766353765356531323463373466346434346231613966346230363537643934633063332e706e67\" alt=\"Tantek's website similarly has no context for these tweets, saying 'likes @jgarber\u2019s tweet at 18:54, tweet at 18:53, @shiflett\u2019s tweet at 18:53, tweet at 18:53, @mathowie\u2019s tweet at 18:53, @leahculver\u2019s tweet at 18:53, tweet at 18:52, and tweet at 18:52'\" /><p>\ud83d\ude02</p>"
},
"author": {
"type": "card",
"name": "Marty McGuire",
"url": "https://martymcgui.re/",
"photo": "https://aperture-proxy.p3k.io/8275f85e3a389bd0ae69f209683436fc53d8bad9/68747470733a2f2f6d617274796d636775692e72652f696d616765732f6c6f676f2e6a7067"
},
"post-type": "note",
"_id": "2530316",
"_is_read": true
}
Looking forward to my third IndieWeb Summit! It’s amazing to reflect on the improvements coming out of the IndieWeb every year. I wonder what I will hack on this time around??
{
"type": "entry",
"published": "2019-03-11T14:02:24-0400",
"rsvp": "yes",
"url": "https://martymcgui.re/2019/03/11/140224/",
"in-reply-to": [
"https://2019.indieweb.org/summit"
],
"content": {
"text": "I'm going!Looking forward to my third IndieWeb Summit! It\u2019s amazing to reflect on the improvements coming out of the IndieWeb every year. I wonder what I will hack on this time around??",
"html": "I'm going!<p>Looking forward to my third IndieWeb Summit! It\u2019s amazing to reflect on the improvements coming out of the IndieWeb every year. I wonder what I will hack on this time around??</p>"
},
"author": {
"type": "card",
"name": "Marty McGuire",
"url": "https://martymcgui.re/",
"photo": "https://aperture-proxy.p3k.io/8275f85e3a389bd0ae69f209683436fc53d8bad9/68747470733a2f2f6d617274796d636775692e72652f696d616765732f6c6f676f2e6a7067"
},
"post-type": "rsvp",
"refs": {
"https://2019.indieweb.org/summit": {
"type": "entry",
"summary": "The ninth annual gathering for independent web creators of all kinds, graphic artists, designers, UX engineers, coders, hackers, to share ideas, create and improve their personal websites, and build upon each others creations.",
"url": "https://2019.indieweb.org/summit",
"name": "IndieWeb Summit",
"author": {
"type": "card",
"name": "2019.indieweb.org",
"url": "http://2019.indieweb.org",
"photo": null
},
"post-type": "article"
}
},
"_id": "2489998",
"_is_read": true
}
... if I get it working and start creating private posts for people on the IndieWeb, it might encourage them to start adding AutoAuth to their projects as well!
Thank you for the write-up Eddie! Yes, if you get it working, I most definitely want to test AutoAuth on my WP site. Looking to experiment with selective access to parts of my postings, and doing so for different audiences. As described here.
{
"type": "entry",
"author": {
"name": "Ton Zijlstra",
"url": "https://www.zylstra.org/blog",
"photo": null
},
"url": "https://www.zylstra.org/blog/2019/03/6167/",
"published": "2019-03-11T16:10:09+00:00",
"content": {
"html": "Replied to <a href=\"https://eddiehinkle.com/2019/03/11/10/article/\">IndieWebCamp Online 2019</a> by <a href=\"https://eddiehinkle.com/\"><img src=\"https://aperture-proxy.p3k.io/cc9591b69c2c835fa2c6e23745b224db4b4b431f/68747470733a2f2f656464696568696e6b6c652e636f6d2f696d616765732f70726f66696c652e6a7067\" alt=\"EddieHinkle\" />EddieHinkle</a>\n<blockquote>... if I get it working and start creating private posts for people on the IndieWeb, it might encourage them to start adding AutoAuth to their projects as well!</blockquote>\n\n<p>Thank you for the write-up Eddie! Yes, if you get it working, I most definitely want to test AutoAuth on my WP site. Looking to experiment with selective access to parts of my postings, and doing so for different audiences. As <a href=\"https://www.zylstra.org/blog/2019/03/getting-authorised-access-posts-on-the-indieweb/\">described here</a>.</p>",
"text": "Replied to IndieWebCamp Online 2019 by EddieHinkle\n... if I get it working and start creating private posts for people on the IndieWeb, it might encourage them to start adding AutoAuth to their projects as well!\n\nThank you for the write-up Eddie! Yes, if you get it working, I most definitely want to test AutoAuth on my WP site. Looking to experiment with selective access to parts of my postings, and doing so for different audiences. As described here."
},
"post-type": "note",
"_id": "2484814",
"_is_read": true
}
Over a year ago I proposed a new blog archive format. The idea was to have a better way to save the posts and photos in your blog, or move your blog to another platform. I’m happy to announce that Micro.blog can now export in this format.
Here’s how it works:
Click Posts → Export → “Export in blog archive format”.
Micro.blog will generate the archive, which is an HTML file with Microformats, a JSON Feed of all posts, and a folder of uploaded photos. The HTML file uses relative img references so you can open it directly without a server. The JSON Feed includes both HTML and Markdown. (Micro.blog actually uses Hugo to generate the HTML. I’ve made the theme available on GitHub.)
The archive is zipped and renamed with the .bar file extension. When you download a .bar file, you can rename it .zip to open it, but having a new extension should make it more convenient to copy the file or import it into other apps.
Micro.blog uploads the file to S3 and sends you an email when it’s available to download.
If you’ve uploaded a lot of photos, the archives can be fairly big. It’s working well for my blog and I’ll be monitoring it to see how well it works for other blogs. If you have a blog-related app that could import or export this format, let me know!
{
"type": "entry",
"author": {
"name": "Manton Reece",
"url": "https://www.manton.org/",
"photo": "https://aperture-proxy.p3k.io/907926e361383204bd1bc913c143c23e70ae69bb/68747470733a2f2f6d6963726f2e626c6f672f6d616e746f6e2f6176617461722e6a7067"
},
"url": "https://www.manton.org/2019/03/11/exporting-a-blog.html",
"name": "Exporting a blog archive",
"content": {
"html": "<p>Over a year ago <a href=\"https://www.manton.org/2017/11/24/blog-archive-format.html\">I proposed a new blog archive format</a>. The idea was to have a better way to save the posts and photos in your blog, or move your blog to another platform. I\u2019m happy to announce that Micro.blog can now export in this format.</p>\n\n<p>Here\u2019s how it works:</p>\n\n<ul><li>Click Posts \u2192 Export \u2192 \u201cExport in blog archive format\u201d.</li>\n<li>Micro.blog will generate the archive, which is an HTML file with Microformats, a JSON Feed of all posts, and a folder of uploaded photos. The HTML file uses relative <code>img</code> references so you can open it directly without a server. The JSON Feed includes both HTML and Markdown. (Micro.blog actually uses Hugo to generate the HTML. I\u2019ve made the theme <a href=\"https://github.com/microdotblog/theme-archive\">available on GitHub</a>.)</li>\n<li>The archive is zipped and renamed with the .bar file extension. When you download a .bar file, you can rename it .zip to open it, but having a new extension should make it more convenient to copy the file or import it into other apps.</li>\n<li>Micro.blog uploads the file to S3 and sends you an email when it\u2019s available to download.</li>\n</ul><p>If you\u2019ve uploaded a lot of photos, the archives can be fairly big. It\u2019s working well for my blog and I\u2019ll be monitoring it to see how well it works for other blogs. If you have a blog-related app that could import or export this format, let me know!</p>",
"text": "Over a year ago I proposed a new blog archive format. The idea was to have a better way to save the posts and photos in your blog, or move your blog to another platform. I\u2019m happy to announce that Micro.blog can now export in this format.\n\nHere\u2019s how it works:\n\nClick Posts \u2192 Export \u2192 \u201cExport in blog archive format\u201d.\nMicro.blog will generate the archive, which is an HTML file with Microformats, a JSON Feed of all posts, and a folder of uploaded photos. The HTML file uses relative img references so you can open it directly without a server. The JSON Feed includes both HTML and Markdown. (Micro.blog actually uses Hugo to generate the HTML. I\u2019ve made the theme available on GitHub.)\nThe archive is zipped and renamed with the .bar file extension. When you download a .bar file, you can rename it .zip to open it, but having a new extension should make it more convenient to copy the file or import it into other apps.\nMicro.blog uploads the file to S3 and sends you an email when it\u2019s available to download.\nIf you\u2019ve uploaded a lot of photos, the archives can be fairly big. It\u2019s working well for my blog and I\u2019ll be monitoring it to see how well it works for other blogs. If you have a blog-related app that could import or export this format, let me know!"
},
"published": "2019-03-11T08:27:14-05:00",
"post-type": "article",
"_id": "2483053",
"_is_read": true
}
This weekend an online virtual IndieWebCamp took place. One of the topics discussed and worked upon has my strong interest: making it possible to authorise selective access to posts.
Imagine me writing here about my intended travel. This I would want to share with my network, but not necessarily announce publicly until after the fact. Similarly, let’s say I want some of those reading here to get an update about our little one, then I’d want to be able to indicate who can have access to that posting.
In a platform like FB, and previously on Google plus with its circles, you can select audiences for specific postings. Especially the circles in Google allowed fine grained control. On my blog it is much less obvious how to do that. Yet, there are IndieWeb components that would allow this. For instance IndieAuth already allows you to log-in to this website and other platforms using your own URL (much like Facebook’s login can be used on multiple sites, although you really don’t want to do that as it lets FB track you across other sites you use). However, for reading individual postings that have restricted access, it would require an action made by a human (accepting the authorisation request), which makes it impractical. Enter AutoAuth, based on IndieAuth, that allows your site to log-in to mine without human intervention.
Selective access to content inside a posting Now, once this is working, I’d like to take it one step further still. The above still assumes I have postings for all and postings for some, and that implies writing entire postings with a specific audience in mind. More often I find I am deliberately vague on some details in my public postings, even though I know some of my network reading here can be trusted with the specifics. Like names, places, photos etc. In those instances writing another posting with that detailed info for restricted access does not make much sense. I’d want to be able to restrict access to specific sentences, paragraphs or details in an otherwise public posting.
This is akin to the way government document management systems are slowly being adapted, where specific parts in a document are protected by data protection laws, while the document itself is public by law. Currently balancing those two obligations means human intervention before sharing, but slowly systems are being adapted to knowing where in documents restricted access material is located. Ideally I want a way of marking up text in a posting like this so that it is only send out by the webserver when an authorisation like sketched above is available.
So that a posting like this is entirely possible:
“Today we went to the zoo with the little one our little one’s name
general IMAGE of zoo visit IMAGE with little one’s face
{
"type": "entry",
"author": {
"name": "Ton Zijlstra",
"url": "https://www.zylstra.org/blog",
"photo": null
},
"url": "https://www.zylstra.org/blog/2019/03/getting-authorised-access-posts-on-the-indieweb/",
"published": "2019-03-11T11:02:10+00:00",
"content": {
"html": "<p>This weekend an online virtual IndieWebCamp took place. One of the topics discussed and worked upon has my strong interest: making it possible to authorise selective access to posts. </p>\n<p>Imagine me writing here about my intended travel. This I would want to share with my network, but not necessarily announce publicly until after the fact. Similarly, let\u2019s say I want some of those reading here to get an update about our little one, then I\u2019d want to be able to indicate who can have access to that posting.</p>\n<p>In a platform like FB, and previously on Google plus with its circles, you can select audiences for specific postings. Especially the circles in Google allowed fine grained control. On my blog it is much less obvious how to do that. Yet, there are IndieWeb components that would allow this. For instance <a href=\"https://indieweb.org/IndieAuth\">IndieAuth</a> already allows you to log-in to this website and other platforms using your own URL (much like Facebook\u2019s login can be used on multiple sites, although you really don\u2019t want to do that as it lets FB track you across other sites you use). However, for reading individual postings that have restricted access, it would require an action made by a human (accepting the authorisation request), which makes it impractical. Enter <a href=\"https://indieweb.org/AutoAuth\">AutoAuth</a>, based on IndieAuth, that allows your site to log-in to mine without human intervention. </p>\n<p><a href=\"https://vanderven.se/martijn/\">Martijn van de Ven</a> and <a href=\"https://www.svenknebel.de/posts/\">Sven Knebel</a> worked on this, as sketched out in the graph below.</p>\n<p><a href=\"https://aperture-proxy.p3k.io/12c0b480df1a2d722d56aa54012fd075263823ff/68747470733a2f2f73766773686172652e636f6d2f692f4268422e737667\"><img src=\"https://aperture-proxy.p3k.io/12c0b480df1a2d722d56aa54012fd075263823ff/68747470733a2f2f73766773686172652e636f6d2f692f4268422e737667\" alt=\"BhB.svg\" /></a></p>\n<p><strong>Selective access to content <em>inside</em> a posting</strong><br />Now, once this is working, I\u2019d like to take it one step further still. The above still assumes I have postings for all and postings for some, and that implies writing entire postings with a specific audience in mind. More often I find I am deliberately vague on some details in my public postings, even though I know some of my network reading here can be trusted with the specifics. Like names, places, photos etc. In those instances writing another posting with that detailed info for restricted access does not make much sense. I\u2019d want to be able to restrict access to specific sentences, paragraphs or details in an otherwise public posting.</p>\n<p>This is akin to the way government document management systems are slowly being adapted, where specific parts in a document are protected by data protection laws, while the document itself is public by law. Currently balancing those two obligations means human intervention before sharing, but slowly systems are being adapted to knowing where in documents restricted access material is located. Ideally I want a way of marking up text in a posting like this so that it is only send out by the webserver when an authorisation like sketched above is available.</p>\n<p>So that a posting like this is entirely possible:</p>\n<p>\u201cToday we went to the zoo with the little one our little one\u2019s name </p>\n<p> general IMAGE of zoo visit<em><br /></em> IMAGE with little one\u2019s face</p>",
"text": "This weekend an online virtual IndieWebCamp took place. One of the topics discussed and worked upon has my strong interest: making it possible to authorise selective access to posts. \nImagine me writing here about my intended travel. This I would want to share with my network, but not necessarily announce publicly until after the fact. Similarly, let\u2019s say I want some of those reading here to get an update about our little one, then I\u2019d want to be able to indicate who can have access to that posting.\nIn a platform like FB, and previously on Google plus with its circles, you can select audiences for specific postings. Especially the circles in Google allowed fine grained control. On my blog it is much less obvious how to do that. Yet, there are IndieWeb components that would allow this. For instance IndieAuth already allows you to log-in to this website and other platforms using your own URL (much like Facebook\u2019s login can be used on multiple sites, although you really don\u2019t want to do that as it lets FB track you across other sites you use). However, for reading individual postings that have restricted access, it would require an action made by a human (accepting the authorisation request), which makes it impractical. Enter AutoAuth, based on IndieAuth, that allows your site to log-in to mine without human intervention. \nMartijn van de Ven and Sven Knebel worked on this, as sketched out in the graph below.\n\nSelective access to content inside a posting\nNow, once this is working, I\u2019d like to take it one step further still. The above still assumes I have postings for all and postings for some, and that implies writing entire postings with a specific audience in mind. More often I find I am deliberately vague on some details in my public postings, even though I know some of my network reading here can be trusted with the specifics. Like names, places, photos etc. In those instances writing another posting with that detailed info for restricted access does not make much sense. I\u2019d want to be able to restrict access to specific sentences, paragraphs or details in an otherwise public posting.\nThis is akin to the way government document management systems are slowly being adapted, where specific parts in a document are protected by data protection laws, while the document itself is public by law. Currently balancing those two obligations means human intervention before sharing, but slowly systems are being adapted to knowing where in documents restricted access material is located. Ideally I want a way of marking up text in a posting like this so that it is only send out by the webserver when an authorisation like sketched above is available.\nSo that a posting like this is entirely possible:\n\u201cToday we went to the zoo with the little one our little one\u2019s name \n general IMAGE of zoo visit\n IMAGE with little one\u2019s face"
},
"name": "Getting Authorised Access Posts on the #Indieweb",
"post-type": "article",
"_id": "2481739",
"_is_read": true
}
{
"type": "entry",
"published": "2019-03-10 15:31-0700",
"url": "https://gregorlove.com/2019/03/jgmac1106-who-was-it-you/",
"syndication": [
"https://twitter.com/gRegorLove/status/1104872504278073344"
],
"content": {
"text": "@jgmac1106 Who was it you wanted to connect me with about a possible IndieWebCamp San Diego?",
"html": "<p>@jgmac1106 Who was it you wanted to connect me with about a possible IndieWebCamp San Diego?</p>"
},
"author": {
"type": "card",
"name": "gRegor Morrill",
"url": "https://gregorlove.com/",
"photo": "https://aperture-proxy.p3k.io/929c8777d059069a2a16a064d96f4c29b65548f8/68747470733a2f2f677265676f726c6f76652e636f6d2f736974652f6173736574732f66696c65732f333437332f70726f66696c652d323031362d6d65642e6a7067"
},
"post-type": "note",
"_id": "2477030",
"_is_read": true
}
Left-to-right: martymcgui.re, dmitri.shuryalov.com