Now I understand why @aaronpk has so much channels in his Monocle screenshots. I'm having 8 channels right now, they're:
- Home (my IndieWeb feed)
- Friends on Silos (mostly Twitter 'cause Instagram via Granary is unstable)
- Comics (XKCD and Naver Webtoons - the last one is crashing @swentel's Indigenous)
- News (Meduza, my favorite Russian electronic newspaper)
- Podcasts (currently only myurlis.com)
- YouTube (some of my YouTube subscriptions - I migrated my pop-science channels there)
- Self (a view on my own posts, very useful for debugging!)
Channel Icons
I use emojis as icons for channel feeds to be more colorful. I like colorfulness of social media silos and I don't want my IndieWeb feeds to be less attractive than silos. Seems like I'm not the only one, since I saw other people do the same thing.
So, what does your reader feed look like?
{
"type": "entry",
"published": "2019-09-18T11:33:06+00:00",
"url": "https://fireburn.ru/posts/1568795586",
"category": [
"Microsub",
"IndieWeb"
],
"content": {
"text": "Now I understand why @aaronpk has so much channels in his Monocle screenshots. I'm having 8 channels right now, they're:\nHome (my IndieWeb feed)\nFriends on Silos (mostly Twitter 'cause Instagram via Granary is unstable)\nComics (XKCD and Naver Webtoons - the last one is crashing @swentel's Indigenous)\nNews (Meduza, my favorite Russian electronic newspaper)\nPodcasts (currently only myurlis.com)\nYouTube (some of my YouTube subscriptions - I migrated my pop-science channels there)\nSelf (a view on my own posts, very useful for debugging!)\nChannel Icons\nI use emojis as icons for channel feeds to be more colorful. I like colorfulness of social media silos and I don't want my IndieWeb feeds to be less attractive than silos. Seems like I'm not the only one, since I saw other people do the same thing.\nSo, what does your reader feed look like?",
"html": "<p>Now I understand why <a href=\"https://aaronparecki.com\">@aaronpk</a> has so much channels in his Monocle screenshots. I'm having 8 channels right now, they're:</p>\n<ul><li>Home (my IndieWeb feed)</li>\n<li>Friends on Silos (mostly Twitter 'cause Instagram via Granary is unstable)</li>\n<li>Comics (XKCD and Naver Webtoons - the last one is crashing <a href=\"https://realize.be/\">@swentel</a>'s Indigenous)</li>\n<li>News (Meduza, my favorite Russian electronic newspaper)</li>\n<li>Podcasts (currently only <a href=\"https://myurlis.com/\">myurlis.com</a>)</li>\n<li>YouTube (some of my YouTube subscriptions - I migrated my pop-science channels there)</li>\n<li>Self (a view on my own posts, very useful for debugging!)</li>\n</ul><h2>Channel Icons</h2>\n<p>I use emojis as icons for channel feeds to be more colorful. I like colorfulness of social media silos and I don't want my IndieWeb feeds to be less attractive than silos. Seems like I'm not the only one, since I saw other people do the same thing.</p>\n<p><em>So, what does your reader feed look like?</em></p>"
},
"author": {
"type": "card",
"name": "Vika",
"url": "https://fireburn.ru/",
"photo": "https://aperture-proxy.p3k.io/53d3494aa1644e34c961228a4c1dd9a91d9ff775/68747470733a2f2f61766174617273312e67697468756275736572636f6e74656e742e636f6d2f752f373935333136333f733d34363026763d34"
},
"post-type": "note",
"_id": "5305410",
"_source": "1371",
"_is_read": true
}
I have solved my biggest problem since the first version of pyindieblog: webmentions were only sent from special fields, like u-in-reply-to, and not from e-content. Now my Micropub endpoint parses HTML content and sends webmentions for all URLs mentioned.
{
"type": "entry",
"published": "2019-09-18T11:46:05+00:00",
"url": "https://fireburn.ru/posts/1568796365",
"content": {
"text": "I have solved my biggest problem since the first version of pyindieblog: webmentions were only sent from special fields, like u-in-reply-to, and not from e-content. Now my Micropub endpoint parses HTML content and sends webmentions for all URLs mentioned.",
"html": "<p>I have solved my biggest problem since the first version of pyindieblog: webmentions were only sent from special fields, like <code>u-in-reply-to</code>, and not from <code>e-content</code>. Now my Micropub endpoint parses HTML content and sends webmentions for all URLs mentioned.</p>"
},
"author": {
"type": "card",
"name": "Vika",
"url": "https://fireburn.ru/",
"photo": "https://aperture-proxy.p3k.io/53d3494aa1644e34c961228a4c1dd9a91d9ff775/68747470733a2f2f61766174617273312e67697468756275736572636f6e74656e742e636f6d2f752f373935333136333f733d34363026763d34"
},
"post-type": "note",
"_id": "5305405",
"_source": "1371",
"_is_read": true
}
So, I'm migrating my YouTube subscriptions to Microsub, thanks to YouTube's RSS support. I think that when I make my own IndieWeb reader, I'll special-case YouTube posts by adding a YouTube embed inside of them. Or maybe by downloading the video with yt-dl and offering it as a u-video. It'll also serve as an archive... but my HDD would explode!
{
"type": "entry",
"published": "2019-09-17T15:52:11+00:00",
"url": "https://fireburn.ru/posts/1568724731",
"category": [
"YouTube",
"silos",
"IndieWeb",
"Microsub",
"ownyourdata"
],
"content": {
"text": "So, I'm migrating my YouTube subscriptions to Microsub, thanks to YouTube's RSS support. I think that when I make my own IndieWeb reader, I'll special-case YouTube posts by adding a YouTube embed inside of them. Or maybe by downloading the video with yt-dl and offering it as a u-video. It'll also serve as an archive... but my HDD would explode!",
"html": "<p>So, I'm migrating my YouTube subscriptions to Microsub, thanks to YouTube's RSS support. I think that when I make my own IndieWeb reader, I'll special-case YouTube posts by adding a YouTube embed inside of them. Or maybe by downloading the video with yt-dl and offering it as a u-video. It'll also serve as an archive... but my HDD would explode!</p>"
},
"author": {
"type": "card",
"name": "Vika",
"url": "https://fireburn.ru/",
"photo": "https://aperture-proxy.p3k.io/53d3494aa1644e34c961228a4c1dd9a91d9ff775/68747470733a2f2f61766174617273312e67697468756275736572636f6e74656e742e636f6d2f752f373935333136333f733d34363026763d34"
},
"post-type": "note",
"_id": "5294602",
"_source": "1371",
"_is_read": true
}
{
"type": "entry",
"published": "2019-09-16T19:43:33+00:00",
"url": "https://fireburn.ru/posts/1568652213",
"category": [
"GitHub",
"IndieWeb",
"ownyourdata"
],
"name": "Own your Git repositories; a concept for IndieWeb-replacement of GitHub features",
"content": {
"text": "I kinda like hosting my own Git repositories on my own premises. It gives me a sense of security; since nobody can access the code without my permission. With my current setup (Gitolite+cgit) I mark repositories as public by writing them in the config like this:\nrepo pyindieblog\n RW+ = vika\n R = @all\n config gitweb.owner = Vika\n config gitweb.description = \"IndieWeb-enabled CMS powered by Python\"\nThis means that the repo will be readable for any user having SSH access (currently only me!) and it'll be posted in the projects.list file which lets cgit know this is something I would like to be public.\nGitHub feature set\nGitHub is not only Git. It is marketed as a \"social coding tool\" and also allows for:\nIssues\nPull requests (the name of which could remind someone of git request-pull)\nComments on commits and changes\nThere are certainly more things, but let's focus on these, as these are the \"social\" features of GitHub, and these are the most widely known.\nMapping this to IndieWeb\nIssues\nWe do have issue posts on IndieWeb! They're kinda raw, but they're described on the wiki. I propose something like this:\nHave source code pages accept Webmentions\nHave an \"Issues\" page that aggregates webmentions with, e.g. u-issue-of link\nHave the webmention endpoint process Salmentions correctly\nThe issue threads will be posted to the repo, and salmentions would allow for threads to be started.\nPull requests\nPull requests on GitHub are actually issues. What if we go the similar way? Have a new microformat, h-pull-request with the following properties:\n\nu-url - the URL from which to pull\n\np-start - the starting commit that needs to be present in the upstream\n\np-end - the branch, tag or commit hash that is the end. Defaults to HEAD if not present.\nThis is inspired by the git request-pull command, which I think everyone forgot about.\nOn the receiving side, such a webmention could have a button to merge the changes instantly, triggering a pull and an automatic merge if possible. Or the repo maintainer could just manually pull the downstream repo and merge it manually.\nComments on commits\nBy far the easiest one. Send a webmention to the page describing the commit, optionally with a fragment URL pointing to the lines you're interested in.\nImplementing\nSadly, I have no working implementation of this yet - this is purely brainstorming. But maybe I'll do one! Who knows? For that, I'll probably need to fork cgit or write my own git repo visualizer responding to HTTP requests. The last one will probably be better.",
"html": "<p>I kinda like hosting my own Git repositories on my own premises. It gives me a sense of security; since nobody can access the code without my permission. With my current setup (Gitolite+cgit) I mark repositories as public by writing them in the config like this:</p>\n<pre><code>repo pyindieblog\n RW+ = vika\n R = @all\n config gitweb.owner = Vika\n config gitweb.description = \"IndieWeb-enabled CMS powered by Python\"</code></pre>\n<p>This means that the repo will be readable for any user having SSH access (currently only me!) and it'll be posted in the projects.list file which lets cgit know this is something I would like to be public.</p>\n<h2>GitHub feature set</h2>\n<p>GitHub is not only Git. It is marketed as a \"social coding tool\" and also allows for:</p>\n<ul><li>Issues</li>\n<li>Pull requests (the name of which could remind someone of <code>git request-pull</code>)</li>\n<li>Comments on commits and changes</li>\n</ul><p>There are certainly more things, but let's focus on these, as these are the \"social\" features of GitHub, and these are the most widely known.</p>\n<h2>Mapping this to IndieWeb</h2>\n<h3>Issues</h3>\n<p>We do have issue posts on IndieWeb! They're kinda raw, but they're described on <a title=\"issue - IndieWeb Wiki\" href=\"https://indieweb.org/issue\">the wiki</a>. I propose something like this:</p>\n<ol><li>Have source code pages accept Webmentions</li>\n<li>Have an \"Issues\" page that aggregates webmentions with, e.g. <code>u-issue-of</code> link</li>\n<li>Have the webmention endpoint process Salmentions correctly</li>\n</ol><p>The issue threads will be posted to the repo, and salmentions would allow for threads to be started.</p>\n<h3>Pull requests</h3>\n<p>Pull requests on GitHub are actually issues. What if we go the similar way? Have a new microformat, <code>h-pull-request</code> with the following properties:</p>\n<ul><li>\n<code>u-url</code> - the URL from which to pull</li>\n<li>\n<code>p-start</code> - the starting commit that needs to be present in the upstream</li>\n<li>\n<code>p-end</code> - the branch, tag or commit hash that is the end. Defaults to HEAD if not present.</li>\n</ul><p>This is inspired by the <code>git request-pull</code> command, which I think everyone forgot about.</p>\n<p>On the receiving side, such a webmention could have a button to merge the changes instantly, triggering a pull and an automatic merge if possible. Or the repo maintainer could just manually pull the downstream repo and merge it manually.</p>\n<h3>Comments on commits</h3>\n<p>By far the easiest one. Send a webmention to the page describing the commit, optionally with a fragment URL pointing to the lines you're interested in.</p>\n<h2>Implementing</h2>\n<p>Sadly, I have no working implementation of this yet - this is purely brainstorming. But maybe I'll do one! Who knows? For that, I'll probably need to fork cgit or write my own git repo visualizer responding to HTTP requests. The last one will probably be better.</p>"
},
"author": {
"type": "card",
"name": "Vika",
"url": "https://fireburn.ru/",
"photo": "https://aperture-proxy.p3k.io/53d3494aa1644e34c961228a4c1dd9a91d9ff775/68747470733a2f2f61766174617273312e67697468756275736572636f6e74656e742e636f6d2f752f373935333136333f733d34363026763d34"
},
"post-type": "article",
"_id": "5285232",
"_source": "1371",
"_is_read": true
}
{
"type": "entry",
"published": "2019-09-16T17:47:00+0100",
"url": "https://www.jvt.me/mf2/78ef0e97-9035-4eed-9c5f-27960e7ed5ab/",
"category": [
"indieweb",
"twitter"
],
"in-reply-to": [
"https://www.zachleat.com/web/own-my-tweets/"
],
"name": "Reply to https://www.zachleat.com/web/own-my-tweets/",
"content": {
"text": "This is a great idea! I may have to look at the same. I'm also hoping to start to start publishing from my site first and then having that send the tweet afterwards using https://brid.gy/"
},
"author": {
"type": "card",
"name": "Jamie Tanna",
"url": "https://www.jvt.me",
"photo": "https://aperture-proxy.p3k.io/f4cac242182744deb91a5ee91d7528d78e657269/68747470733a2f2f7777772e6a76742e6d652f696d672f70726f66696c652e706e67"
},
"post-type": "reply",
"_id": "5283813",
"_source": "2169",
"_is_read": true
}
I fully expect my personal website to outlive Twitter and as such have decided to take full ownership of the content I’ve posted there. In true IndieWeb fashion, I’m taking ownership of my data.
{
"type": "entry",
"published": "2019-09-16T15:22:09Z",
"url": "https://adactio.com/links/15816",
"category": [
"indieweb",
"tweets",
"twitter",
"digital",
"preservation",
"archives",
"hosting"
],
"bookmark-of": [
"https://www.zachleat.com/web/own-my-tweets/"
],
"content": {
"text": "I\u2019m Taking Ownership of My Tweets\u2014zachleat.com\n\n\n\n\n I fully expect my personal website to outlive Twitter and as such have decided to take full ownership of the content I\u2019ve posted there. In true IndieWeb fashion, I\u2019m taking ownership of my data.",
"html": "<h3>\n<a class=\"p-name u-bookmark-of\" href=\"https://www.zachleat.com/web/own-my-tweets/\">\nI\u2019m Taking Ownership of My Tweets\u2014zachleat.com\n</a>\n</h3>\n\n<blockquote>\n <p>I fully expect my personal website to outlive Twitter and as such have decided to take full ownership of the content I\u2019ve posted there. In true <a href=\"https://indieweb.org/\">IndieWeb</a> fashion, I\u2019m taking ownership of my data.</p>\n</blockquote>"
},
"author": {
"type": "card",
"name": "Jeremy Keith",
"url": "https://adactio.com/",
"photo": "https://aperture-proxy.p3k.io/bbbacdf0a064621004f2ce9026a1202a5f3433e0/68747470733a2f2f6164616374696f2e636f6d2f696d616765732f70686f746f2d3135302e6a7067"
},
"post-type": "bookmark",
"_id": "5282525",
"_source": "2",
"_is_read": true
}
{
"type": "entry",
"published": "2019-09-16T13:52:00+0300",
"url": "https://fireburn.ru/posts/1568631120",
"category": [
"Matrix",
"chat",
"server"
],
"name": "I tried Matrix and almost crashed my server (because my server is crap)",
"content": {
"text": "Matrix. The future of communication. HTTP API (which is technically swappable, so you can replace parts of it), encryption, bridging... And high memory usage of the official homeserver implementation! \ud83d\ude02\n\nMatrix recently came out of beta. I decided to try it and bootstrap a homeserver so I could chat. Well, I did it. Federation test was failing for some reason, yet I have successfully joined some chat rooms, including the IndieWeb one.\n\nFirst, it was slow. Well, it's understandable; the server performs a lot of work, including signing and encryption, and my laptop's CPU was clocked down to prevent overheating. But it also ate a lot of memory. People from \"Synapse Admins\" chatroom recommended me to increase the cache factor (which is controlled by SYNAPSE_CACHE_FACTOR variable, if I remember this correctly) to speed it up. I did, and it became faster. Except it ate all of the memory of my laptop!\n\nI left the server running for an hour or so, and when I returned, it was eating 6G of virtual memory, according to htop. I guess it's caching a lot of stuff, which is a good thing. Except my laptop only has 4G of RAM. So it was probably swapping a lot. Sadly, I had to turn the homeserver off. Maybe another time?\n\nRight now Matrix feels a bit like a monoculture - though I saw several homeserver implementations in development, which is a great thing! Maybe it's just not for me, maybe I should just continue to base my life around XMPP (which I have configured too! It's the same as my email).\n\nSummary: Matrix is definitely cool, but a bit resource-hungry for me. I should either get a better machine for the homeserver or wait until it becomes a bit less of a memory-eating CPU-heating (but certainly interesting) protocol.",
"html": "<p>Matrix. The future of communication. HTTP API (which is technically swappable, so you can replace parts of it), encryption, bridging... And high memory usage of the official homeserver implementation! \ud83d\ude02</p>\n\n<p>Matrix recently came out of beta. I decided to try it and bootstrap a homeserver so I could chat. Well, I did it. Federation test was failing for some reason, yet I have successfully joined some chat rooms, including the IndieWeb one.</p>\n\n<p>First, it was <i>slow</i>. Well, it's understandable; the server performs a lot of work, including signing and encryption, and my laptop's CPU was clocked down to prevent overheating. But it also ate a lot of memory. People from \"Synapse Admins\" chatroom recommended me to increase the cache factor (which is controlled by <code>SYNAPSE_CACHE_FACTOR</code> variable, if I remember this correctly) to speed it up. I did, and it became faster. Except it ate all of the memory of my laptop!</p>\n\n<p>I left the server running for an hour or so, and when I returned, it was eating 6G of virtual memory, according to htop. I guess it's caching a lot of stuff, which is a good thing. Except my laptop only has 4G of RAM. So it was probably swapping a lot. Sadly, I had to turn the homeserver off. Maybe another time?</p>\n\n<p>Right now Matrix feels a bit like a monoculture - though I saw several homeserver implementations in development, which is a great thing! Maybe it's just not for me, maybe I should just continue to base my life around XMPP (which I have configured too! It's the same as my email).</p>\n\n<p><b>Summary:</b> Matrix is definitely cool, but a bit resource-hungry for me. I should either get a better machine for the homeserver or wait until it becomes a bit less of a memory-eating CPU-heating (but certainly interesting) protocol.</p>"
},
"author": {
"type": "card",
"name": "Vika",
"url": "https://fireburn.ru/",
"photo": "https://aperture-proxy.p3k.io/53d3494aa1644e34c961228a4c1dd9a91d9ff775/68747470733a2f2f61766174617273312e67697468756275736572636f6e74656e742e636f6d2f752f373935333136333f733d34363026763d34"
},
"post-type": "article",
"_id": "5279251",
"_source": "1371",
"_is_read": true
}
@tElizaRose @tw2113 I've been taking some time off/away from it in the late summer, but I've got some pieces (esp. for/from #WordPress perspective) started:
https://indieweb.org/User:Boffosocko.com/wordpress-draft
https://boffosocko.com/research/indieweb/
{
"type": "entry",
"published": "2019-09-16T04:01:44+00:00",
"url": "http://stream.boffosocko.com/2019/telizarose-tw2113-ive-been-taking-some-time-offaway-from-it",
"category": [
"WordPress"
],
"syndication": [
"https://twitter.com/ChrisAldrich/status/1173446876756094976"
],
"in-reply-to": [
"https://twitter.com/tElizaRose/status/1167938741790339073"
],
"content": {
"text": "@tElizaRose @tw2113 I've been taking some time off/away from it in the late summer, but I've got some pieces (esp. for/from #WordPress perspective) started:\nhttps://indieweb.org/User:Boffosocko.com/wordpress-draft\nhttps://boffosocko.com/research/indieweb/",
"html": "<a href=\"https://twitter.com/tElizaRose\">@tElizaRose</a> <a href=\"https://twitter.com/tw2113\">@tw2113</a> I've been taking some time off/away from it in the late summer, but I've got some pieces (esp. for/from <a href=\"http://stream.boffosocko.com/tag/WordPress\" class=\"p-category\">#WordPress</a> perspective) started:<br /><a href=\"https://indieweb.org/User:Boffosocko.com/wordpress-draft\">https://indieweb.org/User:Boffosocko.com/wordpress-draft</a><br /><a href=\"https://boffosocko.com/research/indieweb/\">https://boffosocko.com/research/indieweb/</a><br />"
},
"author": {
"type": "card",
"name": "Chris Aldrich",
"url": "http://stream.boffosocko.com/profile/chrisaldrich",
"photo": "https://aperture-proxy.p3k.io/4a01a54aa55b69dd1b2633c835610491c575e2e2/687474703a2f2f73747265616d2e626f66666f736f636b6f2e636f6d2f66696c652f36303034323762383166373738356537303465616466653531316139323730662f7468756d622e6a7067"
},
"post-type": "reply",
"_id": "5278127",
"_source": "192",
"_is_read": true
}
{
"type": "entry",
"published": "2019-09-16T04:32:51+00:00",
"url": "http://stream.boffosocko.com/2019/mor10-i-tried-writing-a-non-technical-version-oncearticlewebmentions-enabling-better-communication-on-the-internet",
"syndication": [
"https://twitter.com/ChrisAldrich/status/1173454695710543872"
],
"in-reply-to": [
"https://twitter.com/mor10/status/1169358515330150400"
],
"content": {
"text": "@mor10 I tried writing a non-technical version once:\nhttps://alistapart.com/article/webmentions-enabling-better-communication-on-the-internet/",
"html": "<a href=\"https://twitter.com/mor10\">@mor10</a> I tried writing a non-technical version once:<br /><a href=\"https://alistapart.com/article/webmentions-enabling-better-communication-on-the-internet/\">https://alistapart.com/article/webmentions-enabling-better-communication-on-the-internet/</a>"
},
"author": {
"type": "card",
"name": "Chris Aldrich",
"url": "http://stream.boffosocko.com/profile/chrisaldrich",
"photo": "https://aperture-proxy.p3k.io/4a01a54aa55b69dd1b2633c835610491c575e2e2/687474703a2f2f73747265616d2e626f66666f736f636b6f2e636f6d2f66696c652f36303034323762383166373738356537303465616466653531316139323730662f7468756d622e6a7067"
},
"post-type": "reply",
"_id": "5278126",
"_source": "192",
"_is_read": true
}
@EddieHinkle so, what's the status of
{
"type": "entry",
"published": "2019-09-15T14:22:00+0300",
"url": "https://fireburn.ru/posts/1568546520",
"category": [
"podcast",
"IndieWeb"
],
"content": {
"text": "@EddieHinkle so, what's the status of",
"html": "<a href=\"https://eddiehinkle.com/\">@EddieHinkle</a> so, what's the status of <a href=\"https://myurlis.com/%E2%80%9D\">\n \n </a>"
},
"author": {
"type": "card",
"name": "Vika",
"url": "https://fireburn.ru/",
"photo": "https://aperture-proxy.p3k.io/53d3494aa1644e34c961228a4c1dd9a91d9ff775/68747470733a2f2f61766174617273312e67697468756275736572636f6e74656e742e636f6d2f752f373935333136333f733d34363026763d34"
},
"post-type": "note",
"_id": "5269933",
"_source": "1371",
"_is_read": true
}
I suppose I should apologize for what (at least in my timezone) was feeding a lot of test posts in your timeline. micropub.rocks doesn't allow unlisted posts and I have no "deletion" yet. yet.
{
"type": "entry",
"published": "2019-09-15T05:49:08+00:00",
"url": "https://fireburn.ru/posts/1568515748",
"category": [
"IndieWeb",
"pyindieblog",
"micropub.rocks"
],
"content": {
"text": "I suppose I should apologize for what (at least in my timezone) was feeding a lot of test posts in your timeline. micropub.rocks doesn't allow unlisted posts and I have no \"deletion\" yet. yet.",
"html": "I suppose I should apologize for what (at least in my timezone) was feeding a lot of test posts in your timeline. micropub.rocks doesn't allow unlisted posts and I have no \"deletion\" yet. <b>yet.</b>"
},
"author": {
"type": "card",
"name": "Vika",
"url": "https://fireburn.ru/",
"photo": "https://aperture-proxy.p3k.io/53d3494aa1644e34c961228a4c1dd9a91d9ff775/68747470733a2f2f61766174617273312e67697468756275736572636f6e74656e742e636f6d2f752f373935333136333f733d34363026763d34"
},
"post-type": "note",
"_id": "5268722",
"_source": "1371",
"_is_read": true
}
Test of querying the endpoint for the source content
{
"type": "entry",
"published": "2019-09-14T19:31:39+00:00",
"url": "https://fireburn.ru/posts/1568478699",
"category": [
"micropub",
"test"
],
"content": {
"text": "Test of querying the endpoint for the source content"
},
"author": {
"type": "card",
"name": "Vika",
"url": "https://fireburn.ru/",
"photo": "https://aperture-proxy.p3k.io/53d3494aa1644e34c961228a4c1dd9a91d9ff775/68747470733a2f2f61766174617273312e67697468756275736572636f6e74656e742e636f6d2f752f373935333136333f733d34363026763d34"
},
"post-type": "note",
"_id": "5264725",
"_source": "1371",
"_is_read": true
}
Micropub test of creating an h-entry with one category. This post should have one category, test1
{
"type": "entry",
"published": "2019-09-14T19:30:32+00:00",
"url": "https://fireburn.ru/posts/1568478632",
"category": [
"test1"
],
"content": {
"text": "Micropub test of creating an h-entry with one category. This post should have one category, test1"
},
"author": {
"type": "card",
"name": "Vika",
"url": "https://fireburn.ru/",
"photo": "https://aperture-proxy.p3k.io/53d3494aa1644e34c961228a4c1dd9a91d9ff775/68747470733a2f2f61766174617273312e67697468756275736572636f6e74656e742e636f6d2f752f373935333136333f733d34363026763d34"
},
"post-type": "note",
"_id": "5264727",
"_source": "1371",
"_is_read": true
}
Micropub test of creating a photo referenced by URL
{
"type": "entry",
"published": "2019-09-14T19:30:11+00:00",
"url": "https://fireburn.ru/posts/1568478611",
"photo": [
"https://aperture-proxy.p3k.io/32f95bbff3b0303dc6a0c9dd028e3d32ee287b0a/68747470733a2f2f6d6963726f7075622e726f636b732f6d656469612f73756e7365742e6a7067"
],
"content": {
"text": "Micropub test of creating a photo referenced by URL"
},
"author": {
"type": "card",
"name": "Vika",
"url": "https://fireburn.ru/",
"photo": "https://aperture-proxy.p3k.io/53d3494aa1644e34c961228a4c1dd9a91d9ff775/68747470733a2f2f61766174617273312e67697468756275736572636f6e74656e742e636f6d2f752f373935333136333f733d34363026763d34"
},
"post-type": "photo",
"refs": {
"https://aperture-proxy.p3k.io/32f95bbff3b0303dc6a0c9dd028e3d32ee287b0a/68747470733a2f2f6d6963726f7075622e726f636b732f6d656469612f73756e7365742e6a7067": {
"type": "image",
"ratio": 1.33,
"bytes": 127773
}
},
"_id": "5264728",
"_source": "1371",
"_is_read": true
}
Micropub test of creating an h-entry with categories. This post should have two categories, test1 and test2
{
"type": "entry",
"published": "2019-09-14T19:29:53+00:00",
"url": "https://fireburn.ru/posts/1568478593",
"category": [
"test1",
"test2"
],
"content": {
"text": "Micropub test of creating an h-entry with categories. This post should have two categories, test1 and test2"
},
"author": {
"type": "card",
"name": "Vika",
"url": "https://fireburn.ru/",
"photo": "https://aperture-proxy.p3k.io/53d3494aa1644e34c961228a4c1dd9a91d9ff775/68747470733a2f2f61766174617273312e67697468756275736572636f6e74656e742e636f6d2f752f373935333136333f733d34363026763d34"
},
"post-type": "note",
"_id": "5264729",
"_source": "1371",
"_is_read": true
}
Micropub test of creating a basic h-entry
{
"type": "entry",
"published": "2019-09-14T19:29:39+00:00",
"url": "https://fireburn.ru/posts/1568478579",
"content": {
"text": "Micropub test of creating a basic h-entry"
},
"author": {
"type": "card",
"name": "Vika",
"url": "https://fireburn.ru/",
"photo": "https://aperture-proxy.p3k.io/53d3494aa1644e34c961228a4c1dd9a91d9ff775/68747470733a2f2f61766174617273312e67697468756275736572636f6e74656e742e636f6d2f752f373935333136333f733d34363026763d34"
},
"post-type": "note",
"_id": "5264730",
"_source": "1371",
"_is_read": true
}
Micropub test of creating multiple photos referenced by URL. This post should include a photo of a city at night.
{
"type": "entry",
"published": "2019-09-14T19:28:28+00:00",
"url": "https://fireburn.ru/posts/1568478508",
"photo": [
"https://aperture-proxy.p3k.io/32f95bbff3b0303dc6a0c9dd028e3d32ee287b0a/68747470733a2f2f6d6963726f7075622e726f636b732f6d656469612f73756e7365742e6a7067",
"https://aperture-proxy.p3k.io/316f99e48d21d9a9bd0e528ea4abd2e4d546b200/68747470733a2f2f6d6963726f7075622e726f636b732f6d656469612f636974792d61742d6e696768742e6a7067"
],
"content": {
"text": "Micropub test of creating multiple photos referenced by URL. This post should include a photo of a city at night."
},
"author": {
"type": "card",
"name": "Vika",
"url": "https://fireburn.ru/",
"photo": "https://aperture-proxy.p3k.io/53d3494aa1644e34c961228a4c1dd9a91d9ff775/68747470733a2f2f61766174617273312e67697468756275736572636f6e74656e742e636f6d2f752f373935333136333f733d34363026763d34"
},
"post-type": "photo",
"refs": {
"https://aperture-proxy.p3k.io/32f95bbff3b0303dc6a0c9dd028e3d32ee287b0a/68747470733a2f2f6d6963726f7075622e726f636b732f6d656469612f73756e7365742e6a7067": {
"type": "image",
"ratio": 1.33,
"bytes": 127773
},
"https://aperture-proxy.p3k.io/316f99e48d21d9a9bd0e528ea4abd2e4d546b200/68747470733a2f2f6d6963726f7075622e726f636b732f6d656469612f636974792d61742d6e696768742e6a7067": {
"type": "image",
"ratio": 3,
"bytes": 432331
}
},
"_id": "5264731",
"_source": "1371",
"_is_read": true
}
Micropub test of creating a photo referenced by URL with alt text. This post should include a photo of a sunset.
{
"type": "entry",
"published": "2019-09-14T19:27:57+00:00",
"url": "https://fireburn.ru/posts/1568478477",
"photo": [
"https://aperture-proxy.p3k.io/32f95bbff3b0303dc6a0c9dd028e3d32ee287b0a/68747470733a2f2f6d6963726f7075622e726f636b732f6d656469612f73756e7365742e6a7067"
],
"content": {
"text": "Micropub test of creating a photo referenced by URL with alt text. This post should include a photo of a sunset."
},
"author": {
"type": "card",
"name": "Vika",
"url": "https://fireburn.ru/",
"photo": "https://aperture-proxy.p3k.io/53d3494aa1644e34c961228a4c1dd9a91d9ff775/68747470733a2f2f61766174617273312e67697468756275736572636f6e74656e742e636f6d2f752f373935333136333f733d34363026763d34"
},
"post-type": "photo",
"refs": {
"https://aperture-proxy.p3k.io/32f95bbff3b0303dc6a0c9dd028e3d32ee287b0a/68747470733a2f2f6d6963726f7075622e726f636b732f6d656469612f73756e7365742e6a7067": {
"type": "image",
"ratio": 1.33,
"bytes": 127773
}
},
"_id": "5264732",
"_source": "1371",
"_is_read": true
}
Micropub test of creating an h-entry with a JSON request containing multiple categories. This post should have two categories, test1 and test2.
{
"type": "entry",
"published": "2019-09-14T19:16:19+00:00",
"url": "https://fireburn.ru/posts/1568477779",
"category": [
"test1",
"test2"
],
"content": {
"text": "Micropub test of creating an h-entry with a JSON request containing multiple categories. This post should have two categories, test1 and test2."
},
"author": {
"type": "card",
"name": "Vika",
"url": "https://fireburn.ru/",
"photo": "https://aperture-proxy.p3k.io/53d3494aa1644e34c961228a4c1dd9a91d9ff775/68747470733a2f2f61766174617273312e67697468756275736572636f6e74656e742e636f6d2f752f373935333136333f733d34363026763d34"
},
"post-type": "note",
"_id": "5264734",
"_source": "1371",
"_is_read": true
}
Aperture was down, IndieAuth.com token endpoint was down, and I couldn't access my own site (since renderer uses a token to read posts). Thankfully @aaronpk fixed it all. Thank you ❤
{
"type": "entry",
"published": "2019-09-14T19:29:00+0300",
"url": "https://fireburn.ru/posts/1568478540",
"category": [
"IndieWeb",
"SinglePointOfAaron",
"bugs"
],
"content": {
"text": "Aperture was down, IndieAuth.com token endpoint was down, and I couldn't access my own site (since renderer uses a token to read posts). Thankfully @aaronpk fixed it all. Thank you \u2764",
"html": "<p>Aperture was down, IndieAuth.com token endpoint was down, and I couldn't access my own site (since renderer uses a token to read posts). Thankfully <a href=\"https://aaronparecki.com/\">@aaronpk</a> fixed it all. Thank you \u2764</p>"
},
"author": {
"type": "card",
"name": "Vika",
"url": "https://fireburn.ru/",
"photo": "https://aperture-proxy.p3k.io/53d3494aa1644e34c961228a4c1dd9a91d9ff775/68747470733a2f2f61766174617273312e67697468756275736572636f6e74656e742e636f6d2f752f373935333136333f733d34363026763d34"
},
"post-type": "note",
"_id": "5262224",
"_source": "1371",
"_is_read": true
}
