@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
Any chance you can explain why you think the CDATA wrapper is the issue? My Known feed also wraps description in CDATA and that may be what is causing micro.blog to have trouble with it.
Upgraded Known to latest build; everything seems to be OK but if you spot anything odd, please let me know.
Kinda like Indie Hosters, but more suitable for Gens 3-4? Add Known support and you might get even more customers.
Gavin belonged to a school of one. Throughout most of his career – which was a vocation conducted on his own terms – it was evident to anyone of the slightest sentience that he was the eminent architectural writer of his generation. During much of that time architectural criticism in Ingerlandlandland was no such thing; it was a matter of giving great forelock to a few big names, it was fawning, anilingual sycophancy, a barely dissembled form of PR.
He also, and this may be a little-known fact, designed letterheads for like-minded colleagues, myself included.
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.
1 min read
@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
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.