128
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 31 Jul 2023
128 points (100.0% liked)
196
17062 readers
623 users here now
Be sure to follow the rule before you head out.
Rule: You must post before you leave.
Other rules
Behavior rules:
- No bigotry (transphobia, racism, etc…)
- No genocide denial
- No support for authoritarian behaviour (incl. Tankies)
- No namecalling
- Accounts from lemmygrad.ml, threads.net, or hexbear.net are held to higher standards
- Other things seen as cleary bad
Posting rules:
- No AI generated content (DALL-E etc…)
- No advertisements
- No gore / violence
- Mutual aid posts require verification from the mods first
NSFW: NSFW content is permitted but it must be tagged and have content warnings. Anything that doesn't adhere to this will be removed. Content warnings should be added like: [penis], [explicit description of sex]. Non-sexualized breasts of any gender are not considered inappropriate and therefore do not need to be blurred/tagged.
If you have any questions, feel free to contact us on our matrix channel or email.
Other 196's:
founded 2 years ago
MODERATORS
I vote stay.
While the Fediverse is built to be decentralized, social networks rely on network effects. People gather where other people are. There will always be 'winners' and 'losers' in building an instance, or even making an alternative 196. c/196 f/196, c/195, fedi196.gay, ect. The original started out with over half a million members, small by Reddit standards. We're the largest alternative around, and we got less than 10k.
Administering an entire instance for one community seems like overkill, especially when there is a path forward to reducing costs significantly.
Also I like the vibes here.
But if you are concerned with server costs...
The existing plan should take care of the significant majority of costs. AWS charges out the ass for data egress, and while I don't know the billing specifics, this instance moves roughly 1TB a day, and the majority of it is static images by virtue of well, images. It was mentioned that this covers half of existing costs upwards of 1-2k. So whats the obvious solution? Don't use AWS for storage or transfer.Cloudflare and a significant chunk of other providers are part of something called the Bandwidth Alliance (which AWS declined to be a part of) and most importantly, these providers offer S3 compatible object storage without data egress fees. Lemmy uses something called pict-rs; on default settings, uses local storage that has to be part of the VPS that you rent. Enabling object storage allows you to move storage away from the VPS itself and onto a different provider - one that does not charge data egress fees. (Easy money? idk) Ideally, you also get edge caching as a bonus.
So what about the data transfer not associated with images and can't be easily remedied? Different VPS providers have different benefits. Digital Oceans lets you customize your VPS to the Nth degree, Hertzner offers up to 20TB of transfer with it's VPS offerings. While I can't vouch for them myself, that should be enough to cover a whatever other thumbnails and other data that can't be shoved into object storage. Either way, still cheaper than AWS.
As for AWS load balancing, uhhhhh standard nginx/apache config? I've only used nginx as a reverse proxy but I'm not paying for it.
Not touching DB management with a 10 foot pole
TLDR: AWS is great for small projects and my relatives drooling over A40's but they charge for egress, and other QoL services that typically get used by companies with deep pockets.