![](/static/66c60d9f/assets/icons/icon-96x96.png)
![](https://beehaw.org/pictrs/image/1be75b15-2f18-429d-acf7-dcea8e512a4b.png)
Yes I don’t understand the point of misskey either. It just seems to be a Japanese clone of mastodon with a small, differing interpretation of some parts of ActivityPub.
Yes I don’t understand the point of misskey either. It just seems to be a Japanese clone of mastodon with a small, differing interpretation of some parts of ActivityPub.
You’re wasting your breath. These people cannot be defeated with logic. You can’t reason someone out of a position they didn’t use reason to get into in the first place.
At the very least they will claim “gender neutrality and/or a person’s right to exist is not an ethical OR political issue.”
then what’s the point if you’re still not getting away from the same people?
Non-technical is not the same as political, not even close. I explicitly chose that term because it’s not considered subjective by anyone, but especially not by the people who think gender-neutrality is somehow NOT political. If you claim that it is, they just quip back with “a person’s right to exist is not a political issue but a human rights one”, which of course was never even the debate, they just twist things around to fit their narrative.
AWS literally advertises an isolated “GovCloud” service.
Non-technical discussion should just be banned.
no it’s not, and nobody worth listening to cares anyway.
please stop bringing up this absolute nothingburger.
lol this same post got flagged and taken down from HN
this is the vast majority of all businesses though.
there are many non-systemd distros
not everyone agrees, but that’s ok
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 sounds like the right answer at first, but really, the entire reason ID verification exists is because the whole “just parent your kids” thing already didn’t work, and now here we are. You can’t fix stupid, meanwhile the kids are still doing bad things, and everyone else doing nothing too, solves nothing.
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 don’t understand the point you’re trying to make