IndieWeb Challenge Day 6

{
    "type": "entry",
    "published": "2019-12-06T11:15:00+01:00",
    "url": "https://www.jeremycherfas.net/blog/indieweb%20challenge%20day%206",
    "name": "IndieWeb Challenge Day 6",
    "content": {
        "text": "If one is sufficiently slapdash, fixing something on this site each day is more than doable. A couple of days ago I did some work to tidy up the display of Reviews. Deeply fancy logic (not) to check the name of an image file seemed to do what I wanted. I had forgotten, however, that while the name I gave the image file was constant, it respected the file format of the original image file. My logic was testing for only one file format.",
        "html": "<p>If one is sufficiently slapdash, fixing something on this site each day is more than doable. A couple of days ago I did some work to tidy up the display of Reviews. Deeply fancy logic (not) to check the name of an image file seemed to do what I wanted. I had forgotten, however, that while the name I gave the image file was constant, it respected the file format of the original image file. My logic was testing for only one file format.</p>"
    },
    "author": {
        "type": "card",
        "name": "Jeremy Cherfas",
        "url": "https://jeremycherfas.net",
        "photo": null
    },
    "post-type": "article",
    "_id": "6736167",
    "_source": "202",
    "_is_read": false
}

Vika fireburn.ru

{
    "type": "entry",
    "published": "2019-12-06T08:24:29+00:00",
    "url": "https://fireburn.ru/posts/1575620669",
    "syndication": [
        "https://twitter.com/kisik21/status/1202866411498090501"
    ],
    "content": {
        "text": "Trying syndication to Twitter from my own #Micropub client. Now I don't even need Quill because my client can post anything!",
        "html": "<p>Trying syndication to Twitter from my own #Micropub client. Now I don't even need Quill because my client can post anything!</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": "6734569",
    "_source": "1371",
    "_is_read": false
}

Manton Reece www.manton.org

{
    "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/05/usually-the-indieweb.html",
    "content": {
        "html": "<p>Usually the IndieWeb Meetup in Austin is 1st Wednesday of the month. Next month, that\u2019s New Year\u2019s Day, so we\u2019re bumping it a week to January 8th, 6:30pm at Mozart\u2019s Coffee.</p>",
        "text": "Usually the IndieWeb Meetup in Austin is 1st Wednesday of the month. Next month, that\u2019s New Year\u2019s Day, so we\u2019re bumping it a week to January 8th, 6:30pm at Mozart\u2019s Coffee."
    },
    "published": "2019-12-05T14:53:49-06:00",
    "post-type": "note",
    "_id": "6723539",
    "_source": "12",
    "_is_read": true
}

Vika fireburn.ru

{
    "type": "entry",
    "published": "2019-12-05T20:56:38+00:00",
    "url": "https://fireburn.ru/posts/1575579398",
    "category": [
        "testing"
    ],
    "content": {
        "text": "I'm trying to post from my own Micropub client.",
        "html": "<p>I'm trying to post from my own Micropub client.<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": "6721995",
    "_source": "1371",
    "_is_read": true
}

Vika fireburn.ru

Introducing Kittybox

{
    "type": "entry",
    "published": "2019-12-05T20:21:25+00:00",
    "url": "https://fireburn.ru/posts/1575577285",
    "category": [
        "pyindieblog",
        "kittybox",
        "IndieWeb",
        "Micropub",
        "programming"
    ],
    "name": "Introducing Kittybox",
    "content": {
        "text": "I'm excited to announce that pyindieblog-micropub, my Micropub endpoint software, officially gained a name. It's now called Kittybox! (cat lovers of #IndieWeb, rejoice! @anomalily @aaronpk)Also I'm almost ready to deploy another rewrite of its Micropub endpoint, now asynchronous. I only need Markdown parsing for feature parity...Kittybox is hosted on GitLab here. It has a CI pipeline, Issues section is used as my itches list and when I get my Raspberry Pi 4 I'll set up a Kubernetes cluster and it will auto-update if all tests are green!ArchitectureFIrst of all, Kittybox is asynchronous. This means that my website should become a lot faster under load. The typical ?q=source request takes just 7 milliseconds on my laptop with a test database of several posts! (It should become a little bit slower if there are more posts, but it's mostly fairly efficient since it doesn't fetch posts that it doesn't need)\nSecond, it still stores posts in Redis. I'm considering migrating to MongoDB or try to somehow store posts in flat files, accelerated with Redis caching. The problem with flat files is lack of scalability; I'll need to exploit NFS mounting if I want to scale my app in a multi-node Kubernetes cluster. The problem with Redis is the complicated indexing - you probably don't want to look at RedisBackend class, it's a mess of raw Redis calls. The problem with MongoDB is - I have no idea how it works and how fast it is. I'll probably need to use a caching layer - Redis again could work really well!Third, it now supports arbitrary URL schemes for posts, so I'm no longer limited to single inflexible URL scheme. I can just specify an arbitrary URL on my domain to post it to.Fourth, I've finally implemented newBase60 slugs (thanks @tantek for the format)Fifth: if frontend passes AUTH command in a KittyQL query, Kittybox will show private posts.\nItchesSettings and configurationRIght now I'm thinking about configuration -- most notably syndication endpoints. I'd like to be able to configure them at runtime, but Micropub protocol doesn't have that feature and I'll need to implement it as a separate extension. Current variants of solving this issue are:Introduce a new \"action\" in POST requests - \"config\", that would allow me to dynamically modify syndication endpoints and some other stuff with the same add-replace-delete workflow.\nGet a /micropub/config endpoint that will implement its own API\nTry to somehow package this into a MF2-like post and store it at a well-known URI.\nNickname cacheRemember what I said about arbitrary URLs? It also stores arbitrary MF2 objects. This means I can cache other people's h-cards in there to use for a nickname cache! This can be used by the frontend app to show rich h-cards on mentions.I'm planning to do that with a client app flow like this:Enter the URL in the box and a shortname for the person in the second one\nIt gets fetched, and the h-card gets posted at `https://fireburn.ru/people/<shortname>`\nWhen I need to autocomplete, I could probably use a [KittyQL](https://fireburn.ru/posts/1574643184) query to get the full address book and complete the name!\nWhen it gets posted, my post pre-processor will automatically go through and add links and rich mini-h-cards to @mentions.",
        "html": "<p>I'm excited to announce that pyindieblog-micropub, my Micropub endpoint software, officially gained a name. It's now called Kittybox! (cat lovers of #IndieWeb, rejoice! <a href=\"https://anomalily.net\">@anomalily</a> <a href=\"https://aaronparecki.com/\">@aaronpk</a>)</p><p>Also I'm almost ready to deploy another rewrite of its Micropub endpoint, now asynchronous. I only need Markdown parsing for feature parity...</p><p>Kittybox is hosted on GitLab <a href=\"https://gitlab.com/vikanezrimaya/kittybox\">here</a>. It has a CI pipeline, Issues section is used as my itches list and when I get my Raspberry Pi 4 I'll set up a Kubernetes cluster and it will auto-update if all tests are green!</p><h2>Architecture</h2><p>FIrst of all, Kittybox is asynchronous. This means that my website should become a lot faster under load. The typical ?q=source request takes just 7 milliseconds on my laptop with a test database of several posts! (It should become a little bit slower if there are more posts, but it's mostly fairly efficient since it doesn't fetch posts that it doesn't need)<br /></p><p>Second, it still stores posts in Redis. I'm considering migrating to MongoDB or try to somehow store posts in flat files, accelerated with Redis caching. The problem with flat files is lack of scalability; I'll need to exploit NFS mounting if I want to scale my app in a multi-node Kubernetes cluster. The problem with Redis is the complicated indexing - you probably don't want to look at RedisBackend class, it's a mess of raw Redis calls. The problem with MongoDB is - I have no idea how it works and how fast it is. I'll probably need to use a caching layer - Redis again could work really well!</p><p>Third, it now supports arbitrary URL schemes for posts, so I'm no longer limited to single inflexible URL scheme. I can just specify an arbitrary URL on my domain to post it to.</p><p>Fourth, I've finally implemented newBase60 slugs (thanks <a href=\"https://tantek.com\">@tantek</a> for the format)</p><p>Fifth: if frontend passes AUTH command in a KittyQL query, Kittybox will show private posts.<br /></p><h2>Itches</h2><h3>Settings and configuration</h3><p>RIght now I'm thinking about configuration -- most notably syndication endpoints. I'd like to be able to configure them at runtime, but Micropub protocol doesn't have that feature and I'll need to implement it as a separate extension. Current variants of solving this issue are:</p><ol><li>Introduce a new \"action\" in POST requests - \"config\", that would allow me to dynamically modify syndication endpoints and some other stuff with the same add-replace-delete workflow.</li>\n<li>Get a /micropub/config endpoint that will implement its own API</li>\n<li>Try to somehow package this into a MF2-like post and store it at a well-known URI.</li>\n</ol><h3>Nickname cache</h3><p>Remember what I said about arbitrary URLs? It also stores arbitrary MF2 objects. This means I can cache other people's h-cards in there to use for a nickname cache! This can be used by the frontend app to show rich h-cards on mentions.</p><p>I'm planning to do that with a client app flow like this:</p><ol><li>Enter the URL in the box and a shortname for the person in the second one</li>\n<li>It gets fetched, and the h-card gets posted at `https://fireburn.ru/people/&lt;shortname&gt;`</li>\n<li>When I need to autocomplete, I could probably use a [KittyQL](https://fireburn.ru/posts/1574643184) query to get the full address book and complete the name!</li>\n<li>When it gets posted, my post pre-processor will automatically go through and add links and rich mini-h-cards to @mentions.</li>\n</ol>"
    },
    "author": {
        "type": "card",
        "name": "Vika",
        "url": "https://fireburn.ru/",
        "photo": "https://fireburn.ru/media/f1/5a/fb/9b/081efafb97b4ad59f5025cf2fd0678b8f3e20e4c292489107d52be09.png"
    },
    "post-type": "article",
    "_id": "6721284",
    "_source": "1371",
    "_is_read": true
}

Ben Werdmüller werd.io/profile/benwerd

A Medium dilemma

{
    "type": "entry",
    "published": "2019-12-05T17:48:38+00:00",
    "url": "https://werd.io/2019/a-medium-dilemma",
    "name": "A Medium dilemma",
    "content": {
        "text": "I'm a fan and paid-up member of Medium, the long-form online publishing platform and reader network. I should declare that I'm not unbiased: I worked there in 2016 and know a few of the people who work on it, although the team and product have changed considerably over the last few years.A couple of years ago they began to reverse one of the most alarming trends on the internet - independent artists losing the ability to sustainably create their work - and allowed writers to get paid for their work. It's been a roaring success, and the site is now one of the top 100 in the world. More recently still, they've brought paying publications like the Bold Italic into the fold. Although this is reminscent of a failed strategy from a few years ago that ended up really hurting publications like The Establishment, in the context of the Partner Program and Medium Memberships it makes more sense.What Medium isn't is a generic blogging or publishing platform. It's narrowed its focus into being more like a magazine that everyone can contribute to (and I'm told that more changes are coming in the New Year). In doing so, it inevitably loses some of its early users - and it adds features like a paywall that may drive some casual readers away.Ironically, many of the people who complain about Medium are the same people who care about surveillance capitalism. Yet the site is the biggest, boldest experiment in non-surveillance social media on the internet: a business that makes money by asking for money, and has aligned itself with its community in doing so. No, you don't build a wholly self-owned digital identity like you do on the indieweb; no, it's not a place for billions of people to put their every waking thought for free. But in building a magazine that anyone can contribute to, Medium has opened the door to a more diverse community of writers sharing their lived experiences and getting paid for it as part of a business model that promotes value over blind engagement and doesn't need to profile you all over the web.To say that writers should make their work available for free is the height of privilege - and indeed, usually those voices are well-paid white men who make six figure salaries at technology companies. Our society is richer for having more points of view expressed, but not everyone has the time available to do free work. The net result of Medium's strategy is more writers making a living from their work, and therefore more diverse writers sharing their lived experiences. I'm all for that.Publishing on Medium does not preclude writing on a personal website that you control. You can do both. But just as there's nothing wrong with publishing a long-form piece in a newspaper or a traditional magazine, there's nothing wrong with publishing it on Medium.",
        "html": "<p>I'm a fan and paid-up member of <a href=\"https://medium.com\">Medium</a>, the long-form online publishing platform and reader network. I should declare that I'm not unbiased: I worked there in 2016 and know a few of the people who work on it, although the team and product have changed considerably over the last few years.</p><p>A couple of years ago they began to reverse one of the most alarming trends on the internet - independent artists losing the ability to sustainably create their work - and allowed writers to get paid for their work. It's been a roaring success, and the site is now one of the top 100 in the world. More recently still, <a href=\"https://thebolditalic.com/the-bold-italic-an-evolving-experiment-in-local-journalism-4f64a470240a?gi=dd60dd5aef5f\">they've brought paying publications like the Bold Italic into the fold</a>. Although this is reminscent of a failed strategy from a few years ago that ended up <a href=\"https://www.niemanlab.org/2017/10/stung-by-mediums-pivot-the-establishment-powers-up-for-a-membership-driven-future/\">really hurting publications like The Establishment</a>, in the context of the <a href=\"https://medium.com/creators\">Partner Program</a> and <a href=\"https://medium.com/membership\">Medium Memberships</a> it makes more sense.</p><p>What Medium isn't is a generic blogging or publishing platform. It's narrowed its focus into being more like a magazine that everyone can contribute to (and I'm told that more changes are coming in the New Year). In doing so, it inevitably loses some of its early users - and it adds features like a paywall that may drive some casual readers away.</p><p>Ironically, many of the people who complain about Medium are the same people who care about surveillance capitalism. Yet the site is the biggest, boldest experiment in non-surveillance social media on the internet: a business that makes money by asking for money, and has aligned itself with its community in doing so. No, you don't build a wholly self-owned digital identity like you do on the <a href=\"https://indieweb.org\">indieweb</a>; no, it's not a place for billions of people to put their every waking thought for free. But in building a magazine that anyone can contribute to, Medium has opened the door to a more diverse community of writers sharing their lived experiences <em>and getting paid for it</em> as part of a business model that promotes value over blind engagement and doesn't need to profile you all over the web.</p><p>To say that writers should make their work available for free is the height of privilege - and indeed, usually those voices are well-paid white men who make six figure salaries at technology companies. Our society is richer for having more points of view expressed, but not everyone has the time available to do free work. The net result of Medium's strategy is more writers making a living from their work, and therefore more diverse writers sharing their lived experiences. I'm all for that.</p><p>Publishing on Medium does not preclude writing on a personal website that you control. You can do both. But just as there's nothing wrong with publishing a long-form piece in a newspaper or a traditional magazine, there's nothing wrong with publishing it on Medium.</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": "6717345",
    "_source": "191",
    "_is_read": true
}

Jamie Tanna www.jvt.me

How to Fix Social Media by Injecting A Chunk of the Blogosphere

{
    "type": "entry",
    "published": "2019-12-05T17:24:00Z",
    "url": "https://www.jvt.me/mf2/2019/12/z36mu/",
    "category": [
        "indieweb",
        "personal-website",
        "blogging"
    ],
    "bookmark-of": [
        "https://kottke.org/19/01/how-to-fix-social-media-by-injecting-a-chunk-of-the-blogosphere"
    ],
    "name": "How to Fix Social Media by Injecting A Chunk of the Blogosphere",
    "author": {
        "type": "card",
        "name": "Jamie Tanna",
        "url": "https://www.jvt.me",
        "photo": "https://www.jvt.me/img/profile.png"
    },
    "post-type": "bookmark",
    "_id": "6716929",
    "_source": "2169",
    "_is_read": true
}

Manton Reece www.manton.org

{
    "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/05/we-are-still.html",
    "content": {
        "html": "<p>We are still looking for sponsors for IndieWebCamp Austin. Do you work for a web-friendly company that might be interested? <a href=\"https://www.manton.org/2019/11/07/sponsoring-indiewebcamp-austin.html\">See this blog post</a> for details.</p>",
        "text": "We are still looking for sponsors for IndieWebCamp Austin. Do you work for a web-friendly company that might be interested? See this blog post for details."
    },
    "published": "2019-12-05T09:16:57-06:00",
    "post-type": "note",
    "_id": "6714121",
    "_source": "12",
    "_is_read": true
}

IndieWeb Challenge Day 5

{
    "type": "entry",
    "published": "2019-12-05T15:30:00+01:00",
    "url": "https://www.jeremycherfas.net/blog/indieweb-challenge-day-5",
    "name": "IndieWeb Challenge Day 5",
    "content": {
        "text": "A brief flurry of webmentions to a recent post reminded me that I needed to look again at how those things are presented. In building the new theme, I had discovered the <detail> and <summary> elements and used them to hide interactions as the default. I hope most people know that clicking on the triangle will expose something hidden. Ideally I would like to offer different visual presentation depending on whether either webmentions or comments exist. That is not going to happen for a while.",
        "html": "<p>A brief flurry of webmentions to a recent post reminded me that I needed to look again at how those things are presented. In building the new theme, I had discovered the <code>&lt;detail&gt;</code> and <code>&lt;summary&gt;</code> elements and used them to hide interactions as the default. I hope most people know that clicking on the triangle will expose something hidden. Ideally I would like to offer different visual presentation depending on whether either webmentions or comments exist. That is not going to happen for a while.</p>"
    },
    "author": {
        "type": "card",
        "name": "Jeremy Cherfas",
        "url": "https://jeremycherfas.net",
        "photo": null
    },
    "post-type": "article",
    "_id": "6711918",
    "_source": "202",
    "_is_read": true
}

Jamie Tanna www.jvt.me

{
    "type": "entry",
    "published": "2019-12-05T11:18:00Z",
    "url": "https://www.jvt.me/mf2/2019/12/0ore1/",
    "category": [
        "indieweb"
    ],
    "content": {
        "text": "After seeing my Spotify Wrapped playlist for the year, and some of the usage stats, I think I'm definitely going to be writing an application to get that data out for myself and my own usages",
        "html": "<p>After seeing my Spotify Wrapped playlist for the year, and some of the usage stats, I think I'm definitely going to be writing an application to get that data out for myself and my own usages</p>"
    },
    "author": {
        "type": "card",
        "name": "Jamie Tanna",
        "url": "https://www.jvt.me",
        "photo": "https://www.jvt.me/img/profile.png"
    },
    "post-type": "note",
    "_id": "6708022",
    "_source": "2169",
    "_is_read": true
}

Vika fireburn.ru

{
    "type": "entry",
    "published": "2019-12-05T00:42:00+0300",
    "url": "https://fireburn.ru/posts/1575506520",
    "category": [
        "IndieWeb"
    ],
    "content": {
        "text": "IndieWeb I love you. No seriously.\nOur community is small but it\u2019s cozy here.\n\ud83d\udc96",
        "html": "<p>IndieWeb I love you. No seriously.</p>\n<p>Our community is small but it\u2019s cozy here.</p>\n\ud83d\udc96"
    },
    "author": {
        "type": "card",
        "name": "Vika",
        "url": "https://fireburn.ru/",
        "photo": "https://fireburn.ru/media/f1/5a/fb/9b/081efafb97b4ad59f5025cf2fd0678b8f3e20e4c292489107d52be09.png"
    },
    "post-type": "note",
    "_id": "6693905",
    "_source": "1371",
    "_is_read": true
}

Vika fireburn.ru

{
    "type": "entry",
    "published": "2019-12-01T10:23:05+00:00",
    "url": "https://fireburn.ru/posts/1575195785",
    "category": [
        "pyindieblog",
        "development",
        "programming",
        "caching",
        "Micropub",
        "Redis"
    ],
    "syndication": [
        "https://twitter.com/kisik21/status/1201084338965819392"
    ],
    "content": {
        "text": "Yesterday I\u2019ve learned how to use Prometheus and Grafana to collect performance metrics and also sped up my asyncio-based WIP ver of my #Micropub endpoint by a factor of 7 by caching the token endpoint response. It was the slowest part because I use @RedisLabs\u2019 #Redis for posts.",
        "html": "<p>Yesterday I\u2019ve learned how to use Prometheus and Grafana to collect performance metrics and also sped up my asyncio-based WIP ver of my #Micropub endpoint by a factor of 7 by caching the token endpoint response. It was the slowest part because I use @RedisLabs\u2019 #Redis for posts.</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": "6693914",
    "_source": "1371",
    "_is_read": true
}

Manton Reece www.manton.org

{
    "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/04/if-youre-coming.html",
    "content": {
        "html": "<p>If you\u2019re coming to tonight\u2019s IndieWeb Meetup at 6:30pm, Mozart\u2019s Coffee also has a huge Christmas light show outside. It\u2019s cool! But it means more of a crowd, so plan on arriving a bit early.</p>",
        "text": "If you\u2019re coming to tonight\u2019s IndieWeb Meetup at 6:30pm, Mozart\u2019s Coffee also has a huge Christmas light show outside. It\u2019s cool! But it means more of a crowd, so plan on arriving a bit early."
    },
    "published": "2019-12-04T11:21:14-06:00",
    "post-type": "note",
    "_id": "6687437",
    "_source": "12",
    "_is_read": true
}

IndieWeb Challenge Day 4

{
    "type": "entry",
    "published": "2019-12-04T13:30:00+01:00",
    "url": "https://www.jeremycherfas.net/blog/indieweb-challenge-day-4",
    "name": "IndieWeb Challenge Day 4",
    "content": {
        "text": "Not much to see today, unless you go spelunking into old posts. If you do, however, you will notice that some of the older Reviews now are not quite as messy as they were.",
        "html": "<p>Not much to see today, unless you go spelunking into old posts. If you do, however, you will notice that some of the older Reviews now are not quite as messy as they were.</p>"
    },
    "author": {
        "type": "card",
        "name": "Jeremy Cherfas",
        "url": "https://jeremycherfas.net",
        "photo": null
    },
    "post-type": "article",
    "_id": "6678726",
    "_source": "202",
    "_is_read": true
}

Tantek Çelik tantek.com

{
    "type": "entry",
    "published": "2019-12-03 15:56-0800",
    "url": "http://tantek.com/2019/337/t1/",
    "in-reply-to": [
        "https://twitter.com/andigalpern/status/1201936229748461568"
    ],
    "content": {
        "text": "So glad you can make it @andigalpern!\n\nNo Facebook event (recent experience shows they add zero* value).\n\nPlease share the official event/ticket URL https://2019.indieweb.org/sf with designers or others you\u2019d send a FB invite to. It has user-friendly Tito-based ticketing!\n\n*In practice we\u2019ve found that Facebook events RSVPs do not add any new people that would otherwise have made it, and those that only RSVP on Facebook in practice are nearly all no-shows which is demoralizing to everyone. As a result we have stopped wasting time with creating Facebook events, and linking people to a source of negative social media distractions.\n\nFor @IndieWebCamp events in particular we need more accurate numbers for estimating food needs etc. A proper ticketing system helps with that.",
        "html": "So glad you can make it <a class=\"h-cassis-username\" href=\"https://twitter.com/andigalpern\">@andigalpern</a>!<br /><br />No Facebook event (recent experience shows they add zero* value).<br /><br />Please share the official event/ticket URL <a href=\"https://2019.indieweb.org/sf\">https://2019.indieweb.org/sf</a> with designers or others you\u2019d send a FB invite to. It has user-friendly Tito-based ticketing!<br /><br />*In practice we\u2019ve found that Facebook events RSVPs do not add any new people that would otherwise have made it, and those that only RSVP on Facebook in practice are nearly all no-shows which is demoralizing to everyone. As a result we have stopped wasting time with creating Facebook events, and linking people to a source of negative social media distractions.<br /><br />For <a class=\"h-cassis-username\" href=\"https://twitter.com/IndieWebCamp\">@IndieWebCamp</a> events in particular we need more accurate numbers for estimating food needs etc. A proper ticketing system helps with that."
    },
    "author": {
        "type": "card",
        "name": "Tantek \u00c7elik",
        "url": "http://tantek.com/",
        "photo": "https://aperture-media.p3k.io/tantek.com/acfddd7d8b2c8cf8aa163651432cc1ec7eb8ec2f881942dca963d305eeaaa6b8.jpg"
    },
    "post-type": "reply",
    "refs": {
        "https://twitter.com/andigalpern/status/1201936229748461568": {
            "type": "entry",
            "url": "https://twitter.com/andigalpern/status/1201936229748461568",
            "name": "@andigalpern\u2019s tweet",
            "post-type": "article"
        }
    },
    "_id": "6672093",
    "_source": "1",
    "_is_read": true
}

gRegor Morrill gregorlove.com

{
    "type": "entry",
    "published": "2019-12-03 10:48-0500",
    "rsvp": "yes",
    "url": "https://gregorlove.com/2019/12/im-attending-indiewebcamp-sf/",
    "in-reply-to": [
        "https://2019.indieweb.org/sf"
    ],
    "content": {
        "text": "I\u2019m attending (remote)IndieWebCamp SF 2020!",
        "html": "<p>I\u2019m attending (remote)<a class=\"u-in-reply-to\" href=\"https://2019.indieweb.org/sf\">IndieWebCamp SF 2020</a>!</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": "rsvp",
    "_id": "6664553",
    "_source": "95",
    "_is_read": true
}

{
    "type": "entry",
    "author": {
        "name": "Kh\u00fcrt Williams",
        "url": "https://islandinthenet.com/",
        "photo": null
    },
    "url": "https://islandinthenet.com/open-web/",
    "published": "2019-12-03T14:04:44-05:00",
    "content": {
        "html": "<a href=\"http://beardyguycreative.com/blog/2019/08/20/945/\">The Micro.blog experience and a few thoughts on the open web</a><em> (Beardy Guy Musings)</em>\n<blockquote>I write this and mull it over from the perspective of a creator and as a longer-term user of the \u201cold web\u201d. I have, at least, a basic grasp of the ideal (and importance of) the open web, ownership and access. I write it as someone frustrated with the nastiness of the business practices of the corporate entities that own the big social media as well as the lack of moderation on those sites making them potentially dangerous places. But even amongst the relatively tech fluent (and likely, financially affluent) community of tech/apple oriented users that I follow on Twitter, there is little impulse to move to alternatives such as Micro.blog or Mastodon. I\u2019ve seen evidence of an almost complete lack of interest.</blockquote>\n\n<p>As one of those \"old web\" guys who has been blogging for almost two decades, I understand this anguish over the open web. I've seen the rise and fall of alternative like app.net and despite <a href=\"https://islandinthenet.com/inessential-micro-blog-not-another-app-net/\">what others may think</a>, micro.blog's success isn't ensured. The lack of diversity, both cultural and economic, is perhaps why the \"relatively tech fluent (and likely, financially affluent) community of tech/apple oriented users\" ignore micro.blog. It's one of the reasons why, despite having backed the Kickstarter project, I chose to let my hosted micro.blog <a href=\"https://islandinthenet.com/2018-11-07-10-40-45/\">lapse</a> and use micro.blog more like Twitter.</p>\n<p>I've documented my issues in several blog posts.</p>\n<ul><li><a href=\"https://islandinthenet.com/community-norms/\">Community Norms?</a></li>\n<li><a href=\"https://islandinthenet.com/thoughts-on-micro-blog/\">Thoughts on micro.blog</a></li>\n<li><a href=\"https://islandinthenet.com/micro-blog-and-indieweb/\">Micro.blog and IndieWeb</a></li>\n<li><a href=\"https://islandinthenet.com/web-country-club/\">You Can't Start the Revolution from the Web Country Club</a></li>\n<li><a href=\"https://islandinthenet.com/going-full-indie/\">Going Full Indie</a><br />Others have voiced similar complaints.</li>\n<li>\n<p><a href=\"http://blog.bellebcooper.com/leaving-microblog.html\">Why I'm leaving Micro.blog</a></p>\n</li>\n<li><a href=\"https://islandinthenet.com/phoneboy-abandons-micro-blog/\">PhoneBoy abandons micro.blog</a></li>\n</ul><p>I prefer the approach advocated by the <a href=\"https://islandinthenet.com/indieweb-wordpress/\">IndieWeb</a> and have also written about the <a href=\"https://islandinthenet.com/blog-discovery/\">issue of discovery</a> for independent blogs who don't use social media.</p>",
        "text": "The Micro.blog experience and a few thoughts on the open web (Beardy Guy Musings)\nI write this and mull it over from the perspective of a creator and as a longer-term user of the \u201cold web\u201d. I have, at least, a basic grasp of the ideal (and importance of) the open web, ownership and access. I write it as someone frustrated with the nastiness of the business practices of the corporate entities that own the big social media as well as the lack of moderation on those sites making them potentially dangerous places. But even amongst the relatively tech fluent (and likely, financially affluent) community of tech/apple oriented users that I follow on Twitter, there is little impulse to move to alternatives such as Micro.blog or Mastodon. I\u2019ve seen evidence of an almost complete lack of interest.\n\nAs one of those \"old web\" guys who has been blogging for almost two decades, I understand this anguish over the open web. I've seen the rise and fall of alternative like app.net and despite what others may think, micro.blog's success isn't ensured. The lack of diversity, both cultural and economic, is perhaps why the \"relatively tech fluent (and likely, financially affluent) community of tech/apple oriented users\" ignore micro.blog. It's one of the reasons why, despite having backed the Kickstarter project, I chose to let my hosted micro.blog lapse and use micro.blog more like Twitter.\nI've documented my issues in several blog posts.\nCommunity Norms?\nThoughts on micro.blog\nMicro.blog and IndieWeb\nYou Can't Start the Revolution from the Web Country Club\nGoing Full Indie\nOthers have voiced similar complaints.\n\nWhy I'm leaving Micro.blog\n\nPhoneBoy abandons micro.blog\nI prefer the approach advocated by the IndieWeb and have also written about the issue of discovery for independent blogs who don't use social media."
    },
    "post-type": "note",
    "_id": "6659510",
    "_source": "242",
    "_is_read": true
}

Jamie Tanna www.jvt.me

Self-hosted site outranking Medium Publication

{
    "type": "entry",
    "published": "2019-12-03T09:50:00Z",
    "url": "https://www.jvt.me/mf2/2019/12/ywwsm/",
    "category": [
        "indieweb"
    ],
    "bookmark-of": [
        "https://www.indiehackers.com/product/prototypr-io/self-hosted-site-outranking-medium-publication--LuqyKHQ9gno3JFsyoXc"
    ],
    "name": "Self-hosted site outranking Medium Publication",
    "content": {
        "text": "Another reason folks should be part of the IndieWeb, not only owning your data but getting better SEO!\nhttps://indieweb.org/why",
        "html": "<p>Another reason folks should be part of the IndieWeb, not only owning your data but getting better SEO!\n<a href=\"https://indieweb.org/why\">https://indieweb.org/why</a></p>"
    },
    "author": {
        "type": "card",
        "name": "Jamie Tanna",
        "url": "https://www.jvt.me",
        "photo": "https://www.jvt.me/img/profile.png"
    },
    "post-type": "bookmark",
    "_id": "6647767",
    "_source": "2169",
    "_is_read": true
}

Tantek Çelik tantek.com

{
    "type": "entry",
    "published": "2019-12-02 21:02-0800",
    "rsvp": "yes",
    "url": "http://tantek.com/2019/336/t2/hosting-indiewebcamp-sf",
    "category": [
        "AEASF"
    ],
    "in-reply-to": [
        "https://2019.indieweb.org/sf"
    ],
    "content": {
        "text": "hosting @IndieWebCamp SF this Saturday & Sunday @MozSF with @DShanske\n\n@adactio @dietrich @generativist @JenSimmons will be there!\n\n@ZoeSchiffer @pvh @JohnMattDavis @JackyAlcine @AndiGalpern & #AEASF folks: join us!\n\nTickets: https://2019.indieweb.org/sf",
        "html": "hosting <a class=\"h-cassis-username\" href=\"https://twitter.com/IndieWebCamp\">@IndieWebCamp</a> SF this Saturday &amp; Sunday <a class=\"h-cassis-username\" href=\"https://twitter.com/MozSF\">@MozSF</a> with <a class=\"h-cassis-username\" href=\"https://twitter.com/DShanske\">@DShanske</a><br /><br /><a class=\"h-cassis-username\" href=\"https://twitter.com/adactio\">@adactio</a> <a class=\"h-cassis-username\" href=\"https://twitter.com/dietrich\">@dietrich</a> <a class=\"h-cassis-username\" href=\"https://twitter.com/generativist\">@generativist</a> <a class=\"h-cassis-username\" href=\"https://twitter.com/JenSimmons\">@JenSimmons</a> will be there!<br /><br /><a class=\"h-cassis-username\" href=\"https://twitter.com/ZoeSchiffer\">@ZoeSchiffer</a> <a class=\"h-cassis-username\" href=\"https://twitter.com/pvh\">@pvh</a> <a class=\"h-cassis-username\" href=\"https://twitter.com/JohnMattDavis\">@JohnMattDavis</a> <a class=\"h-cassis-username\" href=\"https://twitter.com/JackyAlcine\">@JackyAlcine</a> <a class=\"h-cassis-username\" href=\"https://twitter.com/AndiGalpern\">@AndiGalpern</a> &amp; #<span class=\"p-category\">AEASF</span> folks: join us!<br /><br />Tickets: <a href=\"https://2019.indieweb.org/sf\">https://2019.indieweb.org/sf</a>"
    },
    "author": {
        "type": "card",
        "name": "Tantek \u00c7elik",
        "url": "http://tantek.com/",
        "photo": "https://aperture-media.p3k.io/tantek.com/acfddd7d8b2c8cf8aa163651432cc1ec7eb8ec2f881942dca963d305eeaaa6b8.jpg"
    },
    "post-type": "rsvp",
    "refs": {
        "https://2019.indieweb.org/sf": {
            "type": "entry",
            "url": "https://2019.indieweb.org/sf",
            "name": "an IndieWeb event",
            "post-type": "article"
        }
    },
    "_id": "6647590",
    "_source": "1",
    "_is_read": true
}

IndieWeb Challenge Day 3

{
    "type": "entry",
    "published": "2019-12-03T10:30:00+01:00",
    "url": "https://www.jeremycherfas.net/blog/indieweb-challenge-day-3",
    "name": "IndieWeb Challenge Day 3",
    "content": {
        "text": "One of the worthwhile things about a commitment like this is that fixing even the smallest thing becomes worthwhile. Today, it was an oddity I noticed in the JSON feed for the site. I noticed it because it seemed that micro.blog had not picked up the two most recent posts. In fact it had, but it had given them a timestamp of midnight on the day in question. And I had also switched from the RSS feed, which was throwing errors, to the JSON feed, which wasn't.",
        "html": "<p>One of the worthwhile things about a commitment like this is that fixing even the smallest thing becomes worthwhile. Today, it was an oddity I noticed in the JSON feed for the site. I noticed it because it seemed that <a href=\"https://micro.blog/\">micro.blog</a> had not picked up the two most recent posts. In fact it had, but it had given them a timestamp of midnight on the day in question. And I had also switched from the RSS feed, which was throwing errors, to the JSON feed, which wasn't.</p>"
    },
    "author": {
        "type": "card",
        "name": "Jeremy Cherfas",
        "url": "https://jeremycherfas.net",
        "photo": null
    },
    "post-type": "article",
    "_id": "6647044",
    "_source": "202",
    "_is_read": true
}