Nutomic
Lemmy is not Facebook, we dont want to store personal info. If people are interested in this they can directly ask for it in polls.
Tested this on lemmy.ml and lemmy.ca. In both cases the API call takes around 400ms, which is consistent with other endpoints `/api/v3/post/list`. So there seems to be no need for...
We could handle this by resolving the post url and following redirects, eg `curl -Ls -o /dev/null -w %{url_effective} "https://youtu.be/pd5iofvLrIU?si=QO2iK1Zw0Z7NDRHo"`. This gives `https://www.youtube.com/watch?si=QO2iK1Zw0Z7NDRHo&v=pd5iofvLrIU&feature=youtu.be` which isnt fully normalized, but the advantage...
How can we tell that its the same request? The [comment form](https://github.com/LemmyNet/lemmy/blob/main/crates/api_common/src/comment.rs#L17) doesnt have any sort of unique identifier. I suppose we could check for existing comments with identical content,...
Reopening this because its definitely a real issue. A better way to solve it might be through a middleware, with an HTTP header containing the request id. That would work...
I also fail to see the purpose of this. It seems you mainly want new posts to be shown to more users? But the amount of people who actually submit...
Closing this as its not very useful nor intuitive.
Included in https://github.com/LemmyNet/lemmy/pull/5122
@dullbananas I agree, individual requests should be logged as `trace`. However Im not even sure where the request logging is coming from, after commentening out [this](https://github.com/LemmyNet/lemmy/blob/main/src/lib.rs#L292) and [this](https://github.com/LemmyNet/lemmy/blob/main/src/lib.rs#L298) line it...
Nothing4You asked in the admin chat if anyone uses it and got no response at all. Anyway we can leave it for 0.20 as its technically a breaking change.