Storage space is one issue. Bandwidth (how many TB/mo goes out the server) is another. And for any "serious" use case transcoding would also be important (so you can keep the other two down for everyone except Apple users who are stubborn to adopt VP9/AV1, and to provide multiple quality options), which unlike the other two requires powerful hardware most instances do not have.
eh
It uses WebTorrent for distribution between viewers watching at the same time which can temporarily help with the load on popular videos, but there still needs to be at least one source instance that's sharing the video "regularly" (for unpopular or old stuff), which ends up having the same bandwidth issues you'd get with any other video platform.
nobody (in terms of both apps or servers) uses the C2S API. the closest you can get to a "de facto" standard is unfortunately the Mastodon API.
Light mode only "clicked" for me when I set my monitor's brightness all the way down. If you're getting "flashbanged" turn that brightness down. It helps (or maybe my monitor is just really fucking bright)
Except Discord which somehow manages to have the worst light theme ever created by mankind. I have no idea how anyone can use light mode without going mad. Everything else's fine.
You have to actually toggle to see it but IMO it massively improves how scrolling feels.
There are a few more scrolling-related options out there on the net if there's a particular "feel" you want to go for. https://github.com/yokoffing/Betterfox/blob/main/Smoothfox.js provides a couple you can try out, and most of these custom scrolling options use msdPhysics as a baseline.
Not obscure but general.smoothScroll.msdPhysics.enabled
=true is a must have IMO.
.ml unblocked the kbinBot UA a couple days ago so as new posts and comments are made it should be syncing up. there are still a few instances out there that seem to not federate as well (in particular beehaw doesn't seem to be federating beyond community discovery) but i believe that's just some reverse proxy misconfiguration (the lemmy-ansible nginx config had some federation related fixes with the release of 0.18.1 they may not have applied) rather than anything intentional
There are signing keys involved, so if someone puts up a new server but uses different keys then all sorts of federation trouble will await them.
That said it shouldn't affect the general network, just that individual server (both the communities and the users of it)
Edit: As for switching domains on an existing server, that would be equally troublesome as ActivityPub kinda relies on domains for all sorts of IDs.
.ml still seems to have the user-agent block in place but plenty of other Lemmy instances that didn't federate before seem to be federating. or at least federating enough that searching picks up their communities.
last time i tried .world was the only instance that federated with kbin properly
It's possible by having the webfinger endpoints at the "root" while keeping the rest of Lemmy on a subdomain. The main thing that determines the domain in your username is webfinger.
No clue if Lemmy or kbin support this config though, but quite a bit of the microblog-only parts of fedi do, and it's a widely used thing.
All of these are "root" mounts. I don't explicitly mount any subvolumes (they get "implicitly" mounted as folders though)