@cn I use the date as the title of a Post in Known, to ensure that the contents of the post gets through to micro.blog intact, and, as so often, he is correct.
All I have to do now is remember to salute him next #micromonday
Why I cannot post bookmarks to Known automatically | Jeremy Cherfas
I've set out in as much detail as I can understand what is happening when I try to POST a Bookmark with a Description to WithKnown.
And to add insult to injury, I'm adding this Description by hand, so I can include a blockquote:
[I]f you try to POST anything other than the URL of the bookmark, it simply never appears. With the help of good IndieWeb people, especially and , we worked out what was happening.
Still puzzled by why some photo posts in Known go through to micro.blog with an image and others don’t. Almost all are PESOS from Instagram. I thought I had an explanation, but it doesn’t hold up.
For all the joy of the #indieweb, and the pleasure of civil discourse, I am becoming incredibly confused by aspects of micro.blog. There’s the question of titleless posts, of which is this is one as an experiment, versus status updates. There are posts that appear to be contributions to an interesting conversation but aren’t because they have been cross-posted automatically from elsewhere. And there is the lack of a scroll back, which means that as I follow more people and choose not to check in the middle of my night, stuff vanishes irretrievably from my timeline.
There are also issues with Known that are nothing to do with micro.blog.
None of this is insurmountable. For me, though, it does add friction.
1 min read
For all the joy of the #indieweb, and the pleasure of civil discourse, I am becoming incredibly confused by aspects of micro.blog. There’s the question of titleless posts, of which is this is one as an experiment, versus status updates. There are posts that appear to be contributions to an interesting conversation but aren’t because they have been cross-posted automatically from elsewhere. And there is the lack of a scroll back, which means that as I follow more people and choose not to check in the middle of my night, stuff vanishes irretrievably from my timeline.
There are also issues with Known that are nothing to do with micro.blog.
None of this is insurmountable. For me, though, it does add friction.
I'm late getting to this, but I would say it depends partly on which CMS you're talking about. I almost always compose directly in Known, and almost never compose directly in either WP or my main site, which runs on Grav. For WP sites, I usually use MarsEdit, which has just shipped version 4 and which is really good and Mac only. For Grav, I tend to compose in Byword and proofread in Marked2.
Horses for courses
1 min read
During the virtual IWC tonight, we were discussing third-party clients for publishing to websites, essentially Micropub clients and MarsEdit. And it occurred to us more or less simultaneously, that I do not use Micropub for the site that supports it out of the box, whereas I do use a client for the site that does not support Micropub out of the box. And that is because the post-creation UI is nice and simple for Known, and a right mess for WordPress.
So, just to be difficult, I'm using Quill for the first time in a long while to create a Post in Known.
Narrowing things down. I can post a photo to Known from my desktop with OS X.
I don’t expect it to show up on micro.blog because that gets a feed of selected categories only, and Photos isn’t one of them.
How about an image in a post?
Amazing work from @chrisaldrich explaining how and why he's gone about bringing his blogroll into the 21st century. I'm honoured to be on the list, with just one comment: the Vaviblog site, while still live, will not be updated, until it reverts to its original purpose. I have not yet found a way to import all the data from that instance of Known to my current instance, as I would like, so for now that site is a relic of my first steps onto the IndieWeb.
Doing a clean install of Known at Dreamhost to trouble shoot my issues with micro.blog (and the instructions). I **will** get this sorted out.