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.

sftp or rsync

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.

Vivaldi is proprietary, FYI.

besides many banks requiring SMS 2FA still, I usually only talk with non-app-using people over e2ee RCS

https://0x0.st/XmAx.png

I was more concerned with government ties.

Removed by mod

since you crawled under a rock /s

I have had nothing but problems with kde connect for years

Removed by mod

when it works. but it’s so incredibly buggy, especially the desktop apps, and double especially the sms desktop app. holy shite is it terrible, and trying to get support is like trying to report a problem to google

so exactly like kde connect then

It won’t in 24.04 because Cosmic doesn’t support anything else

This now makes all current mainstream distros 100% unusable for blind users, as all built-in screen readers are broken on Wayland, and all the main distros now use Wayland, so you cannot even install the OS at all.

Open source is the very worst thing currently going on because it is so incredibly exploitative, it’s far more exploitative than any actual company is of the workers who work at the company.

Even the people who are getting paid in open source are getting massively underpaid to do it compared to how much the people who are using their code are making, it’s nothing compared to the power that is accreted by the people who have co-opted that work thanks to the open source model. And then mark zuckerberg gets to define how the internet works despite having paid for almost none of the software that his company actually needed to make that work.

It’s like feudalism or serfdom, these people did the work and got nothing for it. It’s like you took the worst aspects of capitalism for workers and the worst aspects of socialism for workers and put them together, that’s open source. You get no power and you get no money.

It’s exploitative whether the people chose to be exploited, just because someone chooses to let you exploit them does not meant that you didn’t exploit them. And for the record that’s how most exploitation works; convincing people to do something that turns out to be very bad for them and very good for you, and that’s exactly what the open source movement has turned out to be.

I really don’t see the “we post stuff on github under a gpl2 or lgpl or apache or mit license”, all that is to me now is just exploitation. You can say that there’s solutions but until someone demonstrates that those solutions work, it’s the standard “real communism has never been tried” argument. AGPL is the only thing that I’ve seen so far that’s an attempt to fix these fundamentally unfair compensation practices.

no it’s part of the physical hardware design