I got redirected to some weird URL (http://www.omnimaga.org/23.82.187.93) for a while but I managed to fix it now. Thanks for all the hard work on the website

As for loading time it seems fine for now (posting via quick reply seems faster), but the true test will be from Monday to Friday from 4 PM to 6 PM GMT-5 and when the search engine is enabled again

EDIT Attachments work too, so that's good.

Woops, I'll go fix that. That was me trying to get the old server to force you to use the new one. I'll do some testing with the old search engine to see if it will work fine on the new server.

Wow!  So much cheaper and so much better
The only potential issue I see is what happens when you hit the 2TB cap (if ever )
Some people attacking the server may force it to hit the 2TB cap

We use cloudflare to mitigate attacks. It would be really hard for them to do that. Plus I'm sure if I talked to customer support and they realized it was attack we wouldn't be charged for it. Also, the 2TB cap is way better then paying per MB. We still would have had the same issue on AWS. With the new server we only pay per MB after we hit the 2TB limit per month. The old server averaged around 60GB/mo.

Quote from: Sorunome on September 21, 2013, 07:43:07 am

hm, http://status.omnimaga.org/api.php?req=counts&timestamp=1379763623984 (when going on status.omnimaga.org) gives internel server error

it's possible that this wasn't setup yet. It might have moved, but I don't think status.omnimaga.org, axe.omnimaga.org, asmtools.omnimaga.org and the rest were updated yet.

They all were.


EDIT: I think I fixed the status subdomain. No idea how I did though

We may be able to handle the old search method, SMF hasn't been migrated yet so I can't do stress testing.

2TB bandwidth cap. Not that we even touch 1TB. We will still use cloudflare for security reasons.
The forum will be disabled when I perform the site migration which could take a while since I'll have to copy the files between the servers. The new server shouldn't ever have slowdown due to how powerful it is compared to the current one.

Quote from: Eeems on September 10, 2013, 09:53:30 am

Quote from: Sorunome on September 10, 2013, 07:23:31 am

I will add a general plugin with tons of stuff, and it may happen that there are some easter eggs in there

Also, suggestion: (especially for account hookup testing): get it running one something like oirc3.www.omnimaga.org

Err how about oirc3.omnimaga.org. No need to make subdomains overly nasty looking.

The cookie I currently use to check if it is not embedded on a other site to catch your sig is valid for .www.omnimaga.org (SMF-Cookie666)

We'll have to talk design soon.

Quote

Quote from: Streetwalker on September 10, 2013, 06:31:36 am

Quote from: DJ Omnimaga on September 10, 2013, 01:02:18 am

I particularly like the Omni theme . But will it blend... er I mean include the rickroll easter egg?

Sorunome will add it later. (as in once plugins are possible)

Client side API is already done, so plugins are possible for the client.

i know, i need to get to it, but so few motivation these days

I know the feeling.

Hey everybody. As some people on IRC know, an OmnomIRC3 beta is up and running here so feel free to try it out. Not everything is implemented yet, but there are a couple themes on it and it is hooked up to IRC. I would love to hear your suggestions. If you find a bug please log it on github.

Thanks!

Hasn't this been fixed?

Yes, and as far as I know, Sorunome's IP is already on the whitelist.

Quote from: Eeems on August 03, 2013, 05:30:19 am

Quote from: Streetwalker on August 03, 2013, 02:24:16 am

Quote from: Eeems on August 02, 2013, 02:28:07 pm

Quote from: Sorunome on August 02, 2013, 01:50:11 pm

well, they are send anyways to the db because they are stored (duh).
But yeah, i /could/ write a bot that hooks up with the db but idk how much cpu it would nom

It would be so much easier if you just had a node bot acting like a server that sent the post notifications to IRC whenever a call was made by Omnimaga to it. The posting function that stores the data to the database would also make a quick call to the post bot, thus causing push notifications

That's what I keep saying.

Thats why I'm reiterating it

That's why i didn't understand it
JK, lol, well, but with a real push system, wouldn't that also require adding some extra stuff to the posting.php (or however it is called)

Yes, that's what I've been saying!