Replies from 11 July 2020

So my angle on this is to have a client that is completely auto-populating. It's not necessarily something that will be useful for everyone, I admit (and is a slightly different interaction model than we usually use).

But I think it'd be quite nice to be able to point a Micropub client to a Micropub server, and have it render an editor for all the given post-types, with all the given properties, instead of needing to build the client with some awareness of what is required.

I'm not sure if this was an issue on my side, or on Bridgy's, but when I tried to publish a reply to a GitHub issue, the syndicated comment originally had a >, not a > indicating a blockquote, which meant I needed to manually edit the comment on GitHub to make it render nicer.

Isn't this covered under the following section URL Canonicalization?

As such, if a URL with no path component is ever encountered, it MUST be treated as if it had the path /.

I've not looked at how many other Micropub servers operate, but isn't it quite common to have certain fields as required? I.e. I'm writing this comment on Micropublish and it requires in-reply-to and content for a reply type.

Screenshot

This doesn't seem to have been answered on the forums as a thing that is possible, so I'd still appreciate this to be a feature request.

Answer to my question: Indigenous for Android expects that this list is the full post's content, as it renders some of the information (as seen in https://media.jvt.me/5a9abbb797.png) and I found would break if any nulls were found.

Even aside from this I do check pretty compulsively, as there's always a lot of background noise from us as we have mechanical keyboards - but yeah it's always a risk!