One of the reasons is it makes moderation (including soft moderation by users like downvotes or reports) harder. Users not familiar with Japanese can’t decide whether the post follows the rule and is on topic.
Japanese Speaker. I can read/write some English but not well, so corrections are always appreciated.
プログラミングや音楽に興味があります。いまはkbinのソースやActivityPubの仕様を読んだりしています。
One of the reasons is it makes moderation (including soft moderation by users like downvotes or reports) harder. Users not familiar with Japanese can’t decide whether the post follows the rule and is on topic.
Thanks for the clarification. I switched from Xfce4 to GNOME many years ago because the former doesn’t support Wayland at that time, but I still miss the manual quarter tiling with the shortcut keys.
IIRC Xfce4 supports quad manual tiling like that.
Strong focus on privacy and security (all authentication with the Lemmy API is done through secure httpOnly cookies, user IP addresses are not leaked to external image hosts, etc)
Awesome. The current lemmy-ui sends a lot of traffic to other Lemmy instances to get pictrs-cached images, so this is huge improvement. On the other hand, on next.lemm.ee those requests seems to be gone. As feedback, I noticed this page still seems to send a request to imgur, and the text is difficult to read because of the low-contrast theme. (edit: fixed and now completely readable. thank you @[email protected] )
Interesting. I didn’t know about Akkoma, Pleroma, and MRF. For a future reference,
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.
Have you checked the shell command history? (e.g, history | grep spotify
)
Most cases will be solved with these settings (but some applications may need additional tweeks):
ja_JP.UTF-8
locale, or~/.config/fontconfig/fonts.conf
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.
Can you run the code against another instance, and curl https://lemmy.ml/api/v3/post/list
?
Our software is built on the reasonable assumption that third party servers cannot be trusted. For example, we cache and reprocess images and videos for you to view, so that the originating server cannot get your IP address, browser name, or time of access.
I hope Lemmy also implements the image/media caching in the not so distant future. Currently, Lemmy Web UI sends a lot of HTTP requests to external servers like imgur. (Github Issue)
I guess reddit will close the current free-tier API once the new dev platform for moderators settles down.
Cheese Day