I’m a developer but have utterly no experience with torrent architecture, or for that matter anything outside of standard web services and the kinds of things companies do. But I’ve been wondering if BitTorrent technology would be usable for federating content for things such as Lemmy. After reading that somebody was begging for money to offset the $5k/month they were spending to run an instance (I mean, that shows true dedicaton but holy crap dude), it seems like a distributed architecture would make a lot of sense than somebody having to foot the bill for a big-ass server. I just personally wouldn’t know where to begin on a project like that, but maybe if somebody with the right combo of skills and experience gave it some thought…
2 years ago I talked about the core problem with federated services was the abismal scale ability.
I essentially got ridiculed.
And here we are, with incredibly predictable scaling problems.
If we refuse to acknowledge problems till they become critical, we will never grow past a blip on the corner of the internet. Protocol development is HARD and expensive.
I’m a developer but have utterly no experience with torrent architecture, or for that matter anything outside of standard web services and the kinds of things companies do. But I’ve been wondering if BitTorrent technology would be usable for federating content for things such as Lemmy. After reading that somebody was begging for money to offset the $5k/month they were spending to run an instance (I mean, that shows true dedicaton but holy crap dude), it seems like a distributed architecture would make a lot of sense than somebody having to foot the bill for a big-ass server. I just personally wouldn’t know where to begin on a project like that, but maybe if somebody with the right combo of skills and experience gave it some thought…
2 years ago I talked about the core problem with federated services was the abismal scale ability.
I essentially got ridiculed.
And here we are, with incredibly predictable scaling problems.
If we refuse to acknowledge problems till they become critical, we will never grow past a blip on the corner of the internet. Protocol development is HARD and expensive.