Like Blaze mentioned, the api is a bit of a work in progress and we are revamping the swagger. The version of the api spec you have there (freamon's) is manually created and can have some inaccuracies because of that. We are in the process of making the piefed api self-documenting so that inputs/outputs are validated against the schema, but there are a lot of endpoints still to go in that effort.

Some of those revamped endpoints are going to be coming in the 1.2 release. For the self-documented endpoints that have been done so far, you can check the swagger on crust (the dev instance running right off the main branch).

To keep up with this effort as I am working through it, I have been making posts to !piefed_api@piefed.social.

On a personal note, I would kill for a pythorhead-but-for-piefed to exist. I pretty extensively use pythorhead in my lemmy communities now, so I am hopeful that we can get the api in a stable enough state to enable tools like this to exist in the near future.

https://freamon.github.io/piefed-api/

The updated swagger is here https://crust.piefed.social/api/alpha/swagger

!piefed_api@piefed.social

@wjs018@piefed.social , @andrew_s@piefed.social should the freamon page redirect to the crust one?

Eh, I don't think it's that surprising. Getting a list of comments on a post vs getting them from a search term are very similar operations, so it doesn't make too much sense for these to have different queries in the backend. One thing you could do, but no client to my knowledge does, is add a search bar to a post that searches through the comments only within that thread.

Everything in the backend uses the same sorting as the posts do on that page except comments, which is frustrating. Comments do need a different sort enum as there are some options that don't apply to comments (scaled, new comments, etc.), but yeah the fact the top options don't work for comment search when they should is opaque and not user friendly.

I can't wait for 1.0 to actually come out because I feel like a broken record, but this is fixed there.

Uh oh, I now have a problem: I cannot keep up with remembering all the new features added!? Oh well, I am very pleased to have this issue:-). (\s bc there are Release Notes)

Yes I meant the on-site one developed by Reddit, but agreed that the centralized nature lends itself towards searching by Google.

Although the other way opens up a huge can of worms since every large, general-purpose instance will - due to the nature of how the ActivityPub protocol works - have basically all of the content of the entire Threadiverse. Or as near to that as it works for a first approximation anyway, e.g. someone deciding to index all content appearing on "Lemmy.World" would get all the memes, movie discussions, etc., missing chiefly things like piracy and anarchy and other things that LW has decided to ban. It won't be "correct" in the sense of attribution to the OP, but once someone found their way to the content housed on LW they are but a click away from getting to its original source anyway. So from that standpoint, Google indexing I would naively have thought would not be all that difficult? Except for the increasingly niche content that isn't federated with the largest instances, which is perhaps desirable anyway to not expose mainstream normies to content calling for e.g. actual murder in response to world events (such as occurs routinely on e.g. Hexbear).

A safer, sanitized version of the Threadiverse that is searchable by anyone works to all of our advantage, I would believe?

That could indeed be the case, but that's probably a low priority item for most of the client devs.

I had been asking Rimu to add this feature for a while as Lemmyverse doesn't show Piefed communities on the community search, and as a lot of people use Lemmyverse to search for communities, Piefed communities are basically invisible.

This solves it, if other clients want to implement it too, that would be nice of course

You can have a look at !piefed_css@piefed.social