Twitter's Project Bluesky

{
    "type": "entry",
    "published": "2019-12-11T17:18:53+00:00",
    "url": "https://werd.io/2019/twitters-project-bluesky",
    "name": "Twitter's Project Bluesky",
    "content": {
        "text": "This morning, Jack Dorsey announced that Twitter would be funding an independent group that would develop an open standard for decentralized social networking, with the expectation that the company would use it.\nTwitter is funding a small independent team of up to five open source architects, engineers, and designers to develop an open and decentralized standard for social media. The goal is for Twitter to ultimately be a client of this standard. \ud83e\uddf5\n\u2014 jack \ud83c\udf0d\ud83c\udf0f\ud83c\udf0e (@jack) December 11, 2019\nI've been involved in decentralized social networking since 2004, when I released the first version of Elgg, the open source social networking platform. As I said in an interview with ZDNet in 2006:I think in the future, networks or meta-networks won't be an issue: the network will be decentralised. What I'd like to see is a set of open protocols that mean you can connect to anyone, anywhere, no matter which site they happen to be using.I still fundamentally believe in this vision. My second attempt at an open source platform, Known, uses indieweb standards to a user of a Known site to interact with any other user of any other indieweb-compatible site. Decentralization was something I looked at carefully when I was west coast Director of Investments at Matter Ventures. And it was core to the work I did with the Unlock Protocol.There have been many other attempts. My friend Evan Prodromou created StatusNet and then the ActivityPub protocol; the latter underlies the Mastodon \"fediverse\" of federated social networking platforms. (Known has committed to also joining the fediverse.)Twitter's announcement today builds on many of these efforts in spirit, but it goes its own way. I think this is probably right: whereas all of the aforementioned projects were created by hobbyists, Twitter as a company and a worldwide platform has different needs. If the goal is to run over 126 million daily active users on a decentralized platform, and for the associated platform companies to make money in the process, something new is needed.I don't believe that this new project will come out of lengthy committee deliberations. So while it might rile long-term open standards collaborators, I think this tweet from Twitter's CTO, Parag Agrawal, bodes well:\n3 - The traditionally slow and deliberate consensus-building approach to evolving standards might fail to keep up with a rapidly changing ecosystem and set of consumer needs.\n\u2014 Parag Agrawal (@paraga) December 11, 2019\nThe key will be rapid iteration in the public interest, repeatedly testing not just the feasibility of such a protocol (whether you can build and maintain it at scale), but also its desirability (user risk) and viability (business risk). In other words, it's not enough to make something work. It also has to be able to win user trust, serve as the foundation of an ecosystem, and allow businesses built on the platform to become valuable. As yet, open standards processes have not shown themselves to be capable of this kind of product development.To be clear, this kind of leadership can and does still lead to open projects released under open source licenses. That's what Twitter will need to do here.For Twitter, there are many obvious business benefits as champion of this platform. Particularly in a world where anti-trust reform and regulation of social networks are becoming more prominent topics, getting ahead of the trend and locking in decentralized openness is smart. It could also disrupt other social networking platforms who aren't, or can't be, so forward-thinking.Building it on a blockchain - not Ethereum, but a new, faster, purpose-built chain - may also make sense as a way to lock in both openness and the ability to build value. One interesting property of blockchains is that nodes typically have to process the whole chain; that means that as the traffic on the new protocol increases, the difficulty of processing the chain increases and the number of entities capable of processing it decreases. The value of being an entry point that processes on behalf of others increases. So there's a business in providing an easy access point for developers. But more importantly, designing the protocol from scratch allows a mutually beneficial business model to be baked in. It's not about hoarding the riches for Twitter: it's about baking an ever-increasing pie that everyone can have a slice of.There are lots of very reasonable arguments that open communty advocates will make for this being something to be wary of. But while this move is very, very late in community terms (we've been talking about decentralization for decades), it's very early in corporate terms. The time is right for tech companies to make the shift into open protocols, in a way that allows businesses to make money, users to own their data, and a thousand new social networking interfaces to bloom. And I think that's a progressive move for the web.\u00a0Photo by Anthony Cantin on Unsplash",
        "html": "<p><img src=\"https://werd.io/file/5df124f3b16ea130f6402d12\" alt=\"\" width=\"1000\" height=\"666\" /></p><p>This morning, Jack Dorsey announced that <a href=\"https://twitter.com/jack/status/1204766078468911106\">Twitter would be funding an independent group that would develop an open standard for decentralized social networking</a>, with the expectation that the company would use it.</p><blockquote>\n<p dir=\"ltr\" lang=\"en\" xml:lang=\"en\">Twitter is funding a small independent team of up to five open source architects, engineers, and designers to develop an open and decentralized standard for social media. The goal is for Twitter to ultimately be a client of this standard. \ud83e\uddf5</p>\n<p>\u2014 jack \ud83c\udf0d\ud83c\udf0f\ud83c\udf0e (@jack) <a href=\"https://twitter.com/jack/status/1204766078468911106?ref_src=twsrc%5Etfw\">December 11, 2019</a></p>\n</blockquote><p>I've been involved in decentralized social networking since 2004, when I released the first version of Elgg, the open source social networking platform. <a href=\"https://www.zdnet.com/article/run-your-own-myspace-with-elgg-spaces/\">As I said in an interview with ZDNet in 2006</a>:</p><blockquote><p>I think in the future, networks or meta-networks won't be an issue: the network will be decentralised. What I'd like to see is a set of open protocols that mean you can connect to anyone, anywhere, no matter which site they happen to be using.</p></blockquote><p>I still fundamentally believe in this vision. My second attempt at an open source platform, Known, <a href=\"https://tantek.com/2019/301/b1/redecentralize-indieweb-standards-methods\">uses indieweb standards to a user of a Known site to interact with any other user of any other indieweb-compatible site</a>. Decentralization was something I looked at carefully <a href=\"https://medium.com/matter-driven-narrative/build-the-media-platform-of-tomorrow-49e00e246d20\">when I was west coast Director of Investments at Matter Ventures</a>. And it was core to the work I did with the <a href=\"https://unlock-protocol.com\">Unlock Protocol</a>.</p><p>There have been many other attempts. My friend Evan Prodromou created <a href=\"https://en.wikipedia.org/wiki/GNU_social\">StatusNet</a> and then the <a href=\"https://www.w3.org/TR/activitypub/\">ActivityPub</a> protocol; the latter underlies the <a href=\"https://joinmastodon.org/\">Mastodon</a> \"fediverse\" of federated social networking platforms. (Known has committed to also joining the fediverse.)</p><p>Twitter's announcement today builds on many of these efforts in spirit, but it goes its own way. I think this is probably right: whereas all of the aforementioned projects were created by hobbyists, Twitter as a company and a worldwide platform has different needs. If the goal is to run <a href=\"https://www.washingtonpost.com/technology/2019/02/07/twitter-reveals-its-daily-active-user-numbers-first-time/\">over 126 million daily active users</a> on a decentralized platform, and for the associated platform companies to make money in the process, something new is needed.</p><p>I don't believe that this new project will come out of lengthy committee deliberations. So while it might rile long-term open standards collaborators, I think this tweet from Twitter's CTO, Parag Agrawal, bodes well:</p><blockquote>\n<p dir=\"ltr\" lang=\"en\" xml:lang=\"en\">3 - The traditionally slow and deliberate consensus-building approach to evolving standards might fail to keep up with a rapidly changing ecosystem and set of consumer needs.</p>\n<p>\u2014 Parag Agrawal (@paraga) <a href=\"https://twitter.com/paraga/status/1204766192163901440?ref_src=twsrc%5Etfw\">December 11, 2019</a></p>\n</blockquote><p>The key will be rapid iteration in the public interest, repeatedly testing not just the <em>feasibility</em> of such a protocol (whether you can build and maintain it at scale), but also its <em>desirability</em> (user risk) and <em>viability</em> (business risk). In other words, it's not enough to make something work. It also has to be able to win user trust, serve as the foundation of an ecosystem, and allow businesses built on the platform to become valuable. As yet, open standards processes have not shown themselves to be capable of this kind of product development.</p><p>To be clear, this kind of leadership can and does still lead to open projects released under open source licenses. That's what Twitter will need to do here.</p><p>For Twitter, there are many obvious business benefits as champion of this platform. Particularly in a world where <a href=\"https://www.cnbc.com/2019/09/26/facebook-most-likely-to-suffer-in-antitrust-war-on-silicon-valley.html\">anti-trust reform</a> and <a href=\"https://www.bbc.com/news/technology-47135058\">regulation of social networks</a> are becoming more prominent topics, getting ahead of the trend and locking in decentralized openness is smart. It could also disrupt other social networking platforms who aren't, or can't be, so forward-thinking.</p><p>Building it on a blockchain - not Ethereum, but a new, faster, purpose-built chain - may also make sense as a way to lock in both openness and the ability to build value. One interesting property of blockchains is that nodes typically have to process the whole chain; that means that as the traffic on the new protocol increases, the difficulty of processing the chain increases and the number of entities capable of processing it decreases. The value of being an entry point that processes on behalf of others increases. So there's a business in providing an easy access point for developers. But more importantly, designing the protocol from scratch allows a mutually beneficial business model to be baked in. It's not about hoarding the riches for Twitter: it's about baking an ever-increasing pie that everyone can have a slice of.</p><p>There are lots of very reasonable arguments that open communty advocates will make for this being something to be wary of. But while this move is very, very late in community terms (we've been talking about decentralization for decades), it's very early in corporate terms. The time is right for tech companies to make the shift into open protocols, in a way that allows businesses to make money, users to own their data, and a thousand new social networking interfaces to bloom. And I think that's a progressive move for the web.</p><p>\u00a0</p><p><em>Photo by <a href=\"https://unsplash.com/@arizonanthony?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText\">Anthony Cantin</a> on <a href=\"https://unsplash.com/s/photos/blue-sky?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText\">Unsplash</a></em></p>"
    },
    "author": {
        "type": "card",
        "name": "Ben Werdm\u00fcller",
        "url": "https://werd.io/profile/benwerd",
        "photo": "https://werd.io/file/5d388c5fb16ea14aac640912/thumb.jpg"
    },
    "post-type": "article",
    "_id": "6902516",
    "_source": "191",
    "_is_read": true
}

{
    "type": "entry",
    "published": "2019-12-11T22:29:38+00:00",
    "url": "https://cleverdevil.io/2019/hey-jack-id-like-to-nominate-aaronpk",
    "category": [
        "IndieWeb"
    ],
    "syndication": [
        "https://twitter.com/cleverdevil/status/1204891020665724932"
    ],
    "content": {
        "text": "Hey, @jack, I\u2019d like to nominate @aaronpk and @t to lead @bluesky, perhaps with an assist from @benwerd. They\u2019ve got quite the head start with the #IndieWeb!\n\n\n By the way, I posted this via my own website... how decentralized of me!",
        "html": "Hey, @jack, I\u2019d like to nominate @aaronpk and @t to lead @bluesky, perhaps with an assist from @benwerd. They\u2019ve got quite the head start with the <a href=\"https://cleverdevil.io/tag/IndieWeb\" class=\"p-category\">#IndieWeb</a>!<br /><br />\n By the way, I posted this via my own website... how decentralized of me!"
    },
    "author": {
        "type": "card",
        "name": "Jonathan LaCour",
        "url": "https://cleverdevil.io/profile/cleverdevil",
        "photo": "https://cleverdevil.io/file/fdbc7696a5f73864ea11a828c861e138/thumb.jpg"
    },
    "post-type": "note",
    "_id": "6902031",
    "_source": "71",
    "_is_read": true
}

Twitter to decentralize… something

{
    "type": "entry",
    "author": {
        "name": "Manton Reece",
        "url": "https://www.manton.org/",
        "photo": "https://micro.blog/manton/avatar.jpg"
    },
    "url": "https://www.manton.org/2019/12/11/twitter-to-decentralize.html",
    "name": "Twitter to decentralize\u2026 something",
    "content": {
        "html": "<p>This morning, Jack Dorsey <a href=\"https://twitter.com/jack/status/1204766078468911106\">dropped a bombshell</a>:</p>\n\n<blockquote>\n<p>Twitter is funding a small independent team of up to five open source architects, engineers, and designers to develop an open and decentralized standard for social media. The goal is for Twitter to ultimately be a client of this standard.</p>\n</blockquote>\n\n<p>I should be excited about this, but instead my first reaction was frustration. Ten years after early Twitter employees like Blaine Cook and Alex Payne were pushing for a more open architecture, <em>now</em> Jack Dorsey realizes Twitter is too big and creates a team to work on\u2026 <a href=\"https://twitter.com/jack/status/1204766085037248512\">blockchain-based solutions</a>?</p>\n\n<blockquote>\n<p>Finally, new technologies have emerged to make a decentralized approach more viable. Blockchain points to a series of decentralized solutions for open and durable hosting, governance, and even monetization. Much work to be done, but the fundamentals are there.</p>\n</blockquote>\n\n<p>The first step should be to check out <a href=\"https://indieweb.org/\">the IndieWeb</a>. There are people who have been thinking about and working toward more open social networks for years.</p>\n\n<p>After a closer reading of Jack\u2019s tweets, though, I think my first interpretation wasn\u2019t quite right. Twitter isn\u2019t necessarily interested in decentralizing <em>content</em> or even identity on their platform. Why would they be? Their business is based around having all your tweets in one place.</p>\n\n<p><a href=\"https://twitter.com/jack/status/1204766082206011393\">Early in the thread</a>, Jack hints at what Twitter is trying to do:</p>\n\n<blockquote>\n<p>First, we\u2019re facing entirely new challenges centralized solutions are struggling to meet. For instance, centralized enforcement of global policy to address abuse and misleading information is unlikely to scale over the long-term without placing far too much burden on people.</p>\n</blockquote>\n\n<p>This \u201cburden on people\u201d is the resources it would take for Twitter to actively combat hate and abuse on their platform. Facebook, for example, has hired thousands of moderators. If Twitter is hoping to outsource curation to shared protocols, it should be <em>in addition to</em> \u2014\u00a0not a replacement for \u2014\u00a0the type of effort that Facebook is undertaking. I\u2019ve outlined a better approach in my posts on <a href=\"https://www.manton.org/2019/06/02/open-gardens.html\">open gardens</a> and <a href=\"https://manton.org/2018/09/07/the-way-out.html\">4 parts to fixing social networks</a>, which don\u2019t seem compatible with Twitter\u2019s current business.</p>\n\n<p>I\u2019m going to be paying close attention to this. Good luck to Jack and the new team. I hope they seriously look at existing standards, because we\u2019ve come too far to start over.</p>",
        "text": "This morning, Jack Dorsey dropped a bombshell:\n\n\nTwitter is funding a small independent team of up to five open source architects, engineers, and designers to develop an open and decentralized standard for social media. The goal is for Twitter to ultimately be a client of this standard.\n\n\nI should be excited about this, but instead my first reaction was frustration. Ten years after early Twitter employees like Blaine Cook and Alex Payne were pushing for a more open architecture, now Jack Dorsey realizes Twitter is too big and creates a team to work on\u2026 blockchain-based solutions?\n\n\nFinally, new technologies have emerged to make a decentralized approach more viable. Blockchain points to a series of decentralized solutions for open and durable hosting, governance, and even monetization. Much work to be done, but the fundamentals are there.\n\n\nThe first step should be to check out the IndieWeb. There are people who have been thinking about and working toward more open social networks for years.\n\nAfter a closer reading of Jack\u2019s tweets, though, I think my first interpretation wasn\u2019t quite right. Twitter isn\u2019t necessarily interested in decentralizing content or even identity on their platform. Why would they be? Their business is based around having all your tweets in one place.\n\nEarly in the thread, Jack hints at what Twitter is trying to do:\n\n\nFirst, we\u2019re facing entirely new challenges centralized solutions are struggling to meet. For instance, centralized enforcement of global policy to address abuse and misleading information is unlikely to scale over the long-term without placing far too much burden on people.\n\n\nThis \u201cburden on people\u201d is the resources it would take for Twitter to actively combat hate and abuse on their platform. Facebook, for example, has hired thousands of moderators. If Twitter is hoping to outsource curation to shared protocols, it should be in addition to \u2014\u00a0not a replacement for \u2014\u00a0the type of effort that Facebook is undertaking. I\u2019ve outlined a better approach in my posts on open gardens and 4 parts to fixing social networks, which don\u2019t seem compatible with Twitter\u2019s current business.\n\nI\u2019m going to be paying close attention to this. Good luck to Jack and the new team. I hope they seriously look at existing standards, because we\u2019ve come too far to start over."
    },
    "published": "2019-12-11T15:29:13-06:00",
    "category": [
        "Essays"
    ],
    "post-type": "article",
    "_id": "6900845",
    "_source": "12",
    "_is_read": true
}

{
    "type": "entry",
    "published": "2019-12-11 11:58-0800",
    "url": "https://gregorlove.com/2019/12/check-out-aaronpks-post/",
    "syndication": [
        "https://twitter.com/gRegorLove/status/1204853103004139528"
    ],
    "in-reply-to": [
        "https://twitter.com/niclake/status/1204844561723510785"
    ],
    "content": {
        "text": "Check out @aaronpk's post about readers: https://aaronparecki.com/2018/04/20/46/indieweb-reader-my-new-home-on-the-internet\n\nI've been using Monocle and really enjoying it! More on https://indieweb.org/reader\n\ncc @Edw1nS1984",
        "html": "<p>Check out @aaronpk's post about readers: <a href=\"https://aaronparecki.com/2018/04/20/46/indieweb-reader-my-new-home-on-the-internet\">https://aaronparecki.com/2018/04/20/46/indieweb-reader-my-new-home-on-the-internet</a></p>\n\n<p>I've been using Monocle and really enjoying it! More on <a href=\"https://indieweb.org/reader\">https://indieweb.org/reader</a></p>\n\n<p>cc @Edw1nS1984</p>"
    },
    "author": {
        "type": "card",
        "name": "gRegor Morrill",
        "url": "https://gregorlove.com/",
        "photo": "https://gregorlove.com/site/assets/files/3473/profile-2016-med.jpg"
    },
    "post-type": "reply",
    "refs": {
        "https://twitter.com/niclake/status/1204844561723510785": {
            "type": "entry",
            "url": "https://twitter.com/niclake/status/1204844561723510785",
            "content": {
                "text": "I really miss having an RSS feed reader. I miss the days when that's how I would aggregate all my content. Maybe it's time to redownload NetNewsWire."
            },
            "author": {
                "type": "card",
                "name": "???St. Nicholas???",
                "url": false,
                "photo": "https://gregorlove.com/site/assets/files/3540/f877dd2f3c6fdeaa6755579258d4d6615b31206b836613076e3854c2f9b8a263.jpg"
            },
            "post-type": "note"
        }
    },
    "_id": "6896983",
    "_source": "95",
    "_is_read": true
}

RSVP yes to https://www.eventbrite.com/e/indiewebcamp-london-2020-tickets-85763160923

{
    "type": "entry",
    "published": "2019-12-11T20:00:47.591+01:00",
    "rsvp": "yes",
    "url": "https://www.jvt.me/mf2/2019/12/q7ov3/",
    "in-reply-to": [
        "https://www.eventbrite.com/e/indiewebcamp-london-2020-tickets-85763160923"
    ],
    "name": "RSVP yes to https://www.eventbrite.com/e/indiewebcamp-london-2020-tickets-85763160923",
    "author": {
        "type": "card",
        "name": "Jamie Tanna",
        "url": "https://www.jvt.me",
        "photo": "https://www.jvt.me/img/profile.png"
    },
    "post-type": "rsvp",
    "_id": "6894638",
    "_source": "2169",
    "_is_read": true
}

IndieWeb Challenge Day 11

{
    "type": "entry",
    "published": "2019-12-11T12:30:00+01:00",
    "url": "https://www.jeremycherfas.net/blog/indieweb-challenge-day-11",
    "name": "IndieWeb Challenge Day 11",
    "content": {
        "text": "A very, very small fix today.1\n\n\nThe formatting of footnotes had been driving me nuts, but not nuts enough to do anything about it. Until today. The marker is now where it ought to be, and the font size a smidgen smaller.\u00a0\u21a9",
        "html": "<p>A very, very small fix today.<a href=\"https://www.jeremycherfas.net/blog#fn:1\">1</a></p>\n\n<ol><li>\n<p>The formatting of footnotes had been driving me nuts, but not nuts enough to do anything about it. Until today. The marker is now where it ought to be, and the font size a smidgen smaller.\u00a0<a href=\"https://www.jeremycherfas.net/blog#fnref1:1\">\u21a9</a></p>\n</li>\n</ol>"
    },
    "author": {
        "type": "card",
        "name": "Jeremy Cherfas",
        "url": "https://jeremycherfas.net",
        "photo": null
    },
    "post-type": "article",
    "_id": "6882918",
    "_source": "202",
    "_is_read": true
}

It’s Time to Get Personal

{
    "type": "entry",
    "published": "2019-12-11T09:54:00Z",
    "url": "https://www.jvt.me/mf2/2019/12/3fhvt/",
    "category": [
        "indieweb",
        "personal-website",
        "ownership"
    ],
    "bookmark-of": [
        "https://24ways.org/2019/its-time-to-get-personal/"
    ],
    "name": "It\u2019s Time to Get Personal",
    "content": {
        "text": "This is a great read about the things that being in the https://indieweb.org/ (Independent Web) can empower you with, and the ownership and agency that it affords you.\nI'd recommend a read of https://www.jvt.me/posts/2019/07/22/why-website/ and https://www.jvt.me/posts/2019/10/20/indieweb-talk/ for a bit more info, too.",
        "html": "<p>This is a great read about the things that being in the <a href=\"https://indieweb.org/\">https://indieweb.org/</a> (Independent Web) can empower you with, and the ownership and agency that it affords you.\nI'd recommend a read of <a href=\"https://www.jvt.me/posts/2019/07/22/why-website/\">https://www.jvt.me/posts/2019/07/22/why-website/</a> and <a href=\"https://www.jvt.me/posts/2019/10/20/indieweb-talk/\">https://www.jvt.me/posts/2019/10/20/indieweb-talk/</a> for a bit more info, too.</p>"
    },
    "author": {
        "type": "card",
        "name": "Jamie Tanna",
        "url": "https://www.jvt.me",
        "photo": "https://www.jvt.me/img/profile.png"
    },
    "post-type": "bookmark",
    "_id": "6878828",
    "_source": "2169",
    "_is_read": true
}

{
    "type": "entry",
    "published": "2019-12-11T07:24:13+00:00",
    "url": "https://fireburn.ru/posts/1576049053",
    "syndication": [
        "https://twitter.com/kisik21/status/1204663178623410176"
    ],
    "content": {
        "text": "Writing the API gateway for serious-business and Kittybox is a two-part job. I want that sweet, sweet React goodness but I can't leak my access token that can read arbitrary posts from my Micropub endpoint! so I have two layers:On the top, there is the frontend. It calls to an API gateway via fetch() to receive data (and pass access control checks with cookies - they'll be signed)\nAPI gateway has the token and, never revealing it to the client-side code, fetches posts from Kittybox.\nThe token is not revealed, my private posts are safe, my readers have client-side rendering, everyone is happy!",
        "html": "<p>Writing the API gateway for serious-business and Kittybox is a two-part job. I want that sweet, sweet React goodness but I can't leak my access token that can read arbitrary posts from my Micropub endpoint! so I have two layers:</p><ol><li>On the top, there is the frontend. It calls to an API gateway via fetch() to receive data (and pass access control checks with cookies - they'll be signed)</li>\n<li>API gateway has the token and, never revealing it to the client-side code, fetches posts from Kittybox.</li>\n</ol><p>The token is not revealed, my private posts are safe, my readers have client-side rendering, everyone is happy!<br /></p>"
    },
    "author": {
        "type": "card",
        "name": "Vika",
        "url": "https://fireburn.ru/",
        "photo": "https://fireburn.ru/media/f1/5a/fb/9b/081efafb97b4ad59f5025cf2fd0678b8f3e20e4c292489107d52be09.png"
    },
    "post-type": "note",
    "_id": "6875861",
    "_source": "1371",
    "_is_read": true
}

{
    "type": "entry",
    "published": "2019-12-11T08:09:00+0300",
    "url": "https://fireburn.ru/posts/1576051740",
    "category": [
        "IndieWeb",
        "ownyourdata"
    ],
    "syndication": [
        "https://twitter.com/kisik21/status/1204629280275288064"
    ],
    "content": {
        "text": "The spirit of #IndieWeb is constantly rewriting your site from scratch but being able to keep all your old posts because they are in a universal format! #ownyourdata",
        "html": "<p>The spirit of #IndieWeb is constantly rewriting your site from scratch but being able to keep all your old posts because they are in a universal format! #ownyourdata</p>"
    },
    "author": {
        "type": "card",
        "name": "Vika",
        "url": "https://fireburn.ru/",
        "photo": "https://fireburn.ru/media/f1/5a/fb/9b/081efafb97b4ad59f5025cf2fd0678b8f3e20e4c292489107d52be09.png"
    },
    "post-type": "note",
    "_id": "6872883",
    "_source": "1371",
    "_is_read": true
}

“Link In Bio” is a slow knife

{
    "type": "entry",
    "published": "2019-12-10T23:19:00Z",
    "url": "https://www.jvt.me/mf2/2019/12/3trm9/",
    "category": [
        "indieweb",
        "personal-website",
        "ownership"
    ],
    "bookmark-of": [
        "https://anildash.com/2019/12/10/link-in-bio-is-how-they-tried-to-kill-the-web/"
    ],
    "name": "\u201cLink In Bio\u201d is a slow knife",
    "author": {
        "type": "card",
        "name": "Jamie Tanna",
        "url": "https://www.jvt.me",
        "photo": "https://www.jvt.me/img/profile.png"
    },
    "post-type": "bookmark",
    "_id": "6865246",
    "_source": "2169",
    "_is_read": true
}

{
    "type": "entry",
    "published": "2019-12-10T15:16:00+00:00",
    "url": "https://fireburn.ru/posts/1575990960",
    "photo": [
        "https://fireburn.ru/media/14/b7/73/85/fa05797386d64adf5f7b14dbe8bfb11dbfd1eeba48f775b382721a30.png"
    ],
    "syndication": [
        "https://twitter.com/kisik21/status/1204419530996559872"
    ],
    "content": {
        "text": "Looks like my h-card and the main page are ready. I just need to write functions to fetch data from Micropub.",
        "html": "<p>Looks like my h-card and the main page are ready. I just need to write functions to fetch data from Micropub.</p>"
    },
    "author": {
        "type": "card",
        "name": "Vika",
        "url": "https://fireburn.ru/",
        "photo": "https://fireburn.ru/media/f1/5a/fb/9b/081efafb97b4ad59f5025cf2fd0678b8f3e20e4c292489107d52be09.png"
    },
    "post-type": "photo",
    "_id": "6860564",
    "_source": "1371",
    "_is_read": true
}

{
    "type": "entry",
    "published": "2019-12-10T15:10:07+00:00",
    "url": "https://fireburn.ru/posts/1575990607",
    "syndication": [
        "https://fireburn.ru/None"
    ],
    "in-reply-to": [
        "https://aaronparecki.com/2019/12/09/23/indienews"
    ],
    "content": {
        "text": "\u043f\u043e\u0445\u043e\u0436\u0435, \u0447\u0442\u043e \u044f \u043d\u0435 \u043e\u0434\u043d\u0430 \u0432 IndieWeb \u043f\u0438\u0448\u0443 \u043d\u0430 \u0440\u0443\u0441\u0441\u043a\u043e\u043c! @marinintim \u043f\u0440\u0438\u0432\u0435\u0442!\nLooks like I\u2019m not the only Russian speaker writing in my native language on the IndieWeb! Hi @marinintim",
        "html": "<p>\u043f\u043e\u0445\u043e\u0436\u0435, \u0447\u0442\u043e \u044f \u043d\u0435 \u043e\u0434\u043d\u0430 \u0432 IndieWeb \u043f\u0438\u0448\u0443 \u043d\u0430 \u0440\u0443\u0441\u0441\u043a\u043e\u043c! <a href=\"https://marinintim.com/\">@marinintim</a> \u043f\u0440\u0438\u0432\u0435\u0442!</p>\n<p>Looks like I\u2019m not the only Russian speaker writing in my native language on the IndieWeb! Hi <a href=\"https://marinintim.com/\">@marinintim</a></p>"
    },
    "author": {
        "type": "card",
        "name": "Vika",
        "url": "https://fireburn.ru/",
        "photo": "https://fireburn.ru/media/f1/5a/fb/9b/081efafb97b4ad59f5025cf2fd0678b8f3e20e4c292489107d52be09.png"
    },
    "post-type": "reply",
    "_id": "6860565",
    "_source": "1371",
    "_is_read": true
}

{
    "type": "entry",
    "published": "2019-12-08T21:15:51+00:00",
    "url": "https://fireburn.ru/posts/1575839751",
    "category": [
        "React",
        "nextjs",
        "IndieWeb"
    ],
    "photo": [
        "https://fireburn.ru/media/f1/83/ce/a9/79088f8f36a2c24f790a30609472becae27c64d7f2046847c99ea22c.png"
    ],
    "syndication": [
        "https://twitter.com/kisik21/status/1203785310410293249"
    ],
    "content": {
        "text": "THIS IS IT. I\u2019ve finished the h-entry React component. Looks beautiful, isn\u2019t it? #React #nextjs #IndieWeb",
        "html": "<p>THIS IS IT. I\u2019ve finished the h-entry React component. Looks beautiful, isn\u2019t it? #React #nextjs #IndieWeb</p>"
    },
    "author": {
        "type": "card",
        "name": "Vika",
        "url": "https://fireburn.ru/",
        "photo": "https://fireburn.ru/media/f1/5a/fb/9b/081efafb97b4ad59f5025cf2fd0678b8f3e20e4c292489107d52be09.png"
    },
    "post-type": "photo",
    "_id": "6860566",
    "_source": "1371",
    "_is_read": true
}

{
    "type": "entry",
    "published": "2019-12-08T13:34:36+00:00",
    "url": "https://fireburn.ru/posts/1575812076",
    "category": [
        "nextjs",
        "React",
        "indieweb",
        "JSDR"
    ],
    "photo": [
        "https://fireburn.ru/media/c1/7a/b0/76/adf468a3522b8d392d7873b8b6f7ec4eadc30bc10d20b541dfb47ea0.png"
    ],
    "syndication": [
        "https://twitter.com/kisik21/status/1203669237946077184"
    ],
    "content": {
        "text": "Success! Thanks to #nextjs I\u2019m able to use #React to render my posts without losing ability to curl them. #indieweb #JSDR\nIt even looks pretty enough without JS; though Twemoji icons aren\u2019t rendered.",
        "html": "<p>Success! Thanks to #nextjs I\u2019m able to use #React to render my posts without losing ability to curl them. #indieweb #JSDR</p>\n<p>It even looks pretty enough without JS; though Twemoji icons aren\u2019t rendered.</p>"
    },
    "author": {
        "type": "card",
        "name": "Vika",
        "url": "https://fireburn.ru/",
        "photo": "https://fireburn.ru/media/f1/5a/fb/9b/081efafb97b4ad59f5025cf2fd0678b8f3e20e4c292489107d52be09.png"
    },
    "post-type": "photo",
    "_id": "6860568",
    "_source": "1371",
    "_is_read": true
}

{
    "type": "entry",
    "published": "2019-12-07T22:55:00+0300",
    "url": "https://fireburn.ru/posts/1575759300",
    "category": [
        "indieweb",
        "react"
    ],
    "syndication": [
        "https://twitter.com/kisik21/status/1203402689406787585"
    ],
    "content": {
        "text": "So, I\u2019ve started to learn Next.js and #React. It feels kinda interesting. I was able to start drafting a React component for rendering an h-entry. #indieweb",
        "html": "<p>So, I\u2019ve started to learn Next.js and #React. It feels kinda interesting. I was able to start drafting a React component for rendering an h-entry. #indieweb</p>"
    },
    "author": {
        "type": "card",
        "name": "Vika",
        "url": "https://fireburn.ru/",
        "photo": "https://fireburn.ru/media/f1/5a/fb/9b/081efafb97b4ad59f5025cf2fd0678b8f3e20e4c292489107d52be09.png"
    },
    "post-type": "note",
    "_id": "6860569",
    "_source": "1371",
    "_is_read": true
}

{
    "type": "entry",
    "published": "2019-12-07T16:25:00+00:00",
    "url": "https://fireburn.ru/posts/1575735900",
    "in-reply-to": [
        "https://aaronparecki.com/2019/12/06/25/"
    ],
    "content": {
        "text": "I\u2019m using webmention.io to handle webmentions currently, so it should handle this? :3 I don\u2019t know, still haven\u2019t gotten around to actually showing webmentions",
        "html": "<p>I\u2019m using webmention.io to handle webmentions currently, so it should handle this? :3 I don\u2019t know, still haven\u2019t gotten around to actually showing webmentions</p>"
    },
    "author": {
        "type": "card",
        "name": "Vika",
        "url": "https://fireburn.ru/",
        "photo": "https://fireburn.ru/media/f1/5a/fb/9b/081efafb97b4ad59f5025cf2fd0678b8f3e20e4c292489107d52be09.png"
    },
    "post-type": "reply",
    "_id": "6860570",
    "_source": "1371",
    "_is_read": true
}

{
    "type": "entry",
    "published": "2019-12-07T14:49:32+00:00",
    "url": "https://fireburn.ru/posts/1575730172",
    "syndication": [
        "https://twitter.com/kisik21/status/1203325696535408641"
    ],
    "content": {
        "text": "I got a weird idea of React-based IndieWeb components. With next.js they will be server-side rendered, JS;DR won't be a problem.",
        "html": "<p>I got a weird idea of React-based IndieWeb components. With next.js they will be server-side rendered, JS;DR won't be a problem.<br /></p>"
    },
    "author": {
        "type": "card",
        "name": "Vika",
        "url": "https://fireburn.ru/",
        "photo": "https://fireburn.ru/media/f1/5a/fb/9b/081efafb97b4ad59f5025cf2fd0678b8f3e20e4c292489107d52be09.png"
    },
    "post-type": "note",
    "_id": "6860571",
    "_source": "1371",
    "_is_read": true
}

IndieWeb Challenge Day 10

{
    "type": "entry",
    "published": "2019-12-10T12:30:00+01:00",
    "url": "https://www.jeremycherfas.net/blog/indieweb-challenge-day-10",
    "name": "IndieWeb Challenge Day 10",
    "content": {
        "text": "I've wanted for ages to be able to do visual representations of some of the data I collect, and as I had a bit more time than usual yesterday I finally made the effort to understand chartist.js and put it to work.",
        "html": "<p>I've wanted for ages to be able to do visual representations of some of the data I collect, and as I had a bit more time than usual yesterday I finally made the effort to understand <a href=\"https://gionkunz.github.io/chartist-js/getting-started.html\">chartist.js</a> and put it to work.</p>"
    },
    "author": {
        "type": "card",
        "name": "Jeremy Cherfas",
        "url": "https://jeremycherfas.net",
        "photo": null
    },
    "post-type": "article",
    "_id": "6843883",
    "_source": "202",
    "_is_read": true
}

Blogging Less in the 2020s

{
    "type": "entry",
    "published": "2019-12-10T07:50:00Z",
    "url": "https://www.jvt.me/mf2/2019/12/bjoxz/",
    "category": [
        "blogging",
        "indieweb"
    ],
    "bookmark-of": [
        "https://www.kickscondor.com/blogging-less-in-the-2020s/"
    ],
    "name": "Blogging Less in the 2020s",
    "author": {
        "type": "card",
        "name": "Jamie Tanna",
        "url": "https://www.jvt.me",
        "photo": "https://www.jvt.me/img/profile.png"
    },
    "post-type": "bookmark",
    "_id": "6839634",
    "_source": "2169",
    "_is_read": true
}

{
    "type": "entry",
    "published": "2019-12-09 18:51-0800",
    "url": "https://gregorlove.com/2019/12/following-up-on-easiersvp/",
    "content": {
        "text": "Following up on EasieRSVP: I updated my event pages so Twitter replies that start with \u201crsvp yes\u201d or \u201crsvp no\u201d will show as RSVPs. I also standardized them with emoji and \u201cAttending\u201d or \u201cNot attending\u201d. You can see it in action on this week\u2019s HWC SD event page! Charlotte\u2019s RSVP and mine are indie RSVPs; the other two are Twitter RSVPs. Charlotte\u2019s is currently showing as unknown because the microformats aren\u2019t quite right on their post.",
        "html": "<p>Following up on <a href=\"https://gregorlove.com/2019/11/easiersvp/\">EasieRSVP</a>: I updated my event pages so Twitter replies that start with \u201crsvp yes\u201d or \u201crsvp no\u201d will show as RSVPs. I also standardized them with emoji and \u201cAttending\u201d or \u201cNot attending\u201d. You can see it in action on this week\u2019s <a href=\"https://gregorlove.com/2019/12/homebrew-website-club/#rsvps\">HWC SD</a> event page! Charlotte\u2019s RSVP and mine are indie RSVPs; the other two are Twitter RSVPs. Charlotte\u2019s is currently showing as unknown because the microformats aren\u2019t quite right on their post.</p>"
    },
    "author": {
        "type": "card",
        "name": "gRegor Morrill",
        "url": "https://gregorlove.com/",
        "photo": "https://gregorlove.com/site/assets/files/3473/profile-2016-med.jpg"
    },
    "post-type": "note",
    "_id": "6835905",
    "_source": "95",
    "_is_read": true
}