I 2024-01-24 03:44:07.741389+00:00 Params: [('source', 'https://snarfed.org/2024-01-23_snarfed-org-posted-a-great-overview-of-thoughtful-and-sometimes-heated-discussions-across-blogs-and-the-fediverse-about-how-freely-should-public-posts-comments-on-the-web-flow'), ('target', 'https://fed.brid.gy')]
I 2024-01-24 03:44:07.741839+00:00 webmention from snarfed.org
I 2024-01-24 03:44:07.765457+00:00 User: Key('MagicKey', 'snarfed.org')
D 2024-01-24 03:44:07.778093+00:00 Loading Object https://snarfed.org/2024-01-23_snarfed-org-posted-a-great-overview-of-thoughtful-and-sometimes-heated-discussions-across-blogs-and-the-fediverse-about-how-freely-should-public-posts-comments-on-the-web-flow local=True remote=True, forced refresh requested
I 2024-01-24 03:44:07.778412+00:00 not in datastore
I 2024-01-24 03:44:07.778697+00:00 requests.get https://snarfed.org/2024-01-23_snarfed-org-posted-a-great-overview-of-thoughtful-and-sometimes-heated-discussions-across-blogs-and-the-fediverse-about-how-freely-should-public-posts-comments-on-the-web-flow {'gateway': False}
I 2024-01-24 03:44:10.550147+00:00 Received 200
I 2024-01-24 03:44:10.613878+00:00 Extracted microformats2 entry: {
"type": [
"h-entry"
],
"properties": {
"name": [
""
],
"url": [
"https://snarfed.org/2024-01-23_snarfed-org-posted-a-great-overview-of-thoughtful-and-sometimes-heated-discussions-across-blogs-and-the-fediverse-about-how-freely-should-public-posts-comments-on-the-web-flow"
],
"published": [
"2024-01-23T19:44:06-0800"
],
"author": [
{
"type": [
"h-card"
],
"properties": {
"photo": [
{
"value": "https://secure.gravatar.com/avatar/947b5f3f323da0ef785b6f02d9c265d6?s=96&d=blank&r=g",
"alt": "",
"srcset": {
"2x": "https://secure.gravatar.com/avatar/947b5f3f323da0ef785b6f02d9c265d6?s=192&d=blank&r=g"
}
}
],
"name": [
"Ryan Barrett"
],
"url": [
"https://snarfed.org/"
]
},
"value": "Ryan Barrett",
"lang": "en-US"
}
],
"content": [
{
"value": "Likes https://tantek.com/2024/023/t1/should-public-posts-flow-across-sites. @snarfed.org posted a great overview of thoughtful (and sometimes heated) discussions across blogs and the #fediverse about how freely should \u201cpublic\u201d posts & comments on the web flow across sites: \u201cModerate people, not code\u201d (https://snarfed.org/2024-01-21_moderate-people-not-code) If you are designing or creating any kind of publishing or social features on the web, this post is for you. It touches on topics ranging from #contextCollapse to #federation to #moderation and everything in between. Does your choice of publishing tool set expectations about where your content might propagate, or whether it will be indexed by search engines? Should it? Do the limitations of your server (e.g. js;dr) imply limitations of where your posts go, or whether they can be searched or archived? Should they? When you post something publicly, are you truly posting it for a global audience for all time, or only for one or a few more limited #publics for an ephemerality? When you reply to a post, do you expect your reply to only be visible in the context you posted it, or do you expect it to travel alongside that post to anywhere it might propagate to? On the #IndieWeb, especially for public posts, some of these questions have easier and more obvious answers, because the intent of nearly all public IndieWeb posts is to interact across the web with other posts and sites, typically via the #Webmention protocol. However there are still questions. Are the expectations for a blog and blogging different from a social media site, whether a silo or an instance on a network? Is a personal website with posts still just a blog, or does it become something new when you start posting responses from your site, or receiving (e.g. via Webmention) and displaying responses from across the web to your posts on your site? Or is it now a \u201csocial website\u201d? If you have a social website, what is your responsibility for keeping it, well, social? Do you moderate Webmentions by default? Do you use the Vouch extension for some automatic moderation? Are #POSSE & #backfeed different from federation or are they the same thing from a user-perspective, with merely different names hinting at different implementations? Do you allow anyone from any site to respond or react to your posts? Or do you treat your social website like your home, and follow what I like to call a \u201chouse party protocol\u201d, only letting in those you know, and perhaps allowing them to bring a +1 or 2? I have many more questions. Each of these deserves thoughtful discussions, documentation of what different tools & services do today that we can try out, learn from, and use to make considered decisions when creating new things to post on and across websites. This is post 4 of #100PostsOfIndieWeb. #100Posts \u2190 https://tantek.com/2024/022/t1/indiewebcamp-brighton-planned \u2192 \ud83d\udd2e Post glossary: backfeed https://indieweb.org/backfeed blog https://indieweb.org/blog blogging https://indieweb.org/blogging comments https://indieweb.org/comments context collapse https://indieweb.org/context_collapse ephemerality https://indieweb.org/ephemerality js;dr https://indieweb.org/js;dr moderation https://indieweb.org/moderation POSSE https://indieweb.org/POSSE posts https://indieweb.org/posts publics https://indieweb.org/publics reply https://indieweb.org/reply Vouch https://indieweb.org/Vouch Webmention https://indieweb.org/Webmention \u2013 Tantek",
"lang": "en-US",
"html": "Likes <a class=\"u-like-of\" href=\"https://tantek.com/2024/023/t1/should-public-posts-flow-across-sites\">https://tantek.com/2024/023/t1/should-public-posts-flow-across-sites</a>;..\n<div class=\"e-content\">\n@snarfed.org posted a great overview of thoughtful (and sometimes heated) discussions across blogs and the #fediverse about how freely should \u201cpublic\u201d posts & comments on the web flow across sites: \u201cModerate people, not code\u201d (https://snarfed.org/2024-01-21_moderate-people-not-code) If you are designing or creating any kind of publishing or social features on the web, this post is for you. It touches on topics ranging from #contextCollapse to #federation to #moderation and everything in between. Does your choice of publishing tool set expectations about where your content might propagate, or whether it will be indexed by search engines? Should it? Do the limitations of your server (e.g. js;dr) imply limitations of where your posts go, or whether they can be searched or archived? Should they? When you post something publicly, are you truly posting it for a global audience for all time, or only for one or a few more limited #publics for an ephemerality? When you reply to a post, do you expect your reply to only be visible in the context you posted it, or do you expect it to travel alongside that post to anywhere it might propagate to? On the #IndieWeb, especially for public posts, some of these questions have easier and more obvious answers, because the intent of nearly all public IndieWeb posts is to interact across the web with other posts and sites, typically via the #Webmention protocol. However there are still questions. Are the expectations for a blog and blogging different from a social media site, whether a silo or an instance on a network? Is a personal website with posts still just a blog, or does it become something new when you start posting responses from your site, or receiving (e.g. via Webmention) and displaying responses from across the web to your posts on your site? Or is it now a \u201csocial website\u201d? If you have a social website, what is your responsibility for keeping it, well, social? Do you moderate Webmentions by default? Do you use the Vouch extension for some automatic moderation? Are #POSSE & #backfeed different from federation or are they the same thing from a user-perspective, with merely different names hinting at different implementations? Do you allow anyone from any site to respond or react to your posts? Or do you treat your social website like your home, and follow what I like to call a \u201chouse party protocol\u201d, only letting in those you know, and perhaps allowing them to bring a +1 or 2? I have many more questions. Each of these deserves thoughtful discussions, documentation of what different tools & services do today that we can try out, learn from, and use to make considered decisions when creating new things to post on and across websites. This is post 4 of #100PostsOfIndieWeb. #100Posts \u2190 https://tantek.com/2024/022/t1/indiewebcamp-brighton-planned \u2192 \ud83d\udd2e Post glossary: backfeed https://indieweb.org/backfeed blog https://indieweb.org/blog blogging https://indieweb.org/blogging comments https://indieweb.org/comments context collapse https://indieweb.org/context_collapse ephemerality https://indieweb.org/ephemerality js;dr https://indieweb.org/js;dr moderation https://indieweb.org/moderation POSSE https://indieweb.org/POSSE posts https://indieweb.org/posts publics https://indieweb.org/publics reply https://indieweb.org/reply Vouch https://indieweb.org/Vouch Webmention https://indieweb.org/Webmention \u2013 Tantek\n</div>"
},
{
"value": "@snarfed.org posted a great overview of thoughtful (and sometimes heated) discussions across blogs and the #fediverse about how freely should \u201cpublic\u201d posts & comments on the web flow across sites: \u201cModerate people, not code\u201d (https://snarfed.org/2024-01-21_moderate-people-not-code) If you are designing or creating any kind of publishing or social features on the web, this post is for you. It touches on topics ranging from #contextCollapse to #federation to #moderation and everything in between. Does your choice of publishing tool set expectations about where your content might propagate, or whether it will be indexed by search engines? Should it? Do the limitations of your server (e.g. js;dr) imply limitations of where your posts go, or whether they can be searched or archived? Should they? When you post something publicly, are you truly posting it for a global audience for all time, or only for one or a few more limited #publics for an ephemerality? When you reply to a post, do you expect your reply to only be visible in the context you posted it, or do you expect it to travel alongside that post to anywhere it might propagate to? On the #IndieWeb, especially for public posts, some of these questions have easier and more obvious answers, because the intent of nearly all public IndieWeb posts is to interact across the web with other posts and sites, typically via the #Webmention protocol. However there are still questions. Are the expectations for a blog and blogging different from a social media site, whether a silo or an instance on a network? Is a personal website with posts still just a blog, or does it become something new when you start posting responses from your site, or receiving (e.g. via Webmention) and displaying responses from across the web to your posts on your site? Or is it now a \u201csocial website\u201d? If you have a social website, what is your responsibility for keeping it, well, social? Do you moderate Webmentions by default? Do you use the Vouch extension for some automatic moderation? Are #POSSE & #backfeed different from federation or are they the same thing from a user-perspective, with merely different names hinting at different implementations? Do you allow anyone from any site to respond or react to your posts? Or do you treat your social website like your home, and follow what I like to call a \u201chouse party protocol\u201d, only letting in those you know, and perhaps allowing them to bring a +1 or 2? I have many more questions. Each of these deserves thoughtful discussions, documentation of what different tools & services do today that we can try out, learn from, and use to make considered decisions when creating new things to post on and across websites. This is post 4 of #100PostsOfIndieWeb. #100Posts \u2190 https://tantek.com/2024/022/t1/indiewebcamp-brighton-planned \u2192 \ud83d\udd2e Post glossary: backfeed https://indieweb.org/backfeed blog https://indieweb.org/blog blogging https://indieweb.org/blogging comments https://indieweb.org/comments context collapse https://indieweb.org/context_collapse ephemerality https://indieweb.org/ephemerality js;dr https://indieweb.org/js;dr moderation https://indieweb.org/moderation POSSE https://indieweb.org/POSSE posts https://indieweb.org/posts publics https://indieweb.org/publics reply https://indieweb.org/reply Vouch https://indieweb.org/Vouch Webmention https://indieweb.org/Webmention \u2013 Tantek",
"lang": "en-US",
"html": "@snarfed.org posted a great overview of thoughtful (and sometimes heated) discussions across blogs and the #fediverse about how freely should \u201cpublic\u201d posts & comments on the web flow across sites: \u201cModerate people, not code\u201d (https://snarfed.org/2024-01-21_moderate-people-not-code) If you are designing or creating any kind of publishing or social features on the web, this post is for you. It touches on topics ranging from #contextCollapse to #federation to #moderation and everything in between. Does your choice of publishing tool set expectations about where your content might propagate, or whether it will be indexed by search engines? Should it? Do the limitations of your server (e.g. js;dr) imply limitations of where your posts go, or whether they can be searched or archived? Should they? When you post something publicly, are you truly posting it for a global audience for all time, or only for one or a few more limited #publics for an ephemerality? When you reply to a post, do you expect your reply to only be visible in the context you posted it, or do you expect it to travel alongside that post to anywhere it might propagate to? On the #IndieWeb, especially for public posts, some of these questions have easier and more obvious answers, because the intent of nearly all public IndieWeb posts is to interact across the web with other posts and sites, typically via the #Webmention protocol. However there are still questions. Are the expectations for a blog and blogging different from a social media site, whether a silo or an instance on a network? Is a personal website with posts still just a blog, or does it become something new when you start posting responses from your site, or receiving (e.g. via Webmention) and displaying responses from across the web to your posts on your site? Or is it now a \u201csocial website\u201d? If you have a social website, what is your responsibility for keeping it, well, social? Do you moderate Webmentions by default? Do you use the Vouch extension for some automatic moderation? Are #POSSE & #backfeed different from federation or are they the same thing from a user-perspective, with merely different names hinting at different implementations? Do you allow anyone from any site to respond or react to your posts? Or do you treat your social website like your home, and follow what I like to call a \u201chouse party protocol\u201d, only letting in those you know, and perhaps allowing them to bring a +1 or 2? I have many more questions. Each of these deserves thoughtful discussions, documentation of what different tools & services do today that we can try out, learn from, and use to make considered decisions when creating new things to post on and across websites. This is post 4 of #100PostsOfIndieWeb. #100Posts \u2190 https://tantek.com/2024/022/t1/indiewebcamp-brighton-planned \u2192 \ud83d\udd2e Post glossary: backfeed https://indieweb.org/backfeed blog https://indieweb.org/blog blogging https://indieweb.org/blogging comments https://indieweb.org/comments context collapse https://indieweb.org/context_collapse ephemerality https://indieweb.org/ephemerality js;dr https://indieweb.org/js;dr moderation https://indieweb.org/moderation POSSE https://indieweb.org/POSSE posts https://indieweb.org/posts publics https://indieweb.org/publics reply https://indieweb.org/reply Vouch https://indieweb.org/Vouch Webmention https://indieweb.org/Webmention \u2013 Tantek"
}
],
"like-of": [
"https://tantek.com/2024/023/t1/should-public-posts-flow-across-sites"
]
},
"children": [
{
"type": [
"h-card"
],
"properties": {
"name": [
"Ryan Barrett"
],
"locality": [
"San Francisco"
],
"region": [
"California"
],
"photo": [
{
"value": "https://snarfed.org/ryan_profile_medium.jpg",
"alt": "Ryan"
}
],
"email": [
"mailto:public@ryanb.org"
],
"key": [
"https://snarfed.org/pubkey.txt"
],
"uid": [
"https://snarfed.org/"
],
"url": [
"https://snarfed.org/"
],
"featured": [
"https://snarfed.org/w/wp-content/uploads/2013/06/copy-cropped-iraq_bar.jpg"
]
},
"lang": "en-US"
}
],
"lang": "en-US",
"url": "https://snarfed.org/2024-01-23_snarfed-org-posted-a-great-overview-of-thoughtful-and-sometimes-heated-discussions-across-blogs-and-the-fediverse-about-how-freely-should-public-posts-comments-on-the-web-flow"
}
I 2024-01-24 03:44:10.877983+00:00 Wrote Key('Object', 'https://snarfed.org/2024-01-23_snarfed-org-posted-a-great-overview-of-thoughtful-and-sometimes-heated-discussions-across-blogs-and-the-fediverse-about-how-freely-should-public-posts-comments-on-the-web-flow') {'labels': ['activity'], 'mf2': '...', 'object_ids': ['https://tantek.com/2024/023/t1/should-public-posts-flow-across-sites'], 'source_protocol': 'web', 'type': 'like', 'new': True, 'changed': False}
I 2024-01-24 03:44:10.880293+00:00 From web: Key('Object', 'https://snarfed.org/2024-01-23_snarfed-org-posted-a-great-overview-of-thoughtful-and-sometimes-heated-discussions-across-blogs-and-the-fediverse-about-how-freely-should-public-posts-comments-on-the-web-flow') AS1: {
"objectType": "activity",
"verb": "like",
"published": "2024-01-23T19:44:06-08:00",
"content": "Likes <a class=\"u-like-of\" href=\"https://tantek.com/2024/023/t1/should-public-posts-flow-across-sites\">https://tantek.com/2024/023/t1/should-public-posts-flow-across-sites</a>;..\n<div class=\"e-content\">\n@snarfed.org posted a great overview of thoughtful (and sometimes heated) discussions across blogs and the #fediverse about how freely should \u201cpublic\u201d posts & comments on the web flow across sites: \u201cModerate people, not code\u201d (https://snarfed.org/2024-01-21_moderate-people-not-code) If you are designing or creating any kind of publishing or social features on the web, this post is for you. It touches on topics ranging from #contextCollapse to #federation to #moderation and everything in between. Does your choice of publishing tool set expectations about where your content might propagate, or whether it will be indexed by search engines? Should it? Do the limitations of your server (e.g. js;dr) imply limitations of where your posts go, or whether they can be searched or archived? Should they? When you post something publicly, are you truly posting it for a global audience for all time, or only for one or a few more limited #publics for an ephemerality? When you reply to a post, do you expect your reply to only be visible in the context you posted it, or do you expect it to travel alongside that post to anywhere it might propagate to? On the #IndieWeb, especially for public posts, some of these questions have easier and more obvious answers, because the intent of nearly all public IndieWeb posts is to interact across the web with other posts and sites, typically via the #Webmention protocol. However there are still questions. Are the expectations for a blog and blogging different from a social media site, whether a silo or an instance on a network? Is a personal website with posts still just a blog, or does it become something new when you start posting responses from your site, or receiving (e.g. via Webmention) and displaying responses from across the web to your posts on your site? Or is it now a \u201csocial website\u201d? If you have a social website, what is your responsibility for keeping it, well, social? Do you moderate Webmentions by default? Do you use the Vouch extension for some automatic moderation? Are #POSSE & #backfeed different from federation or are they the same thing from a user-perspective, with merely different names hinting at different implementations? Do you allow anyone from any site to respond or react to your posts? Or do you treat your social website like your home, and follow what I like to call a \u201chouse party protocol\u201d, only letting in those you know, and perhaps allowing them to bring a +1 or 2? I have many more questions. Each of these deserves thoughtful discussions, documentation of what different tools & services do today that we can try out, learn from, and use to make considered decisions when creating new things to post on and across websites. This is post 4 of #100PostsOfIndieWeb. #100Posts \u2190 https://tantek.com/2024/022/t1/indiewebcamp-brighton-planned \u2192 \ud83d\udd2e Post glossary: backfeed https://indieweb.org/backfeed blog https://indieweb.org/blog blogging https://indieweb.org/blogging comments https://indieweb.org/comments context collapse https://indieweb.org/context_collapse ephemerality https://indieweb.org/ephemerality js;dr https://indieweb.org/js;dr moderation https://indieweb.org/moderation POSSE https://indieweb.org/POSSE posts https://indieweb.org/posts publics https://indieweb.org/publics reply https://indieweb.org/reply Vouch https://indieweb.org/Vouch Webmention https://indieweb.org/Webmention \u2013 Tantek\n</div>",
"url": "https://snarfed.org/2024-01-23_snarfed-org-posted-a-great-overview-of-thoughtful-and-sometimes-heated-discussions-across-blogs-and-the-fediverse-about-how-freely-should-public-posts-comments-on-the-web-flow",
"object": "https://tantek.com/2024/023/t1/should-public-posts-flow-across-sites",
"actor": {
"objectType": "person",
"displayName": "Ryan Barrett",
"url": "https://snarfed.org/",
"image": [
{
"url": "https://secure.gravatar.com/avatar/947b5f3f323da0ef785b6f02d9c265d6?s=96&d=blank&r=g"
}
],
"id": "https://snarfed.org/"
},
"id": "https://snarfed.org/2024-01-23_snarfed-org-posted-a-great-overview-of-thoughtful-and-sometimes-heated-discussions-across-blogs-and-the-fediverse-about-how-freely-should-public-posts-comments-on-the-web-flow"
}
D 2024-01-24 03:44:12.063880+00:00 Replacing copies with originals: {}
I 2024-01-24 03:44:12.678120+00:00 Wrote Key('Object', 'https://snarfed.org/2024-01-23_snarfed-org-posted-a-great-overview-of-thoughtful-and-sometimes-heated-discussions-across-blogs-and-the-fediverse-about-how-freely-should-public-posts-comments-on-the-web-flow') {'labels': ['activity'], 'mf2': '...', 'object_ids': ['https://tantek.com/2024/023/t1/should-public-posts-flow-across-sites'], 'source_protocol': 'web', 'type': 'like', 'new': False, 'changed': False}
I 2024-01-24 03:44:13.279500+00:00 Wrote Key('Object', 'https://snarfed.org/2024-01-23_snarfed-org-posted-a-great-overview-of-thoughtful-and-sometimes-heated-discussions-across-blogs-and-the-fediverse-about-how-freely-should-public-posts-comments-on-the-web-flow') {'labels': ['activity'], 'mf2': '...', 'object_ids': ['https://tantek.com/2024/023/t1/should-public-posts-flow-across-sites'], 'source_protocol': 'web', 'type': 'like', 'users': [Key('MagicKey', 'snarfed.org')], 'new': True, 'changed': False}
I 2024-01-24 03:44:13.476543+00:00 Finding recipients and their targets
I 2024-01-24 03:44:13.480699+00:00 Raw targets: ['https://tantek.com/2024/023/t1/should-public-posts-flow-across-sites']
I 2024-01-24 03:44:13.484668+00:00 Skipping same-protocol target https://tantek.com/2024/023/t1/should-public-posts-flow-across-sites
I 2024-01-24 03:44:13.484904+00:00 Direct targets: dict_keys([])
I 2024-01-24 03:44:13.879970+00:00 Wrote Key('Object', 'https://snarfed.org/2024-01-23_snarfed-org-posted-a-great-overview-of-thoughtful-and-sometimes-heated-discussions-across-blogs-and-the-fediverse-about-how-freely-should-public-posts-comments-on-the-web-flow') {'labels': ['activity'], 'mf2': '...', 'object_ids': ['https://tantek.com/2024/023/t1/should-public-posts-flow-across-sites'], 'source_protocol': 'web', 'status': 'ignored', 'type': 'like', 'users': [Key('MagicKey', 'snarfed.org')], 'new': True, 'changed': False}
I 2024-01-24 03:44:13.880626+00:00 Returning 204: No targets, nothing to do ¯\_(ツ)_/¯
E 2024-01-24 03:44:13.881238+00:00 <class 'oauth_dropins.webutil.flask_util.NoContent'>: 204 No Content: No Content