@benroyce the account has been suspended now. We get a lot politically motivated reports, so we are careful with decision making, in this instance obviously too careful, seeing all the unsolicited spam and harassment the account has sent out. We wish not to get involved in geopolitical tensions and try to remain neutral as a service provider, while it is hard at times, as long as it doesn't break server rules or the law.
This is what it looks like when ieji.de gets ddosed, half the cores busy dealing with ksoftirqd processes, didn't took long for it to get filtered using suricata+crowdsec, ssh port was tcp synflooded.
Y'all got to stop pushing your political agendas by reporting conflicting ideologies, try to start civil discussions with them instead of silencing attempts.
It's a #moderation effort no one wants or needs, thanks!
Well, now my #torrent#tracker udp://chihaya.de:6969 running #torrust#actix is using 8 cores, 14gb ram, 830mb DB size. That escalated quickly. Current stats:
Unparalleled performance (80x3Ghz CPU, 256GB RAM, 4TB nvme, 10gbit net), Total obfuscation of your IP and accessible via Tor network, Open federation policy, Unpopular opinions welcome(as long as they are not unlawful), Moderated against harassment, spam and other unwelcome actors, Blocks bluesky bridges and threads, Offers all Mastodon extras, like translation and search.
Feel free to join us in our effort to make this #instance an enjoyable #Mastodon experience.
You know whats scary as sysadmin? When you assume a ~30-40% cpu usage baseline because postgres likes to go berserk and then you see it dropping to 5-10% just like that. I guess the massive postgres congestion is dealt with then? 😅. Still spooky, postgres was like number 1 cpu burner for the last couple of month together with sidekiq and suddenly its not. 12 load looks outlandish. Anyone needs a minecraft server hosted or something?😂
Serving around 7 million torrents at http, https and udp://chihaya.de:6969/announce because after I stopped the tracker like 5 years ago (since the chihaya tracker software wasn't as good as I expected) the traffic was still quite high towards that domain, now using torrust-actix as tracker software, way less resource consumption, barely scraping 1x3ghz cpu core at 7 mil trackers and a million active connections.
@honobono I did add some blocklists, but obviously left out tor exit nodes blocklist, I've started adding tor ips to a whitelist. But yeah you are right, some exit nodes are blocked for abuse.
When a "tech pro" is like "yeah thanks to the NPU, copilot is very fast" and I know it's not using the NPU in the slightest but gets sent to the cloud instead, I loose all respect. Not the tiniest bit of research done.
Updated the server (including postgres) so i stopped mastodon and was doing something else that... more or less made me forget to start it back up. Crap, sorry. :schmusekadser: . I was literally like "wait, 17% cpu usage, I forgot to start something something didn't I? oof."
@adrianmorales it's insane, one reason for me to skip switch 2. I sold the switch after noticing I don't have enough people owning a switch or being interested in playing locally :p.
Alright almost constant usage of 40 cpu cores, thats fine. 40 left for spikes, and the bonus that its not 40 threads like usual but 40 real cores left.
Altruistic, liberal FOSS lover, Tor/Ygg/I2P advocate, LGBTQIA+ allyWell versed linux admin which also hosts this here and the https://rel.re relayAsk me about crowdsecMr. Nutz Progamer