Hello! It seems you have made it to our donation post.
Thankyou
We created Reddthat for the purposes of creating a community, that can be run by the community. We did not want it to be something that is moderated, administered and funded by 1 or 2 people.
Current Recurring Donators on OpenCollective:
Current Total Amazing People on OpenCollective:
Background
In one of very first posts titled “Welcome one and all” we talked about what our short term and long term goals are.
In the last 2 years we have carved out a place for all of us to be heard and enjoy. Images, videos, comments however we communicate, I’m thankful of everyone who calls Reddthat home. Over 5000 users is something I’d never thought possible.
You are what makes Reddthat worth coming back too.
Donation Links (Updated 2025-03)
- Open Collective: https://opencollective.com/reddthat
- (best for recurring donations)
- Stripe 3% + $0.3
- Ko-Fi: https://ko-fi.com/reddthat
- (best for once off donations)
- Stripe 3% + $0.3
- 5% on all recurring (Unless I pay them $8/month for 0% fee)
- Crypto:
- XMR Directly:
4286pC9NxdyTo5Y3Z9Yr9NN1PoRUE3aXnBMW5TeKuSzPHh6eYB6HTZk7W9wmAfPqJR1j684WNRkcHiP9TwhvMoBrUD9PSt3 - BTC Directly:
bc1q8md5gfdr55rn9zh3a30n6vtlktxgg5w4stvvas - LTC Directly:
ltc1qfs92f6d80jelhj6avwf9u7q5p7ldqqzg0twunw
Current Plans & Descriptions
- Keep the server running smoothly!
- Our S3 storage is growing and will only continue to grow.
- Hopefully we can drop the EU Server which acts as a proxy for LW traffic now that Parallel Sending might be possible
- We currently are paying slightly more for our main server than we should, and I’ll keep an eye out for a new and better deal.
Annual Costings:
Our current costs are
- Domain: 15 Euro (~$26 AUD)
- Server: $1080 AUD
- EU Server: 39 Euro (~$70 AUD)
- Wasabi Object Storage: $180 Usd (~$290 AUD)
- Total: ~1456 AUD per year (~$122/month)
That’s our goal. That is the number we need to achieve in funding to keep us going for another year.
Cheers,
Tiff
PS. Thank you to our donators! Your names will forever be remembered by me: Last updated on 2025-03-22
Current Recurring Gods (🌟)
- Nankeru (🌟)
- Incognito (x4 🌟🌟🌟🌟)
- Guest (x3 🌟🌟🌟)
- Bryan (🌟)
- djsaskdja (🌟)
- MentallyExhausted (🌟)
- asqapro (🌟)
- Bitwize01(🌟)
Previous Heroes
- Guest(s) x13
- souperk
- MonsiuerPatEBrown
- Patrick x4
- Stimmed
- MrShankles
- RIPSync
- Alexander
- muffin
- Dave_r
- Ed
- djsaskdja
- hit_the_rails
- ThiccBathtub
- Ashley
- Alex
Thank you for the answer. I have delt with scaling DBs with tons of data so the alarm bells were ringing. DBs tend to be fine up to a point and then fall over as soon as the isn’t enough ram to cache the data and mask issues of the DB architecture. With the exponential growth of both users and content to cache, my gut tells me this will become a problem quickly unless some excellent coding is done on the back end to truncate remote instance data quickly.
Sadly I am better at breaking systems in wonderful ways than building systems for use, so I can’t be too helpful other than to voice concerns about issues I have ran into before.
Hahahaha, are you me?
Yeah the db on the filesystem is double the size of it in memory, the current memory usage is about 200-300mb active for postgre. So I’m not worried about it too much.
There are big wins for sure in the database, and I’m for sure looking at the activity table when I get a few hours to myself. It keeps a log of; every like, from every user that the server federates with, and I think it’s not efficient at all. Each row contains a huge amount of data when I’d expect it to be quite small.
But I digress. I haven’t delved into the intricacies and I’m sure it’s not as simple as I make it out to be. There will be lots of QoL work in 0.18 for sure so stay tuned. I’ll be using this Announcement community for all of our big milestones and to keep everyone updated, as well as to crowd source solutions!