eeh fuck it
he/him btw
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.
alongside the others mentioned here, lemdro.id exists for Android-related stuff and lemmyrs.org exists for Rust stuff (but seems to be running an old version of Lemmy, so YMMV)
Well, the “how” is technically simple. You paste the URL to the search box and you hit subscribe. You can do that right now with:
Lemmy itself only let you subscribe to ActivityPub Group actors though, so it’s quite restrictive in that regard. kbin adds user follows and microblogging into the mix, but you can’t do those through Lemmy yet (or perhaps ever).
However, the real “problem” is presentation. While you can, say, follow a Lemmy group from Mastodon. Mastodon is not intended for groups so it kinda breaks and ends up spamming your home timeline with all the posts and comments. Other implementations such as Akkoma or Misskey or Calckey (pending rename) might end up interacting better (because Mastodon will try to convert everything it gets into Notes in a “lossy” fashion).
While the protocol does allow you the freedom to interact between services, you will not get the best experience if you’re not on a “similar enough” service. Although that does not stop you from following a PixelFed account from Misskey, or a Mastodon user accidentally finding their way into the Lemmy comments section. (You can tell because they’ll be the only comments that end up tagging people when replying)
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.
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.
jsyk, with how ActivityPub works changing the software that’s running from under it will break federation with you in all sorts of subtle ways. When you pick a thing to run under a domain you’re effectively locked into running that software under that domain. And of course there is some cryptographic verification as well so you change the keys (or you wipe or forget to back up the database) you may as well burn that domain from federating ever again.
On a desktop or especially laptop case, it should be equal to (or larger than) your RAM if you use hibernation (as RAM gets copied to swap during hibernation)
On my server, I set it up to be 2GBs, mostly arbitrarily. Right now it’s at 500MB, but my main memory is also only 600-800MB full out of the total 4GBs available, so I’m not running out of RAM anytime soon.
Swap behavior seems to have changed a while ago, so consider reading https://chrisdown.name/2018/01/02/in-defence-of-swap.html on how it works right now. Hell, even that might be outdated nowadays. Up to date info on how swap works really seems hard to come by.
Moreover I also have my swappiness set to 0 because I don’t want stuff swapped out of memory. If I need more memory I need more memory.
I don’t think swappiness has worked that way for a while now.
People aren’t against companies, people are against Meta. In the wider fediverse, anyway.
A while back there was talk of Tumblr potentially joining the fediverse, and it was met with neutral to positive reactions. No idea what happened there, maybe they’re still working on it, but I do not expect a “fedipact against tumblr” to gain as much steam (if any) when they decide to announce they’re ready to flip the ActivityPub switch.
(no idea if my other comment got sent out, this may be a duplicate)
This seems extremely elitist, even if just for the fact that you do not know what other knowledge (and experiences and viewpoints and…) those people who’d be interested in those communities would bring.
If you want a site comprised entirely of - what it seems to me - techbros who talk about how large their homelab Kubernetes clusters are, you should do that by curating your experience with the general platform, not by excluding anyone else, which is what you’re doing here even if you don’t realize it.
I personally want people from all walks of life to set up shop in the fediverse (as long as they’re not jerks). Even if I’ll never see or interact with 99% of what they create, maybe that last 1% will solve an obscure problem I encounter, or recommend me something (whether it be a product or recipe or location or…) that will change my life for the better.
Tildes was always invite only. Granted it is (or was at the time, maybe they slowed down with the influx) really easy to get your hands on one by just asking on r/tildes (or email).
Hell, the site being readable by the general public is a relatively recent introduction compared to it’s history.
I do not agree with the people wanting to control other servers by trying to force defederating from threads. Independent admins running their own server is what the Fediverse is built upon.
As long as authorized fetch is implemented (and correctly), intermediaries can’t “leak” messages out anyways. If Threads wanted to read the contents of a boost, they would have to ask your server for that, and your server can tell them to screw off.
Does kbin or Lemmy implement authorized fetch? If they don’t they should start working on it. And consider enabling it by default. I know versions of Lemmy >= 0.18 can talk to GTS (which enforces AF) so there is partial support for it. And nobody runs 0.17 because of how inefficient it is, so that won’t be too big of a backwards incompatibility issue. No idea how it works on kbin land here, but it should be implemented ASAP if only so that any future enforcement won’t break backwards compatibility.
You could represent booru tags as hashtags, and PixelFed already shows how image sharing can be done.
All that’s left is someone to do the hard work of patching together a booru UI for ActivityPub. Hell, considering the use case it could be a frontend for an already existing backend-only AP software like GoToSocial. That would make the implementation drastically simpler as you wouldn’t need to deal with any of the AP parts at all.
that would be censorship, something the fediverse aims to avoid. We all shit on meta/twitter/other large corps for censoring content, but when instance owner’s do it, its fine? De-federating for ideological reasons like this goes against the principles of federation.
The thing about the Fediverse is that you have the choice to pick an instance. We shit on “big tech” when they do something, because there isn’t anything else to do. I personally want to be on an instance that will defed the fuck out of threads (and anyone else who will bring over people who will delight themselves on harassing me and my friends) should they federate, and if you don’t want that you’re welcome to go to an instance that won’t, and we can still talk to each other.
ps: As far as I’m aware, Fediverse never “aimed to avoid censorship” nor had any “principles on federation”. In fact, there are large parts of Mastodon (well, mostly Pleroma/Akkoma/Soapbox) filled to the brim with the worst kinda people you can imagine, yet they’re all defederated into their own little sandbox. Nobody can decide who can use and build upon ActivityPub but we sure as shit can decide to not federate with a company so shit at moderation that everyone opposing federation with them seems to be a minority in one way or another.
I have no idea if there was a native setting to disable it or if it was RES’s doing but I completely forgot chat even existed.
The solution to this is Authorized Fetch. It trades a little bit of efficiency (individual AP messages being re-shareable by intermediaries) for proper authorization (every server must fetch the messages directly from the source, with the correct authorization). Mastodon implements it behind an env variable, and implementations like GoToSocial force it. No idea how kbin or Lemmy work but they should look into it.
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.