
What does SHellium do with YOUR email address
Posted January 30th, 2009 by bryanstein
Absolutely NOTHING...there was a user who felt that we were trying to collect his email address as if there was a SCAM or something. We do not sell email addresses or send users advertisements. You might get an email from SHellium informing you about changes to your account; we don't care about your email address. When the aliens land we might send you an email warning you to put on your foil hats, but you won't hear from us otherwise
Fingerd is running so you can finger users on SHellium
Posted January 1st, 2009 by bryanstein
OSX users can use the bloated Network Utility or use the command line utility "finger" like us Gnu/Linux users do.
"finger bryan" will show all information within the following files: ~/.plan ~/.project ~/pubkey
You can not do finger bombs, finger bounces, period fingers or zero fingers. The server won't let you!
touch .nofinger to keep others from fingering you on SHellium
If your browser says our certificate is bad....do this
Posted December 27th, 2008 by bryanstein
Firefox/Safari/Opera Users click here: http://www.cacert.org/certs/class3.crt
Install the Client revocation list by going to Preferences(Options on Windows)->Advanced->Encryption->Revocation Lists-> Import then paste this in: http://crl.cacert.org/revoke.crl
It might take a little while so be patient
IE Explorer Users click here: http://www.cacert.org/index.php?id=17
Visit gopher://shellium.org...try man gopher on SHellium for more info
Posted December 27th, 2008 by bryanstein
Click the ink below and see if your browser can display its contents. The whole site will be mirrored into gopher for our dialup users(soon).
gopher://shellium.org
Server processes went out of control; Cron temporarily disabled
Posted December 22nd, 2008 by bryanstein
The server was down for a bit due to cron running a gazillion processes...we don't have an idea of exactly how many but it was well over enough to keep the system somewhat unresponsive. We tried sending the system sysreq kill all signals but nothing worked, so a restart was in order.


