Ah yes, all though I ve never really experienced HTTP days in their full glory

I'll look into using it. If it has a github action or easy way to publish it from cli

I do not see how critisms for the JS API docs are relevant for my openapi documentation.

This documentation aims to solve all those problems in a language agnostic way. It descibes the endpoints, the request object, the status, the response object, the authentication needed in visual/text. It allows you test it right from the browser, allows you to copy a working curl command, search for endpoints based on keywords, allows you to import the entire spec into postman/alts.

I ve never had any problems with CF instances but I mostly test with voyager.lemmy.ml

Looks like the best openapi front. I looked into using it, but it didn't seem free. Too bad this one is outdated. Lemmys API has changed quiet a bit since then.

(Author btw)

Can you expand on this? This was written for Kotlin usage. It automates generating API based on this spec.

I have no idea what you mean with 'using other approaches to calling the endpoints'

Lemmy has only one API. It's same API used for lemmy-ui.

This is just a "better" documentation for it.

The API works for for cloudfare instances too.

There is also a swagger ui variant

https://mv-gh.github.io/lemmy_openapi_spec/swagger_ui.html

The swipe gesture feature uses a new experimental component. As far as I am aware we can't configure the sensitivity. We have decided to have it off by default. We also fixed the swipe direction not being aligned with the description.

The full sentence is This account (%s) is being verified

It's verifying that everything is correct, acc not banned, JWT works, instance alive, ...

It only shows that, if you are attempting something that causes it to be verified while already verifiying that account.

Nbd, should ve resolved itself in a few seconds

Jerboa is just showing you the error it got from your instance. I can look into the source code for Lemmy but that won't be for a while.

"community ban" is not something that is coded into Jerboa as far as I know.

We cannot solve that issue on our end. It is a problem with the toolkit that we use, see https://issuetracker.google.com/issues/294102838

You can disable text corrections if you want a work around

https://github.com/dessalines/jerboa/issues/194#issuecomment-1635789189

It is caused by a bug introduced in lemmy 18.3

https://github.com/dessalines/jerboa/issues/1109

I have a fix for it already

That's a lemmy bug, not Jerboa. I reported the bug already. We don't get a choice as frontend on what gets returned once that option is set.

https://github.com/LemmyNet/lemmy/issues/3691

That list gets generated based on the lemmy instances tracked by fediverse.observer site that have a monthly active user amount greater than 50.