Episode 4: Webmentions and Privacy

{
    "type": "entry",
    "published": "2018-05-08T21:12:39-04:00",
    "url": "https://david.shanske.com/2018/05/08/an-indieweb-podcast-episode-4-webmentions-and-privacy/",
    "audio": [
        "https://aperture-media.p3k.io/david.shanske.com/3625f466be76942a27eb4d3047e7290f18b7503040ebc3ce65bdb65f9cd1a4a4.mp3"
    ],
    "name": "Episode 4: Webmentions and Privacy",
    "content": {
        "text": "This week, Chris Aldrich and I got together a bit late\u2026so I was a bit more quiet than normal.\nWith the GDPR regulations coming into effect in Europe May 25th, privacy seems to be on everyone\u2019s mind. This week, we tackle what webmentions are, using them for backfeed, and the privacy implications.\nThe Indieweb Privacy Challenge: https://sebastiangreger.net/2018/05/indieweb-privacy-challenge-webmentions-backfeeds-gdpr/\n\nWebmention Specification http://webmention.net\n\nRelated IndieWeb wiki pages\nPrinciples https://indieweb.org/principles\n\nWebmention https://indieweb.org/webmention\n\nPrivacy https://indieweb.org/privacy\n\nGDPR https://indieweb.org/GDPR\n\n\u00a0",
        "html": "This week, Chris Aldrich and I got together a bit late\u2026so I was a bit more quiet than normal.\n<p>With the GDPR regulations coming into effect in Europe May 25th, privacy seems to be on everyone\u2019s mind. This week, we tackle what webmentions are, using them for backfeed, and the privacy implications.</p>\n<ul><li>The Indieweb Privacy Challenge: <a href=\"https://sebastiangreger.net/2018/05/indieweb-privacy-challenge-webmentions-backfeeds-gdpr/\">https://sebastiangreger.net/2018/05/indieweb-privacy-challenge-webmentions-backfeeds-gdpr/</a>\n</li>\n<li>Webmention Specification <a href=\"http://webmention.net\">http://webmention.net</a>\n</li>\n</ul><p>Related IndieWeb wiki pages</p>\n<ul><li>Principles <a href=\"https://indieweb.org/principles\">https://indieweb.org/principles</a>\n</li>\n<li>Webmention <a href=\"https://indieweb.org/webmention\">https://indieweb.org/webmention</a>\n</li>\n<li>Privacy <a href=\"https://indieweb.org/privacy\">https://indieweb.org/privacy</a>\n</li>\n<li>GDPR <a href=\"https://indieweb.org/GDPR\">https://indieweb.org/GDPR</a>\n</li>\n</ul><p>\u00a0</p>"
    },
    "author": {
        "type": "card",
        "name": "David Shanske",
        "url": "https://david.shanske.com/",
        "photo": "https://aperture-media.p3k.io/secure.gravatar.com/ee1cea4a5d6465ac3bd8e56fc0bbfdacd25be40ef0968e6b2b2e8016103cb826.png"
    },
    "_id": "307364",
    "_source": "5",
    "_is_read": true
}

{
    "type": "entry",
    "published": "2018-05-09T00:03:03-04:00",
    "summary": "Something like this is possible even without webmention specific support. Essentially it could be done using microformats2 similar to how Events and RSVPs work over webmention. https://indieweb.org/rsvp",
    "url": "https://eddiehinkle.com/2018/05/09/1/reply/",
    "category": [
        "indieweb"
    ],
    "in-reply-to": [
        "https://mobile.twitter.com/jackyalcine/status/994043534025019393"
    ],
    "content": {
        "text": "Something like this is possible even without webmention specific support. Essentially it could be done using microformats2 similar to how Events and RSVPs work over webmention. https://indieweb.org/rsvp",
        "html": "<p>Something like this is possible even without webmention specific support. Essentially it could be done using microformats2 similar to how Events and RSVPs work over webmention. https://indieweb.org/rsvp</p>"
    },
    "author": {
        "type": "card",
        "name": "Eddie Hinkle",
        "url": "https://eddiehinkle.com/",
        "photo": "https://aperture-media.p3k.io/eddiehinkle.com/cf9f85e26d4be531bc908d37f69bff1c50b50b87fd066b254f1332c3553df1a8.jpg"
    },
    "refs": {
        "https://mobile.twitter.com/jackyalcine/status/994043534025019393": {
            "type": "entry",
            "url": "https://mobile.twitter.com/jackyalcine/status/994043534025019393",
            "name": "https://mobile.twitter.com/jackyalcine/status/994043534025019393"
        }
    },
    "_id": "306863",
    "_source": "226",
    "_is_read": true
}

{
    "type": "entry",
    "published": "2018-05-07 15:52-0700",
    "rsvp": "yes",
    "url": "https://gregorlove.com/2018/05/im-attending-indieweb-summit-2018/",
    "in-reply-to": [
        "https://2018.indieweb.org/"
    ],
    "content": {
        "text": "I\u2019m attending IndieWeb Summit 2018!",
        "html": "<p>I\u2019m attending IndieWeb Summit 2018!</p>"
    },
    "author": {
        "type": "card",
        "name": "gRegor Morrill",
        "url": "https://gregorlove.com/",
        "photo": "https://aperture-media.p3k.io/gregorlove.com/1dfe16005864a9fc9564a3884378cdc89abd66b173ed10bce2ac60ed782dab01.jpg"
    },
    "refs": {
        "https://2018.indieweb.org/": {
            "type": "entry",
            "url": "https://2018.indieweb.org/",
            "name": "https://2018.indieweb.org/"
        }
    },
    "_id": "302963",
    "_source": "95",
    "_is_read": true
}

{
    "type": "entry",
    "published": "2018-05-07T09:58:04-04:00",
    "summary": "What a great piece! I think it\u2019s an interesting challenge. The lack of \u201clikes\u201d and such do make the IndieWeb feel more lonely. And yet, when I DO receive real responses (thoughtful, text written responses), it provides a MUCH bigger social satisfaction then I received even from 50 likes.\nAs I started reading your post I thought \u201cwe need to do more to encourage likes on the IndieWeb\u201d, by the end I thought \u201cwe need to do more to help people seamlessly reply to others\u201d I think high quality engagement is the key to beating Facebook. Micro.blog has already provided me with much more substantive responses then I get from friends and family on Facebook.",
    "url": "https://eddiehinkle.com/2018/05/07/3/reply/",
    "in-reply-to": [
        "https://jamesshelley.com/2018/05/06/an-independent-web-that-is-more-social-than-social-media/"
    ],
    "content": {
        "text": "What a great piece! I think it\u2019s an interesting challenge. The lack of \u201clikes\u201d and such do make the IndieWeb feel more lonely. And yet, when I DO receive real responses (thoughtful, text written responses), it provides a MUCH bigger social satisfaction then I received even from 50 likes.\n\nAs I started reading your post I thought \u201cwe need to do more to encourage likes on the IndieWeb\u201d, by the end I thought \u201cwe need to do more to help people seamlessly reply to others\u201d I think high quality engagement is the key to beating Facebook. Micro.blog has already provided me with much more substantive responses then I get from friends and family on Facebook.",
        "html": "<p>What a great piece! I think it\u2019s an interesting challenge. The lack of \u201clikes\u201d and such do make the IndieWeb feel more lonely. And yet, when I DO receive real responses (thoughtful, text written responses), it provides a MUCH bigger social satisfaction then I received even from 50 likes.</p>\n\n<p>As I started reading your post I thought \u201cwe need to do more to encourage likes on the IndieWeb\u201d, by the end I thought \u201cwe need to do more to help people seamlessly reply to others\u201d I think high quality engagement is the key to beating Facebook. Micro.blog has already provided me with much more substantive responses then I get from friends and family on Facebook.</p>"
    },
    "author": {
        "type": "card",
        "name": "Eddie Hinkle",
        "url": "https://eddiehinkle.com/",
        "photo": "https://aperture-media.p3k.io/eddiehinkle.com/cf9f85e26d4be531bc908d37f69bff1c50b50b87fd066b254f1332c3553df1a8.jpg"
    },
    "refs": {
        "https://jamesshelley.com/2018/05/06/an-independent-web-that-is-more-social-than-social-media/": {
            "type": "entry",
            "url": "https://jamesshelley.com/2018/05/06/an-independent-web-that-is-more-social-than-social-media/",
            "name": "https://jamesshelley.com/2018/05/06/an-independent-web-that-is-more-social-than-social-media/"
        }
    },
    "_id": "301942",
    "_source": "226",
    "_is_read": true
}

Commenting

{
    "type": "entry",
    "author": {
        "name": "Kh\u00fcrt Williams",
        "url": "https://islandinthenet.com/",
        "photo": null
    },
    "url": "https://islandinthenet.com/commenting/",
    "published": "2018-05-07T15:14:45+00:00",
    "content": {
        "html": "Replied to <a href=\"https://jacky.wtf/weblog/comments-are-back/\">I Brought Back Commenting On My Site</a> by Jacky Alcin\u00e9<em> (jacky.wtf)</em><blockquote>As part of my mission to get my website to align with my digital identity, I\u2019ve opted to make use of Isso to handle commenting. I\u2019ve enabled it for every blog post and to each of the FAQ pages. This way, I can see that feedback and fold it back into the site a lot easier. I\u2019m a bit fortunate since I have my own infrastructure, I can just spin up this service easily.</blockquote><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>Concerned with some of the language in the EU GDPR, I removed commenting from my WordPress site but retained Webmentions. A newer webmention spec allows for deletion and or modification of webmentions which I feel aligns with the GDPR. I considered using Disqus for commenting I am loath to outsource my comments to a silo. Isso may be a solution that allows me to retain control while also allow commenters control over their comments.<p>The post <a href=\"https://islandinthenet.com/commenting/\">Commenting</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": "Replied to I Brought Back Commenting On My Site by Jacky Alcin\u00e9 (jacky.wtf)As part of my mission to get my website to align with my digital identity, I\u2019ve opted to make use of Isso to handle commenting. I\u2019ve enabled it for every blog post and to each of the FAQ pages. This way, I can see that feedback and fold it back into the site a lot easier. I\u2019m a bit fortunate since I have my own infrastructure, I can just spin up this service easily.Island in the Net - A personal website by Kh\u00fcrt Williams, with imagery, and inchoate ramblings on coffee, beer, and geekery.Concerned with some of the language in the EU GDPR, I removed commenting from my WordPress site but retained Webmentions. A newer webmention spec allows for deletion and or modification of webmentions which I feel aligns with the GDPR. I considered using Disqus for commenting I am loath to outsource my comments to a silo. Isso may be a solution that allows me to retain control while also allow commenters control over their comments.The post Commenting by Kh\u00fcrt Williams appeared first on Island in the Net."
    },
    "name": "Commenting",
    "_id": "301264",
    "_source": "242",
    "_is_read": true
}

{
    "type": "entry",
    "published": "2018-05-06 14:33-0700",
    "url": "https://gregorlove.com/2018/05/i-have-attempted-to-submit/",
    "syndication": [
        "https://feedly.uservoice.com/forums/192636-suggestions/suggestions/34171312-fix-whitespace-with-websub-notifications"
    ],
    "content": {
        "text": "I have attempted to submit this Feedly feedback on their Uservoice forum. In the past I have had issues with the feedback not appearing, so I am making a copy here. The syndication link below is the URL they provided, but is not publicly visible currently.\n\nWhen I send a WebSub notification (previously known as PubSubHubbub) for my Atom feed, the whitespace around links appears collapsed, so linked words run up against words around them. The feed is https://gregorlove.com/articles.atom. You can see this in Feedly with recent posts in my feed.\n\nFor this post, though (https://gregorlove.com/2017/05/ten-years-on/) I neglected to send a WebSub publish notification, so it appears Feedly did a regular poll of the feed and handled the whitespace correctly. It appears it's only for WebSub publish notifications that Feedly collapses the whitespace like this.",
        "html": "<p>I have attempted to submit this Feedly feedback on their Uservoice forum. In the past I have had issues with the feedback not appearing, so I am making a copy here. The syndication link below is the URL they provided, but is not publicly visible currently.\n</p>\n<p>When I send a WebSub notification (previously known as PubSubHubbub) for my Atom feed, the whitespace around links appears collapsed, so linked words run up against words around them. The feed is https://gregorlove.com/articles.atom. You can see this in Feedly with recent posts in my feed.\n</p>\n<p>For this post, though (https://gregorlove.com/2017/05/ten-years-on/) I neglected to send a WebSub publish notification, so it appears Feedly did a regular poll of the feed and handled the whitespace correctly. It appears it's only for WebSub publish notifications that Feedly collapses the whitespace like this.</p>"
    },
    "author": {
        "type": "card",
        "name": "gRegor Morrill",
        "url": "https://gregorlove.com/",
        "photo": "https://aperture-media.p3k.io/gregorlove.com/1dfe16005864a9fc9564a3884378cdc89abd66b173ed10bce2ac60ed782dab01.jpg"
    },
    "_id": "300197",
    "_source": "95",
    "_is_read": true
}

Webmention for ProcessWire Update

{
    "type": "entry",
    "published": "2018-05-06 12:28-0700",
    "url": "https://gregorlove.com/2018/05/webmention-for-processwire-update/",
    "syndication": [
        "https://news.indieweb.org/en",
        "https://twitter.com/gRegorLove/status/993243661365211136"
    ],
    "name": "Webmention for ProcessWire Update",
    "content": {
        "text": "Version 2.0.0 of the Webmention for ProcessWire module is released.\n\nWebmention is a web standard that enables conversations across the web, a powerful building block that is used for a growing federated network of comments, likes, reposts, and other rich interactions across the decentralized social web.\n\nWhen you link to a website, you can send it a Webmention to notify it. If it supports Webmentions, then that website may display your post as a comment, like, or other response, and presto, you\u2019re having a conversation from one site to another!\n\nUpdates in this version\n\nThis version now runs on ProcessWire version 3 as well as version 2! If you are running ProcessWire 3, you can install directly from the ProcessWire modules directory or by downloading this release. If you are running ProcessWire 2, you will need to download and install this release.\n\nNote that if you previously installed this module from the modules directory on a ProcessWire 2 site, you will need to use the link above to download and install this update. The modules directory is now only delivering the ProcessWire 3 version.\n\nUpdate to support ProcessWire 3.x\n\tUpdate php-mf2 library to version 0.4.x\n\tImprove verification of source linking to target\n\tFix delete webmention bug\n\tFix webmention author display in admin\n\tFix WebmentionList render() method\nProcessWire 2 Support\n\nThe modules directory is only delivering the ProcessWire 3 version currently because the majority of new ProcessWire installs should be version 3. However, I am not abandoning ProcessWire 2 support. I anticipate maintaining the ProcessWire 2 version of this module for at least the next year. I am still running ProcessWire 2 myself, so I\u2019m selfdogfooding it for the near future.\n\nFeedback and Development\n\nIf you\u2019re using this module, I\u2019d love to hear from you. Feel free to send webmentions to this post!\n\nIf you run into any bugs or have feedback, you can file an issue on GitHub, comment here, or contact me.\n\nThis module is open source and development takes place on GitHub. The ProcessWire 2 version is now in the master-pw2 branch. The ProcessWire 3 version is in the master branch.\n\nPreviously: Webmention for ProcessWire Update",
        "html": "<p>Version 2.0.0 of the <a href=\"https://modules.processwire.com/modules/webmention/\">Webmention for ProcessWire module</a> is released.</p>\n\n<p><a href=\"https://webmention.net\">Webmention</a> is a web standard that enables conversations across the web, a powerful building block that is used for a growing federated network of comments, likes, reposts, and other rich interactions across the decentralized social web.</p>\n\n<p>When you link to a website, you can send it a Webmention to notify it. If it supports Webmentions, then that website may display your post as a comment, like, or other response, and presto, you\u2019re having a conversation from one site to another!</p>\n\n<h2>Updates in this version</h2>\n\n<p>This version now runs on ProcessWire version 3 as well as version 2! If you are running ProcessWire 3, you can install directly from the <a href=\"https://modules.processwire.com/modules/webmention/\">ProcessWire modules directory</a> or by downloading <a href=\"https://github.com/gRegorLove/ProcessWire-Webmention/releases/tag/v2.0.0\">this release</a>. If you are running ProcessWire 2, you will need to download and install <a href=\"https://github.com/gRegorLove/ProcessWire-Webmention/releases/tag/v2.0.0-pw2\">this release</a>.</p>\n\n<p>Note that if you previously installed this module from the modules directory on a ProcessWire 2 site, you will need to use the link above to download and install this update. The modules directory is now only delivering the ProcessWire 3 version.</p>\n\n<ul><li>Update to support ProcessWire 3.x</li>\n\t<li>Update <a href=\"https://github.com/indieweb/php-mf2\">php-mf2</a> library to version 0.4.x</li>\n\t<li>Improve verification of source linking to target</li>\n\t<li>Fix delete webmention bug</li>\n\t<li>Fix webmention author display in admin</li>\n\t<li>Fix WebmentionList render() method</li>\n</ul><h2>ProcessWire 2 Support</h2>\n\n<p>The modules directory is only delivering the ProcessWire 3 version currently because the majority of <i>new</i> ProcessWire installs should be version 3. However, I am not abandoning ProcessWire 2 support. I anticipate maintaining the ProcessWire 2 version of this module for at least the next year. I am still running ProcessWire 2 myself, so I\u2019m <a href=\"https://indieweb.org/selfdogfood\">selfdogfooding</a> it for the near future.</p>\n\n<h2>Feedback and Development</h2>\n\n<p>If you\u2019re using this module, I\u2019d love to hear from you. Feel free to send webmentions to this post!</p>\n\n<p>If you run into any bugs or have feedback, you can <a href=\"https://github.com/gRegorLove/ProcessWire-Webmention/issues\">file an issue on GitHub</a>, comment here, or <a href=\"https://gregorlove.com/contact/\">contact me</a>.</p>\n\n<p>This module is open source and development takes place on GitHub. The ProcessWire 2 version is now in the <a href=\"https://github.com/gRegorLove/ProcessWire-Webmention/tree/master-pw2\">master-pw2</a> branch. The ProcessWire 3 version is in the <a href=\"https://github.com/gRegorLove/ProcessWire-Webmention/tree/master\">master</a> branch.</p>\n\n<p>Previously: <a href=\"https://gregorlove.com/2017/03/webmention-for-processwire-update/\">Webmention for ProcessWire Update</a></p>"
    },
    "_id": "299719",
    "_source": "179",
    "_is_read": true
}

Privacy

{
    "type": "entry",
    "published": "2018-05-06T11:58:42-04:00",
    "url": "https://david.shanske.com/2018/05/06/privacy/",
    "syndication": [
        "https://www.facebook.com/100002356503167/posts/1685521214869746",
        "https://twitter.com/dshanske/status/993158140043710467"
    ],
    "name": "Privacy",
    "content": {
        "text": "I admit to a certain amount of frustration on the subject of privacy lately. It seems, in all aspects of my life, both personal and professional, the new data privacy regulations that the EU rolls out May 25th are a theme in every discussion.\nI don\u2019t live in the EU, and I know that the European view on privacy is very different than the American one. Anything I say below is my opinion.\nI am also an archivist and librarian by education, if not by profession. We learn about the past by reading the materials of the day. The fact that email is so easy to keep and delete makes things difficult for us to archive for the future. Does the right to privacy mean we lose the ability to look back, because we don\u2019t want to remember?\nHistorical concerns aside, let\u2019s think about today. In the majority of states in the US, only one party partipating in a phone call is required to record a conversation and even post it. Privacy is very lopsided. There is no such thing as absolute privacy.\nFor me, keeping a copy of communications I was a party to is perfectly acceptable. My website is where I keep my copy. It is not covered by privacy regulations. I have no business agenda there. I will not sell your data or use it for anything else but archiving that conversation.\nThe thorny issue is whether or not I have the right to display that information publicly. This is because I am, in some cases, copying that data from another service. For example, Twitter or Facebook. Those services got permission to store that information and you have the right to manage it. But you may not know that I have copied it to ask me to remove the public display of your image.\nBut how is that different than someone creating a screenshot of the post? Which was public information at the time?\nAs a private individual, I think it is mandatory that I post a policy about what I do. And that I will hide or remove information on request. As a developer of Indieweb tools, I think I should give people the option to not store information if they so choose.\nSo, I am going to build the tools for people to not collect data. I am going to stop what I am working on and do some of this right now. But I still will. I am going to try to better secure that data. I am going to be clearer about it. That is the lesson I can take away from this and should. That we need to think about privacy impact.\nI hope those who are more concerned about this tell me through my site they don\u2019t want me to share our public conversations that they were happy to put in a public forum. I will then restrict them to my eyes only.\nIn Indieweb terms, I support webmention deletion. If the original source changes and you send a webmention, my site should remove or update my copy.\nDisclosure: Your responses to this may be captured for archival purposes. Please advise me if there is an issue.\n\u00a0",
        "html": "I admit to a certain amount of frustration on the subject of privacy lately. It seems, in all aspects of my life, both personal and professional, the new data privacy regulations that the EU rolls out May 25th are a theme in every discussion.\n<p>I don\u2019t live in the EU, and I know that the European view on privacy is very different than the American one. Anything I say below is my opinion.</p>\n<p>I am also an archivist and librarian by education, if not by profession. We learn about the past by reading the materials of the day. The fact that email is so easy to keep and delete makes things difficult for us to archive for the future. Does the right to privacy mean we lose the ability to look back, because we don\u2019t want to remember?</p>\n<p>Historical concerns aside, let\u2019s think about today. In the majority of states in the US, only one party partipating in a phone call is required to record a conversation and even post it. Privacy is very lopsided. There is no such thing as absolute privacy.</p>\n<p>For me, keeping a copy of communications I was a party to is perfectly acceptable. My website is where I keep my copy. It is not covered by privacy regulations. I have no business agenda there. I will not sell your data or use it for anything else but archiving that conversation.</p>\n<p>The thorny issue is whether or not I have the right to display that information publicly. This is because I am, in some cases, copying that data from another service. For example, Twitter or Facebook. Those services got permission to store that information and you have the right to manage it. But you may not know that I have copied it to ask me to remove the public display of your image.</p>\n<p>But how is that different than someone creating a screenshot of the post? Which was public information at the time?</p>\n<p>As a private individual, I think it is mandatory that I post a policy about what I do. And that I will hide or remove information on request. As a developer of Indieweb tools, I think I should give people the option to not store information if they so choose.</p>\n<p>So, I am going to build the tools for people to not collect data. I am going to stop what I am working on and do some of this right now. But I still will. I am going to try to better secure that data. I am going to be clearer about it. That is the lesson I can take away from this and should. That we need to think about privacy impact.</p>\n<p>I hope those who are more concerned about this tell me through my site they don\u2019t want me to share our public conversations that they were happy to put in a public forum. I will then restrict them to my eyes only.</p>\n<p>In Indieweb terms, I support webmention deletion. If the original source changes and you send a webmention, my site should remove or update my copy.</p>\n<p>Disclosure: Your responses to this may be captured for archival purposes. Please advise me if there is an issue.</p>\n<p>\u00a0</p>"
    },
    "author": {
        "type": "card",
        "name": "David Shanske",
        "url": "https://david.shanske.com/",
        "photo": "https://aperture-media.p3k.io/secure.gravatar.com/ee1cea4a5d6465ac3bd8e56fc0bbfdacd25be40ef0968e6b2b2e8016103cb826.png"
    },
    "_id": "299670",
    "_source": "5",
    "_is_read": true
}

{
    "type": "entry",
    "published": "2018-05-03T01:09:58-04:00",
    "url": "https://david.shanske.com/2018/05/03/1905/",
    "in-reply-to": [
        "https://sebastiangreger.net/2018/05/indieweb-privacy-challenge-webmentions-backfeeds-gdpr/"
    ],
    "content": {
        "text": "I have been thinking about this issue a lot. GDPR seems to be everywhere, and I\u2019m not sure that storing information on interactions is a privacy issue, but I want to respect people\u2019s concerns. GDPR or not, I do not think this is a use case the law intended to prevent.\nYou use the WordPress suite of plugins. And being as I\u2019m as regular contributor, there are a few ideas I\u2019ve floating that I think are a good start, and invite you to contribute more.\nAdd text to the Webmention form that explains how to use it to delete a mention. Since the form can be used without supporting webmentions on your own site, this is something that should be made clear.\nAdd Setting to not display avatar/photo\nAdd ability to edit mentions, to correct inaccurate data.\nAdd setting to store more/less data.\nAdd privacy policy to plugin for those who install it and add text/link to webmention form.\nExplain how to request a takedown of information.\nPeriodically poll/refresh sources.\nAllow a different level of processing for \u2018native\u2019 webmentions vs backfeed run through a service like Bridgy.\nThis doesn\u2019t solve all of the problems necessarily, but I think these ideas are a good faith effort in that direction.\n\u00a0",
        "html": "I have been thinking about this issue a lot. GDPR seems to be everywhere, and I\u2019m not sure that storing information on interactions is a privacy issue, but I want to respect people\u2019s concerns. GDPR or not, I do not think this is a use case the law intended to prevent.\n<p>You use the WordPress suite of plugins. And being as I\u2019m as regular contributor, there are a few ideas I\u2019ve floating that I think are a good start, and invite you to contribute more.</p>\n<ol><li>Add text to the Webmention form that explains how to use it to delete a mention. Since the form can be used without supporting webmentions on your own site, this is something that should be made clear.</li>\n<li>Add Setting to not display avatar/photo</li>\n<li>Add ability to edit mentions, to correct inaccurate data.</li>\n<li>Add setting to store more/less data.</li>\n<li>Add privacy policy to plugin for those who install it and add text/link to webmention form.</li>\n<li>Explain how to request a takedown of information.</li>\n<li>Periodically poll/refresh sources.</li>\n<li>Allow a different level of processing for \u2018native\u2019 webmentions vs backfeed run through a service like Bridgy.</li>\n</ol><p>This doesn\u2019t solve all of the problems necessarily, but I think these ideas are a good faith effort in that direction.</p>\n<p>\u00a0</p>"
    },
    "author": {
        "type": "card",
        "name": "David Shanske",
        "url": "https://david.shanske.com/",
        "photo": "https://aperture-media.p3k.io/secure.gravatar.com/ee1cea4a5d6465ac3bd8e56fc0bbfdacd25be40ef0968e6b2b2e8016103cb826.png"
    },
    "refs": {
        "https://sebastiangreger.net/2018/05/indieweb-privacy-challenge-webmentions-backfeeds-gdpr/": {
            "type": "entry",
            "url": "https://sebastiangreger.net/2018/05/indieweb-privacy-challenge-webmentions-backfeeds-gdpr/",
            "name": "The Indieweb privacy challenge (Webmentions, silo backfeeds, and the GDPR)",
            "author": {
                "type": "card",
                "name": "Sebastian Greger",
                "url": false,
                "photo": null
            }
        }
    },
    "_id": "299671",
    "_source": "5",
    "_is_read": true
}

Growing the IndieWeb

{
    "type": "entry",
    "author": {
        "name": "Kh\u00fcrt Williams",
        "url": "https://islandinthenet.com/",
        "photo": null
    },
    "url": "https://islandinthenet.com/growing-the-indieweb/",
    "published": "2018-05-06T21:07: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>  Replied to <a href=\"http://fogknife.com/2018-05-04-i-believe-in-the-indieweb-it-needs-to-believe-in-itself.html\">I believe in the IndieWeb. It needs to believe in itself.</a> by Jason McIntosh<em> (Fogknife)</em><blockquote>I call upon IndieWeb to get organized. I want to see at least one real non-profit organization formed out of it. I fully believe that IndieWeb already has, through its years of published hard work, the ability to attract and build a diverse board of highly influential directors who care about the web\u2019s future. From there, it could bring the attention and material resources that IndieWeb not only requires but has long deserved in order to start really reshaping the web at large, letting its ideas at last reach outside the rinky-dink hobby-sphere that currently confines it.</blockquote>What\u2019s next? How do we grow the IndieWeb?<p>The post <a href=\"https://islandinthenet.com/growing-the-indieweb/\">Growing the IndieWeb</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.  Replied to I believe in the IndieWeb. It needs to believe in itself. by Jason McIntosh (Fogknife)I call upon IndieWeb to get organized. I want to see at least one real non-profit organization formed out of it. I fully believe that IndieWeb already has, through its years of published hard work, the ability to attract and build a diverse board of highly influential directors who care about the web\u2019s future. From there, it could bring the attention and material resources that IndieWeb not only requires but has long deserved in order to start really reshaping the web at large, letting its ideas at last reach outside the rinky-dink hobby-sphere that currently confines it.What\u2019s next? How do we grow the IndieWeb?The post Growing the IndieWeb by Kh\u00fcrt Williams appeared first on Island in the Net."
    },
    "name": "Growing the IndieWeb",
    "_id": "299550",
    "_source": "242",
    "_is_read": true
}

Homebrew Website Club Baltimore

{
    "type": "event",
    "name": "Homebrew Website Club Baltimore",
    "published": "2018-05-06T15:26:14-04:00",
    "start": "2018-05-15 19:30-0400",
    "url": "https://martymcgui.re/2018/05/06/152614/",
    "category": [
        "event",
        "HWC",
        "IWC",
        "IndieWeb",
        "HWCBaltimore"
    ],
    "location": [
        "https://martymcgui.re/venues/digital-harbor-foundation-tech-center/"
    ],
    "refs": {
        "https://martymcgui.re/venues/digital-harbor-foundation-tech-center/": {
            "type": "card",
            "name": "Digital Harbor Foundation Tech Center",
            "url": "https://martymcgui.re/venues/digital-harbor-foundation-tech-center/",
            "photo": null
        }
    },
    "_id": "299354",
    "_source": "175",
    "_is_read": true
}

This Week in the IndieWeb Audio Edition • April 28th - May 4th, 2018

{
    "type": "entry",
    "published": "2018-05-06T13:48:16-04:00",
    "url": "https://martymcgui.re/2018/05/06/134816/",
    "category": [
        "podcast",
        "IndieWeb",
        "this-week-indieweb-podcast"
    ],
    "audio": [
        "https://aperture-media.p3k.io/media.martymcgui.re/9692de35a453b9281ce72fb46d99edf5712b2217bca0f9615c8862ef4c43fd54.mp3"
    ],
    "syndication": [
        "https://huffduffer.com/schmarty/475505",
        "https://twitter.com/schmarty/status/993186680264896512",
        "https://www.facebook.com/marty.mcguire.54/posts/10211985605817451"
    ],
    "name": "This Week in the IndieWeb Audio Edition \u2022 April 28th - May 4th, 2018",
    "content": {
        "text": "Show/Hide Transcript  \n            \n            Syndication setbacks, WordPress wisdom, and GDPR wrangling. It\u2019s the audio edition for This Week in the IndieWeb for April 29th - May 5th, 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>Syndication setbacks, WordPress wisdom, and GDPR wrangling. It\u2019s the audio edition for <a href=\"https://indieweb.org/this-week/2018-05-04.html\">This Week in the IndieWeb for April 29th - May 5th, 2018</a>.</p>\n\n<p>You can find all of my audio editions and subscribe with your favorite podcast app here: <a href=\"https://martymcgui.re/podcasts/indieweb/\">martymcgui.re/podcasts/indieweb/</a>.</p>\n\n<p>Music from <a href=\"https://aaronparecki.com/\">Aaron Parecki</a>\u2019s <a href=\"https://100.aaronparecki.com/\">100DaysOfMusic project</a>: <a href=\"https://aaronparecki.com/2017/03/15/14/day85\">Day 85 - Suit</a>, <a href=\"https://aaronparecki.com/2017/02/06/7/day48\">Day 48 - Glitch</a>, <a href=\"https://aaronparecki.com/2017/02/07/4/day49\">Day 49 - Floating</a>, <a href=\"https://aaronparecki.com/2016/12/29/21/day-9\">Day 9</a>, and <a href=\"https://aaronparecki.com/2016/12/31/15/\">Day 11</a></p>\n\n<p>Thanks to everyone in the <a href=\"https://chat.indieweb.org/\">IndieWeb chat</a> for their feedback and suggestions. Please drop me a note if there are any changes you\u2019d like to see for this audio edition!</p>"
    },
    "author": {
        "type": "card",
        "name": "Marty McGuire",
        "url": "https://martymcgui.re/",
        "photo": "https://aperture-media.p3k.io/martymcgui.re/4f9fac2b9e3ae62998c557418143efe288bca8170a119921a9c6bfeb0a1263a2.jpg"
    },
    "_id": "299204",
    "_source": "175",
    "_is_read": true
}

right to be forgotten and non-repudiation

{
    "type": "entry",
    "author": {
        "name": "Kh\u00fcrt Williams",
        "url": "https://islandinthenet.com/",
        "photo": null
    },
    "url": "https://islandinthenet.com/right-to-be-forgotten-and-non-repudiation/",
    "published": "2018-05-06T12:24:10+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>  Replied to <a href=\"https://sebastiangreger.net/2018/05/indieweb-privacy-challenge-webmentions-backfeeds-gdpr/\">The Indieweb privacy challenge (Webmentions, silo backfeeds, and the GDPR) // Sebastian Greger</a> by Sebastian Greger<em> (sebastiangreger.net)</em><blockquote>Originally intended to showcase a privacy-centred implementation of emerging social web technologies \u2013 with the aim to present a solution not initially motivated by legal requirements, but as an example of privacy-aware interaction design \u2013 my \u201csocial backfeed\u201d design process unveiled intric...</blockquote>I have information security-related issues with the \u201cright to be forgotten\u201d. In information security, <a href=\"http://resources.infosecinstitute.com/non-repudiation-digital-signature/\">non-repudiation</a> is the assurance that someone cannot deny something. Systems built for non-repudiation have the ability to ensure that a party to a communication cannot deny the sending of a message that they originated.<p>It seems to me that the \u201cright to be forgotten\u201d circumvents that ability. For example someone posts racist or sexist jokes on twitter, they get called out for it, and the tweets get embedded into my blog or a major news website that is writing about the incident. With the right to be forgotten rule if the tweets are deleted then mine and all website referencing the incident would lose the proof the incident occurred. And if the tweet information was instead copied to my website or the new sites via the Twitter API, we would be on the hook to remove \u201cthe evidence\u201d.</p><p>Perhaps the lawyers who wrote up the GDPR spoke to information scientist and they have some clever way to handle non-repudiation of negative incidents but from the surface, the right to be forgotten seems problematic. Shall I have to resort to taking screenshots?</p><p>The post <a href=\"https://islandinthenet.com/right-to-be-forgotten-and-non-repudiation/\">right to be forgotten and non-repudiation</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.  Replied to The Indieweb privacy challenge (Webmentions, silo backfeeds, and the GDPR) // Sebastian Greger by Sebastian Greger (sebastiangreger.net)Originally intended to showcase a privacy-centred implementation of emerging social web technologies \u2013 with the aim to present a solution not initially motivated by legal requirements, but as an example of privacy-aware interaction design \u2013 my \u201csocial backfeed\u201d design process unveiled intric...I have information security-related issues with the \u201cright to be forgotten\u201d. In information security, non-repudiation is the assurance that someone cannot deny something. Systems built for non-repudiation have the ability to ensure that a party to a communication cannot deny the sending of a message that they originated.It seems to me that the \u201cright to be forgotten\u201d circumvents that ability. For example someone posts racist or sexist jokes on twitter, they get called out for it, and the tweets get embedded into my blog or a major news website that is writing about the incident. With the right to be forgotten rule if the tweets are deleted then mine and all website referencing the incident would lose the proof the incident occurred. And if the tweet information was instead copied to my website or the new sites via the Twitter API, we would be on the hook to remove \u201cthe evidence\u201d.Perhaps the lawyers who wrote up the GDPR spoke to information scientist and they have some clever way to handle non-repudiation of negative incidents but from the surface, the right to be forgotten seems problematic. Shall I have to resort to taking screenshots?The post right to be forgotten and non-repudiation by Kh\u00fcrt Williams appeared first on Island in the Net."
    },
    "name": "right to be forgotten and non-repudiation",
    "_id": "298475",
    "_source": "242",
    "_is_read": true
}

{
    "type": "entry",
    "published": "2018-05-05 16:25-0700",
    "url": "https://gregorlove.com/2018/05/kylewmahan-chat-indieweb-org/",
    "syndication": [
        "https://twitter.com/gRegorLove/status/992908408029409280"
    ],
    "content": {
        "text": "@kylewmahan https://chat.indieweb.org/dev/2018-05-05#t1525560076372400",
        "html": "<p>@kylewmahan <a href=\"https://chat.indieweb.org/dev/2018-05-05#t1525560076372400\">https://chat.indieweb.org/dev/2018-05-05#t1525560076372400</a></p>"
    },
    "author": {
        "type": "card",
        "name": "gRegor Morrill",
        "url": "https://gregorlove.com/",
        "photo": "https://aperture-media.p3k.io/gregorlove.com/1dfe16005864a9fc9564a3884378cdc89abd66b173ed10bce2ac60ed782dab01.jpg"
    },
    "_id": "298090",
    "_source": "95",
    "_is_read": true
}

{
    "type": "entry",
    "published": "2018-05-06T00:47:59+00:00",
    "url": "http://stream.boffosocko.com/2018/federicoculloca-i-havent-heard-the-episode-yet-but-i-actually",
    "syndication": [
        "https://twitter.com/ChrisAldrich/status/992928943983513600"
    ],
    "in-reply-to": [
        "https://twitter.com/FedericoCulloca/status/990875723094220800",
        "https://martymcgui.re/2018/04/28/190950/"
    ],
    "content": {
        "text": "@FedericoCulloca I haven't heard the episode yet, but I actually created a pronunciation page this past week for just this eventuality! If you know where Torvalds' original is, it would be great to document.\nhttps://indieweb.org/pronunciation",
        "html": "@FedericoCulloca I haven't heard the episode yet, but I actually created a pronunciation page this past week for just this eventuality! If you know where Torvalds' original is, it would be great to document.<br /><a href=\"https://indieweb.org/pronunciation\">https://indieweb.org/pronunciation</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": "297735",
    "_source": "192",
    "_is_read": true
}

{
    "type": "entry",
    "url": "http://davidjohnmead.com/blog/2018/05/05/19733/",
    "syndication": [
        "https://twitter.com/davidmead/status/992859152086159361"
    ],
    "content": {
        "text": "Just noticed @phhhoto shut down last year. https://techcrunch.com/2017/06/20/phhhoto-shuts-down/. Another #silo to remove from my homepage.\n\n#indieweb",
        "html": "Just noticed @phhhoto shut down last year. <a href=\"https://techcrunch.com/2017/06/20/phhhoto-shuts-down/\" title=\"Tech Crunch article\" class=\"u-url\">https://techcrunch.com/2017/06/20/phhhoto-shuts-down/</a>. Another #silo to remove from my homepage.<br />\n#indieweb"
    },
    "_id": "297196",
    "_source": "194",
    "_is_read": true
}

{
    "type": "entry",
    "published": "2018-05-05T00:12:09-04:00",
    "summary": "As you\u2019re working on Sublime Feeds keep Microsub spec in mind. It could help with some pre-defined data layouts and also help you interoperate with other feed ecosystem. https://indieweb.org/Microsub",
    "url": "https://eddiehinkle.com/2018/05/05/1/reply/",
    "in-reply-to": [
        "https://vincentritter.com/2018/05/05/02-24-54"
    ],
    "content": {
        "text": "As you\u2019re working on Sublime Feeds keep Microsub spec in mind. It could help with some pre-defined data layouts and also help you interoperate with other feed ecosystem. https://indieweb.org/Microsub",
        "html": "<p>As you\u2019re working on Sublime Feeds keep Microsub spec in mind. It could help with some pre-defined data layouts and also help you interoperate with other feed ecosystem. <a href=\"https://indieweb.org/Microsub\">https://indieweb.org/Microsub</a></p>"
    },
    "author": {
        "type": "card",
        "name": "Eddie Hinkle",
        "url": "https://eddiehinkle.com/",
        "photo": "https://aperture-media.p3k.io/eddiehinkle.com/cf9f85e26d4be531bc908d37f69bff1c50b50b87fd066b254f1332c3553df1a8.jpg"
    },
    "refs": {
        "https://vincentritter.com/2018/05/05/02-24-54": {
            "type": "entry",
            "url": "https://vincentritter.com/2018/05/05/02-24-54",
            "name": "https://vincentritter.com/2018/05/05/02-24-54"
        }
    },
    "_id": "295828",
    "_source": "226",
    "_is_read": true
}

{
    "type": "entry",
    "published": "2018-05-04T22:08:54+00:00",
    "url": "http://stream.boffosocko.com/2018/thanks-for-your-questions-several-of-us-took-a-stab",
    "in-reply-to": [
        "http://www.kimlosey.me/2018/05/04/questions-about-webmentions.html"
    ],
    "content": {
        "text": "Thanks for your questions. Several of us took a stab at answering them in the IndieWeb wiki today. You can find the answers here: https://indieweb.org/Webmention-faq\n\nI recall you said you were in the IndieWeb Slack channel, so if you need more specifics or help, please don't hesitate to stop by and one or more folks there will be happy to help you out the best we can.",
        "html": "Thanks for your questions. Several of us took a stab at answering them in the IndieWeb wiki today. You can find the answers here: <a href=\"https://indieweb.org/Webmention-faq\">https://indieweb.org/Webmention-faq</a><br />\nI recall you said you were in the IndieWeb Slack channel, so if you need more specifics or help, please don't hesitate to stop by and one or more folks there will be happy to help you out the best we can."
    },
    "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": "295145",
    "_source": "192",
    "_is_read": true
}

{
    "type": "entry",
    "published": "2018-05-04T15:23:35-04:00",
    "summary": "These are some great questions! We\u2019ve shared the blog post in the IndieWeb Slack/irc and are working on getting some answers. We\u2019ll let you know when we have it all together! \ud83d\ude42",
    "url": "https://eddiehinkle.com/2018/05/04/10/reply/",
    "in-reply-to": [
        "http://www.kimlosey.me/2018/05/04/questions-about-webmentions.html"
    ],
    "content": {
        "text": "These are some great questions! We\u2019ve shared the blog post in the IndieWeb Slack/irc and are working on getting some answers. We\u2019ll let you know when we have it all together! \ud83d\ude42",
        "html": "<p>These are some great questions! We\u2019ve shared the blog post in the IndieWeb Slack/irc and are working on getting some answers. We\u2019ll let you know when we have it all together! \ud83d\ude42</p>"
    },
    "author": {
        "type": "card",
        "name": "Eddie Hinkle",
        "url": "https://eddiehinkle.com/",
        "photo": "https://aperture-media.p3k.io/eddiehinkle.com/cf9f85e26d4be531bc908d37f69bff1c50b50b87fd066b254f1332c3553df1a8.jpg"
    },
    "refs": {
        "http://www.kimlosey.me/2018/05/04/questions-about-webmentions.html": {
            "type": "entry",
            "url": "http://www.kimlosey.me/2018/05/04/questions-about-webmentions.html",
            "name": "http://www.kimlosey.me/2018/05/04/questions-about-webmentions.html"
        }
    },
    "_id": "294927",
    "_source": "226",
    "_is_read": true
}

{
    "type": "entry",
    "published": "2018-05-04T11:19:47-04:00",
    "url": "https://martymcgui.re/2018/05/04/111947/",
    "bookmark-of": [
        "https://sebastiangreger.net/2018/05/indieweb-privacy-challenge-webmentions-backfeeds-gdpr/#return-note-5622-2"
    ],
    "content": {
        "text": "\ud83d\udd16  Bookmarked https://sebastiangreger.net/2018/05/indieweb-privacy-challenge-webmentions-backfeeds-gdpr/#return-note-5622-2",
        "html": "\ud83d\udd16  Bookmarked <a class=\"u-bookmark-of\" href=\"https://sebastiangreger.net/2018/05/indieweb-privacy-challenge-webmentions-backfeeds-gdpr/#return-note-5622-2\">https://sebastiangreger.net/2018/05/indieweb-privacy-challenge-webmentions-backfeeds-gdpr/#return-note-5622-2</a>"
    },
    "author": {
        "type": "card",
        "name": "Marty McGuire",
        "url": "https://martymcgui.re/",
        "photo": "https://aperture-media.p3k.io/martymcgui.re/4f9fac2b9e3ae62998c557418143efe288bca8170a119921a9c6bfeb0a1263a2.jpg"
    },
    "_id": "293797",
    "_source": "175",
    "_is_read": true
}