(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
Ah I misunderstood, you want list without the thumbnail at all?
In the feed you can find the post view mode in the top right more options menu.
Yeah anywhere were you would use Java. Scala has a too high adoption cost. Kotlin is better suited for enterprise, has a stronger ecosystem and better interop with Java. I did enjoy scala though when experimented with it. The only thing I missed was the lack of control flow, no labels, continue, break
Yes but now it must wait for acknowledgement of a request (activity), before sending the next one. If one request takes 333ms means you can do max 3 requests per second. Now big instances like lemmy.world have activity above that so instances too far will perpetual lag behind
https://github.com/LemmyNet/lemmy/issues/4529
What’s your ping with Lemmy.world?
Mostly because Lemmy has a hard time keeping up with the federation
I genuinely don’t understand how there can be so many languages and all of them be painful to use
What about kotlin?
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.
Probably tommorow
Not really, it would also be hard to implement but I don’t think its impossible.
Hardest part is the ID of the same post differs between instances and the post might not exist yet either. I’ll create a issue for this feature request.
There is a mark read on scroll setting. When post gets scrolled out of view it will be marked read.
There is a bug that in communityview of an 0.18 instance it will only show first page. It is fixed but not released yet.
Can you expand on this? while you are scrolling it randomly refreshes?
I prefer making the action fully configureable (like even setting to nothing), over having a swap action setting.
Bottom bar collapse exists the other way, some users prefer to not see the bar by default and then you can hold to show the bar.
I definitely wanted to make, tap/hold actions fully configureable. It’s somewhere on the backlog, I’ll create an issue if it doesn’t have it already.
Can you expand on this?
It’s more the other way around, some ppl prefered, having the bar collapsed by default. And then hold to reveal it
Not in a way that is easily shareable. Working on a log viewer next.
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