David Shanske david.shanske.com

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
}

David Shanske david.shanske.com

{
    "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
}

Marty McGuire martymcgui.re

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
}

gRegor Morrill gregorlove.com

{
    "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
}

Chris Aldrich stream.boffosocko.com/profile/chrisaldrich

{
    "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
}

Eddie Hinkle eddiehinkle.com

{
    "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
}

Chris Aldrich stream.boffosocko.com/profile/chrisaldrich

{
    "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
}

Eddie Hinkle eddiehinkle.com

{
    "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
}

Marty McGuire martymcgui.re

{
    "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
}

Marcus Povey www.marcus-povey.co.uk/author/marcus/

Unofficial Known packages #indieweb

{
    "type": "entry",
    "published": "2018-05-04T16:30:00+00:00",
    "url": "https://www.marcus-povey.co.uk/2018/05/04/unofficial-known-packages-indieweb/",
    "name": "Unofficial Known packages #indieweb",
    "content": {
        "text": "It has now been almost a year since the last official release binary for Known.\nWhile development has been ongoing, and updates largely incremental via Github, I know that this has caused some confusion for folk. So, while we wait for the official release from the core project devs, I\u2019ve started putting out some unofficial releases.\nThese releases are pretty much just a periodic snapshot of what\u2019s on github, but my hope is that these packages will make it easier for folk who are uncomfortable tracking github master.\nEnjoy!\n\n\n\nThanks for visiting! If you're new here you might like to read a bit about me. \n(Psst... I am also available to hire! Find out more...)\n\n\nFollow @mapkyca\n\n\n\n\nShare this:\nEmail\nLinkedIn\nTwitter\nGoogle\nFacebook\nReddit",
        "html": "<p><img src=\"https://aperture-media.p3k.io/www.marcus-povey.co.uk/fefdce29b84aa7d4a71540937bbcd6baa1a196f293b16f80acbc4d3c09504086.png\" width=\"250\" align=\"right\" alt=\"IzqGaQEL.png\" />\n It has now been almost a year since the last official release binary for Known.</p>\n<p>While development has been ongoing, and updates largely incremental via Github, I know that this has caused some confusion for folk. So, while we wait for the official release from the core project devs, I\u2019ve started putting out some <a href=\"https://withknown.marcus-povey.co.uk/\"><em>unofficial</em> releases</a>.</p>\n<p>These releases are pretty much just a periodic snapshot of what\u2019s on github, but my hope is that these packages will make it easier for folk who are uncomfortable tracking github master.</p>\n<p>Enjoy!</p>\n\n\n\nThanks for visiting! If you're new here you might like to read a bit <a href=\"http://www.marcus-povey.co.uk/about/\">about me</a>. \n<strong><em>(Psst... I am also available to hire! <a href=\"http://www.marcus-povey.co.uk/hire/\">Find out more...</a>)</em></strong>\n\n\n<a href=\"https://twitter.com/mapkyca\">Follow @mapkyca</a>\n\n\n\n\n<h3>Share this:</h3>\n<ul><li><a href=\"https://www.marcus-povey.co.uk/2018/05/04/unofficial-known-packages-indieweb/?share=email\" title=\"Click to email this to a friend\">Email</a></li>\n<li><a href=\"https://www.marcus-povey.co.uk/2018/05/04/unofficial-known-packages-indieweb/?share=linkedin\" title=\"Click to share on LinkedIn\">LinkedIn</a></li>\n<li><a href=\"https://www.marcus-povey.co.uk/2018/05/04/unofficial-known-packages-indieweb/?share=twitter\" title=\"Click to share on Twitter\">Twitter</a></li>\n<li><a href=\"https://www.marcus-povey.co.uk/2018/05/04/unofficial-known-packages-indieweb/?share=google-plus-1\" title=\"Click to share on Google+\">Google</a></li>\n<li><a href=\"https://www.marcus-povey.co.uk/2018/05/04/unofficial-known-packages-indieweb/?share=facebook\" title=\"Click to share on Facebook\">Facebook</a></li>\n<li><a href=\"https://www.marcus-povey.co.uk/2018/05/04/unofficial-known-packages-indieweb/?share=reddit\" title=\"Click to share on Reddit\">Reddit</a></li>\n<li>\n</li></ul>"
    },
    "author": {
        "type": "card",
        "name": "Marcus Povey",
        "url": "https://www.marcus-povey.co.uk/author/marcus/",
        "photo": "https://aperture-media.p3k.io/secure.gravatar.com/ac58839f668a3d27082da0460652e8973127d8180985cb98ddd294855cfea7f0.jpg"
    },
    "_id": "293721",
    "_source": "244",
    "_is_read": true
}

Webstock ‘18: Jeremy Keith - Taking Back The Web on Vimeo

Here’s the talk I gave at Webstock earlier this year all about the indie web:

In these times of centralised services like Facebook, Twitter, and Medium, having your own website is downright disruptive. If you care about the longevity of your online presence, independent publishing is the way to go. But how can you get all the benefits of those third-party services while still owning your own data? By using the building blocks of the Indie Web, that’s how!

Read More

{
    "type": "entry",
    "published": "2018-05-04T06:49:40Z",
    "url": "https://adactio.com/links/13836",
    "category": [
        "video",
        "vimeo",
        "webstock",
        "indieweb",
        "talk",
        "presentation",
        "conference",
        "speaking",
        "decentralisation",
        "independent",
        "publishing",
        "micropub",
        "webmention",
        "posse",
        "pesos",
        "syndication",
        "twitter",
        "facebook",
        "medium"
    ],
    "bookmark-of": [
        "https://vimeo.com/265121482"
    ],
    "content": {
        "text": "Webstock \u201818: Jeremy Keith - Taking Back The Web on Vimeo\n\n\n\nHere\u2019s the talk I gave at Webstock earlier this year all about the indie web:\n\n\n  In these times of centralised services like Facebook, Twitter, and Medium, having your own website is downright disruptive. If you care about the longevity of your online presence, independent publishing is the way to go. But how can you get all the benefits of those third-party services while still owning your own data? By using the building blocks of the Indie Web, that\u2019s how!",
        "html": "<h3>\n<a class=\"p-name u-bookmark-of\" href=\"https://vimeo.com/265121482\">\nWebstock \u201818: Jeremy Keith - Taking Back The Web on Vimeo\n</a>\n</h3>\n\n<p>Here\u2019s the talk I gave at Webstock earlier this year all about the indie web:</p>\n\n<blockquote>\n  <p>In these times of centralised services like Facebook, Twitter, and Medium, having your own website is downright disruptive. If you care about the longevity of your online presence, independent publishing is the way to go. But how can you get all the benefits of those third-party services while still owning your own data? By using the building blocks of the Indie Web, that\u2019s how!</p>\n</blockquote>\n\n<a href=\"https://vimeo.com/265121482\"><img src=\"https://i.vimeocdn.com/video/697613310_640.jpg\" alt=\"Webstock '18: Jeremy Keith - Taking Back The Web\" /></a><br />"
    },
    "_id": "292610",
    "_source": "2",
    "_is_read": true
}

Webmentions and Privacy and GDPR

{
    "type": "entry",
    "author": {
        "name": "Kh\u00fcrt Williams",
        "url": "https://islandinthenet.com/",
        "photo": null
    },
    "url": "https://islandinthenet.com/webmentions-and-privacy-and-gdpr/",
    "published": "2018-05-04T04:40:58+00:00",
    "content": {
        "html": "<p><a href=\"https://islandinthenet.com/\">Island in the Net Transient - A personal website by Kh\u00fcrt Williams, with imagery, and inchoate ramblings on coffee, beer, and geekery.</a></p>  Replied to <a href=\"https://david.shanske.com/2018/05/03/1905/\">Untitled | David Shanske</a> by <a href=\"https://david.shanske.com/\"><img src=\"https://secure.gravatar.com/avatar/681eba02e72ba1d894097034a8110e61?s=125&amp;d=default&amp;r=g\" alt=\"Webmentions and Privacy and GDPR %name\" title=\"Webmentions and Privacy and GDPR\" />David Shanske</a><em> (David Shanske)</em><blockquote><p>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><ul><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><li>Add Setting to not display avatar/photo</li><li>Add ability to edit mentions, to correct inaccurate data.</li><li>Add setting to store more/less data.</li><li>Add privacy policy to plugin for those who install it and add text/link to webmention form.</li><li>Explain how to request a takedown of information.</li><li>Periodically poll/refresh sources.</li><li>Allow a different level of processing for \u2018native\u2019 webmentions vs backfeed run through a service like Bridgy.</li></ul></blockquote><p>David, I think that Sebastian Greger (and perhaps some of the GDPR) is really concerned about anonymity; not privacy. But I think you have responded reasonably. I don\u2019t think one can expect privacy when acting publicly. Imagine if newspapers had to get permission to quote something I said publicly (especially something controversial)? Or a radio or television news cast couldn\u2019t use footage of my public acts because of \u201cprivacy\u201d? I don\u2019t see any level or ethical basis (USA law) for Sebastian\u2018s position. I expect as the GDPR is implemented we\u2019ll see some challenging consequences of the rules.</p><p>The post <a href=\"https://islandinthenet.com/webmentions-and-privacy-and-gdpr/\">Webmentions and Privacy and GDPR</a> by <a href=\"https://islandinthenet.com/\">Kh\u00fcrt Williams</a> appeared first on <a href=\"https://islandinthenet.com/\">Island in the Net Transient</a>.</p>",
        "text": "Island in the Net Transient - A personal website by Kh\u00fcrt Williams, with imagery, and inchoate ramblings on coffee, beer, and geekery.  Replied to Untitled | David Shanske by David Shanske (David Shanske)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.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.Add Setting to not display avatar/photoAdd ability to edit mentions, to correct inaccurate data.Add setting to store more/less data.Add privacy policy to plugin for those who install it and add text/link to webmention form.Explain how to request a takedown of information.Periodically poll/refresh sources.Allow a different level of processing for \u2018native\u2019 webmentions vs backfeed run through a service like Bridgy.David, I think that Sebastian Greger (and perhaps some of the GDPR) is really concerned about anonymity; not privacy. But I think you have responded reasonably. I don\u2019t think one can expect privacy when acting publicly. Imagine if newspapers had to get permission to quote something I said publicly (especially something controversial)? Or a radio or television news cast couldn\u2019t use footage of my public acts because of \u201cprivacy\u201d? I don\u2019t see any level or ethical basis (USA law) for Sebastian\u2018s position. I expect as the GDPR is implemented we\u2019ll see some challenging consequences of the rules.The post Webmentions and Privacy and GDPR by Kh\u00fcrt Williams appeared first on Island in the Net Transient."
    },
    "name": "Webmentions and Privacy and GDPR",
    "_id": "292444",
    "_source": "242",
    "_is_read": true
}

Chris Aldrich stream.boffosocko.com/profile/chrisaldrich

{
    "type": "entry",
    "published": "2018-05-04T04:05:56+00:00",
    "url": "http://stream.boffosocko.com/2018/aschweig-naturally-i-see-this-a-minute-after-the-deadline",
    "category": [
        "openweb",
        "WordPress",
        "IndieWeb",
        "journalism"
    ],
    "syndication": [
        "https://twitter.com/ChrisAldrich/status/992253992557199360"
    ],
    "in-reply-to": [
        "https://twitter.com/aschweig/status/992070955756343298?s=09"
    ],
    "content": {
        "text": "@aschweig Naturally I see this a minute after the deadline :(\n#openweb #WordPress #IndieWeb #journalism\nhttps://indieweb.org/Indieweb_for_Journalism",
        "html": "<a href=\"https://twitter.com/aschweig\">@aschweig</a> Naturally I see this a minute after the deadline :(<br /><a href=\"http://stream.boffosocko.com/tag/openweb\" class=\"p-category\">#openweb</a> <a href=\"http://stream.boffosocko.com/tag/WordPress\" class=\"p-category\">#WordPress</a> <a href=\"http://stream.boffosocko.com/tag/IndieWeb\" class=\"p-category\">#IndieWeb</a> <a href=\"http://stream.boffosocko.com/tag/journalism\" class=\"p-category\">#journalism</a><br /><a href=\"https://indieweb.org/Indieweb_for_Journalism\">https://indieweb.org/Indieweb_for_Journalism</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": "292383",
    "_source": "192",
    "_is_read": true
}

human beings

{
    "type": "entry",
    "author": {
        "name": "Kh\u00fcrt Williams",
        "url": "https://islandinthenet.com/",
        "photo": null
    },
    "url": "https://islandinthenet.com/human-beings/",
    "published": "2018-05-04T00:44:29+00:00",
    "content": {
        "html": "<p><a href=\"https://islandinthenet.com/\">Island in the Net Transient - A personal website by Kh\u00fcrt Williams, with imagery, and inchoate ramblings on coffee, beer, and geekery.</a></p>  Read <a href=\"http://boffosocko.com/2018/05/03/brief-reply-to-the-indieweb-privacy-challenge-webmentions-silo-backfeeds-and-the-gdpr-by-sebastian-greger/\">Reply to The Indieweb privacy challenge (Webmentions, silo backfeeds, and the GDPR) by Sebastian Greger</a> by <a href=\"http://www.boffosocko.com/\"><img src=\"http://1.gravatar.com/avatar/d5fb4e498fe609cc29b04e5b7ad688c4?s=49&amp;d=mm&amp;r=pg\" alt=\"human beings %name\" title=\"human beings\" />Chris Aldrich</a><em> (Chris Aldrich | BoffoSocko)</em><blockquote>Disclaimer: I\u2019m aware that in posting this to my own site that it will trigger a tacit webmention which will ping Sebastian Greger\u2019s website. I give him permission to display any and all data he chooses from the originating web page in perpetuity, or until such time as I send a webmention either modifying or deleting the content of the originating page. I say this all with some jest, while I am really relying on the past twenty years of general social norms built up on the internet and in general society as well as the current practices of the IndieWeb movement to govern what he does with this content.</blockquote><p>I\u2019m saddened that a blog post linking to another blog post might need to include a disclaimer even if some of it is in jest.</p><p>A part of me thinks we\u2019re headed down a path of permission based interactions. Both online and offline. If that happens during my lifetime I\u2019ll exit this experiment called the USA, to places where human beings are still human beings.</p><p>The post <a href=\"https://islandinthenet.com/human-beings/\">human beings</a> by <a href=\"https://islandinthenet.com/\">Kh\u00fcrt Williams</a> appeared first on <a href=\"https://islandinthenet.com/\">Island in the Net Transient</a>.</p>",
        "text": "Island in the Net Transient - A personal website by Kh\u00fcrt Williams, with imagery, and inchoate ramblings on coffee, beer, and geekery.  Read Reply to The Indieweb privacy challenge (Webmentions, silo backfeeds, and the GDPR) by Sebastian Greger by Chris Aldrich (Chris Aldrich | BoffoSocko)Disclaimer: I\u2019m aware that in posting this to my own site that it will trigger a tacit webmention which will ping Sebastian Greger\u2019s website. I give him permission to display any and all data he chooses from the originating web page in perpetuity, or until such time as I send a webmention either modifying or deleting the content of the originating page. I say this all with some jest, while I am really relying on the past twenty years of general social norms built up on the internet and in general society as well as the current practices of the IndieWeb movement to govern what he does with this content.I\u2019m saddened that a blog post linking to another blog post might need to include a disclaimer even if some of it is in jest.A part of me thinks we\u2019re headed down a path of permission based interactions. Both online and offline. If that happens during my lifetime I\u2019ll exit this experiment called the USA, to places where human beings are still human beings.The post human beings by Kh\u00fcrt Williams appeared first on Island in the Net Transient."
    },
    "name": "human beings",
    "_id": "292358",
    "_source": "242",
    "_is_read": true
}

GDPR and the IndieWeb

{
    "type": "entry",
    "author": {
        "name": "Kh\u00fcrt Williams",
        "url": "https://islandinthenet.com/",
        "photo": null
    },
    "url": "https://islandinthenet.com/gdpr-and-the-indieweb/",
    "published": "2018-05-02T21:00:51+00:00",
    "content": {
        "html": "<p><a href=\"https://islandinthenet.com/\">Island in the Net Transient - 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>Given the considerations above, and the GDPR enforcement deadline three weeks away, I decided to at least temporarily remove the Twitter backfeed from my site, delete the personal data accrued in the database, and disable my Brid.gy account (shedding a little tear, as it truly is an ingenious concept and service). While I still believe that my pixelated and de-personalised presentation of the backfeed solved at least most of the ethical issues, I personally don\u2019t want to jump through the hoops of drafting a privacy statement with a shaky argumentation about the lawfulness of storing all that data. At the same time, this releases me from the need to think about how to deal with individuals\u2019 requests as they may execute their rights under the GDPR; it makes this site less social, though \u2013 a strong motivation to keep thinking about solutions!</blockquote><p>Would love to know <a href=\"https://micro.blog/c\">@c</a> thoughts on this <a href=\"https://sebastiangreger.net/2018/05/indieweb-privacy-challenge-webmentions-backfeeds-gdpr/\">post</a> by Sebastian Gregor.</p><p>At first, I thought that Sebastian was misunderstanding the GDPR but as I read further I realized he had done considerably more research than I did.  If his conclusions are correct we have a major problem. I don\u2019t solicit comments from EU readers but I do have some regular visitors from Germany, Italy and the UK.</p><p>I am not as concerned with privacy. I don\u2019t one can have any expectations of privacy when acting in public. But I don\u2019t want laws written in any country other than the USA to apply to me. Ever!</p><p>So I\u2019ve decided to be cautious. I have disabled Brid.gy. I will no longer back feed comments from Twitter, Instagram, et. al. My website has had a privacy statement for several years. I\u2019ve kept the Webmentions feature enabled. If you are using Webmentions I will assume you know how and what it is. You\u2019ve either intentionally sent a Webmention from your website or you have intentionally used the form on my website.</p><p>I am also considering blocking all access to my website from EU member countries. I think that would basically saying stay out.</p><p>I think this sort of thing is an example of the law of unintended consequences. It\u2019s all very stupid when an independent website owner in the USA has to worry about a European law. It\u2019s stupid that I have to remove the ability for commentary. It\u2019s stupid that I have to worry about things that have nothing to do with writing. Stupid.</p><p>The post <a href=\"https://islandinthenet.com/gdpr-and-the-indieweb/\">GDPR and 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 Transient</a>.</p> Syndicated to:<p><a href=\"https://micro.blog/khurt/530518\"> Micro.blog</a></p>",
        "text": "Island in the Net Transient - 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)Given the considerations above, and the GDPR enforcement deadline three weeks away, I decided to at least temporarily remove the Twitter backfeed from my site, delete the personal data accrued in the database, and disable my Brid.gy account (shedding a little tear, as it truly is an ingenious concept and service). While I still believe that my pixelated and de-personalised presentation of the backfeed solved at least most of the ethical issues, I personally don\u2019t want to jump through the hoops of drafting a privacy statement with a shaky argumentation about the lawfulness of storing all that data. At the same time, this releases me from the need to think about how to deal with individuals\u2019 requests as they may execute their rights under the GDPR; it makes this site less social, though \u2013 a strong motivation to keep thinking about solutions!Would love to know @c thoughts on this post by Sebastian Gregor.At first, I thought that Sebastian was misunderstanding the GDPR but as I read further I realized he had done considerably more research than I did.  If his conclusions are correct we have a major problem. I don\u2019t solicit comments from EU readers but I do have some regular visitors from Germany, Italy and the UK.I am not as concerned with privacy. I don\u2019t one can have any expectations of privacy when acting in public. But I don\u2019t want laws written in any country other than the USA to apply to me. Ever!So I\u2019ve decided to be cautious. I have disabled Brid.gy. I will no longer back feed comments from Twitter, Instagram, et. al. My website has had a privacy statement for several years. I\u2019ve kept the Webmentions feature enabled. If you are using Webmentions I will assume you know how and what it is. You\u2019ve either intentionally sent a Webmention from your website or you have intentionally used the form on my website.I am also considering blocking all access to my website from EU member countries. I think that would basically saying stay out.I think this sort of thing is an example of the law of unintended consequences. It\u2019s all very stupid when an independent website owner in the USA has to worry about a European law. It\u2019s stupid that I have to remove the ability for commentary. It\u2019s stupid that I have to worry about things that have nothing to do with writing. Stupid.The post GDPR and the IndieWeb by Kh\u00fcrt Williams appeared first on Island in the Net Transient. Syndicated to: Micro.blog"
    },
    "name": "GDPR and the IndieWeb",
    "_id": "292361",
    "_source": "242",
    "_is_read": true
}

Chris Aldrich stream.boffosocko.com/profile/chrisaldrich

{
    "type": "entry",
    "published": "2018-05-03T19:26:12+00:00",
    "url": "http://stream.boffosocko.com/2018/jgmac1106-dooo-i-think-that-one-day-in-the-not-too-distant",
    "syndication": [
        "https://twitter.com/ChrisAldrich/status/992123183703654400"
    ],
    "in-reply-to": [
        "https://twitter.com/jgmac1106/status/992041193465724930",
        "http://quickthoughts.jgregorymcverry.com/2018/05/03/i-dont-mean-a-new-blogging-platform-i-mean-i",
        "http://quickthoughts.jgregorymcverry.com/2018/05/03/gwg-part-of-the-reason-i-want-to-explore-a"
    ],
    "content": {
        "text": "@jgmac1106 @DoOO I think that one day in the not-too-distant future, the half a dozen IndieWeb plugins for WordPress will not only merge together, but they might also enter the core product, thus making them simpler and easier to use. WordPress can be made much more flexible and extensible with plugins for a variety of purposes and there's a tremendously valuable community and ecosystem that's already there. Further, I think that companies, similar to Reclaim Hosting and the DoOO movement, will eventually spring up to make hosting and owning one's own site simpler and easier. While there's a lot of value baked into Known, its community and resources aren't (yet!) as large or as flexible as WordPress or even other open source communities. Fortunately the IndieWeb principle of plurality will show us the way forward. The more things working toward openness and shared standards will make these ideas all the stronger.\n\n\nWhile the recent spate of work on IndieReaders is awesome and inspiring, I'm also curious what is next after that? IndieBrowsers? IndieHardware?\n\n\nUltimately I'm grateful that we're all here pressing the boundaries and experimenting with what is possible.",
        "html": "@jgmac1106 @DoOO I think that one day in the not-too-distant future, the half a dozen IndieWeb plugins for WordPress will not only merge together, but they might also enter the core product, thus making them simpler and easier to use. WordPress can be made much more flexible and extensible with plugins for a variety of purposes and there's a tremendously valuable community and ecosystem that's already there. Further, I think that companies, similar to Reclaim Hosting and the DoOO movement, will eventually spring up to make hosting and owning one's own site simpler and easier. While there's a lot of value baked into Known, its community and resources aren't (yet!) as large or as flexible as WordPress or even other open source communities. Fortunately the IndieWeb principle of plurality will show us the way forward. The more things working toward openness and shared standards will make these ideas all the stronger.<br /><br />\nWhile the recent spate of work on IndieReaders is awesome and inspiring, I'm also curious what is next after that? IndieBrowsers? IndieHardware?<br /><br />\nUltimately I'm grateful that we're all here pressing the boundaries and experimenting with what is possible."
    },
    "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": "291244",
    "_source": "192",
    "_is_read": true
}