#xo3

The server "xo3" is currently experiencing internal issues. We apologize for any inconvenience caused and we are actively working on bringing services back online.

[[ well!

I’m sure you already know most of this but I’m going to go over it just to cover my bases:

Most homestuck rp blogs tend to focus on online interactions, chiefly, and probably the easiest ways to start rping with one of these blogs is to just hop onto their open posts — say something smart about what they’re blogging about, or whatever — OR, if you’re mutuals, write them a ‘__ started following you’ greeter; that’s probably the easiest, quickest first way to introduce yourself and your muse.

If you’re looking for in-person interactions, you’re going to find them harder to get at without reason for your muse to know theirs — like say, from having spoken online, as above. I, personally, do in-person interactions pretty much exclusively with people from my Kankri’s timeline(s), so with me, i’m afraid you’re not going to have much luck. :x

As for the specific question of how to initiate roleplay with me — seriously, just hop onto one of my open posts, or tell me where your kurloz blog is and if I am following/decide to follow you, i’ll keep an eye out for your open posts and try to think of witty things to say. c:

granted, i dont make a lot of open posts as of late, and i should really work on that

that’s my bad :x

There will be a few brief interruptions of service on XO1, XO2, XO3, and XO4 as we preform planned Infrastructure and Network maintenance. Outages should be relatively short. Thank you for your patience.

We are currently working to restore service to XO3 due to a Network issue. We appreciate your patience.

We are currently investigating issues when sending emails on our free hosting service. We apologise for any inconvenience caused, and hope to have these issues resolved shortly.

We are aware of the issues on xo1, xo2, and xo3 regarding the document_root and remote_address PHP Superglobals returning the wrong data. We're working on identifying the root cause of the issue, and testing, then deploying a fix for it. We thank you for your patience.