Eh, torrenting is fairly common here in Norway. No one in tech circles will raise an eyebrow if you pirate anything for private use, and most outside of tech circles won't care. It is a bit more frowned upon for using in a business, so that's a gotcha.
theterrasque
joined 2 years ago
It's not dumb at all, and it's a common scaling technique. But the software needs to support it, and I have no idea if lemmy has support for running multiple instances for one server.
If I have understood how lemmy works, the post and comment would be on the instance hosting the community. Your server would just post it to the community's server on your behalf.
Disclaimer: I've only looked a bit at the protocols and high levels descriptions of how it works, and this is just my understanding of it. But it seems to track.
let's take .. Selfhosted@lemmy.world for example. Right now lemmy.world is the Source of Truth on this, which means if you sign up for it on a different host, let's say myawersomeinstance.com, that first contacts lemmy.world, copies over posts, and then subscribes on new posts for that. Actually not 100% sure if lemmy.world contacts myawersomeinstance.com when there's a new post, or myawersomeinstance.com polls lemmy.world.. But anyway, point is, lemmy.world is authority on it. myawersomeinstance.com also have Selfhosted@lemmy.world data, but it's a copy of it. And lemmy.world is only authority. So if you post something, your server then sends it to lemmy.world and waits a reply. Then lemmy.world contacts all instances that has at least one user following this to tell about the new post. And that new post now exists on a few hundred databases.
The problem is the scaling is whack. Okay, you can have 5000 federated servers with users subscribing to Selfhosted@lemmy.world, but that means lemmy.world needs to update 5000 servers per post, and there'll be 5000x storage used for that post, and ALL 5000 servers contacts lemmy.world to get the new good stuff.
Frankly, it's a scaling nightmare. As for a different approach, you could have private / public keys and sign updates from lemmy.world and allow the other instances to fetch the new data from each other. That would also allow more relaxed caching, since it would be generally lower cost to re-fetch the data. Now you need aggressive caching because you don't want lemmy.world to keel over and die form every server on the planet wanting to hear the latest and greatest posts all the time.
I posted it on a different post, somehow it ended here. Very sure it wasn't a wrong window or anything since I hadn't opened this post at all before it somehow showed it being posted here.
Anyway, that's why I deleted it. ... please tell me it shows as deleted ...
What setup do you have? Prompt / instruct formatting?
Could use IPFS for file hosting
Out of a 3 minute trailer, I saw 15 seconds of gameplay.
Yeah, I was confused too. Then I found this video: https://www.youtube.com/watch?v=uMOPoAq5vIA - I haven't watched it yet, but it seems to be a new video going through gameplay.
I've noticed that sometimes it takes a long time to show up in results, and sometimes not show at all but worked 10-15 minutes later.
I think servers are overloaded atm
My systems:
- Sunshine - file server and spillover host. Uses ZFS, provides GlusterFS and iSCSI
- Raspi - Raspberry pi 4 - network DHCP, DNS and control unit, spillover host
- Blizzard - Node, glusterfs 2nd server
- Toolbox / GamerStreamer - hybrid windows host with a linux node VM. Windows is used for running windows-only things and stream games via steam
- Cromie - chromebox converted to node
- AcerBox - An Acer box running as node
They're all running in a kubernetes cluster. Nodes are primary deployment targets, sunshine / raspi is set as not preferred, but will be deployed to if there's no other node with resources. Storage is done on glusterfs. Services are provided to network via metallb, and ssl cert handling is done via certbot. Ansible is used to set up and configure the cluster, making it pretty easy to add a new node.
In practice this means any one host can go down without services going down. It will take a 10-15 minute time for kubernetes to flag a node as down and not just rebooting or something and reschedule the services, but it's more or less self healing and usually already fixed before I notice it's been a problem.
As for services.. Some game servers, jellyfin, specialized stream servers for a project, nextcloud, postgres cluster, node red, grafana, influxdb, gotify, proget, a web server, and about 5-10 smaller personal projects.
I went the middle road and settled for 2.5G - still a nice boost, and a lot cheaper. Might be worth a consideration if you can't find cheap enough 10G gear.
Edit: Cost me around 300 dollars to upgrade my network. 2x 8 port switches, and 4x network cards.
Edit2: As a bonus, I could continue using the 1gbit devices directly plugged into the switch, since 2.5G use ethernet and the switches support 1g too.