LoqiLinktree is a site for publishing a flat list of links at a short vanity path (like Twitter and other social media silos) for what appears to be for the sole purpose of seeming to provide multiple links from social media profiles like Instagram which only allow one clickable link in your profile https://indieweb.org/Linktree
[manton]@GWG Hmm, I guess from the first time I had heard about Micropub I thought about as a potential next-generation MetaWeblog. They aren’t exactly comparable but they both solve the “I need to upload a photo and post some text to my blog”. (And MetaWeblog was old and never had a modern replacement. AtomPub was maybe the closest but it never had wide adoption like MetaWeblog did.)
[manton]As a side note, WordPress’s JSON API was a bit of a missed opportunity in my opinion because it was so focused around WP. Micropub for the very common use case is way simpler.
[manton]At the time, there were a few things that Micropub couldn’t do that made it a difficult sell for an app like MarsEdit that was heavily based on XML-RPC. I think most of those holes have been filled now with Micropub extensions, etc.
[jacky]the reason for it would be easier interoperability with existing editors (versus having to ask them to implement Micropub - it should show the power of it and have them opt to move to it that way)
[manton]@barnaby MarsEdit’s support of Micro.blog is based on XML-RPC. Even though Micro.blog’s “native” API is Micropub, I have yet another flavor of MetaWeblog that apps like MarsEdit can use. That was the easier path than MarsEdit adopting Micropub, although it’s still on his radar. https://help.micro.blog/t/micro-blog-xml-rpc-api/108
[jacky]I can imagine from a developer's standpoint, supporting multiple protocols would be a huge amount of work (hence the subtle death of Telepathy in the Freedesktop space)
[aciccarello]Has anyone tried to make a micropub server based off of netlify CMS config? I wonder if I could use the netlify config file for both, either by invoking Netlify CMS's code or by reading the config directly.
[aciccarello]Looking at their repo, they have a nice backend abstraction. Assuming the packages have a usable API, it shouldn't be too hard to setup a node server that translates micropub requests to netlify cms collection edit commands which are then mapped to github/gitlab calls by their packages. https://github.com/netlify/netlify-cms
[schmarty]aciccarello: i think a big issue with NetlifyCMS is that it runs in your browser and makes API calls to GitHub and GitLab as you make changes. Micropub clients expect send requests to a server. There are at least a few projects that will take Micropub requests and update a GitHub repo. for example https://github.com/voxpelli/webpage-micropub-to-github
[aciccarello]Right, NetlifyCMS is clientside so you'd need a server running to handle incoming requests. I've looked into some of the existing static site/github micropub servers but I'd love it if I could keep the configs in sync.
[aciccarello]The existing projects are going to be much more full-featured on the micropub side so I'll probably still go with one of those. But the concept of simplifying the config and having netlify CMS provide the backend abstraction seems intriguing.