Brad, how can you not be logged into the IndieWeb wiki yet!?! You've got your own domain and you've got an IndieAuth endpoint. Click on the login link, put your URL into the field and authenticate. You won't get frog marched anywhere, I promise. If you have questions or need help troubleshooting how to login or editing the page, feel free to pop into chat https://chat.indieweb.org/indieweb/ and we'll all help you out! :)
{
"type": "entry",
"published": "2018-07-18T22:01:34+00:00",
"url": "http://stream.boffosocko.com/2018/brad-how-can-you-not-be-logged-into-the-indieweb",
"in-reply-to": [
"https://ramblinggit.com/2018/07/hey-indieweb-update-on-state-of-webring-hosts-2018"
],
"content": {
"text": "Brad, how can you not be logged into the IndieWeb wiki yet!?! You've got your own domain and you've got an IndieAuth endpoint. Click on the login link, put your URL into the field and authenticate. You won't get frog marched anywhere, I promise. If you have questions or need help troubleshooting how to login or editing the page, feel free to pop into chat https://chat.indieweb.org/indieweb/ and we'll all help you out! :)",
"html": "Brad, how can you not be logged into the IndieWeb wiki yet!?! You've got your own domain and you've got an IndieAuth endpoint. Click on the login link, put your URL into the field and authenticate. You won't get frog marched anywhere, I promise. If you have questions or need help troubleshooting how to login or editing the page, feel free to pop into chat <a href=\"https://chat.indieweb.org/indieweb/\">https://chat.indieweb.org/indieweb/</a> and we'll all help you out! :)"
},
"author": {
"type": "card",
"name": "Chris Aldrich",
"url": "http://stream.boffosocko.com/profile/chrisaldrich",
"photo": "https://aperture-proxy.p3k.io/4a01a54aa55b69dd1b2633c835610491c575e2e2/687474703a2f2f73747265616d2e626f66666f736f636b6f2e636f6d2f66696c652f36303034323762383166373738356537303465616466653531316139323730662f7468756d622e6a7067"
},
"post-type": "reply",
"_id": "657037",
"_source": "192",
"_is_read": true
}
When you send a second webmention, Bridgy replies with: Sorry, you’ve already published that page, and Bridgy Publish doesn’t yet support updating or deleting existing posts.
It would help to add a “url” attribute that provides the url of the previous syndication. This would allow me to send webmentions for posts that had previously be syndicated and get the URL of that syndication into my system :)
{
"type": "entry",
"published": "2018-07-18T15:28:54-04:00",
"summary": "When you send a second webmention, Bridgy replies with: Sorry, you\u2019ve already published that page, and Bridgy Publish doesn\u2019t yet support updating or deleting existing posts.\nIt would help to add a \u201curl\u201d attribute that provides the url of the previous syndication. This would allow me to send webmentions for posts that had previously be syndicated and get the URL of that syndication into my system :)",
"url": "https://eddiehinkle.com/2018/07/18/7/reply/",
"category": [
"issues",
"bridgy",
"indieweb"
],
"in-reply-to": [
"https://github.com/snarfed/bridgy/issues/"
],
"content": {
"text": "When you send a second webmention, Bridgy replies with: Sorry, you\u2019ve already published that page, and Bridgy Publish doesn\u2019t yet support updating or deleting existing posts.\n\nIt would help to add a \u201curl\u201d attribute that provides the url of the previous syndication. This would allow me to send webmentions for posts that had previously be syndicated and get the URL of that syndication into my system :)",
"html": "<p>When you send a second webmention, Bridgy replies with: Sorry, you\u2019ve already published that page, and Bridgy Publish doesn\u2019t yet support updating or deleting existing posts.</p>\n\n<p>It would help to add a \u201curl\u201d attribute that provides the url of the previous syndication. This would allow me to send webmentions for posts that had previously be syndicated and get the URL of that syndication into my system :)</p>"
},
"author": {
"type": "card",
"name": "Eddie Hinkle",
"url": "https://eddiehinkle.com/",
"photo": "https://aperture-proxy.p3k.io/cc9591b69c2c835fa2c6e23745b224db4b4b431f/68747470733a2f2f656464696568696e6b6c652e636f6d2f696d616765732f70726f66696c652e6a7067"
},
"post-type": "reply",
"refs": {
"https://github.com/snarfed/bridgy/issues/": {
"type": "entry",
"url": "https://github.com/snarfed/bridgy/issues/",
"name": "https://github.com/snarfed/bridgy/issues/",
"post-type": "article"
}
},
"_id": "656990",
"_source": "226",
"_is_read": true
}
In town for the Decentralized Web Summit August 1-2 and not otherwise busy on July 31st?
Mozilla invites you to a complementary (and complimentary) all day Decentralized Web Hackers Day and IndieWebCamp SF at our Mozilla San Francisco offices.
Spend a day creating the web you want collaborating with others doing the same, using the latest in decentralized and indieweb technologies.
Schedule 10:00 Opening keynotes and lightning intros/demos 11:00 BarCamp breakout session scheduling 11:30 Open hack day and discussion sessions 16:00 Lightning Demos! 17:00 Wrap-up and transit to DWeb pre-party
We will open the day with a few brief introductory keynotes to set the stage and get your creativity flowing, followed by a round of lightning intros/demos by participants who want to (yes that means you!)
In our usual BarCamp style, we’ll spend a few minutes having participants propose different discussion/hacking sessions for the day and pick rooms & time slots. Sessions will start promptly after scheduling. Don’t worry if this is your first time participating in a BarCamp, we will explain the process for everyone and especially make sure newcomers get a chance to propose their session ideas.
Final sessions and hacking will wrap at 16:00 and we will all reconvene in the main room for a round of lightning demos of hacks, insights, whatever you made or thought up.
Afterwards we’ll direct you to local transit that will take you to the Internet Archive for the Decentralized Web Summit Science Faire and Pre-party (requires separate registration)
Any questions? Ask in #indieweb Slack or IRC
More information: IndieWeb Wiki Event Page
RSVP: post an indie RSVP on your own site or add yourself to the wiki (or both!)
{
"type": "event",
"name": "IndieWebCamp SF / #DWeb Hackers Day",
"summary": "In town for the Decentralized Web Summit August 1-2 and not otherwise busy on July 31st?\nMozilla invites you to a complementary (and complimentary) all day Decentralized Web Hackers Day and IndieWebCamp SF at our Mozilla San Francisco offices.\nSpend a day creating the web you want collaborating with others doing the same, using the latest in decentralized and indieweb technologies.\nSchedule 10:00 Opening keynotes and lightning intros/demos 11:00 BarCamp breakout session scheduling 11:30 Open hack day and discussion sessions 16:00 Lightning Demos! 17:00 Wrap-up and transit to DWeb pre-party\nWe will open the day with a few brief introductory keynotes to set the stage and get your creativity flowing, followed by a round of lightning intros/demos by participants who want to (yes that means you!)\nIn our usual BarCamp style, we\u2019ll spend a few minutes having participants propose different discussion/hacking sessions for the day and pick rooms & time slots. Sessions will start promptly after scheduling. Don\u2019t worry if this is your first time participating in a BarCamp, we will explain the process for everyone and especially make sure newcomers get a chance to propose their session ideas.\nFinal sessions and hacking will wrap at 16:00 and we will all reconvene in the main room for a round of lightning demos of hacks, insights, whatever you made or thought up.\nAfterwards we\u2019ll direct you to local transit that will take you to the Internet Archive for the Decentralized Web Summit Science Faire and Pre-party (requires separate registration)\nAny questions? Ask in #indieweb Slack or IRC\nMore information: IndieWeb Wiki Event Page\nRSVP: post an indie RSVP on your own site or add yourself to the wiki (or both!)",
"published": "2018-07-17 15:45-0700",
"start": "2018-07-31 10:00-0700",
"end": "2018-07-31 17:00-0700",
"url": "http://tantek.com/2018/212/e1/indiewebcamp-sf-dweb-hackers-day",
"location": [
"https://wiki.mozilla.org/SF"
],
"post-type": "event",
"refs": {
"https://wiki.mozilla.org/SF": {
"type": "card",
"name": "Mozilla San Francisco",
"url": "https://wiki.mozilla.org/SF",
"photo": null
}
},
"_id": "653114",
"_source": "1",
"_is_read": true
}
After IndieWebCamp Austin last year, we let the Homebrew Website Club meetups kind of fade away. Time to reboot it. August 1st, 6:30pm at Mozart’s Coffee.
{
"type": "entry",
"author": {
"name": null,
"url": "https://www.manton.org/",
"photo": null
},
"url": "https://www.manton.org/2018/07/17/after-indiewebcamp-austin.html",
"content": {
"html": "<p>After IndieWebCamp Austin last year, we let the <a href=\"https://indieweb.org/Homebrew_Website_Club\">Homebrew Website Club</a> meetups kind of fade away. Time to reboot it. August 1st, 6:30pm at Mozart\u2019s Coffee.</p>",
"text": "After IndieWebCamp Austin last year, we let the Homebrew Website Club meetups kind of fade away. Time to reboot it. August 1st, 6:30pm at Mozart\u2019s Coffee."
},
"published": "2018-07-17T16:56:25-05:00",
"post-type": "note",
"_id": "652580",
"_source": "12",
"_is_read": true
}
{
"type": "entry",
"author": {
"name": null,
"url": "https://monday.micro.blog/",
"photo": null
},
"url": "https://monday.micro.blog/2018/07/16/eddiehinkle.html",
"published": "2018-07-16T12:04:14-07:00",
"content": {
"html": "<p>This week, Jean talks to <a href=\"https://micro.blog/EddieHinkle\">Eddie Hinkle</a>. He\u2019s a software engineer who lives in the Washington DC area, and he is working on several interesting projects, including <a href=\"https://indigenous.abode.pub/ios/\">Indigenous</a>, an iOS app that provides an interface for the IndieWeb. Jean was grateful that Eddie could make the time to chat, especially as he is also a father-to-be whose child is due this week!</p>",
"text": "This week, Jean talks to Eddie Hinkle. He\u2019s a software engineer who lives in the Washington DC area, and he is working on several interesting projects, including Indigenous, an iOS app that provides an interface for the IndieWeb. Jean was grateful that Eddie could make the time to chat, especially as he is also a father-to-be whose child is due this week!"
},
"name": "18: @EddieHinkle",
"audio": [
"https://aperture-proxy.p3k.io/2bd9bc75b4f99c205de44e97153e67feb058682b/687474703a2f2f6d6f6e6461792e6d6963726f2e626c6f672f75706c6f6164732f323031382f323363356338303236362e6d7033"
],
"post-type": "audio",
"_id": "649503",
"_source": "250",
"_is_read": true
}
{
"type": "entry",
"published": "2018-07-17T05:58:22+00:00",
"url": "http://stream.boffosocko.com/2018/matpacker-theres-some-documentation-at-workflow-i-also-suspect-that",
"syndication": [
"https://twitter.com/ChrisAldrich/status/1019098986551173120"
],
"in-reply-to": [
"https://twitter.com/matpacker/status/1018978108077207552",
"https://matpacker.com/2018/07/17/7838"
],
"content": {
"text": "@matpacker There's some documentation at https://indieweb.org/Workflow. \n\nI also suspect that some of the WordPress/iOS crowd hanging out in micro.blog may have some experience with this.Searching in chat may reveal more: https://chat.indieweb.org/indieweb/",
"html": "@matpacker There's some documentation at <a href=\"https://indieweb.org/Workflow\">https://indieweb.org/Workflow</a>. <br />\nI also suspect that some of the WordPress/iOS crowd hanging out in micro.blog may have some experience with this.Searching in chat may reveal more: <a href=\"https://chat.indieweb.org/indieweb/\">https://chat.indieweb.org/indieweb/</a>"
},
"author": {
"type": "card",
"name": "Chris Aldrich",
"url": "http://stream.boffosocko.com/profile/chrisaldrich",
"photo": "https://aperture-proxy.p3k.io/4a01a54aa55b69dd1b2633c835610491c575e2e2/687474703a2f2f73747265616d2e626f66666f736f636b6f2e636f6d2f66696c652f36303034323762383166373738356537303465616466653531316139323730662f7468756d622e6a7067"
},
"post-type": "reply",
"_id": "648798",
"_source": "192",
"_is_read": true
}
{
"type": "entry",
"published": "2018-07-16T18:53:54-04:00",
"url": "https://martymcgui.re/2018/07/16/185354/",
"category": [
"podcast",
"IndieWeb",
"this-week-indieweb-podcast"
],
"audio": [
"https://aperture-proxy.p3k.io/65e5c65286b420966a851390030932a6f864b1f3/68747470733a2f2f6d656469612e6d617274796d636775692e72652f30382f32642f35642f64612f39653938323133636465643831373931306435393164356333383138636561663839373337366662376639663033383439373565333761352e6d7033"
],
"name": "This Week in the IndieWeb Audio Edition \u2022 July 7th - 13th, 2018",
"content": {
"text": "Nostalgia for homepages, IndieAuth gets an explainer, and lots of new events. It\u2019s the audio edition for This Week in the IndieWeb for July 7th - 13th, 2018.\n\nYou can find all of my audio editions and subscribe with your favorite podcast app here: martymcgui.re/podcasts/indieweb/.\n\nMusic from Aaron Parecki\u2019s 100DaysOfMusic project: Day 85 - Suit, Day 48 - Glitch, Day 49 - Floating, Day 9, and Day 11\n\nThanks to everyone in the IndieWeb chat for their feedback and suggestions. Please drop me a note if there are any changes you\u2019d like to see for this audio edition!",
"html": "<p>Nostalgia for homepages, IndieAuth gets an explainer, and lots of new events. It\u2019s the audio edition for <a href=\"https://indieweb.org/this-week/2018-07-13.html\">This Week in the IndieWeb for July 7th - 13th, 2018</a>.</p>\n\n<p>You can find all of my audio editions and subscribe with your favorite podcast app here: <a href=\"https://martymcgui.re/podcasts/indieweb/\">martymcgui.re/podcasts/indieweb/</a>.</p>\n\n<p>Music from <a href=\"https://aaronparecki.com/\">Aaron Parecki</a>\u2019s <a href=\"https://100.aaronparecki.com/\">100DaysOfMusic project</a>: <a href=\"https://aaronparecki.com/2017/03/15/14/day85\">Day 85 - Suit</a>, <a href=\"https://aaronparecki.com/2017/02/06/7/day48\">Day 48 - Glitch</a>, <a href=\"https://aaronparecki.com/2017/02/07/4/day49\">Day 49 - Floating</a>, <a href=\"https://aaronparecki.com/2016/12/29/21/day-9\">Day 9</a>, and <a href=\"https://aaronparecki.com/2016/12/31/15/\">Day 11</a></p>\n\n<p>Thanks to everyone in the <a href=\"https://chat.indieweb.org/\">IndieWeb chat</a> for their feedback and suggestions. Please drop me a note if there are any changes you\u2019d like to see for this audio edition!</p>"
},
"author": {
"type": "card",
"name": "Marty McGuire",
"url": "https://martymcgui.re/",
"photo": "https://aperture-proxy.p3k.io/8275f85e3a389bd0ae69f209683436fc53d8bad9/68747470733a2f2f6d617274796d636775692e72652f696d616765732f6c6f676f2e6a7067"
},
"post-type": "audio",
"_id": "647150",
"_source": "175",
"_is_read": true
}
{
"type": "entry",
"published": "2018-07-16T07:05:56-07:00",
"url": "https://snarfed.org/2018-07-16_introducing-baffle",
"syndication": [
"https://news.indieweb.org/en/snarfed.org/2018-07-16_introducing-baffle",
"https://twitter.com/schnarfed/status/1018888972150267908"
],
"name": "Introducing Baffle",
"content": {
"text": "A while back, I wrote up a design for bridging Microsub clients to traditional feed reader backends. Fast forward to a few weeks ago: I hacked together a bare bones prototype at IndieWebCamp 2018. Fast forward to now: I\u2019m launching Baffle!\nBaffle lets you use Microsub reader apps like Together, Indigenous, and Monocle with traditional feed readers like NewsBlur and maybe eventually Feedly and more.\nRight now, it only supports viewing channels and timelines. If there\u2019s enough interest and usage, I can add channel management, muting, and blocking. I\u2019d also consider adding Feedly if I hear enough desire.\nHappy reading!",
"html": "<p>\n <a href=\"https://baffle.tech/\">\n <img src=\"https://aperture-proxy.p3k.io/ba5fa097747514d3123a876799eae62921760991/68747470733a2f2f736e61726665642e6f72672f772f77702d636f6e74656e742f706c7567696e732f6a65747061636b2f6d6f64756c65732f6c617a792d696d616765732f696d616765732f3178312e7472616e732e676966\" alt=\"1x1.trans.gif\" /></a></p><img src=\"https://aperture-proxy.p3k.io/4d6d8e0cceda2e607f3fa6bc54cf8e1c2d1556de/68747470733a2f2f736e61726665642e6f72672f626166666c652d6c6f676f2e706e67\" alt=\"baffle-logo.png\" />\n<p>A while back, <a href=\"https://snarfed.org/microsub-bridge\">I wrote up a design for bridging Microsub clients to traditional feed reader backends</a>. Fast forward to a few weeks ago: <a href=\"https://chat.indieweb.org/2018-06-27#t1530141961518300\">I hacked together a bare bones prototype</a> at <a href=\"https://2018.indieweb.org/\">IndieWebCamp 2018</a>. Fast forward to now: I\u2019m launching <a href=\"https://baffle.tech/\">Baffle</a>!</p>\n<p>Baffle lets you use <a href=\"https://indieweb.org/Microsub-spec\">Microsub</a> reader apps like <a href=\"https://indieweb.org/Together\">Together</a>, <a href=\"https://indieweb.org/Indigenous\">Indigenous</a>, and <a href=\"https://monocle.p3k.io/\">Monocle</a> with traditional feed readers like <a href=\"https://www.newsblur.com/\">NewsBlur</a> and maybe eventually <a href=\"https://feedly.com/\">Feedly</a> and more.</p>\n<p>Right now, it only supports viewing channels and timelines. If there\u2019s enough interest and usage, I can add channel management, muting, and blocking. I\u2019d also consider adding Feedly if I hear enough desire.</p>\n<p>Happy reading!</p>"
},
"author": {
"type": "card",
"name": "Ryan Barrett",
"url": "https://snarfed.org/",
"photo": "https://aperture-proxy.p3k.io/7e644a0ecb0339b875f998fc405c685591d80cd7/68747470733a2f2f7365637572652e67726176617461722e636f6d2f6176617461722f39343762356633663332336461306566373835623666303264396332363564363f733d393626643d626c616e6b26723d67"
},
"post-type": "article",
"_id": "645526",
"_source": "3",
"_is_read": true
}
Webmention enables a LOT of possibilities, at the root it is just a decentralized notification from one website to another. Currently, the best and most common use case is social media style responses (replies, likes, emoji reactions, and listen posts).
{
"type": "entry",
"published": "2018-07-16T10:20:48-04:00",
"summary": "Webmention enables a LOT of possibilities, at the root it is just a decentralized notification from one website to another. Currently, the best and most common use case is social media style responses (replies, likes, emoji reactions, and listen posts).",
"url": "https://eddiehinkle.com/2018/07/16/3/reply/",
"in-reply-to": [
"https://twitter.com/dialogCRM/status/1018766549274902529"
],
"content": {
"text": "Webmention enables a LOT of possibilities, at the root it is just a decentralized notification from one website to another. Currently, the best and most common use case is social media style responses (replies, likes, emoji reactions, and listen posts).",
"html": "<p>Webmention enables a LOT of possibilities, at the root it is just a decentralized notification from one website to another. Currently, the best and most common use case is social media style responses (replies, likes, emoji reactions, and listen posts).</p>"
},
"author": {
"type": "card",
"name": "Eddie Hinkle",
"url": "https://eddiehinkle.com/",
"photo": "https://aperture-proxy.p3k.io/cc9591b69c2c835fa2c6e23745b224db4b4b431f/68747470733a2f2f656464696568696e6b6c652e636f6d2f696d616765732f70726f66696c652e6a7067"
},
"post-type": "reply",
"refs": {
"https://twitter.com/dialogCRM/status/1018766549274902529": {
"type": "entry",
"url": "https://twitter.com/dialogCRM/status/1018766549274902529",
"name": "https://twitter.com/dialogCRM/status/1018766549274902529",
"post-type": "article"
}
},
"_id": "644952",
"_source": "226",
"_is_read": true
}
{
"type": "entry",
"published": "2018-07-16T08:09:51-04:00",
"url": "https://david.shanske.com/2018/07/16/an-indieweb-podcast-episode-8-interflux/",
"audio": [
"https://aperture-proxy.p3k.io/ba47c2f009dd4dbf331cf1c93996ed277268bba0/68747470733a2f2f64617669642e7368616e736b652e636f6d2f77702d636f6e74656e742f75706c6f6164732f323031382f30372f496e646965776562382e6d7033"
],
"syndication": [
"https://twitter.com/dshanske/status/1018830085900636160"
],
"name": "Episode 8: Interflux",
"content": {
"text": "In this episode, Chris and I recap our takeaways and stories from the Indieweb Summit 2018 last month in Portland, Oregon, discuss Microsub, Vouch, and other ideas.\nVouch\nBrainstorming on Implementing Vouch, Following, and Blogrolls \u2013 David Shanske\nRefbacks\nThe Year of the Reader\nGranary\nMicrosub\nIndiewebring\nSending Your First Webmention \u2013 Aaron Parecki\nOAuth for the Open Web \u2013 Aaron Parecki",
"html": "In this episode, Chris and I recap our takeaways and stories from the <a href=\"http://indieweb.org/2018\">Indieweb Summit 2018</a> last month in Portland, Oregon, discuss Microsub, Vouch, and other ideas.\n<ul><li><a href=\"http://indieweb.org/Vouch\">Vouch</a></li>\n<li><a href=\"https://david.shanske.com/2018/07/01/brainstorming-on-implementing-vouch-following-and-blogrolls/\">Brainstorming on Implementing Vouch, Following, and Blogrolls \u2013 David Shanske</a></li>\n<li><a href=\"http://indieweb.org/refback\">Refbacks</a></li>\n<li>The Year of the Reader</li>\n<li><a href=\"https://granary.io\">Granary</a></li>\n<li><a href=\"http://indieweb.org/Microsub\">Microsub</a></li>\n<li><a href=\"http://indieweb.org/indiewebring\">Indiewebring</a></li>\n<li><a href=\"https://aaronparecki.com/2018/06/30/11/your-first-webmention\">Sending Your First Webmention \u2013 Aaron Parecki</a></li>\n<li><a href=\"https://aaronparecki.com/2018/07/07/7/oauth-for-the-open-web\">OAuth for the Open Web \u2013 Aaron Parecki</a></li>\n</ul>"
},
"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": "audio",
"_id": "643936",
"_source": "5",
"_is_read": true
}
@cogdog I have a lot of email spammers talking about my site who can't spell CONVERSATIONS either. What's worse is that when I contact them, none have ever even heard of simple standards like Webmention.
;)
{
"type": "entry",
"published": "2018-07-15T21:57:51+00:00",
"url": "http://stream.boffosocko.com/2018/cogdog-i-have-a-lot-of-email-spammers-talking-about",
"syndication": [
"https://twitter.com/ChrisAldrich/status/1018615665111035904"
],
"in-reply-to": [
"https://twitter.com/cogdog/status/1017781817594859520"
],
"content": {
"text": "@cogdog I have a lot of email spammers talking about my site who can't spell CONVERSATIONS either. What's worse is that when I contact them, none have ever even heard of simple standards like Webmention. \n\n;)",
"html": "<a href=\"https://twitter.com/cogdog\">@cogdog</a> I have a lot of email spammers talking about my site who can't spell CONVERSATIONS either. What's worse is that when I contact them, none have ever even heard of simple standards like Webmention. <br />\n;)"
},
"author": {
"type": "card",
"name": "Chris Aldrich",
"url": "http://stream.boffosocko.com/profile/chrisaldrich",
"photo": "https://aperture-proxy.p3k.io/4a01a54aa55b69dd1b2633c835610491c575e2e2/687474703a2f2f73747265616d2e626f66666f736f636b6f2e636f6d2f66696c652f36303034323762383166373738356537303465616466653531316139323730662f7468756d622e6a7067"
},
"post-type": "reply",
"_id": "642406",
"_source": "192",
"_is_read": true
}
“A friend gave me design advice once. He said to start with left-aligned black text on a white background, and to apply styling only to solve a specific problem. This is good advice.” @davetron5000 https://brutalist-web.design/#Indieweb
{
"type": "entry",
"published": "2018-07-14T06:13:22+0000",
"url": "http://known.kevinmarks.com/2018/a-friend-gave-me-design-advice-once",
"category": [
"Indieweb"
],
"syndication": [
"https://twitter.com/kevinmarks/status/1018015580358447106"
],
"content": {
"text": "\u201cA friend gave me design advice once. He said to start with left-aligned black text on a white background, and to apply styling only to solve a specific problem. This is good advice.\u201d @davetron5000 \nhttps://brutalist-web.design/ #Indieweb",
"html": "\u201cA friend gave me design advice once. He said to start with left-aligned black text on a white background, and to apply styling only to solve a specific problem. This is good advice.\u201d @davetron5000 <br /><a href=\"https://brutalist-web.design/\">https://brutalist-web.design/</a> <a href=\"http://known.kevinmarks.com/tag/Indieweb\" class=\"p-category\">#Indieweb</a>"
},
"author": {
"type": "card",
"name": "Kevin Marks",
"url": "http://known.kevinmarks.com/profile/kevinmarks",
"photo": "https://aperture-proxy.p3k.io/ed7979fd10a648fc253eae0b54e66fb36e57d3d4/687474703a2f2f6b6e6f776e2e6b6576696e6d61726b732e636f6d2f66696c652f3932353536353636363931373362373836376162383339656536353536663965"
},
"_id": "618802",
"_source": "205",
"_is_read": true
}
That’s a tough decision. I can see both sides. On one side, it’s not too difficult to add an “-x” to the properties in the Micropub servers. On the other side, it seems like leaving it the same until the standard is the simplest step.
Sorry I’m not much help, but I can understand the catch-22.
{
"type": "entry",
"published": "2018-07-13T23:29:55-04:00",
"summary": "That\u2019s a tough decision. I can see both sides. On one side, it\u2019s not too difficult to add an \u201c-x\u201d to the properties in the Micropub servers. On the other side, it seems like leaving it the same until the standard is the simplest step.\nSorry I\u2019m not much help, but I can understand the catch-22.",
"url": "https://eddiehinkle.com/2018/07/13/56/reply/",
"in-reply-to": [
"https://gregorlove.com/2018/07/micropub-properties-for-indiebookclub/"
],
"content": {
"text": "That\u2019s a tough decision. I can see both sides. On one side, it\u2019s not too difficult to add an \u201c-x\u201d to the properties in the Micropub servers. On the other side, it seems like leaving it the same until the standard is the simplest step.\n\nSorry I\u2019m not much help, but I can understand the catch-22.",
"html": "<p>That\u2019s a tough decision. I can see both sides. On one side, it\u2019s not too difficult to add an \u201c-x\u201d to the properties in the Micropub servers. On the other side, it seems like leaving it the same until the standard is the simplest step.</p>\n\n<p>Sorry I\u2019m not much help, but I can understand the catch-22.</p>"
},
"author": {
"type": "card",
"name": "Eddie Hinkle",
"url": "https://eddiehinkle.com/",
"photo": "https://aperture-proxy.p3k.io/cc9591b69c2c835fa2c6e23745b224db4b4b431f/68747470733a2f2f656464696568696e6b6c652e636f6d2f696d616765732f70726f66696c652e6a7067"
},
"refs": {
"https://gregorlove.com/2018/07/micropub-properties-for-indiebookclub/": {
"type": "entry",
"url": "https://gregorlove.com/2018/07/micropub-properties-for-indiebookclub/",
"name": "https://gregorlove.com/2018/07/micropub-properties-for-indiebookclub/"
}
},
"_id": "618215",
"_source": "226",
"_is_read": true
}
{
"type": "entry",
"published": "2018-07-13 17:36-0700",
"url": "https://gregorlove.com/2018/07/micropub-properties-for-indiebookclub/",
"name": "Micropub properties for indiebookclub",
"content": {
"text": "Tantek and I were discussing the read-of and read-status properties and the process of standardizing them in the h-entry specification. I realized read-status may be an overly-specific property name, since the same concept might apply to listen, watch, and exercise posts. Since these are experimental properties, ideally they should be published with the x prefix: p-x-read-status. I noted this in the brainstorming for read posts.\n\nThe problem\n\nI\u2019m trying to decide if/how I should update the indiebookclub Micropub request to reflect this. I know of three Micropub servers processing both properties when publishing:\n\nmicro.blog\n\tMarty McGuire\n\tmy site\nThe WordPress Semantic Linkbacks plugin consumes the read-of property from webmentions to display a separate reading facepile.\n\nThe seemingly correct thing would be for indiebookclub to send these properties as x-read-status and x-read-of. My first reaction is: I don\u2019t want to break the servers above (especially micro.blog) by changing it. My second reaction is: if I do change them now and eventually read properties get standardized, changing at that point will break servers a second time. Is it better to break things once or twice? I wonder if the \u201cbest\u201d thing to do is leave the request as-is and only update it later, once the properties are standardized. This could have the negative effect of encouraging people to keep publishing read-status and read-of, giving the impression they\u2019re standard.\n\nA potential solution?\n\nI could make different versions of the Micropub request and let users toggle them on their settings page. To prevent micro.blog from breaking immediately, I could default micro.blog users to the legacy version. Everyone else would default to v2. Whenever the properties are standardized, v3 would be setup and become the default.\n\nThis solution feels a bit unfriendly to Micropub server implementers, so I keep coming back to wondering if I should keep it as-is and only change when it\u2019s standardized.\n\nI feel a bit stuck, so I\u2019m definitely open to suggestions. Help me, Micropub masters! :]",
"html": "<p><a class=\"h-card\" href=\"http://tantek.com\">Tantek</a> and I were <a href=\"https://chat.indieweb.org/microformats/2018-07-09#t1531169722471100\">discussing</a> the <code>read-of</code> and <code>read-status</code> properties and the process of standardizing them in the <a href=\"http://microformats.org/wiki/h-entry\">h-entry specification</a>. I realized <code>read-status</code> may be an overly-specific property name, since the same concept might apply to listen, watch, and exercise posts. Since these are experimental properties, ideally they should be published with the x prefix: <code>p-x-read-status</code>. I noted this in the <a href=\"https://indieweb.org/read#gRegor_Morrill_thoughts\">brainstorming</a> for read posts.</p>\n\n<h2>The problem</h2>\n\n<p>I\u2019m trying to decide if/how I should update the <a href=\"https://indiebookclub.biz/documentation#micropub\">indiebookclub Micropub request</a> to reflect this. I know of three Micropub servers processing both properties when publishing:</p>\n\n<ul><li><a href=\"https://micro.blog\">micro.blog</a></li>\n\t<li><a class=\"h-card\" href=\"https://martymcgui.re\">Marty McGuire</a></li>\n\t<li>my site</li>\n</ul><p>The WordPress Semantic Linkbacks plugin consumes the <code>read-of</code> property from webmentions to display a separate <i>reading</i> facepile.</p>\n\n<p>The seemingly correct thing would be for indiebookclub to send these properties as <code>x-read-status</code> and <code>x-read-of</code>. My first reaction is: I don\u2019t want to break the servers above (especially micro.blog) by changing it. My second reaction is: if I do change them now and eventually <i>read</i> properties get standardized, changing at that point will break servers a second time. Is it better to break things once or twice? I wonder if the \u201cbest\u201d thing to do is leave the request as-is and only update it later, once the properties are standardized. This could have the negative effect of encouraging people to keep publishing <code>read-status</code> and <code>read-of</code>, giving the impression they\u2019re standard.</p>\n\n<h2>A potential solution?</h2>\n\n<p>I could make different versions of the Micropub request and let users toggle them on their settings page. To prevent micro.blog from breaking immediately, I could default micro.blog users to the <i>legacy</i> version. Everyone else would default to <i>v2</i>. Whenever the properties are standardized, <i>v3</i> would be setup and become the default.</p>\n\n<p>This solution feels a bit unfriendly to Micropub server implementers, so I keep coming back to wondering if I should keep it as-is and only change when it\u2019s standardized.</p>\n\n<p>I feel a bit stuck, so I\u2019m definitely open to suggestions. Help me, Micropub masters! :]</p>"
},
"author": {
"type": "card",
"name": "gRegor Morrill",
"url": "https://gregorlove.com/",
"photo": "https://aperture-proxy.p3k.io/929c8777d059069a2a16a064d96f4c29b65548f8/68747470733a2f2f677265676f726c6f76652e636f6d2f736974652f6173736574732f66696c65732f333437332f70726f66696c652d323031362d6d65642e6a7067"
},
"_id": "616963",
"_source": "95",
"_is_read": true
}
{
"type": "entry",
"author": {
"name": null,
"url": "https://www.manton.org/",
"photo": null
},
"url": "https://www.manton.org/2018/07/13/web-rings-are.html",
"name": "Web rings are back",
"content": {
"html": "<p>One reason that <a href=\"http://manton.org/2018/06/30/indieweb-summit-wrapup.html\">IndieWeb Summit was such a success</a> was the range of projects to come out of the second day as attendees worked on their own projects. There were new tools and features of existing platforms, but also personal site updates and just fun stuff. And web rings are fun!</p>\n\n<p>I know, I know\u2026 Is it 2018 or 1998? I\u2019ve added a <a href=\"http://help.micro.blog/2018/web-rings/\">help page on Micro.blog</a> for how to add a web ring to your blog using \ud83d\udd78\ufe0f\ud83d\udc8d. One of the great things about microblogging at your own domain name is you can experiment with features like this.</p>\n\n<p>Daniel and I talk a little more about this on <a href=\"https://coreint.org/2018/07/episode-336-bringing-webrings-back/\">the new episode of Core Intuition</a> out today. Enjoy.</p>",
"text": "One reason that IndieWeb Summit was such a success was the range of projects to come out of the second day as attendees worked on their own projects. There were new tools and features of existing platforms, but also personal site updates and just fun stuff. And web rings are fun!\n\nI know, I know\u2026 Is it 2018 or 1998? I\u2019ve added a help page on Micro.blog for how to add a web ring to your blog using \ud83d\udd78\ufe0f\ud83d\udc8d. One of the great things about microblogging at your own domain name is you can experiment with features like this.\n\nDaniel and I talk a little more about this on the new episode of Core Intuition out today. Enjoy."
},
"published": "2018-07-13T15:01:29-05:00",
"_id": "615611",
"_source": "12",
"_is_read": true
}
Thanks for writing this up. The standard is stable enough to be used daily but as you said, the features to make the apps (including Indigenous for iOS, which I am developing) excel are still in development. I’ve been able to implement some of what you mentioned (mark posts as read/unread), but others are still on my list of things to tackle (sorting, filtering, etc). I think two things are needed to get where we need to be: 1) all Microsub developers need to use it daily (I’m pretty sure we all do) and 2) People that try it out need to write blog posts just like this one so that we see where we need to improve and iterate.
Thanks for trying Microsub out. Hopefully it won’t be too long before it supports the features you need! 🙂
{
"type": "entry",
"published": "2018-07-13T15:21:49-04:00",
"summary": "Thanks for writing this up. The standard is stable enough to be used daily but as you said, the features to make the apps (including Indigenous for iOS, which I am developing) excel are still in development. I\u2019ve been able to implement some of what you mentioned (mark posts as read/unread), but others are still on my list of things to tackle (sorting, filtering, etc). I think two things are needed to get where we need to be: 1) all Microsub developers need to use it daily (I\u2019m pretty sure we all do) and 2) People that try it out need to write blog posts just like this one so that we see where we need to improve and iterate.\nThanks for trying Microsub out. Hopefully it won\u2019t be too long before it supports the features you need! \ud83d\ude42",
"url": "https://eddiehinkle.com/2018/07/13/18/reply/",
"in-reply-to": [
"https://www.amitgawande.com/state-of-microsub/"
],
"content": {
"text": "Thanks for writing this up. The standard is stable enough to be used daily but as you said, the features to make the apps (including Indigenous for iOS, which I am developing) excel are still in development. I\u2019ve been able to implement some of what you mentioned (mark posts as read/unread), but others are still on my list of things to tackle (sorting, filtering, etc). I think two things are needed to get where we need to be: 1) all Microsub developers need to use it daily (I\u2019m pretty sure we all do) and 2) People that try it out need to write blog posts just like this one so that we see where we need to improve and iterate.\n\nThanks for trying Microsub out. Hopefully it won\u2019t be too long before it supports the features you need! \ud83d\ude42",
"html": "<p>Thanks for writing this up. The standard is stable enough to be used daily but as you said, the features to make the apps (including Indigenous for iOS, which I am developing) excel are still in development. I\u2019ve been able to implement some of what you mentioned (mark posts as read/unread), but others are still on my list of things to tackle (sorting, filtering, etc). I think two things are needed to get where we need to be: 1) all Microsub developers need to use it daily (I\u2019m pretty sure we all do) and 2) People that try it out need to write blog posts just like this one so that we see where we need to improve and iterate.</p>\n\n<p>Thanks for trying Microsub out. Hopefully it won\u2019t be too long before it supports the features you need! \ud83d\ude42</p>"
},
"author": {
"type": "card",
"name": "Eddie Hinkle",
"url": "https://eddiehinkle.com/",
"photo": "https://aperture-proxy.p3k.io/cc9591b69c2c835fa2c6e23745b224db4b4b431f/68747470733a2f2f656464696568696e6b6c652e636f6d2f696d616765732f70726f66696c652e6a7067"
},
"refs": {
"https://www.amitgawande.com/state-of-microsub/": {
"type": "entry",
"url": "https://www.amitgawande.com/state-of-microsub/",
"name": "https://www.amitgawande.com/state-of-microsub/"
}
},
"_id": "614970",
"_source": "226",
"_is_read": true
}
I tried very hard in that book, when it came to social media, to be platform agnostic, to emphasize that social media sites come and go, and to always invest first and foremost in your own media (website, blog, etc.) and mailing list.
I still stand by that advice, but if I re-wrote the book now, I would encourage artists to use much more caution when it comes to using social media websites like Facebook, Twitter, and Instagram.
{
"type": "entry",
"published": "2018-07-13T08:04:10Z",
"url": "https://adactio.com/links/14127",
"category": [
"indieweb",
"social",
"media",
"publishing",
"attention",
"publicity"
],
"bookmark-of": [
"https://austinkleon.com/2018/07/05/you-dont-have-to-live-in-public/"
],
"content": {
"text": "You don\u2019t have to live in public\n\n\n\n\n I tried very hard in that book, when it came to social media, to be platform agnostic, to emphasize that social media sites come and go, and to always invest first and foremost in your own media (website, blog, etc.) and mailing list.\n \n I still stand by that advice, but if I re-wrote the book now, I would encourage artists to use much more caution when it comes to using social media websites like Facebook, Twitter, and Instagram.",
"html": "<h3>\n<a class=\"p-name u-bookmark-of\" href=\"https://austinkleon.com/2018/07/05/you-dont-have-to-live-in-public/\">\nYou don\u2019t have to live in public\n</a>\n</h3>\n\n<blockquote>\n <p>I tried very hard in that book, when it came to social media, to be platform agnostic, to emphasize that social media sites come and go, and to always invest first and foremost in your own media (website, blog, etc.) and mailing list.</p>\n \n <p>I still stand by that advice, but if I re-wrote the book now, I would encourage artists to use much more caution when it comes to using social media websites like Facebook, Twitter, and Instagram.</p>\n</blockquote>"
},
"_id": "609580",
"_source": "2",
"_is_read": true
}
