Yours is a little bit easier to read, but my main problems remain the same. Here’s some initial comments looking at your swagger link from the perspective of a user who is brand new to the lemmy API (and doesn’t use Javascript):

• I can’t tell what the general flow of the API usage in general is. Am I supposed to login/authorize somehow first? Some common examples, especially in at least one programming language (whether that’s curl or python or whatever) I think would go a long way to help people understand what they’re supposed to do.

• How do I know if I need to authorize for a particular endpoint?

• What is the entire URL for any given endpoint? It’s never really explained clearly.

• What is this “servers” dropdown? What’s the difference between those?

• Endpoint descriptions are often unhelpful. /user says “Get the details for a person.” It doesn’t tell me this is actually how I’m supposed to find their comments or posts. Nothing tells us this.

• We have to guess what endpoint we might need for a lot of things. Example: /post/like is also for dislikes, but it doesn’t tell you that. It also never tells you HOW to like or dislike anything, the valid values of score do not appear to be documented. And you’re left to assume that’s the right field to even use for it.

• What is the content type of the request supposed to be? JSON is never mentioned anywhere.

• What are these named “parameters”? Is that a query parameter? Why does it say “object” and “(query)”? Does this parameter go in the request body instead? /user shows a parameter called “GetPersonDetails” except in reality this name is (I guess) supposed to be completely ignored, because no part of the request actually uses the string “GetPersonDetails”.

• Schema is missing for many endpoints, like the request part of /user.

• What are all these fields under “GetPersonDetails”? Are they all required? Only some? It doesn’t say anything about it.

• Many of the possible error codes are undocumented.

There’s probably more but that’s the main stuff I think.

This thread sums everything up nicely I think: https://lemmy.ml/post/98675/95459

And for programming.dev specifically, the API did not work for me when they had CF bot protection turned on (endpoints always returned the “Just a moment…” bot check html), it was only after it was turned off a few days ago that it started working for me, because CF doesn’t like my IP/browser/something and always gives me endless captcha loops. Previously their stance was that bot IPs had to be explicitly whitelisted to be allowed on their server.

This is still written from a javascript perspective and assumes many things that are not true when using other approaches to calling the endpoints.

curl 'https://lemmy.world/api/v3/user?username=egeres&sort=New&page=1&limit=20' | jq .posts

https://join-lemmy.org/api/classes/LemmyHttp.html#getPersonDetails

The documentation is really terrible and the developers try to defend it anyways.

Some instances also employ cloudflare or other anti-ddos techniques that make automated API usage impossible.

I really do not like these docs and find it extremely confusing for anyone not using Javascript. For example that “form” parameter that’s on almost everything, doesn’t even exist and can’t be used when you’re using curl, but it doesn’t tell you that.

I have had nothing but problems with kde connect for years

Removed by mod

so exactly like kde connect then

I reject your reality and substitute my own!

keeping a list of changes in the source code

Source?

Doesn’t really matter if you’re not positioned to be able to defend your license in court.

A really important thing to remember with all licenses is that they’re only as useful as your ability to enforce them… in court. And there’s a non-zero chance that at least some of these are practically unenforceable anyways.

I only use AGPL+non-commercial+racistword

IPFS is doomed because the design does not allow it to grow and stay fast, it’s already too slow with barely any users. Trying to find a single file can often take minutes, which is simply unacceptable.

I think torrent 2.0 is a much better technology but almost nobody uses it.

I think for that to happen, it would have to be on a server hosted in the EU, owned by a corporation, with a user that just happened to report them for violations.

While I think federated services are a good idea in theory, the unfortunate reality is that they’re also privacy and GDPR minefields that nobody has figured out how to make legal yet.

shouldn’t be deadly

Police don’t know people’s medical history or current health conditions, there’s always the very real possibility of it stopping your heart and it happens more than you think.

Paradox of Tolerance

Yes that’s exactly what I was referring to.

They should be tolerant of people that don’t agree with them, and vice versa. But that shouldn’t IMO mean we have to like it or be banned from a discussion just because of a difference of opinion… but I have been seeing a hair trigger on anyone even remotely disagreeing on this.

That is why I qualified the statement with “if you’re not hurting anyone”… of course I am not blind to violence by others.

Genuine naive question, but why is it such an inherent problem being anti-trans if you’re not hurting anyone with that belief? Isn’t it even more “equal” to accept people’s right to have opinions you don’t like? I don’t think trans people shouldn’t exist, but that shouldn’t mean I have to like it.