I want to see him declared a flight risk and denied bail, even if it gets reversed next week.
Community replication & redirects probably need to become a thing to allow for smooth merges. As of today, if two communities want to merge, one is going to lose all of its history on their new instance. At best the smaller community sticks around its original instance, permanently locked down with a stickied post telling users to go to the new instance.
Kinda ballsy to ask for a payout when he's being hit with dozens of Espionage Act charges. Have fun, Donny!
I'm interested, but I don't know Rust and haven't done frontend work in years. Might be able to do some work around scalability and contribute to a Kubernetes deployment guide (and/or Helm chart).
There's nothing to stop Facebook or Google or whoever from spinning up a large Lemmy instance, piling it up with ads and shilling it to their users. As long as it's federated the rest of us could still use non-bloated instances to read/interact with content.
The real risk is companies showing up and injecting bots everywhere. It wouldn't take much for some company to register bot accounts to any open instance out there and spam ads on local and remote communities, making moderating in general more difficult.
23 sticks out over the edges of 22, builders couldn't measure
This is going to have to be a per-instance thing. Smaller instances may be fine indefinitely with no donations/outside funding, but large instances will eventually require dedicated hardware or kubernetes clusters to scale adequately. Larger instances absolutely should run funding drives as they need to in order to keep up with their expenses. That, or we get ads on here eventually... which would suck.
Another option would be to do federation-wide fundraising and split it out with crypto or something to instance owners that opt in... take some arbitrary cut for the Lemmy devs and split the rest out to participating instances based on their share of active users or something. But that would need some serious anti-fraud controls to keep a rogue instance owner from creating a ton of local spam accounts to rake in funds.
I've been running on All - New to get a feed of everything currently indexed on my instance. Active seems to be moving pretty slowly, so I probably need to go index a bunch more communities.
Communities can unfederate themselves at the click of a button (by an admin, of course). Or they can blacklist "bad" instances. Or whitelist specific instances and connect to nobody else.
Instances can choose to federate specifically with a group of other instances already. If I wanted to turn mine into a right-wing circlejerk or off the rails conspiracy group, all I have to do is find some other Lemmy instances and add them to the Allowlist, which tells my instance to only connect to those I've listed.
Yes, I've got separate subnets & vlans for a few things. My PCs/phone/tablets/etc, homelab, IoT devices (i.e. loads of Govee bulbs/ropes, gaming consoles, oven, etc), Guest (all isolated from everything else internal) and one for my roommate. I'm on a Unifi Dream Machine Pro so setting up traffic rules to allow certain traffic from PC vlan to homelab (and the other way) was pretty straightforward.
As for the VPN, yes a full tunnel would force all traffic over the VPN, but for all but my *arr stuff that's overkill. I just join all my VMs to Zerotier and force traffic from the public LB in via their VPN IP, but the VMs can still pull yum updates and anything else they want over my WAN link.
Mine is public, yes. Not sure how many active users I have, 28 signups but my sidebar shows 5 monthly active users so far. I imagine this will pick up once people start commenting and posting more.