F(C)GI And Terrible Nonsense

20251118 Emil - F(C)GI And Terrible Nonsense

I Regret Nothing

I wrote and set up an IRC using libircclient, it should only be deployed locally. It's a very brain damaged specimen and should be handled with care. [Here.]

FCGI in C was remarkably easy. Highly recommended. [Initial test.] [Fingerprinting tool.]

Invoke them with spawn-fcgi -s sock -n ip -u www-data -g www-data and with NGINX (A.K.A. Retard Strength Apache):

location ~ / {
	include fastcgi_params;
	fastcgi_pass unix:path/to/sock;
}

Anon Anonymous told me of his schizophrenic tranny friend "Perl" who has since committed ritual suicide. Mr. Anonymous is reportly derranged and inside a federal institution for the criminally insane, making up shit about finishing a "gorilla's" "nest." which he claims will melt Gitweb users and torture Gitweb developers for all of time.

My setup for git has gotten worse over time. Initially, being retarded, I used Gitea, which is profoundly shit (but worked) and exploded. Then I became substantially more schizophrenic by thinking "this tool integrated with git itself must be a good web interface worth deploying!" This was retarded and stupid behavior. Gitweb has presented issues since the beginning, requiring name mangling, offering weird URLs that don't fucking clone, and shit not fucking updating. cgit is an objectively better choice, offering HTTP cloning and cleaner design. Gitolite is fine, and is a decent replacement in the face of the webshit menace, and can be made public to rectify some issues. Presumably Anon's Gorillanest would occupy a value similar to Gitea on the webshitend, while providing SSH interactions natively, offering comprehensive coverage with first class SSH support.

Apt, according to its maintainers, has trooned out. Meaning, in 3-5 years when this version of Debian invalidates, I'll be required to move over to a less shit operating system. I'm thinking *BSD.

I set up OpenVPN for LAN gaming. Past generating the PKI and finding good information on the server/client configuration, it was brief and functional. This is strictly for a LAN-like network connection for users who only have IPv4/limited IPv6 support in-game.

List of services so far:

http://xolagit3eapakwcfkcch2qr4kitud4dg57yawc4zdwcjlleebxp4h3qd.onion/	| Top Secret
ircs://xolatile.top/							| Text
mumble://xolatile.top/							| Talk
https://files.xolatile.top/						| HTML & File Delivery
https://xolatile.top/							| HTML
https://chud.cyou/							| HTML
https://chud.cyou/chud/weather						| Really fucking stupid
https://pufka.xolatile.top/						| Anon's HTML
https://mail.chud.cyou/							| Email
https://up.chud.cyou/							| FCGI & File Delivery
https://ip.chud.cyou/							| FCGI
https://finger.chud.cyou/						| FCGI
https://birdz.dev/							| Hosting
https://3chen.org/							| Not a particularly good image board
https://c.xolatile.top/							| ^ minus the domain
gopher://xolatile.top/							| Literally nothing but a tech demo of trannywarez
ssh://xolatile.top/                                                     | Implicit
OpenVPN                                                                 | Optional but technically useful

So in a new server what would have to change is the following:

IRC daemon would probably have to switch, for the simple fact that it might not fucking build under FreeBSD. (effects n=10) Mail daemon would have to change or be severely altered such that passwords would be rotated. (thankfully only n=2) Mumble could be swapped out for XMPP, which could be integrated with IRC, provide calling/video, but probably not because last time I tried that it was a massive pile of shit.

The HTML nightmare gallary could be better isolated and better managed, look into lighttpd and unshittifying my organization. Presumably all the FCGI services should be trivial to migrate. chud.cyou and xolatile.top should be made entirely separate structurally, as both domains will remain per them both being cheap.

The services of Email and Upchud have no way to control limits internally, which should be taken into consideration when deciding on infastructure for the two. Currently I mount preallocated files for them.

For me to actually use a *BSD would imply not using Linux, and thereby foregoing anything depending on Linux, such as most Linux-native proprietary game servers. Given if deemed exceedly important, something like Gentoo could be employed for reasonable amounts of pain in setting up, should provide the best performance, should mitigate any catastrophic problems such as needing to migrate Email/IRC.

3chen.org will be dropped on 2026-04-15, in favor of c.xolatile.top (though that'll probably just get archived and vaporized forever.)

birdz.dev will be dropped on 2026-06-14 (unless the birdman himself revives from the dead.)

MPD. As per advisory from a professional tranny (A.K.A. the TRUE professionals of utterly inane mirconiche-of-a-microniche trash), I set up MPD. it was useful until I realized how retarded it was when it comes to infrastructure and support. As for a Internet radio station, it's a really nice and simple solution, however the minute you want remote control and integration with your system requires n>1 trannies. My goal with this sort of thing, would be an authorized endpoint that streams audio via the Internet that would simply be all of my desktop audio plus music, and some kind of control that can list and interact with playing videos, and play music. Essentially, a full remote video player, which MPD is not.

Gopher. I deployed gopher using a tranny's Haskell warez, which is shockingly pretty functional past some human-manual inspection. I haven't actually done much with it, because it's fucking Gopher and I could be doing literally anything else with my life. the package in Debian is venusia.