oh damn, relays really *are* that busy holy crap that's a lot of statuses
@r000t like a mastodon relay or nostr?
or, and i hesitate to ask, an x.25 packet relay, or APRS...
@picofarad
I've joined a throwaway domain to a few popular activitypub relays, for as:Public indexing. They are... Busy.
@graf
Relays or throwaway domains?
@picofarad
@graf
Also what would you recommend for an NVMe dedicated server not in the EU that won't cave to Karens?
@picofarad
@graf
Low to mid double digits, you *know* these losers are gonna try hitting up my clients next, so I gotta budget.
@graf
Any processor should be fine, I'd probably be looking at 2x1TB or better for the storage, at least 16GB of memory.
What I really need to do is sit down and actually optimize postgres so I can raise the retention time without raising the time it takes to perform a search. I'd like to have indefinite hashtag search.
@picofarad
@graf
I don't think I'll need more than 1TB of transfer, collection always happens away from the database to prevent IP blocking.
ECC is preferred but not a hard requirement. I'll probably WAL replicate the database to my house.
@picofarad
@graf
Mhm. Though for $55 I'd definitely want nicer specs.
I'm making new crypto wallets for as:Public to accept donos tomorrow.
@picofarad
@graf
I really want RAID-1 if I'm going to take this seriously, ya know?
@picofarad
@graf
Um.... Right now a:P is meant to be a relay *client* I'd have to look at what changes I'd need to make for it to be a relay server. I don't think I'd actually have it send statuses back out, sounds like a lot of traffic.
@picofarad