Media endpoint should allow async processing

Micropub specs allows for a 202 Accepted answer for creating a new h-entry, as explained in 3.3.6 Response:

If the endpoint chooses to process the request asynchronously rather than creating and storing the post immediately, it MUST return an HTTP 202 Accepted status code, and MUST also return the Location header.

But the Media Endpoint only allows for a 201 Created answer, as explained in 3.6.4 Response.

I propose we extend the usage of 202 Accepted to the media endpoint to make static site generators compliant with the spec.

Just to give an example of my setup: my blog is statically generated in CI, and my micropub server is a stateless container that converts incoming requests into git commits, those commits in turn triggers my CI and the blog is published.

With such enviroment it will be not possible to make the image immediately available.

18:00 on 2021-08-20 (l0g.in 5EKG00)

1

0

#micropub

#indieweb

Posting HTML articles with micropub

This article was posted with Quill it’s an IndieWeb tool for publishing.

I used to only post notes with this, but now I implemented also the HTML version.

It supports pre-formatted text

As well as other features like:

bullet lists

block quotes

17:07 on 2021-08-19 (l0g.in 5EJF7f)

0

#indieweb

in reply to https://amberwilson.co.uk/blog/grow-the-indieweb-with-webmentions/

Oh yes! Webmentions are a lot of fun 🎉

12:28 on 2020-12-10 (l0g.in 5A6BU4)

0

#indieweb

Sending your first webmention

HOWTO send your first #indieweb webmention.

Yes, this website supports IndieWeb webmentions!

Webmention is a web standard for mentions and conversations across the web, a powerful building block that is used for a growing federated network of comments, likes, reposts, and other rich interactions across the decentralized social web.

This means that in order send a reply you need to publish it on your website first.

This is an example of a very simple reply to this page, if you can publish it somewere online and put your URL in the box at the end of this page, it will eventually appear on my website!

<!doctype html>
<meta charset="utf-8">
<title>My first webmention reply</title>
<body>
  <div class="h-entry">
    <!-- change the content with your own info, all fiels are optional -->
    <div class="u-author h-card"> 
      <img src="https://abisso.org/avatar.jpg" class="u-photo" width="40">
      <a href="https://abisso.org/" class="u-url p-name">Alessio Caiazza</a>
    </div>
    <p>
      in reply to:
      <a
      class="u-in-reply-to"
      href="https://abisso.org/stream/2020/11/24/wementions/">
        @nolith
      </a>
    </p>
    <p class="e-content">This is my first webmention!</p>
  </div>
</body>

Don’t know where to start? Take a look at the IndieWeb Getting Started page.

If you don’t have a website yet, you may consider using my GitLab Pages template to quickly create and deploy one.

13:41 on 2020-11-24 (l0g.in 59qCgD)

2

0

3

#indieweb

#webmention

#abisso.org

in reply to aaronpk/IndieAuth.com#204

Thank you @aaronpk 🎉

I’ll take a look to see if we can scale down the scope to read_user instead of api. I can’t see why we need full read/write API access.

Tested now to access quill, it works like a charm!

10:08 on 2020-11-22 (l0g.in 59o98T)

0

#indieweb

#indieauth.com

#gitlab

micro.blog syndication ✅

18:28 on 2020-11-17 (l0g.in 59iHUg)

0

#abisso.org

#indieweb

bookmarked https://dissertation.jackjamieson.net/

17:25 on 2020-11-16 (l0g.in 59hGRL)

0

#indieweb

in reply to https://qm64.tech/posts/202006-ipfs-orbitdb-likes/

This is really cool Lorenzo!

I’d like to suggest you take a look at the indieweb movement.

There are new technologies, like webmentions that you could use to implement likes and reply in a federated way.

And a static site like yours (or mine), can leverage https://webmention.io/ as a free backend.

As an example, this reply was posted on my own site, and syndicated here on your Disqus.

10:32 on 2020-11-05 (l0g.in 59X9YE)

0

#indieweb

in reply to snarfed/bridgy#986 (comment 721413829)

🎉

08:35 on 2020-11-04 (l0g.in 59W7au)

0

#brid.gy

#indieweb

in reply to snarfed/bridgy#985 (comment 721273595)

Thank you. It’s working now 🎊

20:05 on 2020-11-03 (l0g.in 59VK55)

3

0

#indieweb

#brid.gy

in reply to snarfed/bridgy#985 (comment 721244157)

sorry for the trouble!

Please don’t feel sorry for this, you made a lot available for free to all of us.

Thanks for checking.

My site is statically generated and I implemented newbase60 deterministic short links with javascript redirects (not the best option).

I have 2 options I can apply easily:

add webmention links in <head> in the shortlink pages, but then will brid.gy send mentions to my canonical URL or to the permashortlink?
this is more complex to implement, but I could generate a config file that will force the webserver to issue 302 redirects for the permashortlinks.

Will option n. 1 be enough for fixing this?

18:00 on 2020-11-03 (l0g.in 59VH0G)

2

0

#indieweb

#brig.gy

in reply to https://jamesg.blog/2020/09/15/privacy-social-media-and-this-website.html

Thanks for sharing this. I will watch The Social Dilemma

17:44 on 2020-11-03 (l0g.in 59VGje)

0

#indieweb

#privacy