RSS is kind of an invisible technology. People call RSS dead because you can’t see it. There’s no feed, no login, no analytics. RSS feels subsurface.
But I believe we’re living in a golden age of RSS. Blogging is booming. My feed reader has 280 feeds in it.
{
"type": "entry",
"published": "2022-05-01T09:06:52Z",
"url": "https://adactio.com/links/19038",
"category": [
"indieweb",
"personal",
"publishing",
"social",
"networks",
"rss",
"feeds",
"syndication",
"blogs",
"blogging",
"opml",
""
],
"bookmark-of": [
"https://tomcritchlow.com/2022/04/21/new-rss/"
],
"content": {
"text": "Increasing the surface area of blogging\n\n\n\n\n RSS is kind of an invisible technology. People call RSS dead because you can\u2019t see it. There\u2019s no feed, no login, no analytics. RSS feels subsurface.\n\n But I believe we\u2019re living in a golden age of RSS. Blogging is booming. My feed reader has 280 feeds in it.",
"html": "<h3>\n<a class=\"p-name u-bookmark-of\" href=\"https://tomcritchlow.com/2022/04/21/new-rss/\">\nIncreasing the surface area of blogging\n</a>\n</h3>\n\n<blockquote>\n <p>RSS is kind of an invisible technology. People call RSS dead because you can\u2019t see it. There\u2019s no feed, no login, no analytics. RSS feels subsurface.</p>\n\n <p>But I believe we\u2019re living in a golden age of RSS. Blogging is booming. My feed reader has 280 feeds in it.</p>\n</blockquote>"
},
"author": {
"type": "card",
"name": "Jeremy Keith",
"url": "https://adactio.com/",
"photo": "https://adactio.com/images/photo-150.jpg"
},
"post-type": "bookmark",
"_id": "28811483",
"_source": "2",
"_is_read": true
}
How is all this social? It’s just slow social. If you want to respond to me, publish something linking to what I said. If I want to respond to you, I publish something linking to what you wrote. Old school. Good school. It’s high-effort, but I think the required effort is a positive thing for a social network. Forces you to think more.
{
"type": "entry",
"published": "2022-05-01T09:05:01Z",
"url": "https://adactio.com/links/19037",
"category": [
"indieweb",
"personal",
"publishing",
"social",
"networks",
"rss",
"feeds",
"syndication",
"blogs",
"blogging"
],
"bookmark-of": [
"https://chriscoyier.net/2022/04/29/rss-3/"
],
"content": {
"text": "RSS - Chris Coyier\n\n\n\n\n How is all this social? It\u2019s just slow social. If you want to respond to me, publish something linking to what I said. If I want to respond to you, I publish something linking to what you wrote. Old school. Good school. It\u2019s high-effort, but I think the required effort is a positive thing for a social network. Forces you to think more.",
"html": "<h3>\n<a class=\"p-name u-bookmark-of\" href=\"https://chriscoyier.net/2022/04/29/rss-3/\">\nRSS - Chris Coyier\n</a>\n</h3>\n\n<blockquote>\n <p>How is all this social? It\u2019s just slow social. If you want to respond to me, publish something linking to what I said. If I want to respond to you, I publish something linking to what you wrote. Old school. Good school. It\u2019s high-effort, but I think the required effort is a positive thing for a social network. Forces you to think more.</p>\n</blockquote>"
},
"author": {
"type": "card",
"name": "Jeremy Keith",
"url": "https://adactio.com/",
"photo": "https://adactio.com/images/photo-150.jpg"
},
"post-type": "bookmark",
"_id": "28811484",
"_source": "2",
"_is_read": true
}
{
"type": "entry",
"published": "2022-04-30T16:15:00-07:00",
"url": "https://www.jeremycherfas.net/blog/how-to-fix-a-problem-with-gregwarimage",
"name": "How to fix a problem with Gregwar/Image",
"content": {
"text": "There is an IndieWebCamp going on in Dusseldorf, and during a session on the presentation of photos I thought about sharing my own efforts in that department. Then I discovered, to my horror, that search was completely broken on the website, in production and locally, where I tinker with things. Obv...",
"html": "<p>There is an IndieWebCamp going on in Dusseldorf, and during a session on the presentation of photos I thought about sharing my own efforts in that department. Then I discovered, to my horror, that search was completely broken on the website, in production and locally, where I tinker with things. Obv...</p>"
},
"author": {
"type": "card",
"name": "Jeremy Cherfas",
"url": "https://jeremycherfas.net",
"photo": "https://www.jeremycherfas.net/user/themes/tailwind/images/zoot.jpg"
},
"post-type": "article",
"_id": "28797877",
"_source": "202",
"_is_read": true
}
{
"type": "entry",
"published": "2022-04-29 09:59-0700",
"rsvp": "yes",
"url": "http://tantek.com/2022/119/t1/",
"in-reply-to": [
"https://events.indieweb.org/2022/04/indiewebcamp-d%C3%BCsseldorf-ht968fpXyhij"
],
"content": {
"text": "co-organizing @IndieWebCamp D\u00fcsseldorf this weekend with @marcthiele @calum_ryan @jkphl!\n\ud83d\uddd3 2022-04-30\u202605-01\n\ud83d\udccd @cgi_global\n\ud83c\udf9f https://btco.nf/iwcdus22\n\u2139\ufe0f https://indieweb.org/2022/DUS\n\nAlso excited for the @btconf main event! https://twitter.com/btconf/status/1519910629561319424",
"html": "co-organizing <a class=\"h-cassis-username\" href=\"https://twitter.com/IndieWebCamp\">@IndieWebCamp</a> D\u00fcsseldorf this weekend with <a class=\"h-cassis-username\" href=\"https://twitter.com/marcthiele\">@marcthiele</a> <a class=\"h-cassis-username\" href=\"https://twitter.com/calum_ryan\">@calum_ryan</a> <a class=\"h-cassis-username\" href=\"https://twitter.com/jkphl\">@jkphl</a>!<br />\ud83d\uddd3 2022-04-30\u202605-01<br />\ud83d\udccd <a class=\"h-cassis-username\" href=\"https://twitter.com/cgi_global\">@cgi_global</a><br />\ud83c\udf9f <a href=\"https://btco.nf/iwcdus22\">https://btco.nf/iwcdus22</a><br />\u2139\ufe0f <a href=\"https://indieweb.org/2022/DUS\">https://indieweb.org/2022/DUS</a><br /><br />Also excited for the <a class=\"h-cassis-username\" href=\"https://twitter.com/btconf\">@btconf</a> main event! <a href=\"https://twitter.com/btconf/status/1519910629561319424\">https://twitter.com/btconf/status/1519910629561319424</a>"
},
"author": {
"type": "card",
"name": "Tantek \u00c7elik",
"url": "http://tantek.com/",
"photo": "http://tantek.com/photo.jpg"
},
"post-type": "rsvp",
"refs": {
"https://events.indieweb.org/2022/04/indiewebcamp-d%C3%BCsseldorf-ht968fpXyhij": {
"type": "entry",
"url": "https://events.indieweb.org/2022/04/indiewebcamp-d%C3%BCsseldorf-ht968fpXyhij",
"name": "an IndieWeb event",
"post-type": "article"
}
},
"_id": "28783526",
"_source": "1",
"_is_read": true
}
@u_map_prop @olynch@mathstodon.xyz I remember a few years back trying to talk @johncarlosbaez into supporting this sort of syndication and webmentions on his site when he was irked at Google+ shutting down. Glad to see more people getting it working.
{
"type": "entry",
"published": "2022-04-28T19:16:20+00:00",
"url": "http://stream.boffosocko.com/2022/u_map_prop-olynchmathstodonxyz-i-remember-a-few-years-back-trying-to",
"syndication": [
"https://twitter.com/ChrisAldrich/status/1519757560865243138",
"https://mastodon.social/@chrisaldrich/108211301291345320"
],
"in-reply-to": [
"https://mathstodon.xyz/@olynch/108210438434780083",
"https://twitter.com/u_map_prop/status/1519702459517743106",
"https://owenlynch.org/posts/2022-04-28-mastodon/"
],
"content": {
"text": "@u_map_prop @olynch@mathstodon.xyz I remember a few years back trying to talk @johncarlosbaez into supporting this sort of syndication and webmentions on his site when he was irked at Google+ shutting down. Glad to see more people getting it working."
},
"author": {
"type": "card",
"name": "Chris Aldrich",
"url": "http://stream.boffosocko.com/profile/chrisaldrich",
"photo": "http://stream.boffosocko.com/file/600427b81f7785e704eadfe511a9270f/thumb.jpg"
},
"post-type": "reply",
"_id": "28761704",
"_source": "192",
"_is_read": true
}
{
"type": "entry",
"published": "2022-04-28T11:33:43Z",
"url": "https://adactio.com/journal/19029",
"category": [
"trust",
"suspicion",
"frontend",
"development",
"frameworks",
"libraries",
"code",
"browsers",
"compatibility",
"interoperability",
"native",
"features",
"css",
"javascript",
"jquery",
"react",
"bootstrap",
"blogging",
"responses",
"indieweb",
"blogs",
"conversation",
"discussion"
],
"name": "Suspicion",
"content": {
"text": "I\u2019ve already had some thoughtful responses to yesterday\u2019s post about trust. I wrapped up my thoughts with a request:\n\n\n I would love it if someone could explain why they\u2019re avoid native browser features but use third-party code.\n\n\nChris obliged:\n\n\n I can\u2019t speak for the industry, but I have a guess. Third-party code (like the referenced Bootstrap and React) have a history of smoothing over significant cross-browser issues and providing better-than-browser ergonomic APIs. jQuery was created to smooth over cross-browser JavaScript problems. That\u2019s trust.\n\n\nVery true! jQuery is the canonical example of a library smoothing over the bumpy landscape of browser compatibilities. But jQuery is also the canonical example of a library we no longer need because the browsers have caught up \u2026and those browsers support standards directly influenced by jQuery. That\u2019s a library success story!\n\nCharles Harries takes on my question in his post Libraries over browser features:\n\n\n I think this perspective of trust has been hammered into developers over the past maybe like 5 years of JavaScript development based almost exclusively on inequality of browser feature support. Things are looking good in 2022; but as recently as 2019, 4 of the 5 top web developer needs had to do with browser compatibility.\n \n Browser compatibility is one of the underlying promises that libraries\u2014especially the big ones that Jeremy references, like React and Bootstrap\u2014make to developers.\n\n\nSo again, it\u2019s browser incompatibilities that made libraries attractive.\n\nJim Nielsen responds with the same message in his post Trusting Browsers:\n\n\n We distrust the browser because we\u2019ve been trained to. Years of fighting browser deficiencies where libraries filled the gaps. Browser enemy; library friend.\n \n For example: jQuery did wonders to normalize working across browsers. Write code once, run it in any browser \u2014 confidently.\n\n\nThree for three. My question has been answered: people gravitated towards libraries because browsers had inconsistent implementations.\n\nI\u2019m deliberately using the past tense there. I think Jim is onto something when he says that we\u2019ve been trained not to trust browsers to have parity when it comes to supporting standards. But that has changed.\n\nCharles again:\n\n\n This approach isn\u2019t a sustainable practice, and I\u2019m trying to do as little of it as I can. Jeremy is right to be suspicious of third-party code. Cross-browser compatibility has gotten a lot better, and campaigns like Interop 2022 are doing a lot to reduce the burden. It\u2019s getting better, but the exasperated I-just-want-it-to-work mindset is tough to uninstall.\n\n\nI agree. Inertia is a powerful force. No matter how good cross-browser compatibility gets, it\u2019s going to take a long time for developers to shed their suspicion.\n\nJim is glass-half-full kind of guy:\n\n\n I\u2019m optimistic that trust in browser-native features and APIs is being restored.\n\n\nHe also points to a very sensible mindset when it comes to third-party libraries and frameworks:\n\n\n In this sense, third-party code and abstractions can be wonderful polyfills for the web platform. The idea being that the default posture should be: leverage as much of the web platform as possible, then where there are gaps to creating great user experiences, fill them in with exploratory library or framework features (features which, conceivably, could one day become native in browsers).\n\n\nYes! A kind of progressive enhancement approach to using third-party code makes a lot of sense. I\u2019ve always maintained that you should treat libraries and frameworks like cattle, not pets. Don\u2019t get too attached. If the library is solving a genuine need, it will be replaced by stable web standards in browsers (again, see jQuery).\n\nI think that third-party libraries and frameworks work best as polyfills. But the whole point of polyfills is that you only use them when the browsers don\u2019t supply features natively (and you also go back and remove the polyfill later when browsers do support the feature). But that\u2019s not how people are using libraries and frameworks today. Developers are reaching for them by default instead of treating them as a last resort.\n\nI like Jim\u2019s proposed design princple:\n\n\n Where available, default to browser-native features over third party code, abstractions, or idioms.\n\n\n(P.S. It\u2019s kind of lovely to see this kind of thoughtful blog-to-blog conversation happening. Right at a time when Twitter is about to go down the tubes, this is a demonstration of an actual public square with more nuanced discussion. Make your own website and join the conversation!)",
"html": "<p>I\u2019ve already had some thoughtful responses to yesterday\u2019s post about <a href=\"https://adactio.com/journal/19021\">trust</a>. I wrapped up my thoughts with a request:</p>\n\n<blockquote>\n <p>I would love it if someone could explain why they\u2019re avoid native browser features but use third-party code.</p>\n</blockquote>\n\n<p><a href=\"https://chriscoyier.net/2022/04/27/trust/\">Chris obliged</a>:</p>\n\n<blockquote>\n <p>I can\u2019t speak for the industry, but I have a guess. Third-party code (like the referenced Bootstrap and React) have a history of smoothing over significant cross-browser issues and providing better-than-browser ergonomic APIs. jQuery was created to smooth over cross-browser JavaScript problems. That\u2019s trust.</p>\n</blockquote>\n\n<p>Very true! jQuery is the canonical example of a library smoothing over the bumpy landscape of browser compatibilities. But jQuery is also the canonical example of a library we no longer need because the browsers have caught up \u2026and those browsers support standards directly influenced by jQuery. That\u2019s a library success story!</p>\n\n<p>Charles Harries takes on my question in his post <a href=\"https://charlesharri.es/stream/libraries-over-browser-features\">Libraries over browser features</a>:</p>\n\n<blockquote>\n <p>I think this perspective of trust has been hammered into developers over the past maybe like 5 years of JavaScript development based almost exclusively on inequality of browser feature support. Things are looking good in 2022; but as recently as 2019, <a href=\"https://insights.developer.mozilla.org/reports/mdn-web-developer-needs-assessment-2019.html#needs-assessment-overall-needs-ranking\">4 of the 5 top web developer needs</a> had to do with browser compatibility.</p>\n \n <p>Browser compatibility is one of the underlying promises that libraries\u2014especially the big ones that Jeremy references, like React and Bootstrap\u2014make to developers.</p>\n</blockquote>\n\n<p>So again, it\u2019s browser incompatibilities that made libraries attractive.</p>\n\n<p>Jim Nielsen responds with the same message in his post <a href=\"https://blog.jim-nielsen.com/2022/trusting-browsers/\">Trusting Browsers</a>:</p>\n\n<blockquote>\n <p>We distrust the browser because we\u2019ve been trained to. Years of fighting browser deficiencies where libraries filled the gaps. Browser enemy; library friend.</p>\n \n <p>For example: jQuery did wonders to normalize working across browsers. Write code once, run it in any browser \u2014 confidently.</p>\n</blockquote>\n\n<p>Three for three. My question has been answered: people gravitated towards libraries because browsers had inconsistent implementations.</p>\n\n<p>I\u2019m deliberately using the past tense there. I think Jim is onto something when he says that we\u2019ve been trained not to trust browsers to have parity when it comes to supporting standards. But that has changed.</p>\n\n<p>Charles again:</p>\n\n<blockquote>\n <p>This approach isn\u2019t a sustainable practice, and I\u2019m trying to do as little of it as I can. Jeremy is right to be suspicious of third-party code. Cross-browser compatibility has gotten a lot better, and campaigns like <a href=\"https://web.dev/interop-2022/\">Interop 2022</a> are doing <em>a lot</em> to reduce the burden. It\u2019s getting better, but the exasperated I-just-want-it-to-work mindset is tough to uninstall.</p>\n</blockquote>\n\n<p>I agree. Inertia is a powerful force. No matter how good cross-browser compatibility gets, it\u2019s going to take a long time for developers to shed their suspicion.</p>\n\n<p>Jim is glass-half-full kind of guy:</p>\n\n<blockquote>\n <p>I\u2019m optimistic that trust in browser-native features and APIs is being restored.</p>\n</blockquote>\n\n<p>He also points to a very sensible mindset when it comes to third-party libraries and frameworks:</p>\n\n<blockquote>\n <p>In this sense, third-party code and abstractions can be wonderful polyfills for the web platform. The idea being that the default posture should be: leverage as much of the web platform as possible, then where there are gaps to creating great user experiences, fill them in with exploratory library or framework features (features which, conceivably, could one day become native in browsers).</p>\n</blockquote>\n\n<p>Yes! A kind of progressive enhancement approach to using third-party code makes a lot of sense. I\u2019ve always maintained that you should treat libraries and frameworks like cattle, not pets. Don\u2019t get too attached. If the library is solving a genuine need, it will be replaced by stable web standards in browsers (again, see jQuery).</p>\n\n<p>I think that third-party libraries and frameworks work best as polyfills. But the whole point of polyfills is that you only use them when the browsers don\u2019t supply features natively (and you also go back and remove the polyfill later when browsers <em>do</em> support the feature). But that\u2019s not how people are using libraries and frameworks today. Developers are reaching for them by default instead of treating them as a last resort.</p>\n\n<p>I like Jim\u2019s proposed design princple:</p>\n\n<blockquote>\n <p>Where available, default to browser-native features over third party code, abstractions, or idioms.</p>\n</blockquote>\n\n<p>(P.S. It\u2019s kind of lovely to see this kind of thoughtful blog-to-blog conversation happening. Right at a time when Twitter is about to go down the tubes, this is a demonstration of an <em>actual</em> public square with more nuanced discussion. Make your own website and join the conversation!)</p>"
},
"author": {
"type": "card",
"name": "Jeremy Keith",
"url": "https://adactio.com/",
"photo": "https://adactio.com/images/photo-150.jpg"
},
"post-type": "article",
"_id": "28750869",
"_source": "2",
"_is_read": true
}
{
"type": "entry",
"author": {
"name": "fluffy",
"url": "http://beesbuzz.biz/",
"photo": null
},
"url": "http://beesbuzz.biz/blog/3951-Twitter-alternatives",
"published": "2022-04-27T16:36:32-07:00",
"content": {
"html": "<p>Because of Twitter\u2019s <a href=\"https://www.nbcnews.com/tech/tech-news/elon-musk-reaches-deal-buy-twitter-rcna25806\">impending buyout</a> a lot of people are talking about alternatives to Twitter, including Mastodon. I could write a bunch of long rambles about this, but I already have:</p>\n<ul><li><a href=\"http://beesbuzz.biz/blog/1912-Slowcial-networking\">Slowcial networking</a></li>\n<li><a href=\"http://beesbuzz.biz/blog/2316-Distributed-toxicity-and-the-IndieWeb\">Distributed toxicity and the IndieWeb</a></li>\n<li><a href=\"http://beesbuzz.biz/blog/12455-Indieweb-vs-Fediverse\">Indieweb vs. Fediverse</a></li>\n</ul><p>Basically, my problem with Twitter isn\u2019t that it\u2019s centralized, but that it\u2019s Twitter.</p>\n\n\n<h3><a href=\"http://beesbuzz.biz/blog/3951-Twitter-alternatives#3951_h3_1_Mastodon\"></a>Mastodon</h3><p>Mastodon has some good stuff going for it; communities can be small and it can be an easy way for folks to share things without needing An Blog\u2122. But it\u2019s still an environment where much of the motivation is around hot takes and cold takedowns. I see so much toxicity take place all the time from people criticizing each other and turning a simple misunderstanding into a Fediverse-wide dogpile. Perhaps not to the same extent as what happens on Twitter daily, but it happens, and it\u2019s getting worse.</p><p>There are also many, many technological issues with Mastodon which need addressing. The biggest one is the privacy model. <em>At best</em> you can sorta-limit a post\u2019s reach, but the permissions are precisely inverted (since it\u2019s based on sending it to people who follow you, rather than people you follow, or better yet a <a href=\"http://beesbuzz.biz/blog/12341-Private-friends-only-IndieWeb-stuff\">fullly-controled access model</a>, but also what few privacy options <em>do</em> exist are mostly a veneer around an insecure protocol. Your DMs are visible to the admin of your instance, as well as the admins on the instance that you\u2019re messaging, for example.</p><p>Mastodon, being ActivityPub, also aspires to interoperate with other ActivityPub things, but this leads to even more of a mismatch. Not all ActivityPub things are built with a Mastodon experience in mind, and even things that are Mastodon-like (such as Pleroma) don\u2019t abide by the same security model. As I understand it, \u201cunboostable\u201d Mastodon toots are still quite boostable from Pleroma. Including DMs.</p><p>The entire privacy model is also predicated on ActivityPub being push-based; the way a post is \u201cprivate\u201d is simply by it not being available in an outbox/feed. This means that there\u2019s no way for followers to backfill when granted access.</p><p>ActivityPub being purely push-based also exacerbates some reliability and scaling issues. If an instance goes down, then other instances trying to send a message to it get stuck in a retry loop. A much better approach is for failed pushes to just fall on the floor and for the instance to backfill them through a pull when it comes back online. Which is exactly how RSS/Atom + WebSub works, <a href=\"http://beesbuzz.biz/blog/2535-ActivityPub-hot-take\">just saying</a>.</p><p>I <em>appreciate</em> the interactions I have <a href=\"http://beesbuzz.biz/mastodon\">on Mastodon</a> and it\u2019s definitely an environment which is\u2026 less <em>bad</em> than Twitter. But it still leaves a lot to be desired, and if Mastodon were to get as popular as Twitter, it\u2019ll have many of the same problems, and probably plenty of new ones too.</p><p>I know I sound like a broken record on this, but my preferred way of publishing and sharing my thoughts remains posting to this site and having the interactions take place here. The unfortunate reality is that most people only follow me on Twitter and Mastodon so I will continue to <a href=\"https://indieweb.org/POSSE\">POSSE</a> my posts there, and it\u2019ll be a long time before I can stop posting the \u201cprivacy stub\u201d posts for my <a href=\"http://beesbuzz.biz/3922\">authenticated posts</a>, but that\u2019s the balance I\u2019m comfortable with.</p><p>The blog does present a barrier to being able to quickly share my thoughts with the world, but it turns out I <a href=\"http://beesbuzz.biz/blog/1912-Slowcial-networking\">don\u2019t really need to do that anyway</a>; I\u2019m not an Influencer\u2122 and I don\u2019t really desire to be one, either.</p><p>I do still <a href=\"https://plush.city/@fluffy/106597162850559257\">have fun on Mastodon</a>, and I occasionally <a href=\"https://twitter.com/fluffy/with_replies\">fall into conversations on Twitter</a>, but I\u2019m finding myself doing less and less of that, and I feel like I\u2019m better for it.</p><h3><a href=\"http://beesbuzz.biz/blog/3951-Twitter-alternatives#3951_h3_2_Tumblr\"></a>Tumblr</h3><p>My big hope is that Tumblr realizes that they\u2019re in a really good position to become an IndieWeb provider, and does so. It wouldn\u2019t take much for them, either:</p>\n<ul><li>Allow subscribing to external RSS/Atom feeds</li>\n<li>Accept external <a href=\"https://indieweb.org/webmention\">webmentions</a> as notes</li>\n<li>Send webmentions for reblogs of external items (which would require removing the <code>href.li</code> link wrappers, but it\u2019s incredibly unclear what purpose those serve anyway)</li>\n</ul><p>Tumblr has found that they Get It and know how to build a social networking site that\u2019s not completely awful, and their current renaissance (with their experiments in monetization, ad-free and \u201cblaze\u201d in particular) has them on a really good path forward. Tumblr also still has many of the toxicity problems inherent in a wide-scale timeline-based quick-interaction social network, but I\u2019d be much more comfortable with the idea of social media turning more Tumblr-like than it turning more Twitter-like.</p><h3><a href=\"http://beesbuzz.biz/blog/3951-Twitter-alternatives#3951_h3_3_Facebook\"></a>Facebook</h3><p>As much as I dislike Facebook, it does have some stuff going for it:</p>\n<ul><li>A good privacy model</li>\n<li>Moderated user groups</li>\n</ul><p>The user-facing privacy model isn\u2019t too far-removed from how I implemented privacy in Publ (which was modeled after Google+\u2019s \u201ccircles\u201d concept, incidentally), and user groups just feel like a special case of <a href=\"https://indieweb.org/u-syndication\">syndication</a> (as implemented on e.g. <a href=\"https://news.indieweb.org/en/submit\">IndieWeb News</a>). Distributed privacy is <a href=\"http://beesbuzz.biz/blog/12341-Private-friends-only-IndieWeb-stuff\">a work in progress</a> but great strides have taken place. There\u2019s still a long ways to go, though, especially around use cases like webmention. But lack of post privacy clearly hasn\u2019t been a detriment to folks using Twitter or Mastodon so far.</p><p>(Twitter <em>does</em> provide \u201clocked accounts\u201d but those are a pretty gnarly hack and break a lot of things, even on Twitter. Needing multiple identities to curate an audience is not a scalable solution either way.)</p><h3><a href=\"http://beesbuzz.biz/blog/3951-Twitter-alternatives#3951_h3_4_Blogging-or-just-dont-do-social\"></a>Blogging (or: just don\u2019t do social media)</h3><p>I feel like in general, humans just weren\u2019t built to be so interconnected. We operate best when we have small, localized communities of shared interest. Expanding out from that based on referrals works well. Being forced to operate at large scale thanks to algorithmic discovery just leads to problems all around.</p><p>When I write a blog entry, it\u2019s mostly to keep my friends in the loop on what\u2019s going on with me, or to share some sort of unstructured musing (such as this). I also have control over the presentation based on the sort of content it is; this website isn\u2019t one-size-fits-all, and I can post <a href=\"http://beesbuzz.biz/\">all sorts of other things</a> to it, each with a presentation that\u2019s better for the content in question (and allows for easier perusal). I also still don\u2019t really care about instant engagement. I want people to come across is organically, while perusing the Internet or doing a search. I love seeing conversations pop up on other sites (yes, even Hacker News and Reddit) without it necessarily being put on my doorstep. I also keep my comments mostly open (but <a href=\"http://beesbuzz.biz/comment-policy\">moderated</a>) because that\u2019s an interaction model that I\u2019m comfortable with.</p><p>I like that I can keep control over my own domain, and that I\u2019m not subject to the rules of the platform, or needing Maximum Engagement to generate ad revenue and so on. And I can choose not to allow abusive responses or spam to be a part of what I present along with my own subject matter.</p><p>And most of all, I like that a single unhinged billionaire can\u2019t decide to take over my personal website as part of a categorical power grab.</p>\n\n<p><a href=\"http://beesbuzz.biz/blog/3951-Twitter-alternatives#comments\">comments</a></p>",
"text": "Because of Twitter\u2019s impending buyout a lot of people are talking about alternatives to Twitter, including Mastodon. I could write a bunch of long rambles about this, but I already have:\nSlowcial networking\nDistributed toxicity and the IndieWeb\nIndieweb vs. Fediverse\nBasically, my problem with Twitter isn\u2019t that it\u2019s centralized, but that it\u2019s Twitter.\n\n\nMastodonMastodon has some good stuff going for it; communities can be small and it can be an easy way for folks to share things without needing An Blog\u2122. But it\u2019s still an environment where much of the motivation is around hot takes and cold takedowns. I see so much toxicity take place all the time from people criticizing each other and turning a simple misunderstanding into a Fediverse-wide dogpile. Perhaps not to the same extent as what happens on Twitter daily, but it happens, and it\u2019s getting worse.There are also many, many technological issues with Mastodon which need addressing. The biggest one is the privacy model. At best you can sorta-limit a post\u2019s reach, but the permissions are precisely inverted (since it\u2019s based on sending it to people who follow you, rather than people you follow, or better yet a fullly-controled access model, but also what few privacy options do exist are mostly a veneer around an insecure protocol. Your DMs are visible to the admin of your instance, as well as the admins on the instance that you\u2019re messaging, for example.Mastodon, being ActivityPub, also aspires to interoperate with other ActivityPub things, but this leads to even more of a mismatch. Not all ActivityPub things are built with a Mastodon experience in mind, and even things that are Mastodon-like (such as Pleroma) don\u2019t abide by the same security model. As I understand it, \u201cunboostable\u201d Mastodon toots are still quite boostable from Pleroma. Including DMs.The entire privacy model is also predicated on ActivityPub being push-based; the way a post is \u201cprivate\u201d is simply by it not being available in an outbox/feed. This means that there\u2019s no way for followers to backfill when granted access.ActivityPub being purely push-based also exacerbates some reliability and scaling issues. If an instance goes down, then other instances trying to send a message to it get stuck in a retry loop. A much better approach is for failed pushes to just fall on the floor and for the instance to backfill them through a pull when it comes back online. Which is exactly how RSS/Atom + WebSub works, just saying.I appreciate the interactions I have on Mastodon and it\u2019s definitely an environment which is\u2026 less bad than Twitter. But it still leaves a lot to be desired, and if Mastodon were to get as popular as Twitter, it\u2019ll have many of the same problems, and probably plenty of new ones too.I know I sound like a broken record on this, but my preferred way of publishing and sharing my thoughts remains posting to this site and having the interactions take place here. The unfortunate reality is that most people only follow me on Twitter and Mastodon so I will continue to POSSE my posts there, and it\u2019ll be a long time before I can stop posting the \u201cprivacy stub\u201d posts for my authenticated posts, but that\u2019s the balance I\u2019m comfortable with.The blog does present a barrier to being able to quickly share my thoughts with the world, but it turns out I don\u2019t really need to do that anyway; I\u2019m not an Influencer\u2122 and I don\u2019t really desire to be one, either.I do still have fun on Mastodon, and I occasionally fall into conversations on Twitter, but I\u2019m finding myself doing less and less of that, and I feel like I\u2019m better for it.TumblrMy big hope is that Tumblr realizes that they\u2019re in a really good position to become an IndieWeb provider, and does so. It wouldn\u2019t take much for them, either:\nAllow subscribing to external RSS/Atom feeds\nAccept external webmentions as notes\nSend webmentions for reblogs of external items (which would require removing the href.li link wrappers, but it\u2019s incredibly unclear what purpose those serve anyway)\nTumblr has found that they Get It and know how to build a social networking site that\u2019s not completely awful, and their current renaissance (with their experiments in monetization, ad-free and \u201cblaze\u201d in particular) has them on a really good path forward. Tumblr also still has many of the toxicity problems inherent in a wide-scale timeline-based quick-interaction social network, but I\u2019d be much more comfortable with the idea of social media turning more Tumblr-like than it turning more Twitter-like.FacebookAs much as I dislike Facebook, it does have some stuff going for it:\nA good privacy model\nModerated user groups\nThe user-facing privacy model isn\u2019t too far-removed from how I implemented privacy in Publ (which was modeled after Google+\u2019s \u201ccircles\u201d concept, incidentally), and user groups just feel like a special case of syndication (as implemented on e.g. IndieWeb News). Distributed privacy is a work in progress but great strides have taken place. There\u2019s still a long ways to go, though, especially around use cases like webmention. But lack of post privacy clearly hasn\u2019t been a detriment to folks using Twitter or Mastodon so far.(Twitter does provide \u201clocked accounts\u201d but those are a pretty gnarly hack and break a lot of things, even on Twitter. Needing multiple identities to curate an audience is not a scalable solution either way.)Blogging (or: just don\u2019t do social media)I feel like in general, humans just weren\u2019t built to be so interconnected. We operate best when we have small, localized communities of shared interest. Expanding out from that based on referrals works well. Being forced to operate at large scale thanks to algorithmic discovery just leads to problems all around.When I write a blog entry, it\u2019s mostly to keep my friends in the loop on what\u2019s going on with me, or to share some sort of unstructured musing (such as this). I also have control over the presentation based on the sort of content it is; this website isn\u2019t one-size-fits-all, and I can post all sorts of other things to it, each with a presentation that\u2019s better for the content in question (and allows for easier perusal). I also still don\u2019t really care about instant engagement. I want people to come across is organically, while perusing the Internet or doing a search. I love seeing conversations pop up on other sites (yes, even Hacker News and Reddit) without it necessarily being put on my doorstep. I also keep my comments mostly open (but moderated) because that\u2019s an interaction model that I\u2019m comfortable with.I like that I can keep control over my own domain, and that I\u2019m not subject to the rules of the platform, or needing Maximum Engagement to generate ad revenue and so on. And I can choose not to allow abusive responses or spam to be a part of what I present along with my own subject matter.And most of all, I like that a single unhinged billionaire can\u2019t decide to take over my personal website as part of a categorical power grab.\n\ncomments"
},
"name": "fluffy rambles: Twitter alternatives",
"post-type": "article",
"_id": "28744354",
"_source": "3782",
"_is_read": true
}
@alexwilliams Micro.blog is an inexpensive turnkey IndieWeb friendly solution for doing something like that. Bring your own domain or subdomain and you're off to the races with all the benefits and none of the overhead or work.
{
"type": "entry",
"published": "2022-04-28T01:19:30+00:00",
"url": "http://stream.boffosocko.com/2022/alexwilliams-microblog-is-an-inexpensive-turnkey-indieweb-friendly-solution-for",
"syndication": [
"https://twitter.com/ChrisAldrich/status/1519486486911008772"
],
"in-reply-to": [
"https://twitter.com/alexwilliams/status/1519357286870749185"
],
"content": {
"text": "@alexwilliams Micro.blog is an inexpensive turnkey IndieWeb friendly solution for doing something like that. Bring your own domain or subdomain and you're off to the races with all the benefits and none of the overhead or work.",
"html": "<a href=\"https://twitter.com/alexwilliams\">@alexwilliams</a> Micro.blog is an inexpensive turnkey IndieWeb friendly solution for doing something like that. Bring your own domain or subdomain and you're off to the races with all the benefits and none of the overhead or work."
},
"author": {
"type": "card",
"name": "Chris Aldrich",
"url": "http://stream.boffosocko.com/profile/chrisaldrich",
"photo": "http://stream.boffosocko.com/file/600427b81f7785e704eadfe511a9270f/thumb.jpg"
},
"post-type": "reply",
"_id": "28743385",
"_source": "192",
"_is_read": true
}
@wynlim Your site is awesome. I love the design/simplicity, ideas, & writing. I'm seeing so many topics/collections I love including digital gardens, notes, IndieWeb, etc., and you're following so many people I know and read myself. Such a small world.
{
"type": "entry",
"published": "2022-04-27T23:06:42+00:00",
"url": "http://stream.boffosocko.com/2022/wynlim-your-site-is-awesome-i-love-the-designsimplicity-ideas",
"syndication": [
"https://twitter.com/ChrisAldrich/status/1519453039739949057"
],
"in-reply-to": [
"https://twitter.com/wynlim/status/1519450366030807041",
"http://stream.boffosocko.com/2022/peterhagen_-i-suspect-youll-appreciate-some-of-the-ideas-and"
],
"content": {
"text": "@wynlim Your site is awesome. I love the design/simplicity, ideas, & writing. I'm seeing so many topics/collections I love including digital gardens, notes, IndieWeb, etc., and you're following so many people I know and read myself. Such a small world.",
"html": "@wynlim Your site is awesome. I love the design/simplicity, ideas, & writing. I'm seeing so many topics/collections I love including digital gardens, notes, IndieWeb, etc., and you're following so many people I know and read myself. Such a small world."
},
"author": {
"type": "card",
"name": "Chris Aldrich",
"url": "http://stream.boffosocko.com/profile/chrisaldrich",
"photo": "http://stream.boffosocko.com/file/600427b81f7785e704eadfe511a9270f/thumb.jpg"
},
"post-type": "reply",
"_id": "28741738",
"_source": "192",
"_is_read": true
}
@okikio_dev This is a good place to start: https://indieweb.org/Webmention
There are lots of implementations in many languages you can use as examples or borrow from. Ask in chat.indieweb.org/dev/ for pointers/advice/help to cut through documentation and jargon.
{
"type": "entry",
"published": "2022-04-27T19:24:54+00:00",
"url": "http://stream.boffosocko.com/2022/okikio_dev-this-is-a-good-place-to-start-webmentionthere-are",
"syndication": [
"https://twitter.com/ChrisAldrich/status/1519397310932955137"
],
"in-reply-to": [
"https://twitter.com/okikio_dev/status/1519003572037378050"
],
"content": {
"text": "@okikio_dev This is a good place to start: https://indieweb.org/Webmention\n\nThere are lots of implementations in many languages you can use as examples or borrow from. Ask in chat.indieweb.org/dev/ for pointers/advice/help to cut through documentation and jargon.",
"html": "<a href=\"https://twitter.com/okikio_dev\">@okikio_dev</a> This is a good place to start: <a href=\"https://indieweb.org/Webmention\">https://indieweb.org/Webmention</a><br />\nThere are lots of implementations in many languages you can use as examples or borrow from. Ask in chat.indieweb.org/dev/ for pointers/advice/help to cut through documentation and jargon."
},
"author": {
"type": "card",
"name": "Chris Aldrich",
"url": "http://stream.boffosocko.com/profile/chrisaldrich",
"photo": "http://stream.boffosocko.com/file/600427b81f7785e704eadfe511a9270f/thumb.jpg"
},
"post-type": "reply",
"_id": "28737679",
"_source": "192",
"_is_read": true
}
Twitter’s only conclusion can be abandonment: an overdue MySpace-ification. I am totally confident about this prediction, but that’s an easy confidence, because in the long run, we’re all MySpace-ified.
What Robin said.
{
"type": "entry",
"published": "2022-04-27T08:45:51Z",
"url": "https://adactio.com/links/19020",
"category": [
"twitter",
"social",
"networks",
"silos",
"indieweb",
"myspace",
"platforms"
],
"bookmark-of": [
"https://www.robinsloan.com/lab/lost-thread/"
],
"content": {
"text": "The lost thread\n\n\n\n\n Twit\u00adter\u2019s only con\u00adclu\u00adsion can be abandonment: an over\u00addue MySpace-ification. I am totally con\u00adfi\u00addent about this prediction, but that\u2019s an easy confidence, because in the long run, we\u2019re all MySpace-ified.\n\n\nWhat Robin said.",
"html": "<h3>\n<a class=\"p-name u-bookmark-of\" href=\"https://www.robinsloan.com/lab/lost-thread/\">\nThe lost thread\n</a>\n</h3>\n\n<blockquote>\n <p>Twit\u00adter\u2019s only con\u00adclu\u00adsion can be abandonment: an over\u00addue MySpace-ification. I am totally con\u00adfi\u00addent about this prediction, but that\u2019s an easy confidence, because in the long run, we\u2019re all MySpace-ified.</p>\n</blockquote>\n\n<p>What Robin said.</p>"
},
"author": {
"type": "card",
"name": "Jeremy Keith",
"url": "https://adactio.com/",
"photo": "https://adactio.com/images/photo-150.jpg"
},
"post-type": "bookmark",
"_id": "28725315",
"_source": "2",
"_is_read": true
}
@lauren_n_roth I'd buy! I can't wait to see what you come up with...
I've been helping to collect some prior art, examples, and UI patterns here if it helps to jumpstart your research/work: https://indieweb.org/directory
{
"type": "entry",
"published": "2022-04-26T22:49:40+00:00",
"url": "http://stream.boffosocko.com/2022/lauren_n_roth-id-buy-i-cant-wait-to-see-what-you",
"syndication": [
"https://twitter.com/ChrisAldrich/status/1519086420916424707"
],
"in-reply-to": [
"https://twitter.com/lauren_n_roth/status/1518646498992480257"
],
"content": {
"text": "@lauren_n_roth I'd buy! I can't wait to see what you come up with...\n\nI've been helping to collect some prior art, examples, and UI patterns here if it helps to jumpstart your research/work: https://indieweb.org/directory",
"html": "<a href=\"https://twitter.com/lauren_n_roth\">@lauren_n_roth</a> I'd buy! I can't wait to see what you come up with...<br />\nI've been helping to collect some prior art, examples, and UI patterns here if it helps to jumpstart your research/work: <a href=\"https://indieweb.org/directory\">https://indieweb.org/directory</a>"
},
"author": {
"type": "card",
"name": "Chris Aldrich",
"url": "http://stream.boffosocko.com/profile/chrisaldrich",
"photo": "http://stream.boffosocko.com/file/600427b81f7785e704eadfe511a9270f/thumb.jpg"
},
"post-type": "reply",
"_id": "28717045",
"_source": "192",
"_is_read": true
}
Welcome to all new faces. I hope some of you become passionate about the indieweb and our slice of it 🙂
{
"type": "entry",
"author": {
"name": "Fabio Russo",
"url": "https://fabiorusso.net",
"photo": "https://micro.blog/fabio/avatar.jpg"
},
"url": "https://www.fabiorusso.net/2022/04/26/welcome-to-all.html",
"content": {
"html": "<p>Welcome to all new faces. I hope some of you become passionate about the <a href=\"https://indieweb.org\">indieweb</a> and our slice of it \ud83d\ude42</p>",
"text": "Welcome to all new faces. I hope some of you become passionate about the indieweb and our slice of it \ud83d\ude42"
},
"published": "2022-04-26T14:16:32+00:00",
"post-type": "note",
"_id": "33380002",
"_source": "7224",
"_is_read": true
}
Not sure why, but seems like a lot of people on Twitter are sharing this link about downloading an archive of your data: https://twitter.com/settings/download_your_data
#OwnYourData #IndieWeb
{
"type": "entry",
"published": "2022-04-26T00:41:33+00:00",
"url": "http://stream.boffosocko.com/2022/not-sure-why-but-seems-like-a-lot-of-people",
"category": [
"OwnYourData",
"IndieWeb"
],
"syndication": [
"https://twitter.com/ChrisAldrich/status/1518752791665287169"
],
"content": {
"text": "Not sure why, but seems like a lot of people on Twitter are sharing this link about downloading an archive of your data: https://twitter.com/settings/download_your_data\n#OwnYourData #IndieWeb",
"html": "Not sure why, but seems like a lot of people on Twitter are sharing this link about downloading an archive of your data: <a href=\"https://twitter.com/settings/download_your_data\">https://twitter.com/settings/download_your_data</a><br /><a href=\"http://stream.boffosocko.com/tag/OwnYourData\" class=\"p-category\">#OwnYourData</a> <a href=\"http://stream.boffosocko.com/tag/IndieWeb\" class=\"p-category\">#IndieWeb</a>"
},
"author": {
"type": "card",
"name": "Chris Aldrich",
"url": "http://stream.boffosocko.com/profile/chrisaldrich",
"photo": "http://stream.boffosocko.com/file/600427b81f7785e704eadfe511a9270f/thumb.jpg"
},
"post-type": "note",
"_id": "28695212",
"_source": "192",
"_is_read": true
}
{
"type": "entry",
"published": "2022-04-25T18:38:18+02:00",
"url": "https://notiz.blog/2022/04/25/die-twitter-posse/",
"name": "Die (Twitter) Posse",
"content": {
"text": "Im modernen Sprachgebrauch wird der Begriff [Posse] in \u00fcbertragenem Sinn [\u2026] genutzt, um als grotesk empfundene Vorg\u00e4nge in Gesellschaft und Politik zu beschreiben.\nhttps://de.wikipedia.org/wiki/Posse\n\n\n\n\nWer sich (aus gegebenem Anlass) sorgen um Twitter macht, sollte sich mal mit der etwas anderen POSSE befassen.\n\n\n\n\nPOSSE is an abbreviation for Publish (on your) Own Site, Syndicate Elsewhere, the practice of posting content on your own site first, then publishing copies or sharing links to third parties (like social media silos) with original post links to provide viewers a path to directly interacting with your content.\nhttps://indieweb.org/POSSE\n\n\n\n\nInstalliert euch WordPress! Ver\u00f6ffentlicht Texte, Bilder, Videos und Ideen nicht auf Twitter sondern auf eurer eigenen Seite! Teilt eure Inhalte \u00fcber Twitter!\n\n\n\nUnd sollte Twitter \u201everschwinden\u201c, teilt es \u00fcber Mastodon! usw, usw\u2026\n\n\n\nSchaut euch dazu gerne auch mal Brid.gy an!",
"html": "<blockquote>\n<p>Im modernen Sprachgebrauch wird der Begriff [Posse] in \u00fcbertragenem Sinn [\u2026] genutzt, um als grotesk empfundene Vorg\u00e4nge in Gesellschaft und Politik zu beschreiben.</p>\n<a href=\"https://de.wikipedia.org/wiki/Posse\">https://de.wikipedia.org/wiki/Posse</a>\n</blockquote>\n\n\n\n<p>Wer sich (<a href=\"https://www.faz.net/aktuell/wirtschaft/unternehmen/twitter-offenbar-doch-zum-verkauf-bereit-was-hat-elon-musk-vor-17982559.html\">aus gegebenem Anlass</a>) sorgen um Twitter macht, sollte sich mal mit der etwas anderen <strong>POSSE</strong> befassen.</p>\n\n\n\n<blockquote>\n<p><strong>POSSE</strong> is an abbreviation for <strong>Publish (on your) Own Site, <a href=\"https://indieweb.org/Category:syndication\">Syndicate</a> Elsewhere</strong>, the practice of posting content on your own site first, then publishing copies or sharing links to third parties (like <a href=\"https://indieweb.org/social_media\">social media</a> silos) with <a href=\"https://indieweb.org/original_post_link\">original post links</a> to provide viewers a path to directly interacting with your content.</p>\n<a href=\"https://indieweb.org/POSSE\">https://indieweb.org/POSSE</a>\n</blockquote>\n\n\n\n<p>Installiert euch WordPress! Ver\u00f6ffentlicht Texte, Bilder, Videos und Ideen nicht auf Twitter sondern auf eurer eigenen Seite! Teilt eure Inhalte \u00fcber Twitter!</p>\n\n\n\n<p>Und <a href=\"https://indieweb.org/site-deaths\">sollte Twitter \u201everschwinden\u201c</a>, <a href=\"https://notiz.blog/2020/12/31/activitypub-fuer-wordpress/\">teilt es \u00fcber Mastodon</a>! usw, usw\u2026</p>\n\n\n\n<p>Schaut euch dazu gerne auch mal <a href=\"https://notiz.blog/2014/01/16/bridgy-webmentions-fuer-twitter-und-facebook/\">Brid.gy</a> an!</p>"
},
"author": {
"type": "card",
"name": "Matthias Pfefferle",
"url": "https://notiz.blog/author/matthias-pfefferle/",
"photo": "https://secure.gravatar.com/avatar/75512bb584bbceae57dfc503692b16b2?s=40&d=mm&r=g"
},
"post-type": "article",
"_id": "28691294",
"_source": "206",
"_is_read": true
}
Everybody on Twitter wants to know where to go now. The answer is your own website, syndicating out to wherever else people end up. This is the IndieWeb. Let me know if you’d be interested in a talk about how to get set up.
{
"type": "entry",
"author": {
"name": "Kimberly Hirsh, PhD",
"url": "https://kimberlyhirsh.com",
"photo": "https://avatars.micro.blog/avatars/2022/8984.jpg"
},
"url": "https://kimberlyhirsh.com/2022/04/25/everybody-on-twitter.html",
"content": {
"html": "<p>Everybody on Twitter wants to know where to go now. The answer is your own website, syndicating out to wherever else people end up. This is the <a href=\"https://indieweb.org/\">IndieWeb</a>. Let me know if you\u2019d be interested in a talk about how to get set up.</p>",
"text": "Everybody on Twitter wants to know where to go now. The answer is your own website, syndicating out to wherever else people end up. This is the IndieWeb. Let me know if you\u2019d be interested in a talk about how to get set up."
},
"published": "2022-04-25T17:02:46+00:00",
"post-type": "note",
"_id": "33380003",
"_source": "7224",
"_is_read": true
}
As I continue reading and sometimes re-posting things written on this day, I've decided to do one more thing at the end of a session: go to a random site in the IndieWeb WebRing. Today, I found something that resonates down the years: how to organise the content of a weblog.
{
"type": "entry",
"author": {
"name": "Jeremy Cherfas",
"url": "https://jeremycherfas.net/",
"photo": "https://www.gravatar.com/avatar/0649cdd53ddf1146308f316b3406f97f?s=96&d=https%3A%2F%2Fmicro.blog%2Fimages%2Fblank_avatar.png"
},
"url": "https://stream.jeremycherfas.net/2022/as-i-continue-reading-and-sometimes-re-posting",
"content": {
"html": "<p>As I continue reading and sometimes re-posting things written on this day, I've decided to do one more thing at the end of a session: go to a random site in the IndieWeb WebRing. Today, I found something that resonates down the years: how to organise the content of a weblog.</p>",
"text": "As I continue reading and sometimes re-posting things written on this day, I've decided to do one more thing at the end of a session: go to a random site in the IndieWeb WebRing. Today, I found something that resonates down the years: how to organise the content of a weblog."
},
"published": "2022-04-25T07:36:39+00:00",
"post-type": "note",
"_id": "33380004",
"_source": "7224",
"_is_read": true
}
{
"type": "entry",
"published": "2022-04-21T17:32:00+0100",
"url": "https://www.jvt.me/mf2/2022/04/leh7m/",
"category": [
"indieauth"
],
"bookmark-of": [
"https://david.shanske.com/2022/04/21/indieauth-spec-updates-2022/"
],
"author": {
"type": "card",
"name": "Jamie Tanna",
"url": "https://www.jvt.me",
"photo": "https://www.jvt.me/img/profile.png"
},
"post-type": "bookmark",
"refs": {
"https://david.shanske.com/2022/04/21/indieauth-spec-updates-2022/": {
"type": "entry",
"summary": "Over the course of 2021, the IndieWeb community had several popup sessions to continue the refining of the spec. This culminated in a release of the latest iteration on February 22, 2022. I really \u2026",
"url": "https://david.shanske.com/2022/04/21/indieauth-spec-updates-2022/",
"name": "IndieAuth Spec Updates 2022",
"author": {
"type": "card",
"name": "David Shanske",
"url": "https://david.shanske.com/",
"photo": null
},
"post-type": "article"
}
},
"_id": "28609872",
"_source": "2169",
"_is_read": true
}
{
"type": "entry",
"published": "2022-04-21T11:47:38-04:00",
"syndication": [
"https://news.indieweb.org/en/david.shanske.com/2022/04/21/indieauth-spec-updates-2022/",
"https://twitter.com/dshanske/status/1517168901976727553",
"https://micro.blog/dshanske/12729173"
],
"name": "IndieAuth Spec Updates 2022 - April 21, 2022",
"author": {
"type": "card",
"name": "David Shanske",
"url": "https://david.shanske.com/",
"photo": "https://david.shanske.com/avatar/dshanske?s=96"
},
"post-type": "article",
"_id": "28608429",
"_source": "5",
"_is_read": true
}
{
"type": "entry",
"published": "2022-04-21T11:47:38-04:00",
"syndication": [
"https://news.indieweb.org/en/david.shanske.com/2022/04/21/indieauth-spec-updates-2022/",
"https://twitter.com/dshanske/status/1517168901976727553"
],
"name": "IndieAuth Spec Updates 2022 - April 21, 2022",
"author": {
"type": "card",
"name": "David Shanske",
"url": "https://david.shanske.com/",
"photo": "https://david.shanske.com/avatar/dshanske?s=96"
},
"post-type": "article",
"_id": "28608412",
"_source": "5",
"_is_read": true
}
