- cross-posted to:
- fedigrow@lemmy.zip
- fediverse@lemmy.world
- cross-posted to:
- fedigrow@lemmy.zip
- fediverse@lemmy.world
To see it in action:
Crust.piefed.social (the Piefed development instance)
Not all instances implement it yet, I guess it depends how often they pull from the dev branch
Example of search for ‘movies’



I’ll just remove the ‘freamon’ one when the auto-generated one is up to date.
The manually-generated one had 5 missing routes, which I’ve since added.
The auto-generated one at crust has about 48 missing routes. It’s the right approach, and I’ll help out with it when I can, but - for now at least - it makes no sense to redirect people to it (either automatically or via a comment).
Some thoughts for @wjs018@piefed.social
/site/instance_chooserprobably doesn’t need to be a route. It’s just the data format returned by/site/instance_chooser_search. As a route, it’s returning the instance info for the site you’re querying, so if you want to keep it as a route, it should probably be called/site/instance_infoor something.In the query for
/site/instance_chooser_search,nsfwandnewbieare both booleans. With the rest of the API, these are sent as ‘true’ or ‘false’, but they are ‘yes’ and ‘no’ for this route. Thenewbiequery should probably benewbie_friendlyIn the response,monthsmonitoredshould probably bemonths_monitoredThere’s no way to exclude communities for the response to
/topic/listand/feed/list: If you don’t put ‘include_communities’ in the query, it’s defaults to True, but if you put ‘include_communities=false’ in the query it ends up being True also (because the word ‘include_communities’ is in the data).TIL that rimu added instance chooser endpoints. I’ll take a look at those before 1.2 gets shipped. Same with the topic and feed endpoints. The easiest time to make changes to them is now before they get more widely used.
I have about 10 more endpoints (working through
/userright now) I have finished transitioning in a dev branch right now, so we are making progress.Thank you