While thinking about the similarities between Vero and Google Plus I also started considering those between Plus and micro.blog.
From the outset a big problem with Google Plus was the public perception of it. People didn't really understand it's scope seeing a particular aspect and assuming that was the extent of it. There was a "duality between its roles as a social network and social layer" which confused users.
As I've mentioned before, a similar duality exists within micro.blog in that it appears to be a social network when it is actually a networked collection of (micro)blogs. When you further add the complication of having both hosted and external blogs things can get a little convoluted.
When you consider replies in the timeline are really comments in response to blog posts, and these comments can be sent to external blogs using webmentions, it's role as a social layer is apparent but not necessarily obvious to the uninitiated.
A network providing a social layer is not actually anything unusual. Facebook have offered a comments box as part of their API for years and Plus followed suit in 2013. The difference with micro.blog, however, is that it isn't a "true" social network and, in webmentions, utilises something far more powerful and wide reaching but that most haven't heard of let alone understand.
{
"type": "entry",
"author": {
"name": "Colin Walker",
"url": "https://colinwalker.blog/",
"photo": null
},
"url": "https://colinwalker.blog/01-03-2018-1539/",
"published": "2018-03-01T15:39:35+00:00",
"content": {
"html": "<p>While thinking about the similarities between Vero and Google Plus I also started considering those between Plus and micro.blog.</p>\n<p>From the outset a big problem with Google Plus was the <a href=\"https://colinwalker.blog/the-problem-with-google/\">public perception</a> of it. People didn't really understand it's scope seeing a particular aspect and assuming that was the extent of it. There was a <em>\"duality between its roles as a social network and social layer\"</em> which confused users.</p>\n<p>As I've mentioned before, a similar duality exists within micro.blog in that it <em>appears</em> to be a social network when it is actually a networked collection of (micro)blogs. When you further add the complication of having both hosted and external blogs things can get a little convoluted.</p>\n<p>When you consider replies in the timeline are really comments in response to blog posts, and these comments can be sent to external blogs using webmentions, it's role as a social layer is apparent but not necessarily <em>obvious</em> to the uninitiated.</p>\n<p>A network providing a social layer is not actually anything unusual. Facebook have offered a comments box as part of their API for years and Plus followed suit in 2013. The difference with micro.blog, however, is that it isn't a \"true\" social network and, in webmentions, utilises something far more powerful and wide reaching but that most haven't heard of let alone understand.</p>",
"text": "While thinking about the similarities between Vero and Google Plus I also started considering those between Plus and micro.blog.\nFrom the outset a big problem with Google Plus was the public perception of it. People didn't really understand it's scope seeing a particular aspect and assuming that was the extent of it. There was a \"duality between its roles as a social network and social layer\" which confused users.\nAs I've mentioned before, a similar duality exists within micro.blog in that it appears to be a social network when it is actually a networked collection of (micro)blogs. When you further add the complication of having both hosted and external blogs things can get a little convoluted.\nWhen you consider replies in the timeline are really comments in response to blog posts, and these comments can be sent to external blogs using webmentions, it's role as a social layer is apparent but not necessarily obvious to the uninitiated.\nA network providing a social layer is not actually anything unusual. Facebook have offered a comments box as part of their API for years and Plus followed suit in 2013. The difference with micro.blog, however, is that it isn't a \"true\" social network and, in webmentions, utilises something far more powerful and wide reaching but that most haven't heard of let alone understand."
},
"_id": "124050",
"_source": "237",
"_is_read": true
}
{
"type": "entry",
"published": "2018-02-27T08:36:18+0000",
"url": "http://known.kevinmarks.com/2018/i-love-that-om-coined-quotmicro-pubsquot-in-2003-for-the",
"category": [
"micropub",
"indieweb"
],
"syndication": [
"https://twitter.com/kevinmarks/status/968404411226574848"
],
"content": {
"text": "I love that @om coined \u201cmicro-pubs\u201d in 2003 for the wave of professional media blogs, and now #micropub is the #indieweb standard for posting on your own small b blog https://om.co/2018/02/26/small-b-blogging-vs-big-b-blogging/",
"html": "I love that @om coined \u201cmicro-pubs\u201d in 2003 for the wave of professional media blogs, and now <a href=\"http://known.kevinmarks.com/tag/micropub\" class=\"p-category\">#micropub</a> is the <a href=\"http://known.kevinmarks.com/tag/indieweb\" class=\"p-category\">#indieweb</a> standard for posting on your own small b blog <a href=\"https://om.co/2018/02/26/small-b-blogging-vs-big-b-blogging/\">https://om.co/2018/02/26/small-b-blogging-vs-big-b-blogging/</a>"
},
"author": {
"type": "card",
"name": "Kevin Marks",
"url": "http://known.kevinmarks.com/profile/kevinmarks",
"photo": "http://known.kevinmarks.com/file/9255656669173b7867ab839ee6556f9e"
},
"_id": "100350",
"_source": "205",
"_is_read": true
}
“I think most people would be better served by subscribing to small b blogging. What you want is something with YOUR personality. Writing and ideas that are addressable (ie you can find and link to them easily in the future) and archived” http://tomcritchlow.com/2018/02/23/small-b-blogging/#indieweb via @om
{
"type": "entry",
"published": "2018-02-27T08:31:03+0000",
"url": "http://known.kevinmarks.com/2018/i-think-most-people-would-be-better-served-by-subscribing",
"category": [
"indieweb"
],
"syndication": [
"https://twitter.com/kevinmarks/status/968403091484585984"
],
"content": {
"text": "\u201cI think most people would be better served by subscribing to small b blogging. What you want is something with YOUR personality. Writing and ideas that are addressable (ie you can find and link to them easily in the future) and archived\u201d http://tomcritchlow.com/2018/02/23/small-b-blogging/ #indieweb via @om",
"html": "\u201cI think most people would be better served by subscribing to small b blogging. What you want is something with YOUR personality. Writing and ideas that are addressable (ie you can find and link to them easily in the future) and archived\u201d <a href=\"http://tomcritchlow.com/2018/02/23/small-b-blogging/\">http://tomcritchlow.com/2018/02/23/small-b-blogging/</a> <a href=\"http://known.kevinmarks.com/tag/indieweb\" class=\"p-category\">#indieweb</a> via @om"
},
"author": {
"type": "card",
"name": "Kevin Marks",
"url": "http://known.kevinmarks.com/profile/kevinmarks",
"photo": "http://known.kevinmarks.com/file/9255656669173b7867ab839ee6556f9e"
},
"_id": "100351",
"_source": "205",
"_is_read": true
}
Fun side effect of using https://granary.io and Aperture to follow conference hashtags is I end up with a private archive of all the tweets! #indieweb#microsub
{
"type": "entry",
"published": "2018-02-26T21:35:18-08:00",
"url": "https://aaronparecki.com/2018/02/26/51/",
"category": [
"indieweb",
"microsub"
],
"content": {
"text": "Fun side effect of using https://granary.io and Aperture to follow conference hashtags is I end up with a private archive of all the tweets! #indieweb #microsub",
"html": "Fun side effect of using <a href=\"https://granary.io\">https://granary.io</a> and Aperture to follow conference hashtags is I end up with a private archive of all the tweets! <a href=\"https://aaronparecki.com/tag/indieweb\">#indieweb</a> <a href=\"https://aaronparecki.com/tag/microsub\">#microsub</a>"
},
"author": {
"type": "card",
"name": "Aaron Parecki",
"url": "https://aaronparecki.com/",
"photo": "https://aaronparecki.com/images/profile.jpg"
},
"_id": "86141",
"_source": "16",
"_is_read": true
}
{
"type": "entry",
"published": "2018-02-26T17:13:02-05:00",
"url": "https://martymcgui.re/2018/02/26/171302/",
"category": [
"podcast",
"IndieWeb",
"this-week-indieweb-podcast"
],
"audio": [
"https://media.martymcgui.re/04/87/4a/eb/b89a6a9045ee1ef999ca795dc6d3e72f12370f1a6dbbf2b1b3dc9d3e.mp3"
],
"syndication": [
"https://huffduffer.com/schmarty/462419",
"https://twitter.com/schmarty/status/968248111670972417",
"https://www.facebook.com/marty.mcguire.54/posts/10211486972351926"
],
"name": "This Week in the IndieWeb Audio Edition \u2022 February 17th - 23rd, 2018",
"content": {
"text": "Show/Hide Transcript \n \n Audio edition for This Week in the IndieWeb for February 17th - 23rd, 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": "Show/Hide Transcript \n \n <p>Audio edition for <a href=\"https://indieweb.org/this-week/2018-02-23.html\">This Week in the IndieWeb for February 17th - 23rd, 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://martymcgui.re/images/logo.jpg"
},
"_id": "85982",
"_source": "175",
"_is_read": true
}
{
"type": "entry",
"published": "2018-02-25T17:44:27-0500",
"summary": "Hey, I\u2019ve done a lot with IndieAuth and Micropub. If you have any questions about how to do anything, feel free to reach out.",
"url": "https://eddiehinkle.com/2018/02/25/11/reply/",
"in-reply-to": [
"https://micro.blog/chrislopez/364556"
],
"content": {
"text": "Hey, I\u2019ve done a lot with IndieAuth and Micropub. If you have any questions about how to do anything, feel free to reach out.",
"html": "<p>Hey, I\u2019ve done a lot with IndieAuth and Micropub. If you have any questions about how to do anything, feel free to reach out.</p>"
},
"author": {
"type": "card",
"name": "Eddie Hinkle",
"url": "https://eddiehinkle.com/",
"photo": "https://eddiehinkle.com/images/profile.jpg"
},
"refs": {
"https://micro.blog/chrislopez/364556": {
"type": "entry",
"url": "https://micro.blog/chrislopez/364556",
"name": "https://micro.blog/chrislopez/364556"
}
},
"_id": "123265",
"_source": "226",
"_is_read": true
}
@scott_gruber@clivewalker Once you've gotten them working, don't forget to write a few documentation notes to help others who come along after you. Naturally on your own website first, and then perhaps to https://indieweb.org/Perch
{
"type": "entry",
"published": "2018-02-23T22:14:54+0000",
"url": "http://stream.boffosocko.com/2018/scott_gruber-clivewalker-once-youve-gotten-them-working-dont-forget-to",
"syndication": [
"https://twitter.com/ChrisAldrich/status/967160880713621504"
],
"in-reply-to": [
"https://twitter.com/scott_gruber/status/967064999276396544"
],
"content": {
"text": "@scott_gruber @clivewalker Once you've gotten them working, don't forget to write a few documentation notes to help others who come along after you. Naturally on your own website first, and then perhaps to https://indieweb.org/Perch",
"html": "<a href=\"https://twitter.com/scott_gruber\">@scott_gruber</a> <a href=\"https://twitter.com/clivewalker\">@clivewalker</a> Once you've gotten them working, don't forget to write a few documentation notes to help others who come along after you. Naturally on your own website first, and then perhaps to <a href=\"https://indieweb.org/Perch\">https://indieweb.org/Perch</a>"
},
"author": {
"type": "card",
"name": "Chris Aldrich",
"url": "http://stream.boffosocko.com/profile/chrisaldrich",
"photo": "http://stream.boffosocko.com/file/600427b81f7785e704eadfe511a9270f/thumb.jpg"
},
"_id": "99793",
"_source": "192",
"_is_read": true
}
@scott_gruber, sorry I didn't see this until this morning. Last night I had some issues connecting to the wifi for the first chunk of the meeting, so I didn't get the chance to document things into the chat as we went along.
It sounds to me like you got a lot of great things arranged and working on your site though! Congratulations on the Webmentions progress. That's awesome!!
{
"type": "entry",
"published": "2018-02-22T21:03:32+0000",
"url": "http://stream.boffosocko.com/2018/scott_gruber-sorry-i-didnt-see-this-until-this-morning-last",
"syndication": [
"https://twitter.com/ChrisAldrich/status/966780548344614912"
],
"in-reply-to": [
"https://twitter.com/scott_gruber/status/966586059399217153",
"https://scottgruber.me/blog/2018-02-21-homebrew-website-club-feb-21",
"http://boffosocko.com/2018/02/14/homebrew-website-club-meetup-on-february-21-2018/"
],
"content": {
"text": "@scott_gruber, sorry I didn't see this until this morning. Last night I had some issues connecting to the wifi for the first chunk of the meeting, so I didn't get the chance to document things into the chat as we went along.\n\n\nIt sounds to me like you got a lot of great things arranged and working on your site though! Congratulations on the Webmentions progress. That's awesome!!",
"html": "@scott_gruber, sorry I didn't see this until this morning. Last night I had some issues connecting to the wifi for the first chunk of the meeting, so I didn't get the chance to document things into the chat as we went along.<br /><br />\nIt sounds to me like you got a lot of great things arranged and working on your site though! Congratulations on the Webmentions progress. That's awesome!!"
},
"author": {
"type": "card",
"name": "Chris Aldrich",
"url": "http://stream.boffosocko.com/profile/chrisaldrich",
"photo": "http://stream.boffosocko.com/file/600427b81f7785e704eadfe511a9270f/thumb.jpg"
},
"_id": "99794",
"_source": "192",
"_is_read": true
}
Add support for destination configuration. From a UI perspective, posting to multiple micropub endpoint versus posting to a single micropub endpoint with multiple destinations should be the same.
https://github.com/indieweb/micropub-extensions/issues/3
The one part to think about is defaults. How should I default the destination? Should it be the first destination in the list or the last destination used? I currently allow someone to set a default Micropub Endpoint, but a default Destination is different. Maybe that’s the answer, maybe if they have more than one destination, I need to allow an option to choose a default destination on the micropub endpoint settings page.
{
"type": "entry",
"published": "2018-02-20T16:47:31-05:00",
"summary": "Add support for destination configuration. From a UI perspective, posting to multiple micropub endpoint versus posting to a single micropub endpoint with multiple destinations should be the same. \n\nhttps://github.com/indieweb/micropub-extensions/issues/3 \n\nThe one part to think about is defaults. How should I default the destination? Should it be the first destination in the list or the last destination used? I currently allow someone to set a default Micropub Endpoint, but a default Destination is different. Maybe that\u2019s the answer, maybe if they have more than one destination, I need to allow an option to choose a default destination on the micropub endpoint settings page.",
"url": "https://eddiehinkle.com/2018/02/20/12/reply/",
"category": [
"indieweb",
"indigenous"
],
"in-reply-to": [
"https://github.com/EdwardHinkle/indigenous-ios"
],
"name": "Add support for mp q=config destination",
"author": {
"type": "card",
"name": "Eddie Hinkle",
"url": "https://eddiehinkle.com",
"photo": null
},
"refs": {
"https://github.com/EdwardHinkle/indigenous-ios": {
"type": "entry",
"url": "https://github.com/EdwardHinkle/indigenous-ios",
"name": "https://github.com/EdwardHinkle/indigenous-ios"
}
},
"_id": "67356",
"_source": "39",
"_is_read": true
}
Just created a Lambda function that looks at my website's On This Day page, and publishes the memories to a special channel in my Microsub server. #IndieWeb#OwnYourMemories
{
"type": "entry",
"published": "2018-02-19T01:44:38+00:00",
"url": "https://cleverdevil.io/2018/just-created-a-lambda-function-that-looks",
"category": [
"IndieWeb",
"OwnYourMemories"
],
"syndication": [
"https://twitter.com/cleverdevil/status/965401712012951552"
],
"content": {
"text": "Just created a Lambda function that looks at my website's On This Day page, and publishes the memories to a special channel in my Microsub server. #IndieWeb #OwnYourMemories",
"html": "Just created a Lambda function that looks at my website's On This Day page, and publishes the memories to a special channel in my Microsub server. <a href=\"https://cleverdevil.io/tag/IndieWeb\" class=\"p-category\">#IndieWeb</a> <a href=\"https://cleverdevil.io/tag/OwnYourMemories\" class=\"p-category\">#OwnYourMemories</a>"
},
"author": {
"type": "card",
"name": "Jonathan LaCour",
"url": "https://cleverdevil.io/profile/cleverdevil",
"photo": "https://cleverdevil.io/file/fdbc7696a5f73864ea11a828c861e138/thumb.jpg"
},
"_id": "60711",
"_source": "71",
"_is_read": true
}
Maybe I’m weird, but it just feels good. It feels good to reclaim my turf. It feels good to have a spot to think out loud in public where people aren’t spitting and shitting all over the place.
{
"type": "entry",
"published": "2018-02-17T06:03:17Z",
"url": "https://adactio.com/links/13455",
"category": [
"indieweb",
"personal",
"publishing",
"blogging",
"writing",
"sharing",
"frequency",
"flow",
"stock"
],
"bookmark-of": [
"https://austinkleon.com/2017/11/20/a-few-notes-on-daily-blogging/"
],
"content": {
"text": "A few notes on daily blogging\n\n\n\n\n Maybe I\u2019m weird, but it just feels good. It feels good to reclaim my turf. It feels good to have a spot to think out loud in public where people aren\u2019t spitting and shitting all over the place.",
"html": "<h3>\n<a class=\"p-name u-bookmark-of\" href=\"https://austinkleon.com/2017/11/20/a-few-notes-on-daily-blogging/\">\nA few notes on daily blogging\n</a>\n</h3>\n\n<blockquote>\n <p>Maybe I\u2019m weird, but it just <em>feels</em> good. It feels good to reclaim my turf. It feels good to have a spot to think out loud in public where people aren\u2019t spitting and shitting all over the place.</p>\n</blockquote>"
},
"_id": "56356",
"_source": "2",
"_is_read": true
}
{
"type": "entry",
"published": "2018-02-17T01:28:35+00:00",
"url": "http://stream.boffosocko.com/2018/wimleers-google-drupal-timmillwood-i-remember-doing-an-indieweb-presentation",
"category": [
"IndieWeb",
"ownyourdata"
],
"syndication": [
"https://twitter.com/ChrisAldrich/status/964672909187969026"
],
"in-reply-to": [
"https://twitter.com/wimleers/status/964668303896662023"
],
"content": {
"text": "@wimleers @Google @drupal @timmillwood I remember doing an #IndieWeb presentation at DrupalCamp LA a couple of years ago right after a Piwik (@matomo_org) talk and it seemed like an interesting #ownyourdata solution at the time.\nhttps://www.drupal.org/project/piwik",
"html": "<a href=\"https://twitter.com/wimleers\">@wimleers</a> <a href=\"https://twitter.com/Google\">@Google</a> <a href=\"https://twitter.com/drupal\">@drupal</a> <a href=\"https://twitter.com/timmillwood\">@timmillwood</a> I remember doing an <a href=\"http://stream.boffosocko.com/tag/IndieWeb\" class=\"p-category\">#IndieWeb</a> presentation at DrupalCamp LA a couple of years ago right after a Piwik (@matomo_org) talk and it seemed like an interesting <a href=\"http://stream.boffosocko.com/tag/ownyourdata\" class=\"p-category\">#ownyourdata</a> solution at the time.<br /><a href=\"https://www.drupal.org/project/piwik\">https://www.drupal.org/project/piwik</a>"
},
"author": {
"type": "card",
"name": "Chris Aldrich",
"url": "http://stream.boffosocko.com/profile/chrisaldrich",
"photo": "http://stream.boffosocko.com/file/600427b81f7785e704eadfe511a9270f/thumb.jpg"
},
"_id": "99798",
"_source": "192",
"_is_read": true
}
@Dries How awesome would it be if I could use @buffer not only to post to social media, but to post to my own website using the Micropub spec? https://www.w3.org/TR/micropub/
{
"type": "entry",
"published": "2018-02-16T22:02:31+00:00",
"url": "http://stream.boffosocko.com/2018/dries-how-awesome-would-it-be-if-i-could-use",
"syndication": [
"https://twitter.com/ChrisAldrich/status/964621051304071168"
],
"in-reply-to": [
"https://twitter.com/Dries/status/964486539844685825",
"https://dri.es/my-posse-plan-for-evolving-my-site"
],
"content": {
"text": "@Dries How awesome would it be if I could use @buffer not only to post to social media, but to post to my own website using the Micropub spec? https://www.w3.org/TR/micropub/",
"html": "@Dries How awesome would it be if I could use @buffer not only to post to social media, but to post to my own website using the Micropub spec? <a href=\"https://www.w3.org/TR/micropub/\">https://www.w3.org/TR/micropub/</a>"
},
"author": {
"type": "card",
"name": "Chris Aldrich",
"url": "http://stream.boffosocko.com/profile/chrisaldrich",
"photo": "http://stream.boffosocko.com/file/600427b81f7785e704eadfe511a9270f/thumb.jpg"
},
"_id": "99799",
"_source": "192",
"_is_read": true
}
{
"type": "entry",
"published": "2018-02-16 11:09-0800",
"url": "https://gregorlove.com/2018/02/care-package/",
"photo": [
"https://gregorlove.com/site/assets/files/4947/img_20180214_150450.750x0-is.jpg"
],
"syndication": [
"https://twitter.com/gRegorLove/status/964579280939245568",
"https://www.facebook.com/gregorlove/posts/10103476988633974"
],
"name": "Care Package",
"content": {
"text": "I received this awesome Valentine\u2019s Day care package from a special new ...lady in my life. Her name is Hollie and as you can see, she appreciates puns and corny humor like me.\n\nHollie messaged me on OKCupid in October because, as she later told me, she \u201cwanted to talk to a cute California guy\u201d even though she lives in Maryland. The conversation was going well, but I don\u2019t think either of us expected much to come of it. In November I was helping my parents move across the country so I was taking longer to respond. She interpreted that as me not being interested and sent a \u201ctake care\u201d message. I wrote her back explaining the delay, but didn\u2019t hear anything back. I figured that was that. Apparently she didn\u2019t see that message until January, though, which is when she got back in touch. We started chatting more often and were hitting it off.\n\nCoincidentally, I was already going to be in Baltimore for IndieWebCamp, so I mentioned we could meet up. That same week we talked on the phone for the first time. We talked for two hours and I definitely had a good feeling about the two of us. Unfortunately she wasn\u2019t able to come into Baltimore to meet, but we both agreed we needed to meet eventually. That Saturday night in Baltimore I was thinking it over. If I was already willing to fly out again at some point to meet her, why not spend a little extra effort while I\u2019m already nearby? I suggested I could drive out to meet her Sunday night before my early return flight on Monday.\n\nWe met at a Barnes & Noble. I arrived on time and called her, but she didn\u2019t answer. Then I texted and waited a few minutes before calling again. Still no answer. That paranoid little voice in my head started wondering \u201cDid she chicken out on meeting me? Oh no, is she even real? Alright, where is Ashton Kutcher?\u201d To distract myself from the voices temporarily, I decided to browse some books. I didn\u2019t have to wait more than a few minutes, though, when she walked up to me. She was a very real lady, quite happy to see me, and gave me a good hug. No Ashton Kutcher was sighted.\n\nIt was totally worth it, which is probably obvious from the fact you are reading this post now. We clicked and felt comfortable with each other right away. It felt like we had known each other for a much longer time. We had some good conversation about relationships, long-distance, and our concerns. I made my interest clear, but didn\u2019t ask her that night. She was definitely interested, but had some hesitation. I did ask her to be my valentine that night, though, and she said yes. A few days later we discussed it some more and now we\u2019re dating!\n\nLikely To Be Asked Questions\n\nQ: Maryland? Isn\u2019t that pretty far away from San Diego?\n\nA: Yes, it is.\n\nQ: So, are you moving?\n\nA: Not anytime soon. This is among the things we discussed. She has wanted to move to California for a while (yes, before meeting me).\n\nQ: Where is a picture of you two?!\n\nA: Unfortunately we did not take one when we met. She\u2019s totally real, you guys! She goes to another school. You don\u2019t know her.",
"html": "<p></p>\n\n<p>I received this awesome Valentine\u2019s Day care package from a special new ...lady in my life. Her name is Hollie and as you can see, she appreciates puns and corny humor like me.</p>\n\n<p>Hollie messaged me on OKCupid in October because, as she later told me, she \u201cwanted to talk to a cute California guy\u201d even though she lives in Maryland. The conversation was going well, but I don\u2019t think either of us expected much to come of it. In November I was helping my parents move across the country so I was taking longer to respond. She interpreted that as me not being interested and sent a \u201ctake care\u201d message. I wrote her back explaining the delay, but didn\u2019t hear anything back. I figured that was that. Apparently she didn\u2019t see that message until January, though, which is when she got back in touch. We started chatting more often and were hitting it off.</p>\n\n<p>Coincidentally, I was already going to be in Baltimore for <a href=\"https://2018.indieweb.org/baltimore\">IndieWebCamp</a>, so I mentioned we could meet up. That same week we talked on the phone for the first time. We talked for two hours and I definitely had a good feeling about the two of us. Unfortunately she wasn\u2019t able to come into Baltimore to meet, but we both agreed we needed to meet eventually. That Saturday night in Baltimore I was thinking it over. If I was already willing to fly out again at some point to meet her, why not spend a little extra effort while I\u2019m already nearby? I suggested I could drive out to meet her Sunday night before my early return flight on Monday.</p>\n\n<p>We met at a Barnes & Noble. I arrived on time and called her, but she didn\u2019t answer. Then I texted and waited a few minutes before calling again. Still no answer. That paranoid little voice in my head started wondering \u201cDid she chicken out on meeting me? Oh no, is she even real? Alright, where is Ashton Kutcher?\u201d To distract myself from the voices temporarily, I decided to browse some books. I didn\u2019t have to wait more than a few minutes, though, when she walked up to me. She was a very real lady, quite happy to see me, and gave me a good hug. No Ashton Kutcher was sighted.</p>\n\n<p>It was totally worth it, which is probably obvious from the fact you are reading this post now. We clicked and felt comfortable with each other right away. It felt like we had known each other for a much longer time. We had some good conversation about relationships, long-distance, and our concerns. I made my interest clear, but didn\u2019t ask her that night. She was definitely interested, but had some hesitation. I did ask her to be my valentine that night, though, and she said yes. A few days later we discussed it some more and now we\u2019re dating!</p>\n\n<h2>Likely To Be Asked Questions</h2>\n\n<p>Q: Maryland? Isn\u2019t that pretty far away from San Diego?<br />\nA: Yes, it is.</p>\n\n<p>Q: So, are you moving?<br />\nA: Not anytime soon. This is among the things we discussed. She has wanted to move to California for a while (yes, before meeting me).</p>\n\n<p>Q: Where is a picture of you two?!<br />\nA: Unfortunately we did not take one when we met. She\u2019s totally real, you guys! She goes to another school. You don\u2019t know her.</p>"
},
"_id": "98982",
"_source": "179",
"_is_read": true
}
When Brid.gy sends webmentions for people invited via a Facebook POSSE copy, the webmentions for these people don't show up properly in comments because `semantic_linkbacks_type` is set to "invite" instead of "rsvp:invited".
{
"type": "entry",
"published": "2018-02-15T01:06:58+00:00",
"url": "http://stream.boffosocko.com/2018/rsvp-invited-issue-156-pfefferlewordpress-semantic-linkbacks-pfefferlewordpress-semantic-linkbacksissues156when-bridgy-sends-webmentions-for",
"content": {
"text": "RSVP invited \u00b7 Issue #156 \u00b7 pfefferle/wordpress-semantic-linkbacks https://github.com/pfefferle/wordpress-semantic-linkbacks/issues/156\n\n\nWhen Brid.gy sends webmentions for people invited via a Facebook POSSE copy, the webmentions for these people don't show up properly in comments because `semantic_linkbacks_type` is set to \"invite\" instead of \"rsvp:invited\".\n\n\nManually effecting the change in the database provides the expected display. See: http://boffosocko.com/2018/02/14/homebrew-website-club-meetup-on-february-21-2018/#Invited",
"html": "RSVP invited \u00b7 Issue #156 \u00b7 pfefferle/wordpress-semantic-linkbacks <a href=\"https://github.com/pfefferle/wordpress-semantic-linkbacks/issues/156\">https://github.com/pfefferle/wordpress-semantic-linkbacks/issues/156</a><br /><br />\nWhen Brid.gy sends webmentions for people invited via a Facebook POSSE copy, the webmentions for these people don't show up properly in comments because `semantic_linkbacks_type` is set to \"invite\" instead of \"rsvp:invited\".<br /><br />\nManually effecting the change in the database provides the expected display. See: <a href=\"http://boffosocko.com/2018/02/14/homebrew-website-club-meetup-on-february-21-2018/#Invited\">http://boffosocko.com/2018/02/14/homebrew-website-club-meetup-on-february-21-2018/#Invited</a>"
},
"author": {
"type": "card",
"name": "Chris Aldrich",
"url": "http://stream.boffosocko.com/profile/chrisaldrich",
"photo": "http://stream.boffosocko.com/file/600427b81f7785e704eadfe511a9270f/thumb.jpg"
},
"_id": "99802",
"_source": "192",
"_is_read": true
}
{
"type": "entry",
"published": "2018-02-15T00:28:53+00:00",
"url": "http://stream.boffosocko.com/2018/something-about-his-website-makes-me-think-that-weslinda-might",
"syndication": [
"https://twitter.com/ChrisAldrich/status/963933113578598401"
],
"content": {
"text": "Something about his website makes me think that @weslinda might appreciate Homebrew Website Club in Baltimore next week: https://indieweb.org/events/2018-02-20-homebrew-website-club",
"html": "Something about his website makes me think that @weslinda might appreciate Homebrew Website Club in Baltimore next week: <a href=\"https://indieweb.org/events/2018-02-20-homebrew-website-club\">https://indieweb.org/events/2018-02-20-homebrew-website-club</a>"
},
"author": {
"type": "card",
"name": "Chris Aldrich",
"url": "http://stream.boffosocko.com/profile/chrisaldrich",
"photo": "http://stream.boffosocko.com/file/600427b81f7785e704eadfe511a9270f/thumb.jpg"
},
"_id": "99803",
"_source": "192",
"_is_read": true
}
{
"type": "entry",
"published": "2018-02-14T21:45:32+0000",
"url": "https://notiz.blog/2018/02/14/openid-connect-federation/",
"name": "OpenID Connect Federation",
"content": {
"text": "Irgendwann letzte oder vorletzte Woche ist die \u00dcberschrift \"OpenID Connect Federation 1.0 \u2013 draft XX\" in meinem Feed-Reeder aufgetaucht und auf Buzz-Words wie Federation o. \u00c4. springe ich nat\u00fcrlich immer noch sofort auf!\n\nSpezifikationen lesen, macht ja generell nicht viel Spa\u00df, aber bei der OpenID Connect Federation 1.0 kam ich nicht mal bis zur H\u00e4lfte. Bevor man wirklich versteht was das Protokoll eigentlich macht (f\u00fcr mich h\u00f6rt es sich \u00e4hnlich an wie OpenID Connect Dynamic Client Registration), geht es um Metadaten, JSON Web Signature (JWS), JSON Web Tokens (JWT) und JSON Web Keys (JWK).\n\nEigentlich dachte ich, dass OpenID Connect durch OAuth 2 super simpel sein soll\u2026 Immerhin basiert ja OAuth 2 auf SSL/TLS und nicht wie OAuth 1 auf komplizierte Signaturen.\n\n\n The majority of failed OAuth 1.0 implementation attempts are caused by the complexity of the cryptographic requirements of the specification. The fact that the original specification was poorly written didn\u2019t help, but even with the newly published RFC 5849, OAuth 1.0 is still not trivial to use on the client side. The convenient and ease offered by simply using passwords is sorely missing in OAuth.\nEran Hammer\n\n\nDie OpenID Foundation scheint ihre Meinung ge\u00e4ndert zu haben\u2026 SSL scheint wohl doch nicht auszureichen.\n\n\n Another problem that has been raised is the dependency on TLS as the sole protection against attacks on the transferred information. These last couple of years a number of problems with OpenSSL, which is probably the most widely used TLS library, have been discovered that put reasonable doubt into this dependency.\nOpenID Connect Dynamic Client Registration\n\n\nSchade, schade\u2026\n\nWer eine wirkliche Alternative zu OpenID Connect sucht, der soll sich mal IndieAuth anschauen. IndieAuth kommt der urspr\u00fcnglichen Idee von OpenID Connect sehr nahe und ist relativ einfach zu verstehen und auch zu implementieren!",
"html": "<p>Irgendwann letzte oder vorletzte Woche ist die \u00dcberschrift \"OpenID Connect Federation 1.0 \u2013 draft XX\" in meinem Feed-Reeder aufgetaucht und auf Buzz-Words wie <strong>Federation</strong> o. \u00c4. springe ich nat\u00fcrlich immer noch sofort auf!</p>\n\n<p>Spezifikationen lesen, macht ja generell nicht viel Spa\u00df, aber bei der <em><a href=\"http://openid.net/specs/openid-connect-federation-1_0.html\"><strong>OpenID Connect Federation 1.0</strong></a></em> kam ich nicht mal bis zur H\u00e4lfte. Bevor man wirklich versteht was das Protokoll eigentlich macht (f\u00fcr mich h\u00f6rt es sich \u00e4hnlich an wie <a href=\"https://openid.net/specs/openid-connect-registration-1_0.html\"><strong>OpenID Connect Dynamic Client Registration</strong></a>), geht es um Metadaten, <a href=\"https://tools.ietf.org/html/rfc7515\">JSON Web Signature (JWS)</a>, JSON Web Tokens (JWT) und <a href=\"https://tools.ietf.org/html/rfc7517\">JSON Web Keys (JWK)</a>.</p>\n\n<p>Eigentlich dachte ich, dass <em>OpenID Connect</em> durch <em>OAuth 2</em> super simpel sein soll\u2026 Immerhin basiert ja <em>OAuth 2</em> auf SSL/TLS und nicht wie <em>OAuth 1</em> auf komplizierte Signaturen.</p>\n\n<blockquote>\n <p>The majority of failed OAuth 1.0 implementation attempts are caused by the complexity of the cryptographic requirements of the specification. The fact that the original specification was poorly written didn\u2019t help, but even with the newly published <a href=\"http://tools.ietf.org/html/rfc5849\">RFC 5849</a>, OAuth 1.0 is still not trivial to use on the client side. The convenient and ease offered by simply using passwords is sorely missing in OAuth.</p>\n<a href=\"https://hueniverse.com/introducing-oauth-2-0-b5681da60ce2\">Eran Hammer</a>\n</blockquote>\n\n<p>Die OpenID Foundation scheint ihre Meinung ge\u00e4ndert zu haben\u2026 SSL scheint wohl doch nicht auszureichen.</p>\n\n<blockquote>\n <p>Another problem that has been raised is the dependency on TLS as the sole protection against attacks on the transferred information. These last couple of years a number of problems with OpenSSL, which is probably the most widely used TLS library, have been discovered that put reasonable doubt into this dependency.</p>\n<a href=\"https://openid.net/specs/openid-connect-registration-1_0.html\">OpenID Connect Dynamic Client Registration</a>\n</blockquote>\n\n<p>Schade, schade\u2026</p>\n\n<p>Wer eine wirkliche Alternative zu <em>OpenID Connect</em> sucht, der soll sich mal <a href=\"https://www.w3.org/TR/indieauth/\"><strong>IndieAuth</strong></a> anschauen. <strong>IndieAuth</strong> kommt der urspr\u00fcnglichen Idee von <a href=\"https://web.archive.org/web/20100609191041/http://openidconnect.com:80/\"><em>OpenID Connect</em></a> sehr nahe und ist relativ einfach zu verstehen und auch zu implementieren!</p>"
},
"author": {
"type": "card",
"name": "Matthias Pfefferle",
"url": "https://notiz.blog/author/matthias-pfefferle/",
"photo": "https://secure.gravatar.com/avatar/75512bb584bbceae57dfc503692b16b2?s=40&d=mm&r=g"
},
"_id": "100357",
"_source": "206",
"_is_read": true
}