This is why I never bother with any “easy install” scripts of any kind. Give me a list of Docker images, a list of environment variables / config files, and some form of reverse proxy configuration and I’ll figure out the rest. You don’t know how my server works better than I do.

Wayland very good on AMD and Intel these days. Nvidia was unsupported, but last year nVidia made a business decision to support EGL(?) so with fresh drives work has begun in Gnome and KDE to support Nvidia in Wayland. I’m not sure how mature Nvidia on Wayland is yet

Clarification: GBM is what Intel, AMD and the general “nice players” of the Linux graphics ecosystem decided, whereas EGLStreams was something NVidia came up with because it worked better with their proprietary drivers (AFAIK)

Gnome and KDE were fine going out of their way to support both, but smaller implementations such as wlroots (the thing behind sway and Hyprland and other non-Weston “window managers”) didn’t feel the tradeoff was worth it (in both philosophical and manpower reasons) and stuck to GBM.

NVidia comparatively recently “caved in” and got GBM support working (alongside kernel mode setting, PRIME & other terms you don’t really need to know about), and being one of the few proprietary players in the ecosystem they have not been able to benefit from help from the community, which is one of the reasons why their Wayland support is immature compared to the likes of Intel and AMD.

My instance seems to be able to access yours. I assume it’s just the general Reddit migration straining the big servers. I know .world is struggling pretty heavily right now.

Encryption is hard to get right. Which doesn’t help when it’s essentially useless unless you get it right

https://github.com/soatok/mastodon-e2ee-specification was a thing but it doesn’t seem to be updated for months now.

Also note that Lemmy does dıd not implement Authorized Fetch until two weeks ago, meaning certain instances won’t be able to contact Lemmy instances even if you do everything correctly.

The main issue you’re gonna encouter is CORS. There is no real upstream decision on loosening the existing CORS permissions. The alternative is to proxy every request from everyone which will not only get you rate limited but also you will have to deal with storing people’s authentication tokens which requires not only complete trust in every step of the way but also not accidentally messing things up and exposing them somewhere.

Communities are not exclusive to people from their own instances. Otherwise single-user instances like the one I’m replying from would be impossible.

The health of the fediverse depends on smaller instances existing. The fact that larger “untouchable” instances exist at all is harming the fediverse as we speak. Mastodon folk are already familiar with this problem regarding dot social & dot online.

That’s admins of other instances you’re federating with banning people from their own instances.

Feel free to go do that then

Please make sure that you’re only indexing Lemmy communities and Kbin magazines (i.e. not microblogs)

In the wider fediverse, there is an actual expectation of privacy beyond “well it’s technically possible to scrape everything so we may as well give up”. Several people (with reasons of innocent naivete & explicit and blatant malice alike) have tried making fediverse search engines, but all of them are either dead or blocked.

Lemmy/Kbin is in a unique position where global search does make some sense to have, due to it being a public forum focused on topics (and not people), but there is a very real chance that assholes could use an “unbounded” fediverse search engine to find vulnerable people (quite a few of them specifically fleeing to the fediverse to avoid that kind of problem) and harass them.

Nobody can do caching right

Unless something is horrifyingly misconfigured it should only be cosmetic

Edit: You seem to already have mentioned the steam issue. I’m kinda stupid, sorry

see also: gamersriseup