Oddly, the endpoint on lemm.el and lemmy.ml return comments:

> curl 'https://lemm.ee/api/v3/comment/list?post_id=45734814' | jq '.comments.[] | .comment.content[:50]'
"Yeah, you're right. I didn't read enough of the do"
"Thank you for the tip ... but whatever I try with "
"~~In 0.19.5, they removed the deprecated `post_id`"

> curl 'https://lemmy.ml/api/v3/comment/list?post_id=21766749' | jq '.comments.[] | .comment.content[:50]'
"Yeah, you're right. I didn't read enough of the do"
"Thank you for the tip ... but whatever I try with "
"~~In 0.19.5, they removed the deprecated `post_id`"

I think it would be better to ask the admin of the instance before creating the issue.

I think GET /api/v3/resolve_object should work:

curl --url-query q=https://feddit.org/post/2401677 \
    https://lemmy.ml/api/v3/resolve_object \
    | jq .

(note that the value of q is url-encoded by --url-query)

You can get 50 items at most with limit=50. Try

https://lemmy.ml/feeds/c/lemmy_support.xml?sort=New&limit=50

Not a direct solution but GET /api/v3/site may help.

If I understood correctly, the first match expression doesn’t take the ownership of the prev_data.kind because the prev_data.kind is a place expression:

https://doc.rust-lang.org/stable/reference/expressions.html#place-expressions-and-value-expressions

A place expression is an expression that represents a memory location.

https://doc.rust-lang.org/stable/reference/expressions/match-expr.html#match-expressions

When the scrutinee expression is a place expression, the match does not allocate a temporary location; however, a by-value binding may copy or move from the memory location.

I’m not sure what “a by-value binding may copy or move from the memory location” does mean, but I beleive no allocation means no move.

For the second match, move happens. The tuple (prev_data.kind, new_data.kind) tries to take an ownership of the prev_data.kind, but the prev_data is &Data (borrowed from the vec data), so the tuple can’t take the ownership.

Oh I didn’t know the book is freely available under the CC license; I bought the Japanese translated version just a week ago. The book is quite difficult for me but the first chapter was very good read.

Interesting. I didn’t know about Akkoma, Pleroma, and MRF. For a future reference,

• Do not pass transient undo-y activities through MRF · dcf58a3c53 - AkkomaGang/akkoma - Akkoma Development
• Message Rewrite Facility - Pleroma Documentation

Oh I was completely wrong. cmp() takes a number (not Ordering) and returns Ordering. Sorry for bothering you.

The Enum Ordering provides compile-time safety. For example, if cmp() takes a string or int, the compiler can’t catch invalid inputs (“less”, “equal”, -123, …) at compile time and crash at runtime.

I think it’s a really good candidate for code reading for understanding how Lemmy API client works. I’d try to write some toy program with the crate in this week.

I think you’re right. In CGI, web server spawns a process for each incoming request to the CGI app, so the author provide static files for visitors to reduce the overhead.

Edit: here is the repository: https://codeberg.org/seppo/seppo and written in OCaml, so the single file CGI app is a compiled binary.

Maybe some rules in nginx.conf has been delegated to nginx-internal.conf.

I suspect your instance was used to backup the original communities.

You shouldn’t post the auth value here - it works like a username and password.