@jgmac1106 A few short thoughts:
1. The explanatory text is nice, but runs a bit long for the uninitiated. I'm always worried that the length turns folks off? Perhaps something shorter for the gist of the idea with a link instead to a particular page that lays it out in more detail? I've also considered hiding some of the extra explanation behind a pop up or by using an abbr (or other appropriate html) tag with appropriate CSS hover markup so that when one hovers over a portion, they get a title-like window with all the gory details. Ideally, over time, with the spread of the concept the explanation won't be necessary at all.
2. One potentially crucial piece you're missing is that the post on their webpage HAS to have the permalink URL for your post on the page, otherwise the webmention will fail. Worse, without this bit of knowledge they won't know why it failed.
{
"type": "entry",
"published": "2018-05-19T15:55:05+00:00",
"url": "http://stream.boffosocko.com/2018/jgmac1106-a-few-short-thoughts1-the-explanatory-text-is-nice",
"syndication": [
"https://twitter.com/ChrisAldrich/status/997868257175638016"
],
"in-reply-to": [
"https://twitter.com/jgmac1106/status/997470649818939393",
"https://jgregorymcverry.com/hey-edtechchat-digiuri-literacies-digped-friends-i-need-your-help-can-you-read-this-and-then-define-webmention/"
],
"content": {
"text": "@jgmac1106 A few short thoughts:\n\n1. The explanatory text is nice, but runs a bit long for the uninitiated. I'm always worried that the length turns folks off? Perhaps something shorter for the gist of the idea with a link instead to a particular page that lays it out in more detail? I've also considered hiding some of the extra explanation behind a pop up or by using an abbr (or other appropriate html) tag with appropriate CSS hover markup so that when one hovers over a portion, they get a title-like window with all the gory details. Ideally, over time, with the spread of the concept the explanation won't be necessary at all.\n\n2. One potentially crucial piece you're missing is that the post on their webpage HAS to have the permalink URL for your post on the page, otherwise the webmention will fail. Worse, without this bit of knowledge they won't know why it failed.",
"html": "@jgmac1106 A few short thoughts:<br />\n1. The explanatory text is nice, but runs a bit long for the uninitiated. I'm always worried that the length turns folks off? Perhaps something shorter for the gist of the idea with a link instead to a particular page that lays it out in more detail? I've also considered hiding some of the extra explanation behind a pop up or by using an abbr (or other appropriate html) tag with appropriate CSS hover markup so that when one hovers over a portion, they get a title-like window with all the gory details. Ideally, over time, with the spread of the concept the explanation won't be necessary at all.<br />\n2. One potentially crucial piece you're missing is that the post on their webpage HAS to have the permalink URL for your post on the page, otherwise the webmention will fail. Worse, without this bit of knowledge they won't know why it failed.<br />"
},
"author": {
"type": "card",
"name": "Chris Aldrich",
"url": "http://stream.boffosocko.com/profile/chrisaldrich",
"photo": "https://aperture-media.p3k.io/stream.boffosocko.com/d0ba9f65fcbf0cef3bdbcccc0b6a1f42b1310f7ab2e07208c7a396166cde26b1.jpg"
},
"_id": "341118",
"_source": "192",
"_is_read": true
}
@jgmac1106 If you're as poor a theme tinkerer as I am but about to embark on adding microformats to a theme, I might recommend taking a look at the individual commit changes that David Shanske goes through in converting the base Twenty Sixteen Theme into a more IndieWeb friendly theme. The list of commits with useful labels can be found here: https://github.com/dshanske/twentysixteen-indieweb/commits/master Clicking on each of the changes will give you highlighted changes for what he did.
I would recommend starting at the bottom and then slowly reading your way to the top to try to understand what he's doing in each section. Note that there are one or two places where he splits a particular change up between a few commits or occasionally backtracks. There's also a section in which he "rips" out the WP core functionality of Post Formats in favor of using the Post Kinds Plugin--I'd recommend you don't do this to make your resultant theme the most flexible. I believe there's also a section in which he adds a "comment walker" and later removes it because the experimentaly functionality was later merged into the Webmentions/Semantic Linkbacks plugin to better handle comments, so you can safely ignore may of those chunks which are now stable.
I suspect that between this and the code models for SemPress and Independent Publisher (which should also have some David Shanske specific commits and related discussion that you can look up) you may be somewhat better off.
Good luck! We're all cheering for you!
{
"type": "entry",
"published": "2018-05-19T15:42:54+00:00",
"url": "http://stream.boffosocko.com/2018/jgmac1106-if-youre-as-poor-a-theme-tinkerer-as-i",
"syndication": [
"https://twitter.com/ChrisAldrich/status/997865235351506944"
],
"in-reply-to": [
"https://twitter.com/jgmac1106/status/997859786803867649",
"https://jgregorymcverry.com/end-goal-for-my-14-day-indieweb-wordpress-experiment"
],
"content": {
"text": "@jgmac1106 If you're as poor a theme tinkerer as I am but about to embark on adding microformats to a theme, I might recommend taking a look at the individual commit changes that David Shanske goes through in converting the base Twenty Sixteen Theme into a more IndieWeb friendly theme. The list of commits with useful labels can be found here: https://github.com/dshanske/twentysixteen-indieweb/commits/master Clicking on each of the changes will give you highlighted changes for what he did. \n\n\nI would recommend starting at the bottom and then slowly reading your way to the top to try to understand what he's doing in each section. Note that there are one or two places where he splits a particular change up between a few commits or occasionally backtracks. There's also a section in which he \"rips\" out the WP core functionality of Post Formats in favor of using the Post Kinds Plugin--I'd recommend you don't do this to make your resultant theme the most flexible. I believe there's also a section in which he adds a \"comment walker\" and later removes it because the experimentaly functionality was later merged into the Webmentions/Semantic Linkbacks plugin to better handle comments, so you can safely ignore may of those chunks which are now stable.\n\n\nI suspect that between this and the code models for SemPress and Independent Publisher (which should also have some David Shanske specific commits and related discussion that you can look up) you may be somewhat better off.\n\n\nGood luck! We're all cheering for you!",
"html": "@jgmac1106 If you're as poor a theme tinkerer as I am but about to embark on adding microformats to a theme, I might recommend taking a look at the individual commit changes that David Shanske goes through in converting the base Twenty Sixteen Theme into a more IndieWeb friendly theme. The list of commits with useful labels can be found here: <a href=\"https://github.com/dshanske/twentysixteen-indieweb/commits/master\">https://github.com/dshanske/twentysixteen-indieweb/commits/master</a> Clicking on each of the changes will give you highlighted changes for what he did. <br /><br />\nI would recommend starting at the bottom and then slowly reading your way to the top to try to understand what he's doing in each section. Note that there are one or two places where he splits a particular change up between a few commits or occasionally backtracks. There's also a section in which he \"rips\" out the WP core functionality of Post Formats in favor of using the Post Kinds Plugin--I'd recommend you don't do this to make your resultant theme the most flexible. I believe there's also a section in which he adds a \"comment walker\" and later removes it because the experimentaly functionality was later merged into the Webmentions/Semantic Linkbacks plugin to better handle comments, so you can safely ignore may of those chunks which are now stable.<br /><br />\nI suspect that between this and the code models for SemPress and Independent Publisher (which should also have some David Shanske specific commits and related discussion that you can look up) you may be somewhat better off.<br /><br />\nGood luck! We're all cheering for you!"
},
"author": {
"type": "card",
"name": "Chris Aldrich",
"url": "http://stream.boffosocko.com/profile/chrisaldrich",
"photo": "https://aperture-media.p3k.io/stream.boffosocko.com/d0ba9f65fcbf0cef3bdbcccc0b6a1f42b1310f7ab2e07208c7a396166cde26b1.jpg"
},
"_id": "341119",
"_source": "192",
"_is_read": true
}
Just FYI, I have some IndieAuth Swift classes in my Indigenous app. Eventually I want to turn them into a Swift library. However you are welcome to embed any of them in Icro that might help make login easier. Also, I’m happy to answer any questions you might have 🙂
{
"type": "entry",
"published": "2018-05-18T14:30:37-04:00",
"summary": "Just FYI, I have some IndieAuth Swift classes in my Indigenous app. Eventually I want to turn them into a Swift library. However you are welcome to embed any of them in Icro that might help make login easier. Also, I\u2019m happy to answer any questions you might have \ud83d\ude42",
"url": "https://eddiehinkle.com/2018/05/18/3/reply/",
"in-reply-to": [
"https://micro.blog/hartlco/570560"
],
"content": {
"text": "Just FYI, I have some IndieAuth Swift classes in my Indigenous app. Eventually I want to turn them into a Swift library. However you are welcome to embed any of them in Icro that might help make login easier. Also, I\u2019m happy to answer any questions you might have \ud83d\ude42",
"html": "<p>Just FYI, I have <a href=\"https://github.com/EdwardHinkle/indigenous-ios/tree/master/IndieAuth\">some IndieAuth Swift classes</a> in my Indigenous app. Eventually I want to turn them into a Swift library. However you are welcome to embed any of them in Icro that might help make login easier. Also, I\u2019m happy to answer any questions you might have \ud83d\ude42</p>"
},
"author": {
"type": "card",
"name": "Eddie Hinkle",
"url": "https://eddiehinkle.com/",
"photo": "https://aperture-media.p3k.io/eddiehinkle.com/cf9f85e26d4be531bc908d37f69bff1c50b50b87fd066b254f1332c3553df1a8.jpg"
},
"refs": {
"https://micro.blog/hartlco/570560": {
"type": "entry",
"url": "https://micro.blog/hartlco/570560",
"name": "https://micro.blog/hartlco/570560"
}
},
"_id": "338766",
"_source": "226",
"_is_read": true
}
@khurtwilliams @koolinus In case you'd like to see a comparison of the web we lost to the new #IndieWeb that we're building, this overview chart can be helpful: https://indieweb.org/lost_infrastructure
{
"type": "entry",
"published": "2018-05-18T16:55:21+00:00",
"url": "http://stream.boffosocko.com/2018/khurtwilliams-koolinus-in-case-youd-like-to-see-a-comparison",
"category": [
"IndieWeb"
],
"syndication": [
"https://twitter.com/ChrisAldrich/status/997521053193789440"
],
"in-reply-to": [
"https://twitter.com/khurtwilliams/status/997429855775084546",
"https://islandinthenet.com/web-lost/",
"https://koolinus.wordpress.com/2018/05/17/the-web-we-lost/"
],
"content": {
"text": "@khurtwilliams @koolinus In case you'd like to see a comparison of the web we lost to the new #IndieWeb that we're building, this overview chart can be helpful: https://indieweb.org/lost_infrastructure",
"html": "@khurtwilliams @koolinus In case you'd like to see a comparison of the web we lost to the new <a href=\"http://stream.boffosocko.com/tag/IndieWeb\" class=\"p-category\">#IndieWeb</a> that we're building, this overview chart can be helpful: <a href=\"https://indieweb.org/lost_infrastructure\">https://indieweb.org/lost_infrastructure</a>"
},
"author": {
"type": "card",
"name": "Chris Aldrich",
"url": "http://stream.boffosocko.com/profile/chrisaldrich",
"photo": "https://aperture-media.p3k.io/stream.boffosocko.com/d0ba9f65fcbf0cef3bdbcccc0b6a1f42b1310f7ab2e07208c7a396166cde26b1.jpg"
},
"_id": "338689",
"_source": "192",
"_is_read": true
}
{
"type": "entry",
"author": {
"name": "manton",
"url": "http://www.manton.org",
"photo": null
},
"url": "http://www.manton.org/2018/05/twitter-streaming-api-and-micro-blog.html",
"name": "Twitter streaming API and Micro.blog",
"content": {
"html": "<p>The writing has been on the wall <a href=\"https://www.manton.org/2018/05/twitter-executing-on-2012-vision.html\">for years</a>. Now that Twitter plans to move ahead with <a href=\"http://apps-of-a-feather.com/\">deprecating APIs</a> that apps like Twitterrific and Tweetbot use, it\u2019s even more clear that there\u2019s no overlap between Twitter\u2019s priorities for the API and what traditional clients need.</p>\n<p>When <a href=\"http://www.manton.org/2018/05/icro-1-0.html\">I wrote about Icro</a>, the first third-party app for Micro.blog, I said that I always want to encourage other developers building for Micro.blog. It\u2019s worth exploring how these Twitter API changes compare to Micro.blog and how we can improve.</p>\n<p>The streaming API is a big part of this. Twitter apps currently use the streaming API to deliver tweets in real-time without polling, or to notice when someone is @-mentioned so that a push notification can be delivered. Losing this API is especially frustrating because it means developers need to rewrite a bunch of code only to make their apps a little worse instead of better.</p>\n<p>Micro.blog doesn\u2019t actually have a streaming API yet. Micro.blog supports <a href=\"http://help.micro.blog/2018/api-overview/\">multiple APIs</a>, but no persistent connection. The new app Icro doesn\u2019t have push notifications, although the official Micro.blog app does. For a brand new app like Icro, it would be a lot for the developer to also run a server just to do push notifications.</p>\n<p>As I think about how we solve this, I remember a discussion in the Twitter developer community when the iPhone first got push notifications. It was an open question: should Twitter third-party developers run their own servers for push notifications, or should Twitter itself deliver push notifications on behalf of third-party apps? Obviously third-party developers have had to run their own servers.</p>\n<p>I think a goal for us with Micro.blog should be that third-party developers get access to the same basic tools that we use to build our own apps. Rate-limits should be the same for an app like Icro as they are for the official Micro.blog app, for example.</p>\n<p>With that in mind, I\u2019ve mentioned before that I\u2019d like to offer a push notification service for developers. iOS and Android developers could upload their push notification credentials from Apple and Google. Micro.blog would store them and deliver push notifications directly to third-party apps.</p>\n<p>This has a few pretty big advantages:</p>\n<ul><li>Third-party developers won\u2019t need to run their own servers. This levels the playing field so that any Micro.blog app, no matter how small, can offer basic features like notifications.</li>\n<li>Push notifications are more capable now than at their introduction in 2009. They can be used not just for an alert message but for silently sending data to an app in the background, such as when new posts have been added to someone\u2019s timeline.</li>\n<li>It\u2019s more efficient. Instead of keeping persistent connections open to Micro.blog servers, Apple and Google handle the persistent connections between devices and the cloud. Micro.blog can simply forward @-mentions to the clients that have requested them via Apple and Google infrastructure.</li>\n</ul><p>This is a little bit of extra work for Micro.blog, but Micro.blog is already doing similar processing when a reply comes through. For every reply to a blog post, Micro.blog checks if there is a Webmention endpoint so that it can forward that reply to an external site, such as one hosted on WordPress. Opening up push notifications feels like a natural extension to that.</p>\n<p>Some developers might not be comfortable outsourcing this to Micro.blog. That\u2019s fine. In particular I\u2019d like to hear any concerns over security or features where this approach would be too limited. (To be clear, we\u2019d offer this for free. Our business is blog hosting.)</p>\n<p>Back to the Twitter news. <a href=\"https://daringfireball.net/2018/05/the_end_of_third_party_twitter_clients\">John Gruber summed it up</a> this way:</p>\n<blockquote><p>\n Twitter isn\u2019t explicitly saying that they\u2019re shutting down third-party clients, but I don\u2019t know that it\u2019s feasible for them to exist if they don\u2019t have access to these APIs. It\u2019s like breaking up with someone by being a jerk to them rather than telling them you\u2019re breaking up.\n</p></blockquote>\n<p>That\u2019s a great analogy. Micro.blog is barely a year old, so there is plenty still to do, and there are parts of the API that aren\u2019t as mature yet as they will be. But I think we\u2019re transparent about what we\u2019re trying to do and how we can support developers. We\u2019re not going to be jerks about it.</p>\n<p>I\u2019m really excited by what I\u2019m seeing from the community. Icro is <a href=\"https://itunes.apple.com/us/app/icro/id1375296597?ls=1&mt=8\">in the App Store</a>. Slate is another iPhone app currently in beta. <a href=\"http://dialog.micro.blog/\">Dialog for Android</a> is in the Google Play Store as a public beta. And then there are all the apps following IndieWeb standards that are compatible with Micro.blog.</p>\n<p>WWDC is only a couple weeks away. We\u2019ll have a Micro.blog meetup on Tuesday (June 5th) at lunch. I\u2019d love to talk to developers at the meetup or anytime that week in San Jose to get feedback on how we should handle streaming and notifications.</p>",
"text": "The writing has been on the wall for years. Now that Twitter plans to move ahead with deprecating APIs that apps like Twitterrific and Tweetbot use, it\u2019s even more clear that there\u2019s no overlap between Twitter\u2019s priorities for the API and what traditional clients need.\nWhen I wrote about Icro, the first third-party app for Micro.blog, I said that I always want to encourage other developers building for Micro.blog. It\u2019s worth exploring how these Twitter API changes compare to Micro.blog and how we can improve.\nThe streaming API is a big part of this. Twitter apps currently use the streaming API to deliver tweets in real-time without polling, or to notice when someone is @-mentioned so that a push notification can be delivered. Losing this API is especially frustrating because it means developers need to rewrite a bunch of code only to make their apps a little worse instead of better.\nMicro.blog doesn\u2019t actually have a streaming API yet. Micro.blog supports multiple APIs, but no persistent connection. The new app Icro doesn\u2019t have push notifications, although the official Micro.blog app does. For a brand new app like Icro, it would be a lot for the developer to also run a server just to do push notifications.\nAs I think about how we solve this, I remember a discussion in the Twitter developer community when the iPhone first got push notifications. It was an open question: should Twitter third-party developers run their own servers for push notifications, or should Twitter itself deliver push notifications on behalf of third-party apps? Obviously third-party developers have had to run their own servers.\nI think a goal for us with Micro.blog should be that third-party developers get access to the same basic tools that we use to build our own apps. Rate-limits should be the same for an app like Icro as they are for the official Micro.blog app, for example.\nWith that in mind, I\u2019ve mentioned before that I\u2019d like to offer a push notification service for developers. iOS and Android developers could upload their push notification credentials from Apple and Google. Micro.blog would store them and deliver push notifications directly to third-party apps.\nThis has a few pretty big advantages:\nThird-party developers won\u2019t need to run their own servers. This levels the playing field so that any Micro.blog app, no matter how small, can offer basic features like notifications.\nPush notifications are more capable now than at their introduction in 2009. They can be used not just for an alert message but for silently sending data to an app in the background, such as when new posts have been added to someone\u2019s timeline.\nIt\u2019s more efficient. Instead of keeping persistent connections open to Micro.blog servers, Apple and Google handle the persistent connections between devices and the cloud. Micro.blog can simply forward @-mentions to the clients that have requested them via Apple and Google infrastructure.\nThis is a little bit of extra work for Micro.blog, but Micro.blog is already doing similar processing when a reply comes through. For every reply to a blog post, Micro.blog checks if there is a Webmention endpoint so that it can forward that reply to an external site, such as one hosted on WordPress. Opening up push notifications feels like a natural extension to that.\nSome developers might not be comfortable outsourcing this to Micro.blog. That\u2019s fine. In particular I\u2019d like to hear any concerns over security or features where this approach would be too limited. (To be clear, we\u2019d offer this for free. Our business is blog hosting.)\nBack to the Twitter news. John Gruber summed it up this way:\n\n Twitter isn\u2019t explicitly saying that they\u2019re shutting down third-party clients, but I don\u2019t know that it\u2019s feasible for them to exist if they don\u2019t have access to these APIs. It\u2019s like breaking up with someone by being a jerk to them rather than telling them you\u2019re breaking up.\n\nThat\u2019s a great analogy. Micro.blog is barely a year old, so there is plenty still to do, and there are parts of the API that aren\u2019t as mature yet as they will be. But I think we\u2019re transparent about what we\u2019re trying to do and how we can support developers. We\u2019re not going to be jerks about it.\nI\u2019m really excited by what I\u2019m seeing from the community. Icro is in the App Store. Slate is another iPhone app currently in beta. Dialog for Android is in the Google Play Store as a public beta. And then there are all the apps following IndieWeb standards that are compatible with Micro.blog.\nWWDC is only a couple weeks away. We\u2019ll have a Micro.blog meetup on Tuesday (June 5th) at lunch. I\u2019d love to talk to developers at the meetup or anytime that week in San Jose to get feedback on how we should handle streaming and notifications."
},
"published": "2018-05-18T15:42:42+00:00",
"updated": "2018-05-18T15:42:42+00:00",
"_id": "338672",
"_source": "12",
"_is_read": true
}
{
"type": "entry",
"author": {
"name": "Kh\u00fcrt Williams",
"url": "https://islandinthenet.com/",
"photo": null
},
"url": "https://islandinthenet.com/my-ban-on-eu-website-traffic-has-been-lifted/",
"published": "2018-05-17T22:08:40+00:00",
"content": {
"html": "<p><a href=\"https://islandinthenet.com/\">Island in the Net - A personal website by Kh\u00fcrt Williams, with imagery, and inchoate ramblings on coffee, beer, and geekery.</a></p>\nDue to concerns about my <strong>legal</strong> responsibilities around compliance the European Union General Data Protection Regulations, I configured my web application firewall (WAF) to block all traffic origination in EU member countries. While some people think this was an extreme move, a lack of clarity around what is expected of small website operators and that I operate an information technology related consultancy, left me feeling vulnerable. Until I could understand what/if I needed to do to comply with GDPR\u2019s \u201cright to be forgotten\u201d, I simply did not want the risk.\n<p>Today, I have removed the WAF rules that restrict traffic originating in the EU. <a href=\"https://automattic.com/\">Automattic</a>, the company behind WordPress.com and the supporters of WordPress.org, have updated/are <a href=\"https://automattic.com/privacy/\">updating</a> JetPack and other properties to comply with the GDPR. Currently, my self-hosted WordPress uses the Jetpack plug-in to handle things like comments and website traffic analysis. This moves some of the risks off to Automattic. They will be the data controller for information collected via comments and website analytics.</p>\n<p>Automattic has provided information on what <a href=\"https://jetpack.com/support/markdown/#privacy\">information JetPack collects for comments</a> and how that data is used. They have done the same for <a href=\"https://jetpack.com/support/wordpress-com-stats/#privacy\">website analytics</a>. Click on those links to find out more.</p>\n<p>I have added \u201cDo Not Track\u201d <a href=\"https://jetpack.com/support/wordpress-com-stats/#honoring-dnt\">code</a> to my WordPress config via JetPack. According to <a href=\"https://jetpack.com/support/wordpress-com-stats/#data-visibility-and-retention\">Automattic</a>.</p>\n<blockquote><p>\n Any piece of data explicitly identifying a specific user (IP address, WordPress.com ID, WordPress.com username, etc.) is not visible to the site owner when using this feature. For example, a site owner can see that a specific post has 285 views, but he/she cannot see which specific users/accounts viewed that post.</p>\n<p> Stats logs \u2014 containing visitor IP addresses and WordPress.com usernames (if available) \u2014 are retained by Automattic for 28 days and are used only for the purpose of powering this feature.\n</p></blockquote>\n<p>Comments on my blog will be restricted to what JetPack and Webmentions provide. I expect that JetPack comments will soon have the ability for commenters to delete comments, allowing compliance with GDPR requirements. I expect that people using Webmentions understand how they work and understand that they can delete a comment by sending another Webmention to do so.</p>\n<p>I do not intend to collect any information on visitors or commenters to this website other than what JetPacks collects.</p>\n<p>I am basing my decision to remove the WAF rules based on the changes that Automattic is making and also on guidance in this <a href=\"https://www.codeinwp.com/blog/complete-wordpress-gdpr-guide/\">codeinwp.blog</a> post.</p>\n<p>I guess what\u2019s really pissing me off is that although I live in the United States of American, some fucking European law can reach across the ocean and potentially affect me. That last European country that tried that shit ended up with causing the people to <a href=\"http://www.wikiwand.com/en/American_Revolution\">revolt</a>.</p>\n<img src=\"https://islandinthenet.com/wp-content/uploads/2018/05/Screen-Shot-2018-05-17-at-6.12.47-PM.jpg\" alt=\"My ban on EU website traffic has been lifted. Screen Shot 2018 05 17 at 6.12.47 PM\" title=\"My ban on EU website traffic has been lifted.\" />Geography of the visitors to Island in the Net.<p>The post <a href=\"https://islandinthenet.com/my-ban-on-eu-website-traffic-has-been-lifted/\">My ban on EU website traffic has been lifted.</a> by <a href=\"https://islandinthenet.com/\">Kh\u00fcrt Williams</a> appeared first on <a href=\"https://islandinthenet.com/\">Island in the Net</a>.</p>",
"text": "Island in the Net - A personal website by Kh\u00fcrt Williams, with imagery, and inchoate ramblings on coffee, beer, and geekery.\nDue to concerns about my legal responsibilities around compliance the European Union General Data Protection Regulations, I configured my web application firewall (WAF) to block all traffic origination in EU member countries. While some people think this was an extreme move, a lack of clarity around what is expected of small website operators and that I operate an information technology related consultancy, left me feeling vulnerable. Until I could understand what/if I needed to do to comply with GDPR\u2019s \u201cright to be forgotten\u201d, I simply did not want the risk.\nToday, I have removed the WAF rules that restrict traffic originating in the EU. Automattic, the company behind WordPress.com and the supporters of WordPress.org, have updated/are updating JetPack and other properties to comply with the GDPR. Currently, my self-hosted WordPress uses the Jetpack plug-in to handle things like comments and website traffic analysis. This moves some of the risks off to Automattic. They will be the data controller for information collected via comments and website analytics.\nAutomattic has provided information on what information JetPack collects for comments and how that data is used. They have done the same for website analytics. Click on those links to find out more.\nI have added \u201cDo Not Track\u201d code to my WordPress config via JetPack. According to Automattic.\n\n Any piece of data explicitly identifying a specific user (IP address, WordPress.com ID, WordPress.com username, etc.) is not visible to the site owner when using this feature. For example, a site owner can see that a specific post has 285 views, but he/she cannot see which specific users/accounts viewed that post.\n Stats logs \u2014 containing visitor IP addresses and WordPress.com usernames (if available) \u2014 are retained by Automattic for 28 days and are used only for the purpose of powering this feature.\n\nComments on my blog will be restricted to what JetPack and Webmentions provide. I expect that JetPack comments will soon have the ability for commenters to delete comments, allowing compliance with GDPR requirements. I expect that people using Webmentions understand how they work and understand that they can delete a comment by sending another Webmention to do so.\nI do not intend to collect any information on visitors or commenters to this website other than what JetPacks collects.\nI am basing my decision to remove the WAF rules based on the changes that Automattic is making and also on guidance in this codeinwp.blog post.\nI guess what\u2019s really pissing me off is that although I live in the United States of American, some fucking European law can reach across the ocean and potentially affect me. That last European country that tried that shit ended up with causing the people to revolt.\nGeography of the visitors to Island in the Net.The post My ban on EU website traffic has been lifted. by Kh\u00fcrt Williams appeared first on Island in the Net."
},
"name": "My ban on EU website traffic has been lifted.",
"_id": "335675",
"_source": "242",
"_is_read": true
}
It would be fun to have other folks in the community read the “standard” introductions for each section of This Week in the IndieWeb Audio Edition! I can take them in .wav for or .flac or anything that Audacity can open in a lossless way.
Regarding the webring: there has been no progress! I intended to circle back with Doug Beal about it but it was forgotten. I have been playing with glitch.com for several IndieWeb-related projects, recently, and that would be a fun one!
{
"type": "entry",
"published": "2018-05-17T17:47:02-04:00",
"url": "https://martymcgui.re/2018/05/17/174702/",
"in-reply-to": [
"https://david.shanske.com/2018/05/13/an-indieweb-podcast-episode-5-indieweb-summit-and-more/"
],
"content": {
"text": "It would be fun to have other folks in the community read the \u201cstandard\u201d introductions for each section of This Week in the IndieWeb Audio Edition! I can take them in .wav for or .flac or anything that Audacity can open in a lossless way.\nRegarding the webring: there has been no progress! I intended to circle back with Doug Beal about it but it was forgotten. I have been playing with glitch.com for several IndieWeb-related projects, recently, and that would be a fun one!",
"html": "<p>It would be fun to have other folks in the community read the \u201cstandard\u201d introductions for each section of This Week in the IndieWeb Audio Edition! I can take them in .wav for or .flac or anything that Audacity can open in a lossless way.</p>\n<p>Regarding the webring: there has been no progress! I intended to circle back with Doug Beal about it but it was forgotten. I have been playing with glitch.com for several IndieWeb-related projects, recently, and that would be a fun one!</p>"
},
"author": {
"type": "card",
"name": "Marty McGuire",
"url": "https://martymcgui.re/",
"photo": "https://aperture-media.p3k.io/martymcgui.re/4f9fac2b9e3ae62998c557418143efe288bca8170a119921a9c6bfeb0a1263a2.jpg"
},
"refs": {
"https://david.shanske.com/2018/05/13/an-indieweb-podcast-episode-5-indieweb-summit-and-more/": {
"type": "entry",
"published": "2018-05-13T21:27:59-04:00",
"summary": "With the Indieweb Summit coming up, we should discuss what the Summit is like, community and how to participate, etc. \u00a0 Links Do I know anyone interested in building #indieweb tech or federated services? I\u2019m having trouble conceptualizing some things without having people to bounce ideas off of. https://twitter.com/davidlaietta/status/995485455675162626 That\u2019s what this is all about! I have always been an...",
"url": "https://david.shanske.com/2018/05/13/an-indieweb-podcast-episode-5-indieweb-summit-and-more/",
"audio": [
"https://david.shanske.com/wp-content/uploads/2018/05/Indieweb5.mp3"
],
"name": "An Indieweb Podcast Episode 5: Indieweb Summit and More",
"author": {
"type": "card",
"name": "David Shanske",
"url": "https://david.shanske.com/",
"photo": "https://martymcgui.re/imageproxy/60,sskRXk4dDfMNcYrdZBToHRR_l5VTLWKah7OT4hVvtvNo=/https://secure.gravatar.com/avatar/681eba02e72ba1d894097034a8110e61?s=125&d=default&r=g"
}
}
},
"_id": "335664",
"_source": "175",
"_is_read": true
}
Testing post from Icro via Micropub.
{
"type": "entry",
"published": "2018-05-17T21:15:13+00:00",
"url": "https://cleverdevil.io/2018/testing-post-from-icro-via-micropub",
"content": {
"text": "Testing post from Icro via Micropub."
},
"author": {
"type": "card",
"name": "Jonathan LaCour",
"url": "https://cleverdevil.io/profile/cleverdevil",
"photo": "https://aperture-media.p3k.io/cleverdevil.io/abdf4969f052cb64177f73cda9be6a709931eb55607f8c1fb2c69eb135841acf.jpg"
},
"_id": "335654",
"_source": "71",
"_is_read": true
}
Hmm, looks like my new inline micropub browser extension is just about ready for testing! #indieweb
{
"type": "entry",
"published": "2018-05-17T01:58:47.356Z",
"url": "https://grant.codes/2018/05/17/5afce1d7310c2519f662a7b5",
"syndication": [
"https://twitter.com/grantcodes/status/996933018270003201",
"https://www.facebook.com/2238399679511169"
],
"content": {
"text": "Hmm, looks like my new inline micropub browser extension is just about ready for testing! #indieweb",
"html": "<p>Hmm, looks like my new inline micropub browser extension is just about ready for testing! #indieweb</p>"
},
"author": {
"type": "card",
"name": "Grant Richmond",
"url": "https://grant.codes",
"photo": "https://aperture-media.p3k.io/grant.codes/ca9d913e6e49b5ef5a5492313c9a7908cee0a33d0e188ea842a59c1968da2dd1.jpg"
},
"_id": "332530",
"_source": "11",
"_is_read": true
}
I most definitely want to start getting some Health data into my website! It’s tough because I want to do ALL of it, but it’s probably better to just do a couple at a time. Right now I want to definitely get sleep data. Activity Rings is also a great idea.
I kind of feel like Health should probably be its own app as to avoid Indigenous becoming EVERYTHING. Thankfully I’ve tried to keep the IndieWeb controllers separated from my Indigenous centric code to be able to do multiple apps easier and eventually push out some swift libraries to make Micropub apps easier for everyone on iOS. What would be your more important Health data?
{
"type": "entry",
"published": "2018-05-16T20:43:40-04:00",
"summary": "I most definitely want to start getting some Health data into my website! It\u2019s tough because I want to do ALL of it, but it\u2019s probably better to just do a couple at a time. Right now I want to definitely get sleep data. Activity Rings is also a great idea.\nI kind of feel like Health should probably be its own app as to avoid Indigenous becoming EVERYTHING. Thankfully I\u2019ve tried to keep the IndieWeb controllers separated from my Indigenous centric code to be able to do multiple apps easier and eventually push out some swift libraries to make Micropub apps easier for everyone on iOS. What would be your more important Health data?",
"url": "https://eddiehinkle.com/2018/05/16/18/reply/",
"in-reply-to": [
"https://micro.blog/cleverdevil/568267"
],
"content": {
"text": "I most definitely want to start getting some Health data into my website! It\u2019s tough because I want to do ALL of it, but it\u2019s probably better to just do a couple at a time. Right now I want to definitely get sleep data. Activity Rings is also a great idea.\n\nI kind of feel like Health should probably be its own app as to avoid Indigenous becoming EVERYTHING. Thankfully I\u2019ve tried to keep the IndieWeb controllers separated from my Indigenous centric code to be able to do multiple apps easier and eventually push out some swift libraries to make Micropub apps easier for everyone on iOS. What would be your more important Health data?",
"html": "<p>I most definitely want to start getting some Health data into my website! It\u2019s tough because I want to do ALL of it, but it\u2019s probably better to just do a couple at a time. Right now I want to definitely get sleep data. Activity Rings is also a great idea.</p>\n\n<p>I kind of feel like Health should probably be its own app as to avoid Indigenous becoming EVERYTHING. Thankfully I\u2019ve tried to keep the IndieWeb controllers separated from my Indigenous centric code to be able to do multiple apps easier and eventually push out some swift libraries to make Micropub apps easier for everyone on iOS. What would be your more important Health data?</p>"
},
"author": {
"type": "card",
"name": "Eddie Hinkle",
"url": "https://eddiehinkle.com/",
"photo": "https://aperture-media.p3k.io/eddiehinkle.com/cf9f85e26d4be531bc908d37f69bff1c50b50b87fd066b254f1332c3553df1a8.jpg"
},
"refs": {
"https://micro.blog/cleverdevil/568267": {
"type": "entry",
"url": "https://micro.blog/cleverdevil/568267",
"name": "https://micro.blog/cleverdevil/568267"
}
},
"_id": "332395",
"_source": "226",
"_is_read": true
}
This was a great episode. I don’t do much private stuff on my website, but I do a little. Sometimes there are location checkins or watch posts that are more for my own memories than things I want to share publicly. In those cases I have them use the Micropub visibility property. Technically all of my posts support that but I’ve mainly just used it with checkins and watch posts. Since not many Micropub clients support visibility I added a text shortcut that if I add to my post content it will add the visibility hidden inside my Micropub endpoint.
{
"type": "entry",
"published": "2018-05-16T15:00:04-04:00",
"summary": "This was a great episode. I don\u2019t do much private stuff on my website, but I do a little. Sometimes there are location checkins or watch posts that are more for my own memories than things I want to share publicly. In those cases I have them use the Micropub visibility property. Technically all of my posts support that but I\u2019ve mainly just used it with checkins and watch posts. Since not many Micropub clients support visibility I added a text shortcut that if I add to my post content it will add the visibility hidden inside my Micropub endpoint.",
"url": "https://eddiehinkle.com/2018/05/16/8/reply/",
"in-reply-to": [
"http://cleverca.st/2018/05/16/episode-more-than.html"
],
"content": {
"text": "This was a great episode. I don\u2019t do much private stuff on my website, but I do a little. Sometimes there are location checkins or watch posts that are more for my own memories than things I want to share publicly. In those cases I have them use the Micropub visibility property. Technically all of my posts support that but I\u2019ve mainly just used it with checkins and watch posts. Since not many Micropub clients support visibility I added a text shortcut that if I add to my post content it will add the visibility hidden inside my Micropub endpoint.",
"html": "<p>This was a great episode. I don\u2019t do much private stuff on my website, but I do a little. Sometimes there are location checkins or watch posts that are more for my own memories than things I want to share publicly. In those cases I have them use the Micropub visibility property. Technically all of my posts support that but I\u2019ve mainly just used it with checkins and watch posts. Since not many Micropub clients support visibility I added a text shortcut that if I add to my post content it will add the visibility hidden inside my Micropub endpoint.</p>"
},
"author": {
"type": "card",
"name": "Eddie Hinkle",
"url": "https://eddiehinkle.com/",
"photo": "https://aperture-media.p3k.io/eddiehinkle.com/cf9f85e26d4be531bc908d37f69bff1c50b50b87fd066b254f1332c3553df1a8.jpg"
},
"refs": {
"http://cleverca.st/2018/05/16/episode-more-than.html": {
"type": "entry",
"url": "http://cleverca.st/2018/05/16/episode-more-than.html",
"name": "http://cleverca.st/2018/05/16/episode-more-than.html"
}
},
"_id": "331909",
"_source": "226",
"_is_read": true
}
@dsample I suspect you're already aware, but for others who come along, some of these functionalities are relatively solid/stable plugins, which we all wish were in core, including https://wordpress.org/plugins/indieweb-post-kinds/
{
"type": "entry",
"published": "2018-05-16T16:36:26+00:00",
"url": "http://stream.boffosocko.com/2018/dsample-i-suspect-youre-already-aware-but-for-others-who",
"syndication": [
"https://twitter.com/ChrisAldrich/status/996791519393796102"
],
"in-reply-to": [
"https://twitter.com/dsample/status/996517800951865344"
],
"content": {
"text": "@dsample I suspect you're already aware, but for others who come along, some of these functionalities are relatively solid/stable plugins, which we all wish were in core, including https://wordpress.org/plugins/indieweb-post-kinds/",
"html": "<a href=\"https://twitter.com/dsample\">@dsample</a> I suspect you're already aware, but for others who come along, some of these functionalities are relatively solid/stable plugins, which we all wish were in core, including <a href=\"https://wordpress.org/plugins/indieweb-post-kinds/\">https://wordpress.org/plugins/indieweb-post-kinds/</a>"
},
"author": {
"type": "card",
"name": "Chris Aldrich",
"url": "http://stream.boffosocko.com/profile/chrisaldrich",
"photo": "https://aperture-media.p3k.io/stream.boffosocko.com/d0ba9f65fcbf0cef3bdbcccc0b6a1f42b1310f7ab2e07208c7a396166cde26b1.jpg"
},
"_id": "331107",
"_source": "192",
"_is_read": true
}
{
"type": "entry",
"author": {
"name": "Will Norris",
"url": "https://willnorris.com/",
"photo": null
},
"url": "http://willnorris.dev/2016/06/indieweb-demo",
"published": "2016-06-04T18:44:49+00:00",
"content": {
"html": "<p>Demoing my simple publishing workflow at IndieWeb Summit 2016.</p>",
"text": "Demoing my simple publishing workflow at IndieWeb Summit 2016."
},
"name": "IndieWeb Summit 2016 Demo",
"_id": "329439",
"_source": "248",
"_is_read": true
}
{
"type": "entry",
"author": {
"name": "Will Norris",
"url": "https://willnorris.com/",
"photo": null
},
"url": "http://willnorris.dev/2016/05/indieweb-summit",
"published": "2016-05-25T19:44:41+00:00",
"content": {
"html": "<img src=\"http://willnorris.dev/indiewebcamp-logo-lockup-color.svg\" alt=\"\" /><p>I\u2019ll be attending <a href=\"http://2016.indieweb.org/\">IndieWeb Summit</a> in Portland next week, probably working on the\n<a href=\"http://willnorris.dev/go/microformats\">go microformats library</a> which I started focusing on a few weeks ago as part of a\nwebmention service I\u2019ve been thinking about lately. As I\u2019ve been working on that library though,\nI\u2019ve found a few discrepancies between the different popular microformat libraries, so there\u2019s a\npretty good chance I\u2019ll spend at least a little time building a little service to compare the\nresults from those.</p>",
"text": "I\u2019ll be attending IndieWeb Summit in Portland next week, probably working on the\ngo microformats library which I started focusing on a few weeks ago as part of a\nwebmention service I\u2019ve been thinking about lately. As I\u2019ve been working on that library though,\nI\u2019ve found a few discrepancies between the different popular microformat libraries, so there\u2019s a\npretty good chance I\u2019ll spend at least a little time building a little service to compare the\nresults from those."
},
"name": "Attending IndieWeb Summit 2016",
"_id": "329440",
"_source": "248",
"_is_read": true
}
{
"type": "entry",
"author": {
"name": "Will Norris",
"url": "https://willnorris.com/",
"photo": null
},
"url": "http://willnorris.dev/2015/10/attending-indiewebcamp",
"published": "2015-10-23T16:28:15+00:00",
"content": {
"html": "<p>I\u2019m looking forward to attending <a href=\"https://kylewm.com/2015/12/indiewebcamp-sf-2015\">IndieWebCamp SF 2015</a> this year. I\u2019ve missed the last couple of events for\nvarious reasons, and really want to get back into things. I\u2019m thinking about maybe hacking on <a href=\"https://camlistore.org/\">Camlistore</a> a bit this year, perhaps doing some <a href=\"https://github.com/camlistore/camlistore/commits?author=willnorris\">more work</a> on\ndocumentation.</p>",
"text": "I\u2019m looking forward to attending IndieWebCamp SF 2015 this year. I\u2019ve missed the last couple of events for\nvarious reasons, and really want to get back into things. I\u2019m thinking about maybe hacking on Camlistore a bit this year, perhaps doing some more work on\ndocumentation."
},
"name": "Attending IndieWebCamp SF 2015",
"_id": "329443",
"_source": "248",
"_is_read": true
}
@benwerd Instead of Gutenberg, I'd have core support for the micropub spec and allow a free ecosystem for creating small user friendly custom apps for creating posts of all kinds.
{
"type": "entry",
"published": "2018-05-15T23:32:01+00:00",
"url": "http://stream.boffosocko.com/2018/benwerd-instead-of-gutenberg-id-have-core-support-for-the",
"syndication": [
"https://twitter.com/ChrisAldrich/status/996533706893545472"
],
"in-reply-to": [
"https://twitter.com/benwerd/status/996394932028899328"
],
"content": {
"text": "@benwerd Instead of Gutenberg, I'd have core support for the micropub spec and allow a free ecosystem for creating small user friendly custom apps for creating posts of all kinds.",
"html": "<a href=\"https://twitter.com/benwerd\">@benwerd</a> Instead of Gutenberg, I'd have core support for the micropub spec and allow a free ecosystem for creating small user friendly custom apps for creating posts of all kinds."
},
"author": {
"type": "card",
"name": "Chris Aldrich",
"url": "http://stream.boffosocko.com/profile/chrisaldrich",
"photo": "https://aperture-media.p3k.io/stream.boffosocko.com/d0ba9f65fcbf0cef3bdbcccc0b6a1f42b1310f7ab2e07208c7a396166cde26b1.jpg"
},
"_id": "328783",
"_source": "192",
"_is_read": true
}
If I write a post that is a reply to one of Manton’s posts on my site, and then I send a webmention, micro.blog takes that reply and inserts it into the timeline as a reply to Manton’s post.
{
"type": "entry",
"published": "2018-05-15T17:52:58-04:00",
"summary": "If I write a post that is a reply to one of Manton\u2019s posts on my site, and then I send a webmention, micro.blog takes that reply and inserts it into the timeline as a reply to Manton\u2019s post.",
"url": "https://eddiehinkle.com/2018/05/15/21/reply/",
"category": [
"microblog",
"indieweb",
"issue"
],
"in-reply-to": [
"https://github.com/microdotblog/issues"
],
"name": "Should receive webmentions for replies to externally posted replies",
"author": {
"type": "card",
"name": "Eddie Hinkle",
"url": "https://eddiehinkle.com/",
"photo": "https://aperture-media.p3k.io/eddiehinkle.com/cf9f85e26d4be531bc908d37f69bff1c50b50b87fd066b254f1332c3553df1a8.jpg"
},
"refs": {
"https://github.com/microdotblog/issues": {
"type": "entry",
"url": "https://github.com/microdotblog/issues",
"name": "https://github.com/microdotblog/issues"
}
},
"_id": "328407",
"_source": "226",
"_is_read": true
}
Yep, I have an “On This Day” feature of my website. My website is mostly Jekyll so it’s definitely possible with Jekyll, but if/when manton decided to implement it, it would probably be easiest to store the posts in some external system rather than integrating it with the actual Jekyll instance.
I think On This Day is a great feature. I really enjoy it. I actually wonder if there is some way to build an external service that could follow/parse a site and provide your posts back to you 🤔 Maybe something IndieWeb related that just parses mf2. We’d need to improve the mf2 on some of the m.b themes first though
{
"type": "entry",
"published": "2018-05-15T01:38:56-04:00",
"summary": "Yep, I have an \u201cOn This Day\u201d feature of my website. My website is mostly Jekyll so it\u2019s definitely possible with Jekyll, but if/when manton decided to implement it, it would probably be easiest to store the posts in some external system rather than integrating it with the actual Jekyll instance. I think On This Day is a great feature. I really enjoy it. I actually wonder if there is some way to build an external service that could follow/parse a site and provide your posts back to you \ud83e\udd14 Maybe something IndieWeb related that just parses mf2. We\u2019d need to improve the mf2 on some of the m.b themes first though",
"url": "https://eddiehinkle.com/2018/05/15/6/reply/",
"in-reply-to": [
"https://micro.blog/smokey/563066"
],
"content": {
"text": "Yep, I have an \u201cOn This Day\u201d feature of my website. My website is mostly Jekyll so it\u2019s definitely possible with Jekyll, but if/when manton decided to implement it, it would probably be easiest to store the posts in some external system rather than integrating it with the actual Jekyll instance.\nI think On This Day is a great feature. I really enjoy it. I actually wonder if there is some way to build an external service that could follow/parse a site and provide your posts back to you \ud83e\udd14 Maybe something IndieWeb related that just parses mf2. We\u2019d need to improve the mf2 on some of the m.b themes first though",
"html": "<p>Yep, I have an \u201cOn This Day\u201d feature of my website. My website is mostly Jekyll so it\u2019s definitely possible with Jekyll, but if/when manton decided to implement it, it would probably be easiest to store the posts in some external system rather than integrating it with the actual Jekyll instance.\nI think On This Day is a great feature. I really enjoy it. I actually wonder if there is some way to build an external service that could follow/parse a site and provide your posts back to you \ud83e\udd14 Maybe something IndieWeb related that just parses mf2. We\u2019d need to improve the mf2 on some of the m.b themes first though</p>"
},
"author": {
"type": "card",
"name": "Eddie Hinkle",
"url": "https://eddiehinkle.com/",
"photo": "https://aperture-media.p3k.io/eddiehinkle.com/cf9f85e26d4be531bc908d37f69bff1c50b50b87fd066b254f1332c3553df1a8.jpg"
},
"refs": {
"https://micro.blog/smokey/563066": {
"type": "entry",
"url": "https://micro.blog/smokey/563066",
"name": "https://micro.blog/smokey/563066"
}
},
"_id": "325813",
"_source": "226",
"_is_read": true
}
@fionajvoss Just for fun I built an own your own AMA page using webmention:
https://boffosocko.com/about/ama/
{
"type": "entry",
"published": "2018-05-15T04:45:13+00:00",
"url": "http://stream.boffosocko.com/2018/fionajvoss-just-for-fun-i-built-an-own-your-own",
"syndication": [
"https://twitter.com/ChrisAldrich/status/996250210228756480"
],
"in-reply-to": [
"https://twitter.com/fionajvoss/status/996203404404944897"
],
"content": {
"text": "@fionajvoss Just for fun I built an own your own AMA page using webmention: \nhttps://boffosocko.com/about/ama/",
"html": "<a href=\"https://twitter.com/fionajvoss\">@fionajvoss</a> Just for fun I built an own your own AMA page using webmention: <br /><a href=\"https://boffosocko.com/about/ama/\">https://boffosocko.com/about/ama/</a>"
},
"author": {
"type": "card",
"name": "Chris Aldrich",
"url": "http://stream.boffosocko.com/profile/chrisaldrich",
"photo": "https://aperture-media.p3k.io/stream.boffosocko.com/d0ba9f65fcbf0cef3bdbcccc0b6a1f42b1310f7ab2e07208c7a396166cde26b1.jpg"
},
"_id": "325695",
"_source": "192",
"_is_read": true
}
As we count down to #GDPR Christmas on the 25th May, @dsearls explains why you may need to rethink your entire approach to communicating with people. Talk to them. Assume they are human. Don't treat them as eyeballs attached to wallets. https://blogs.harvard.edu/doc/2018/05/12/gdpr/ #indieweb
{
"type": "entry",
"published": "2018-05-14T23:38:00+0000",
"url": "http://known.kevinmarks.com/2018/as-we-count-down-to-gdpr-christmas",
"category": [
"GDPR",
"indieweb"
],
"syndication": [
"https://twitter.com/kevinmarks/status/996172813068206086"
],
"content": {
"text": "As we count down to #GDPR Christmas on the 25th May, @dsearls explains why you may need to rethink your entire approach to communicating with people. Talk to them. Assume they are human. Don't treat them as eyeballs attached to wallets. https://blogs.harvard.edu/doc/2018/05/12/gdpr/ #indieweb",
"html": "As we count down to <a href=\"http://known.kevinmarks.com/tag/GDPR\" class=\"p-category\">#GDPR</a> Christmas on the 25th May, @dsearls explains why you may need to rethink your entire approach to communicating with people. Talk to them. Assume they are human. Don't treat them as eyeballs attached to wallets. <a href=\"https://blogs.harvard.edu/doc/2018/05/12/gdpr/\">https://blogs.harvard.edu/doc/2018/05/12/gdpr/</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-media.p3k.io/known.kevinmarks.com/f893d11435a62200ec9585e0ea3d84b2bdc478aa0a056dda35a43ce4c04d58a0.jpg"
},
"_id": "325370",
"_source": "205",
"_is_read": true
}
