I'm hoping that I'll keep a bit more on top of mentions not being sent, and may even look at scheduling a batch to re-process mentions that haven't sent (although I'm pretty sure I set up my Webmention processor to do that for me)
{
"type": "entry",
"published": "2020-04-20T23:31:32.752+02:00",
"url": "https://www.jvt.me/mf2/2020/04/vafra/",
"in-reply-to": [
"https://www.jvt.me/mf2/2020/04/knfnz/"
],
"content": {
"text": "I'm hoping that I'll keep a bit more on top of mentions not being sent, and may even look at scheduling a batch to re-process mentions that haven't sent (although I'm pretty sure I set up my Webmention processor to do that for me)",
"html": "<p>I'm hoping that I'll keep a bit more on top of mentions not being sent, and may even look at scheduling a batch to re-process mentions that haven't sent (although I'm pretty sure I set up my Webmention processor to do that for me)</p>"
},
"author": {
"type": "card",
"name": "Jamie Tanna",
"url": "https://www.jvt.me",
"photo": "https://www.jvt.me/img/profile.png"
},
"post-type": "reply",
"_id": "10926986",
"_source": "2169",
"_is_read": true
}
Steve Ivy
Also, I really need to implement a webmention server https://webmention.rocks/
{
"type": "entry",
"published": "2020-04-20 05:30:50",
"url": "http://monkinetic.blog/2020/04/20/#txt-ba6781d",
"content": {
"text": "Also, I really need to implement a webmention server https://webmention.rocks/",
"html": "<p>Also, I really need to implement a webmention server <a href=\"https://webmention.rocks/\">https://webmention.rocks/</a></p>"
},
"author": {
"type": "card",
"name": "Steve Ivy",
"url": false,
"photo": "http://monkinetic.blog/static/images/sivy_avatar_256.png"
},
"post-type": "note",
"_id": "10926580",
"_source": "4486",
"_is_read": true
}
{
"type": "entry",
"author": {
"name": "Manton Reece",
"url": "https://www.manton.org/",
"photo": "https://micro.blog/manton/avatar.jpg"
},
"url": "https://www.manton.org/2020/04/20/api-history-detour.html",
"name": "API history detour for Micro.blog + MarsEdit 4.4",
"content": {
"html": "<p>Micro.blog supports primarily 2 APIs for posting to hosted blogs:</p>\n\n<ul><li><strong>Micropub</strong>, the IndieWeb API used in the official Micro.blog apps.</li>\n<li><strong>MetaWeblog</strong>, the XML-RPC API used in MarsEdit for macOS.</li>\n</ul><p>XML-RPC used to be the standard for blog posting, widely supported in all blogging platforms. It is still used in WordPress today, and I\u2019ve supported it in Micro.blog from the beginning. I\u2019ve always wanted Micro.blog to be compatible with as many apps as possible, especially MarsEdit.</p>\n\n<p>To understand XML-RPC, we have to go <em>way back</em> in blogging history, to 2001 and the original Blogger API by Evan Williams. Micro.blog\u2019s support for XML-RPC still closely matches what the API looked like nearly 20 years ago.</p>\n\n<p>As is obvious from the name, requests and responses in XML-RPC are sent as XML. Common data types such as integers, strings, and structs are encoded with rules outlined in the XML-RPC specification. To create a new post in the original Blogger API with the words \u201cHello world\u201d, the request to the method <code>blogger.newPost</code> might look like this:</p>\n\n<pre><code><?xml version=\"1.0\"?>\n<methodCall>\n <methodName>blogger.newPost</methodName>\n <params>\n <param>\n <value><int>app ID</int></value>\n </param>\n <param>\n <value><int>blog ID</int></value>\n </param>\n <param>\n <value><string>manton</string></value>\n </param>\n <param>\n <value><string>mypassword</string></value>\n </param>\n <param>\n <value><string>Hello world.</string></value>\n </param>\n <param>\n <value><boolean>1</boolean></value>\n </param>\n </params>\n</methodCall>\n</code></pre>\n\n<p>Subsequent blogging platforms extended the Blogger API with their own features. Instead of <code>blogger.newPost</code>, Movable Type had <code>mt.newPost</code> with similar parameters, adding a title field. WordPress had <code>wordpress.newPost</code>.</p>\n\n<p>To try to unify future improvements under a vendor-neutral standard, Dave Winer proposed the <a href=\"http://1998.xmlrpc.com/metaWeblogApi.html\">MetaWeblog API</a>. MetaWeblog switched to passing content as structs, which could more easily be extended with additional fields, and added an image upload API, <code>metaWeblog.newMediaObject</code>. Dave patterned the field names after RSS:</p>\n\n<blockquote>\n<p>The MetaWeblog API uses an XML-RPC struct to represent a weblog post. Rather than invent a new vocabulary for the metadata of a weblog post, we use the vocabulary for an <a href=\"https://cyber.harvard.edu/rss/rss.html#hrelementsOfLtitemgt\">item</a> in RSS 2.0. So you can refer to a post\u2019s title, link and description; or its author, comments, enclosure, guid, etc using the already-familiar names given to those elements in RSS 2.0.</p>\n</blockquote>\n\n<p>Dave wasn\u2019t the only one who hoped to bring consistency between feed formats and a blogging API. A couple years later, AtomPub was created based on Atom feeds.</p>\n\n<p>Ben Trott of Six Apart, makers of Movable Type, <a href=\"https://web.archive.org/web/20030707045207/http://www.sixapart.com/log/2003/06/why_we_need_ech.shtml\">blogged at the time</a> about the benefits to basing an API on the Atom feed format, which back then was called Echo:</p>\n\n<blockquote>\n<p>Benefits to developers: using the same data model and serialization for syndication, archiving, and editing simplifies the development of tools to work with (produce and consume) these formats, for obvious reasons: code written to produce an item in an Echo feed, for example, can also be used for producing data sent in an API request or packaged up for archiving.</p>\n</blockquote>\n\n<p>AtomPub was adopted in Blogger but is not supported in any other modern blogging platforms. Earlier this year, MarsEdit developer Daniel Jalkut announced that he would also be phasing out support for posting to Blogger.</p>\n\n<p>Between the early 2000s when there was so much activity around blogging standards, and the growth of the IndieWeb and W3C-recommended standard Micropub API in 2017, there was a notable lack of innovation in blogging. Everyone was pulled away to social networks. Platform-specific APIs became the norm. It is because if this lull that XML-RPC survived so long without a modern replacement.</p>\n\n<p>So that brings us to today. Micro.blog has always worked with MarsEdit, but because it\u2019s based on a standard that was frozen, MarsEdit could not support all of Micro.blog\u2019s features. And while Micropub is clearly the future, there is more we could do <em>now</em> without requiring MarsEdit to be adapted for Micropub.</p>\n\n<p>I\u2019ve been working with Daniel to identity what is missing from MetaWeblog and rolling that into a new Micro.blog-specific flavor of XML-RPC. This is essentially what Movable Type and WordPress had done years ago. I had avoided it until now because Micro.blog should default to supporting standards wherever possible before inventing something new.</p>\n\n<p>We talked through this on <a href=\"https://coreint.org/2020/04/episode-416-wait-ten-years/\">Core Intuition 416</a>. Now that there\u2019s <a href=\"https://danielpunkass.micro.blog/2020/04/17/marsedit-will-include.html\">an alpha of MarsEdit 4.4</a> available, I\u2019ve <a href=\"https://help.micro.blog/2020/xmlrpc-microblog/\">documented the new API parameters here</a>. It is based on MetaWeblog, but cleaned up with more consistent field names and support for new features such as creating and editing pages on your blog, server drafts, and downloading all posts.</p>\n\n<p>Micro.blog now shows up in MarsEdit as one of the supported blog systems, along with Tumblr and WordPress:</p>\n\n<p><img src=\"https://www.manton.org/uploads/2020/b3d856155a.png\" alt=\"MarsEdit systems\" border=\"0\" width=\"313\" height=\"356\" style=\"max-width:313px;\" /></p>\n\n<p>I\u2019ve been using the new MarsEdit for the last few days, and it really is a big improvement for Micro.blog. Keep an eye out for the final release.</p>",
"text": "Micro.blog supports primarily 2 APIs for posting to hosted blogs:\n\nMicropub, the IndieWeb API used in the official Micro.blog apps.\nMetaWeblog, the XML-RPC API used in MarsEdit for macOS.\nXML-RPC used to be the standard for blog posting, widely supported in all blogging platforms. It is still used in WordPress today, and I\u2019ve supported it in Micro.blog from the beginning. I\u2019ve always wanted Micro.blog to be compatible with as many apps as possible, especially MarsEdit.\n\nTo understand XML-RPC, we have to go way back in blogging history, to 2001 and the original Blogger API by Evan Williams. Micro.blog\u2019s support for XML-RPC still closely matches what the API looked like nearly 20 years ago.\n\nAs is obvious from the name, requests and responses in XML-RPC are sent as XML. Common data types such as integers, strings, and structs are encoded with rules outlined in the XML-RPC specification. To create a new post in the original Blogger API with the words \u201cHello world\u201d, the request to the method blogger.newPost might look like this:\n\n<?xml version=\"1.0\"?>\n<methodCall>\n <methodName>blogger.newPost</methodName>\n <params>\n <param>\n <value><int>app ID</int></value>\n </param>\n <param>\n <value><int>blog ID</int></value>\n </param>\n <param>\n <value><string>manton</string></value>\n </param>\n <param>\n <value><string>mypassword</string></value>\n </param>\n <param>\n <value><string>Hello world.</string></value>\n </param>\n <param>\n <value><boolean>1</boolean></value>\n </param>\n </params>\n</methodCall>\n\n\nSubsequent blogging platforms extended the Blogger API with their own features. Instead of blogger.newPost, Movable Type had mt.newPost with similar parameters, adding a title field. WordPress had wordpress.newPost.\n\nTo try to unify future improvements under a vendor-neutral standard, Dave Winer proposed the MetaWeblog API. MetaWeblog switched to passing content as structs, which could more easily be extended with additional fields, and added an image upload API, metaWeblog.newMediaObject. Dave patterned the field names after RSS:\n\n\nThe MetaWeblog API uses an XML-RPC struct to represent a weblog post. Rather than invent a new vocabulary for the metadata of a weblog post, we use the vocabulary for an item in RSS 2.0. So you can refer to a post\u2019s title, link and description; or its author, comments, enclosure, guid, etc using the already-familiar names given to those elements in RSS 2.0.\n\n\nDave wasn\u2019t the only one who hoped to bring consistency between feed formats and a blogging API. A couple years later, AtomPub was created based on Atom feeds.\n\nBen Trott of Six Apart, makers of Movable Type, blogged at the time about the benefits to basing an API on the Atom feed format, which back then was called Echo:\n\n\nBenefits to developers: using the same data model and serialization for syndication, archiving, and editing simplifies the development of tools to work with (produce and consume) these formats, for obvious reasons: code written to produce an item in an Echo feed, for example, can also be used for producing data sent in an API request or packaged up for archiving.\n\n\nAtomPub was adopted in Blogger but is not supported in any other modern blogging platforms. Earlier this year, MarsEdit developer Daniel Jalkut announced that he would also be phasing out support for posting to Blogger.\n\nBetween the early 2000s when there was so much activity around blogging standards, and the growth of the IndieWeb and W3C-recommended standard Micropub API in 2017, there was a notable lack of innovation in blogging. Everyone was pulled away to social networks. Platform-specific APIs became the norm. It is because if this lull that XML-RPC survived so long without a modern replacement.\n\nSo that brings us to today. Micro.blog has always worked with MarsEdit, but because it\u2019s based on a standard that was frozen, MarsEdit could not support all of Micro.blog\u2019s features. And while Micropub is clearly the future, there is more we could do now without requiring MarsEdit to be adapted for Micropub.\n\nI\u2019ve been working with Daniel to identity what is missing from MetaWeblog and rolling that into a new Micro.blog-specific flavor of XML-RPC. This is essentially what Movable Type and WordPress had done years ago. I had avoided it until now because Micro.blog should default to supporting standards wherever possible before inventing something new.\n\nWe talked through this on Core Intuition 416. Now that there\u2019s an alpha of MarsEdit 4.4 available, I\u2019ve documented the new API parameters here. It is based on MetaWeblog, but cleaned up with more consistent field names and support for new features such as creating and editing pages on your blog, server drafts, and downloading all posts.\n\nMicro.blog now shows up in MarsEdit as one of the supported blog systems, along with Tumblr and WordPress:\n\n\n\nI\u2019ve been using the new MarsEdit for the last few days, and it really is a big improvement for Micro.blog. Keep an eye out for the final release."
},
"published": "2020-04-20T12:44:45-05:00",
"category": [
"Photos",
"Essays",
"Podcasts"
],
"post-type": "article",
"_id": "10925248",
"_source": "12",
"_is_read": true
}
I've been doing a lot of #IndieWeb things recently which allow me to own my data a lot better - such as this tweet which is actually published to my site first, then gets syndicated to Twitter - been fun for many reasons
{
"type": "entry",
"published": "2020-04-20T09:38:00+01:00",
"url": "https://www.jvt.me/mf2/2020/04/jowbi/",
"category": [
"indieweb"
],
"in-reply-to": [
"https://twitter.com/saronyitbarek/status/1252038372484358145"
],
"content": {
"text": "I've been doing a lot of #IndieWeb things recently which allow me to own my data a lot better - such as this tweet which is actually published to my site first, then gets syndicated to Twitter - been fun for many reasons",
"html": "<p>I've been doing a lot of <a href=\"https://www.jvt.me/tags/indieweb/\">#IndieWeb</a> things recently which allow me to own my data a lot better - such as this tweet which is actually published to my site first, then gets syndicated to Twitter - been fun for many reasons</p>"
},
"author": {
"type": "card",
"name": "Jamie Tanna",
"url": "https://www.jvt.me",
"photo": "https://www.jvt.me/img/profile.png"
},
"post-type": "reply",
"_id": "10908065",
"_source": "2169",
"_is_read": true
}
Hey Spencer, thanks for the kind words.
Have you seen indiebookclub.biz? That’s a little tool I’ve put together that makes it easier to post those read posts to your site. It’s via Micropub and there is an indieweb plugin that adds Micropub support to Wordpress sites, so you might be closer to achieving this than you think!
I’m not super familiar with the WordPress plugin, but the IndieWeb WordPress community would be happy to help with any questions. There’s a dedicated chat channel for WordPress if you want to stop by. More details at indieweb.org/discuss.
{
"type": "entry",
"published": "2020-04-19 00:27-0700",
"url": "https://gregorlove.com/2020/04/hey-spencer-thanks-for-the/",
"in-reply-to": [
"https://blog.spencerdub.me/like-gregor-morrill-reading/"
],
"content": {
"text": "Hey Spencer, thanks for the kind words.\n\nHave you seen indiebookclub.biz? That\u2019s a little tool I\u2019ve put together that makes it easier to post those read posts to your site. It\u2019s via Micropub and there is an indieweb plugin that adds Micropub support to Wordpress sites, so you might be closer to achieving this than you think!\n\nI\u2019m not super familiar with the WordPress plugin, but the IndieWeb WordPress community would be happy to help with any questions. There\u2019s a dedicated chat channel for WordPress if you want to stop by. More details at indieweb.org/discuss.",
"html": "<p>Hey Spencer, thanks for the kind words.</p>\n\n<p>Have you seen <a href=\"https://indiebookclub.biz\">indiebookclub.biz</a>? That\u2019s a little tool I\u2019ve put together that makes it easier to post those read posts to your site. It\u2019s via Micropub and there is an indieweb plugin that adds Micropub support to Wordpress sites, so you might be closer to achieving this than you think!</p>\n\n<p>I\u2019m not super familiar with the WordPress plugin, but the IndieWeb WordPress community would be happy to help with any questions. There\u2019s a dedicated chat channel for WordPress if you want to stop by. More details at <a href=\"https://indieweb.org/discuss\">indieweb.org/discuss</a>.</p>"
},
"post-type": "reply",
"refs": {
"https://blog.spencerdub.me/like-gregor-morrill-reading/": {
"type": "entry",
"url": "https://blog.spencerdub.me/like-gregor-morrill-reading/",
"name": "https://blog.spencerdub.me/like-gregor-morrill-reading/",
"post-type": "article"
}
},
"_id": "10884526",
"_source": "95",
"_is_read": true
}
Hey @kickscondor not sure if you've seen but the cert for https://indieweb.xyz/ seems to have expired - "4/18/2020, 12:32:43 AM (British Summer Time)" according to the cert. May need a nudge to renew it!
{
"type": "entry",
"published": "2020-04-18T15:22:52.839+02:00",
"url": "https://www.jvt.me/mf2/2020/04/gtepu/",
"content": {
"text": "Hey @kickscondor not sure if you've seen but the cert for https://indieweb.xyz/ seems to have expired - \"4/18/2020, 12:32:43 AM (British Summer Time)\" according to the cert. May need a nudge to renew it!",
"html": "<p>Hey <span class=\"h-card\"><a class=\"u-url\" href=\"https://twitter.com/kickscondor\">@kickscondor</a></span> not sure if you've seen but the cert for <a href=\"https://indieweb.xyz/\">https://indieweb.xyz/</a> seems to have expired - \"4/18/2020, 12:32:43 AM (British Summer Time)\" according to the cert. May need a nudge to renew it!</p>"
},
"author": {
"type": "card",
"name": "Jamie Tanna",
"url": "https://www.jvt.me",
"photo": "https://www.jvt.me/img/profile.png"
},
"post-type": "note",
"_id": "10861949",
"_source": "2169",
"_is_read": true
}
Code is merged, bugs fixed in both Micropub and post-deploy, so this should work!
{
"type": "entry",
"published": "2020-04-18T14:31:04.736+02:00",
"url": "https://www.jvt.me/mf2/2020/04/esl2l/",
"in-reply-to": [
"https://twitter.com/JamieTanna/status/1251200698274009094"
],
"content": {
"text": "Code is merged, bugs fixed in both Micropub and post-deploy, so this should work!",
"html": "<p>Code is merged, bugs fixed in both Micropub and post-deploy, so this should work!</p>"
},
"author": {
"type": "card",
"name": "Jamie Tanna",
"url": "https://www.jvt.me",
"photo": "https://www.jvt.me/img/profile.png"
},
"post-type": "reply",
"_id": "10861434",
"_source": "2169",
"_is_read": true
}
{
"type": "entry",
"published": "2020-04-17T14:47:32-0400",
"url": "https://martymcgui.re/2020/04/17/indieweb-nyc-aka-virtual-hwc-us-east-meetup-2020-04-15-wrap-up/",
"category": [
"IndieWeb",
"meetup",
"HWC",
"NYC",
"virtual",
"vHWC",
"wrap-up"
],
"name": "IndieWeb NYC (aka Virtual HWC US East) Meetup 2020-04-15 Wrap-Up",
"content": {
"text": "IndieWeb NYC's meetup for April 2020 (also virtual Homebrew Website Club US East, met on Zoom from 6pm - 8pm EDT on April 15th. It was mostly NYC folks, with one joining briefly from Portland!\nHere are some notes from the meeting!\njmac.org \u2014 writing about webmentions on fogknife.com. Learned a lot about them through sending a \"strange\" RSVP to an event at events.indieweb.org. The RSVP was a longer post, which also included an RSVP inside it. events.indieweb.org treated the post as both an RSVP and a blog post about the event. Jason enjoyed learning about moderating webmentions through that experience! He also accidentally reposted a bunch of links to IndieNews because his site moved from http to https, and those are \"new links\". Eek!\n\n aaronpk.com \u2014 had some time between giving a workshop and speaking at allthetalks.online. can now post photos from his Nintendo Switch to his website by making a new Twitter account that is just for posts from his Switch, then setting up a cron task to pull and post new tweets to special tags on his site, like the #ACNH tag for posts from Animal Crossing New Horizons.\n \n\ndavid.shanske.com \u2014 now a member of NOAA's Citizen Weather Observing Program (CWOP)! Making him an official weather source. Working on a large project of archiving IndieWeb event videos from YouTube to archive.org. Hopes to find interested in re-watching some older IndieWebCamp videos to reconstruct notes that were lost when Mozilla recently shut down their Etherpad instance.\nmartymcgui.re \u2014 Still posting one cat GIF per day during the COVID-19 shutdown in NYC. Recently started work on a \"consolidated watch later\" list using IndieWeb building blocks - mostly with microsub channels in Aperture as a queuing mechanism.\nOther topics of discussion.\nHome studios! aaronpk has a very nice setup with multiple cameras, switchers, and great lighting. Marty has some parts on order so he can use a DLSR as a webcam. GWG has a nice set up also!\n Personal \"this is how I IndieWeb\" pages might be useful for helping on-board developers, since each is a personal setup and won't immediately be considered \"expert advice\". For example, Marty's page on the IndieWeb wiki. Starts at a very high level and adds more detail the further you read.\n More open tests for Webmentions (beyond the strictly-plumbing webmention.rocks)\n Sourcing home supplies in this time of lockdown. GWG recommends bidets.\nLeft-to-right: david.shanske.com, jmac.org, martymcgui.reThanks to all who joined us! We will see you all again at our next IndieWeb NYC (aka vHWC US East) meetup online on May 20th! Keep an eye on indieweb.nyc or events.indieweb.org/tag/nyc for the exact date, time, and online location!",
"html": "<p><a href=\"https://events.indieweb.org/2020/04/online-indieweb-meetup-nyc-xzPxXTK5HGbe\">IndieWeb NYC's meetup for April 2020 (also virtual Homebrew Website Club US East</a>, met on Zoom from 6pm - 8pm EDT on April 15th. It was mostly NYC folks, with one joining briefly from Portland!</p>\n<p>Here are some notes from the meeting!</p>\n<p>jmac.org \u2014 writing about webmentions on fogknife.com. Learned a lot about them through sending a \"strange\" RSVP to an event at events.indieweb.org. The RSVP was a longer post, which also included an RSVP inside it. events.indieweb.org treated the post as both an RSVP and a blog post about the event. Jason enjoyed learning about moderating webmentions through that experience! He also accidentally reposted a bunch of links to IndieNews because his site moved from http to https, and those are \"new links\". Eek!</p>\n<p>\n aaronpk.com \u2014 had some time between giving a workshop and speaking at <a href=\"https://allthetalks.online/\">allthetalks.online</a>. can now post photos from his Nintendo Switch to his website by making a new Twitter account that is just for posts from his Switch, then setting up a cron task to pull and post new tweets to special tags on his site, like the <a href=\"https://aaronparecki.com/tag/acnh\">#ACNH tag </a>for posts from Animal Crossing New Horizons.\n <br /></p>\n<p>david.shanske.com \u2014 now a member of NOAA's <a href=\"https://en.wikipedia.org/wiki/Citizen_Weather_Observer_Program\">Citizen Weather Observing Program (CWOP)</a>! Making him an official weather source. Working on a large project of archiving IndieWeb event videos from YouTube to archive.org. Hopes to find interested in re-watching some older IndieWebCamp videos to reconstruct notes that were lost when Mozilla recently shut down their Etherpad instance.</p>\n<p>martymcgui.re \u2014 Still posting <a href=\"https://martymcgui.re/tag/caturday/\">one cat GIF per day</a> during the COVID-19 shutdown in NYC. Recently started work on a \"consolidated watch later\" list using IndieWeb building blocks - mostly with microsub channels in Aperture as a queuing mechanism.</p>\n<p>Other topics of discussion.</p>\n<ul><li>Home studios! aaronpk has a <a href=\"https://www.youtube.com/watch?v=yNzU-TPdxR4\">very nice setup</a> with multiple cameras, switchers, and great lighting. Marty has some parts on order so he can use a DLSR as a webcam. GWG has a nice set up also!</li>\n <li>Personal \"this is how I IndieWeb\" pages might be useful for helping on-board developers, since each is a personal setup and won't immediately be considered \"expert advice\". For example, <a href=\"https://indieweb.org/User:Martymcgui.re#My_IndieWeb_Setup\">Marty's page on the IndieWeb wiki</a>. Starts at a very high level and adds more detail the further you read.</li>\n <li>More open tests for Webmentions (beyond the strictly-plumbing <a href=\"https://webmention.rocks/\">webmention.rocks</a>)</li>\n <li>Sourcing home supplies in this time of lockdown. GWG recommends bidets.</li>\n</ul><img src=\"https://media.martymcgui.re/54/d9/22/a5/0cb622d13f60ff4cb32e7752eadb577dbaa4805950003ea9198c7a2f.png\" alt=\"\" />Left-to-right: david.shanske.com, jmac.org, martymcgui.re<p>Thanks to all who joined us! We will see you all again at our next <a href=\"https://events.indieweb.org/2020/05/online-indieweb-meetup-nyc-vkY32vBfCTEJ\">IndieWeb NYC (aka vHWC US East) meetup online on May 20th</a>! Keep an eye on <a href=\"https://indieweb.nyc/\">indieweb.nyc</a> or <a href=\"https://events.indieweb.org/tag/nyc\">events.indieweb.org/tag/nyc</a> for the exact date, time, and online location!\n</p>"
},
"author": {
"type": "card",
"name": "Marty McGuire",
"url": "https://martymcgui.re/",
"photo": "https://martymcgui.re/images/logo.jpg"
},
"post-type": "article",
"_id": "10842159",
"_source": "175",
"_is_read": true
}
This note will be published to Twitter, and then have its syndicated Twitter URL updated in the post's metadata when the Webmentions are send, so shortly after seeing this post, it'll link directly to its tweet!
{
"type": "entry",
"published": "2020-04-17T18:15:02.959+02:00",
"url": "https://www.jvt.me/mf2/2020/04/ehqnl/",
"content": {
"text": "This note will be published to Twitter, and then have its syndicated Twitter URL updated in the post's metadata when the Webmentions are send, so shortly after seeing this post, it'll link directly to its tweet!",
"html": "<p>This note will be published to Twitter, and then have its syndicated Twitter URL updated in the post's metadata when the Webmentions are send, so shortly after seeing this post, it'll link directly to its tweet!</p>"
},
"author": {
"type": "card",
"name": "Jamie Tanna",
"url": "https://www.jvt.me",
"photo": "https://www.jvt.me/img/profile.png"
},
"post-type": "note",
"_id": "10836593",
"_source": "2169",
"_is_read": true
}
This note will be published to Twitter, and then have its syndicated Twitter URL updated in the post's metadata when the Webmentions are send, so shortly after seeing this post, it'll link directly to its tweet!
{
"type": "entry",
"published": "2020-04-17T18:14:42.94+02:00",
"url": "https://www.jvt.me/mf2/2020/04/noxvu/",
"content": {
"text": "This note will be published to Twitter, and then have its syndicated Twitter URL updated in the post's metadata when the Webmentions are send, so shortly after seeing this post, it'll link directly to its tweet!",
"html": "<p>This note will be published to Twitter, and then have its syndicated Twitter URL updated in the post's metadata when the Webmentions are send, so shortly after seeing this post, it'll link directly to its tweet!</p>"
},
"author": {
"type": "card",
"name": "Jamie Tanna",
"url": "https://www.jvt.me",
"photo": "https://www.jvt.me/img/profile.png"
},
"post-type": "note",
"_id": "10836594",
"_source": "2169",
"_is_read": true
}
A lot of interesting ideas here! The individual book entries appear to be a hybrid of a citation and a review, so I wonder about using microformats2 h-cite and h-review.
On my list of reading posts I use h-cite to mark up the books with the uid being the ISBN or DOI. Check out the parsed result of that page. My list isn’t really a bookshelf since each post has its own read-status, but take a look at the parsed h-cite within each post.
This gets more hypothetical since I have not posted a lot of reviews, but an h-review post could have the item be the book’s h-cite. A bookshelf would then be a stream of h-cite and h-review posts. A nice benefit of that is social readers are already able to subscribe to and display those streams.
{
"type": "entry",
"published": "2020-04-16 17:38-0700",
"url": "https://gregorlove.com/2020/04/a-lot-of-interesting-ideas/",
"in-reply-to": [
"https://tomcritchlow.com/2020/04/15/library-json/"
],
"content": {
"text": "A lot of interesting ideas here! The individual book entries appear to be a hybrid of a citation and a review, so I wonder about using microformats2 h-cite and h-review.\n\nOn my list of reading posts I use h-cite to mark up the books with the uid being the ISBN or DOI. Check out the parsed result of that page. My list isn\u2019t really a bookshelf since each post has its own read-status, but take a look at the parsed h-cite within each post.\n\nThis gets more hypothetical since I have not posted a lot of reviews, but an h-review post could have the item be the book\u2019s h-cite. A bookshelf would then be a stream of h-cite and h-review posts. A nice benefit of that is social readers are already able to subscribe to and display those streams.",
"html": "<p>A lot of interesting ideas here! The individual book entries appear to be a hybrid of a citation and a review, so I wonder about using microformats2 <a href=\"http://microformats.org/wiki/h-cite\">h-cite</a> and <a href=\"http://microformats.org/wiki/h-review\">h-review</a>.</p>\n\n<p>On my <a href=\"https://gregorlove.com/channels/reading/\">list of reading posts</a> I use <code>h-cite</code> to mark up the books with the <code>uid</code> being the <abbr title=\"International Standard Book Number\">ISBN</abbr> or <abbr title=\"Digital object identifier\">DOI</abbr>. Check out the <a href=\"https://php.microformats.io/?url=https%3A%2F%2Fgregorlove.com%2Fchannels%2Freading%2F\">parsed result</a> of that page. My list isn\u2019t really a bookshelf since each post has its own <code>read-status</code>, but take a look at the parsed <code>h-cite</code> within each post.</p>\n\n<p>This gets more hypothetical since I have not posted a lot of reviews, but an <code>h-review</code> post could have the <code>item</code> be the book\u2019s <code>h-cite</code>. A bookshelf would then be a stream of <code>h-cite</code> and <code>h-review</code> posts. A nice benefit of that is <a href=\"https://indieweb.org/social_reader\">social readers</a> are already able to subscribe to and display those streams.</p>"
},
"post-type": "reply",
"refs": {
"https://tomcritchlow.com/2020/04/15/library-json/": {
"type": "entry",
"url": "https://tomcritchlow.com/2020/04/15/library-json/",
"name": "https://tomcritchlow.com/2020/04/15/library-json/",
"post-type": "article"
}
},
"_id": "10821616",
"_source": "95",
"_is_read": true
}
Having a lot of fun on Zoom with my friend Andy, showing off IndieWeb!
{
"type": "entry",
"published": "2020-04-17T00:35:45+00:00",
"url": "https://cleverdevil.io/2020/having-a-lot-of-fun-on-zoom",
"syndication": [
"https://twitter.com/cleverdevil/status/1250946021741510662",
"https://mastodon.social/@cleverdevil/104011120577372338"
],
"content": {
"text": "Having a lot of fun on Zoom with my friend Andy, showing off IndieWeb!"
},
"author": {
"type": "card",
"name": "Jonathan LaCour",
"url": "https://cleverdevil.io/profile/cleverdevil",
"photo": "https://cleverdevil.io/file/fdbc7696a5f73864ea11a828c861e138/thumb.jpg"
},
"post-type": "note",
"_id": "10819082",
"_source": "71",
"_is_read": true
}
This is more-or-less what the IndieWeb is about but with HTML instead of Atom/RSS https://fosstodon.org/@alexbuzzbee/104010481623432265
{
"type": "entry",
"published": "2020-04-16T15:16:45.83134-07:00",
"url": "https://v2.jacky.wtf/post/c688adb8-4971-482c-a542-ff0c431f4e85",
"content": {
"text": "This is more-or-less what the IndieWeb is about but with HTML instead of Atom/RSS https://fosstodon.org/@alexbuzzbee/104010481623432265",
"html": "<p>This is more-or-less what the IndieWeb is about but with HTML instead of Atom/RSS <a href=\"mailto:https://fosstodon.org/@alexbuzzbee/104010481623432265\">https://fosstodon.org/@alexbuzzbee/104010481623432265</a></p>"
},
"author": {
"type": "card",
"name": "",
"url": "https://v2.jacky.wtf",
"photo": null
},
"post-type": "note",
"_id": "10814614",
"_source": "1886",
"_is_read": true
}
{
"type": "entry",
"published": "2020-04-15 15:52-0700",
"rsvp": "yes",
"url": "http://tantek.com/2020/106/t1/homebrew-website-club-west-coast",
"in-reply-to": [
"https://events.indieweb.org/2020/04/online-homebrew-website-club-west-coast-v0BQQ1BYfuhI"
],
"content": {
"text": "going to ONLINE Homebrew Website Club West Coast\n\ud83d\uddd3 18:00 today, now weekly!\n\ud83c\udf9f RSVP & more: https://events.indieweb.org/2020/04/online-homebrew-website-club-west-coast-v0BQQ1BYfuhI\n\u2709\ufe0f Join us! @brb_irl @Kongaloosh @AllAboutGeorge @JackyAlcine @AndiGalpern @indirect @generativist @BenWerd @pvh @JohnMattDavis @html5cat",
"html": "going to ONLINE Homebrew Website Club West Coast<br />\ud83d\uddd3 18:00 today, now weekly!<br />\ud83c\udf9f RSVP & more: <a href=\"https://events.indieweb.org/2020/04/online-homebrew-website-club-west-coast-v0BQQ1BYfuhI\">https://events.indieweb.org/2020/04/online-homebrew-website-club-west-coast-v0BQQ1BYfuhI</a><br />\u2709\ufe0f Join us! <a class=\"h-cassis-username\" href=\"https://twitter.com/brb_irl\">@brb_irl</a> <a class=\"h-cassis-username\" href=\"https://twitter.com/Kongaloosh\">@Kongaloosh</a> <a class=\"h-cassis-username\" href=\"https://twitter.com/AllAboutGeorge\">@AllAboutGeorge</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> <a class=\"h-cassis-username\" href=\"https://twitter.com/indirect\">@indirect</a> <a class=\"h-cassis-username\" href=\"https://twitter.com/generativist\">@generativist</a> <a class=\"h-cassis-username\" href=\"https://twitter.com/BenWerd\">@BenWerd</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/html5cat\">@html5cat</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://events.indieweb.org/2020/04/online-homebrew-website-club-west-coast-v0BQQ1BYfuhI": {
"type": "entry",
"url": "https://events.indieweb.org/2020/04/online-homebrew-website-club-west-coast-v0BQQ1BYfuhI",
"name": "an IndieWeb event",
"post-type": "article"
}
},
"_id": "10783945",
"_source": "1",
"_is_read": true
}
Webmentions are great! They're how I handle all my interactions with my site i.e. https://www.jvt.me/posts/2020/01/11/homebrew-website-club-nottingham-url/ under Interactions with this post and there's great support for WordPress and many static sites, among others!
{
"type": "entry",
"published": "2020-04-15T19:09:49.635+02:00",
"url": "https://www.jvt.me/mf2/2020/04/1w57q/",
"in-reply-to": [
"https://twitter.com/paulienuh/status/1250405998432567296"
],
"content": {
"text": "Webmentions are great! They're how I handle all my interactions with my site i.e. https://www.jvt.me/posts/2020/01/11/homebrew-website-club-nottingham-url/ under Interactions with this post and there's great support for WordPress and many static sites, among others!",
"html": "<p>Webmentions are great! They're how I handle all my interactions with my site i.e. <a href=\"https://www.jvt.me/posts/2020/01/11/homebrew-website-club-nottingham-url/\">https://www.jvt.me/posts/2020/01/11/homebrew-website-club-nottingham-url/</a> under <code>Interactions with this post</code> and there's great support for WordPress and many static sites, among others!</p>"
},
"author": {
"type": "card",
"name": "Jamie Tanna",
"url": "https://www.jvt.me",
"photo": "https://www.jvt.me/img/profile.png"
},
"post-type": "reply",
"_id": "10772732",
"_source": "2169",
"_is_read": true
}
It's #HomebrewWebsiteClub Nottingham tomorrow, which again will only be available for Nottingham folks - apologies in advance! The Zoom link will be available on the Tech Nottingham slack before the event https://events.indieweb.org/2020/04/online-homebrew-website-club-nottingham-h2HHF0o7NPtg
{
"type": "entry",
"published": "2020-04-14T07:43:00+01:00",
"url": "https://www.jvt.me/mf2/2020/04/l04ka/",
"category": [
"homebrew-website-club"
],
"content": {
"text": "It's #HomebrewWebsiteClub Nottingham tomorrow, which again will only be available for Nottingham folks - apologies in advance! The Zoom link will be available on the Tech Nottingham slack before the event https://events.indieweb.org/2020/04/online-homebrew-website-club-nottingham-h2HHF0o7NPtg",
"html": "<p>It's <a href=\"https://www.jvt.me/tags/homebrew-website-club/\">#HomebrewWebsiteClub</a> Nottingham tomorrow, which again will only be available for Nottingham folks - apologies in advance! The Zoom link will be available on the Tech Nottingham slack before the event <a href=\"https://events.indieweb.org/2020/04/online-homebrew-website-club-nottingham-h2HHF0o7NPtg\">https://events.indieweb.org/2020/04/online-homebrew-website-club-nottingham-h2HHF0o7NPtg</a></p>"
},
"author": {
"type": "card",
"name": "Jamie Tanna",
"url": "https://www.jvt.me",
"photo": "https://www.jvt.me/img/profile.png"
},
"post-type": "note",
"_id": "10726682",
"_source": "2169",
"_is_read": true
}
I'm going!Let’s do another Zoom meetup! Watch the events.indieweb.org page for a meeting link to appear shortly before 6pm.
{
"type": "entry",
"published": "2020-04-13T16:25:11-0400",
"rsvp": "yes",
"url": "https://martymcgui.re/2020/04/13/162511/",
"in-reply-to": [
"https://events.indieweb.org/2020/04/online-indieweb-meetup-nyc-xzPxXTK5HGbe"
],
"content": {
"text": "I'm going!Let\u2019s do another Zoom meetup! Watch the events.indieweb.org page for a meeting link to appear shortly before 6pm.",
"html": "I'm going!<p>Let\u2019s do another Zoom meetup! Watch the events.indieweb.org page for a meeting link to appear shortly before 6pm.</p>"
},
"author": {
"type": "card",
"name": "Marty McGuire",
"url": "https://martymcgui.re/",
"photo": "https://martymcgui.re/images/logo.jpg"
},
"post-type": "rsvp",
"refs": {
"https://events.indieweb.org/2020/04/online-indieweb-meetup-nyc-xzPxXTK5HGbe": {
"type": "entry",
"summary": "Join us... on \u2728The Internet!\u2728",
"url": "https://events.indieweb.org/2020/04/online-indieweb-meetup-nyc-xzPxXTK5HGbe",
"name": "ONLINE: IndieWeb Meetup NYC",
"author": {
"type": "card",
"name": "events.indieweb.org",
"url": "http://events.indieweb.org",
"photo": null
},
"post-type": "article"
}
},
"_id": "10718210",
"_source": "175",
"_is_read": true
}
Woo! Got #Micropub edit functionality working 🙌 https://gitlab.com/jamietanna/jvt.me/-/commit/fda688f955c351000095a7e5c8ee294513afad6b is my first update through the API. Next will be getting my syndication links auto updated once syndication is reported as successful, but not one to do tonight
{
"type": "entry",
"published": "2020-04-13T23:29:27.142+02:00",
"url": "https://www.jvt.me/mf2/2020/04/srktw/",
"category": [
"www.jvt.me",
"micropub"
],
"content": {
"text": "Woo! Got #Micropub edit functionality working \ud83d\ude4c https://gitlab.com/jamietanna/jvt.me/-/commit/fda688f955c351000095a7e5c8ee294513afad6b is my first update through the API. Next will be getting my syndication links auto updated once syndication is reported as successful, but not one to do tonight",
"html": "<p>Woo! Got <a href=\"https://www.jvt.me/tags/micropub/\">#Micropub</a> edit functionality working \ud83d\ude4c <a href=\"https://gitlab.com/jamietanna/jvt.me/-/commit/fda688f955c351000095a7e5c8ee294513afad6b\">https://gitlab.com/jamietanna/jvt.me/-/commit/fda688f955c351000095a7e5c8ee294513afad6b</a> is my first update through the API. Next will be getting my syndication links auto updated once syndication is reported as successful, but not one to do tonight</p>"
},
"author": {
"type": "card",
"name": "Jamie Tanna",
"url": "https://www.jvt.me",
"photo": "https://www.jvt.me/img/profile.png"
},
"post-type": "note",
"_id": "10716336",
"_source": "2169",
"_is_read": true
}
{
"type": "entry",
"published": "2020-04-13T12:16:58+0000",
"url": "https://seblog.nl/2020/04/13/3/private-commenting-systems",
"category": [
"indieweb"
],
"syndication": [
"https://twitter.com/sebandeweg/status/1249674051880210435",
"https://news.indieweb.org/en/seblog.nl/2020/04/13/3/private-commenting-systems"
],
"name": "On Private Commenting Systems",
"content": {
"text": "Jan-Lukas wrote about an article by Matt from Write.as called Towards a Commenting System. The article describes a commenting system with two flavour: private and public. For private comments, an e-mail to the author is used; for public comments, one is prompted to publish the comment on their own space first and then notify the original post. It feels very IndieWeb friendly.\nThen, Jan-Lukas points out his own site already does this with webmention (as does mine), and that he also has a contact form, which people could use to reply private (at the time of writing I have no contact form).\nI like the idea of private comments taking another route than public comments. Just having a contact page is not the same though: to complete the idea you can link it with a call-to-action underneath your posts. Let\u2019s not have illusions here: most people will probably not read my posts on my site but in their reader or some other syndicated copy. But, it would give a nice UX for those on my site.\nIt also reminds me of how stories on Instagram work. There is a text box underneath it, which the user can tab to type a message. This message is then sent as a direct message to the creator of the story, and not visible to anyone but the creator and the commenter. It seems to work in that context: I do reply to friends in that way sometimes, because it feels very personal.\nAnother point is that this keeps private comments easier to implement for some and actually possible for those with static generated sites. My site has a way for visitors to log in, and I can build some form of private comments in that way. It is, however, way more work to build and maintain a site that does this, and not everyone is willing to do so. Doing private comments via a different channel makes it easier to have them.\nThe flip-side is that private comments cannot be shared among a group in this way. If you open a post to a certain circle of friends on, say, Facebook, all those friends can comment and also comment on each other\u2019s comments. This kind of interaction is very hard to do, though, if you don\u2019t have the luxury of a central service that guards access to all the posts \u2014 like Facebook does.\nThe conversation is also more likely to be ephemeral, for there are only two readers, both responsible for keeping their copies, with no help of, say, the Internet Archive.\nI remember a moment at IndieWebCamp Brighton when a session about private posts was about to start. Jeremy Keith walked out of the room while making a comment that he didn\u2019t see private pages as something the Web needed. This does not mean I can\u2019t have them, but it did make me think about why I want them and what they would mean to the Web and the world.\nBy putting the private comments on a separate channel, you are also removing them from the Web. This makes the Web a place for open and public conversations again. (Again: one could argue that thing on the \u2018Private Web\u2019 are not on the Web either.) The last few months I\u2019ve been reading more blogs and I must say I really enjoy that open Web. \nThe separation of private comments creates a clearer boundary between the open and the private, and maybe that\u2019s a good thing. It makes an easier question: it\u2019s harder to answer \u201cwhich people should be able to read this post?\u201d, than it is to answer \u201cdoes this concern only me and the author, or could there possibly be someone out there who\u2019s interested?\u201d.\nNo real plans for removal yet, but I keep being torn about private posts.",
"html": "<p>Jan-Lukas <a href=\"https://jlelse.blog/links/2020/04/remark-as/\">wrote about</a> an article by Matt from Write.as called <em><a href=\"https://write.as/matt/towards-a-commenting-system\">Towards a Commenting System</a></em>. The article describes a commenting system with two flavour: private and public. For private comments, an e-mail to the author is used; for public comments, one is prompted to publish the comment on their own space first and then notify the original post. It feels very IndieWeb friendly.</p>\n<p>Then, Jan-Lukas points out his own site already does this with webmention (as does mine), and that he also has a contact form, which people could use to reply private (at the time of writing I have no contact form).</p>\n<p>I like the idea of private comments taking another route than public comments. Just having a contact page is not the same though: to complete the idea you can link it with a call-to-action underneath your posts. Let\u2019s not have illusions here: most people will probably not read my posts on my site but in their reader or some other syndicated copy. But, it would give a nice UX for those on my site.</p>\n<p>It also reminds me of how stories on Instagram work. There is a text box underneath it, which the user can tab to type a message. This message is then sent as a direct message to the creator of the story, and not visible to anyone but the creator and the commenter. It seems to work in that context: I do reply to friends in that way sometimes, because it feels very personal.</p>\n<p>Another point is that this keeps private comments easier to implement for some and actually possible for those with <a href=\"https://indieweb.org/static_site_generator\">static generated sites</a>. My site has a way for visitors to log in, and I can build some form of private comments in that way. It is, however, way more work to build and maintain a site that does this, and not everyone is willing to do so. Doing private comments via a different channel makes it easier to have them.</p>\n<p>The flip-side is that private comments cannot be shared among a group in this way. If you open a post to a certain circle of friends on, say, Facebook, all those friends can comment and also comment on each other\u2019s comments. This kind of interaction is very hard to do, though, if you don\u2019t have the luxury of a central service that guards access to all the posts \u2014 like Facebook does.</p>\n<p>The conversation is also more likely to be ephemeral, for there are only two readers, both responsible for keeping their copies, with no help of, say, the Internet Archive.</p>\n<p>I remember a moment at <a href=\"https://indieweb.org/2019/Brighton\">IndieWebCamp Brighton</a> when a session about private posts was about to start. <a href=\"https://adactio.com/\">Jeremy Keith</a> walked out of the room while making a comment that he didn\u2019t see private pages as something the Web needed. This does not mean I can\u2019t have them, but it did make me think about why I want them and what they would mean to the Web and the world.</p>\n<p>By putting the private comments on a separate channel, you are also removing them from the Web. This makes the Web a place for open and public conversations again. (Again: one could argue that thing on the \u2018Private Web\u2019 are not on the Web either.) The last few months I\u2019ve been reading more blogs and I must say I really enjoy that open Web. </p>\n<p>The separation of private comments creates a clearer boundary between the open and the private, and maybe that\u2019s a good thing. It makes an easier question: it\u2019s harder to answer \u201cwhich people should be able to read this post?\u201d, than it is to answer \u201cdoes this concern only me and the author, or could there possibly be someone out there who\u2019s interested?\u201d.</p>\n<p>No real plans for removal yet, but I keep being torn about private posts.</p>"
},
"author": {
"type": "card",
"name": "Sebastiaan Andeweg",
"url": "https://seblog.nl/",
"photo": "https://seblog.nl/photo.jpg"
},
"post-type": "article",
"_id": "10703010",
"_source": "1366",
"_is_read": true
}
For those wanting a bit more info on the IndieWeb, see the discussion and post on https://lobste.rs/s/zg6iok/indieweb_movement_owning_your_data_being where I shared a transcript of a conference talk I did on the subject
{
"type": "entry",
"published": "2020-04-12T13:18:00+01:00",
"url": "https://www.jvt.me/mf2/2020/04/hqtyq/",
"in-reply-to": [
"https://lobste.rs/s/lm7hcu/implementing_indieweb_into_my_website"
],
"content": {
"text": "For those wanting a bit more info on the IndieWeb, see the discussion and post on https://lobste.rs/s/zg6iok/indieweb_movement_owning_your_data_being where I shared a transcript of a conference talk I did on the subject",
"html": "<p>For those wanting a bit more info on the IndieWeb, see the discussion and post on <a href=\"https://lobste.rs/s/zg6iok/indieweb_movement_owning_your_data_being\">https://lobste.rs/s/zg6iok/indieweb_movement_owning_your_data_being</a> where I shared a transcript of a conference talk I did on the subject</p>"
},
"author": {
"type": "card",
"name": "Jamie Tanna",
"url": "https://www.jvt.me",
"photo": "https://www.jvt.me/img/profile.png"
},
"post-type": "reply",
"_id": "10676477",
"_source": "2169",
"_is_read": true
}
