I'm back here. Was kept out due to.....an unknown problem like you said admin2.
Well everything seems to be working now for me.
Well everything seems to be working now for me.
I've implemented fail2ban on the image webserver, if you trigger mod_evasive 20 times a second you'll get banned for 10 minutes..
mod_evasive? What is that?admin2 said:
I've implemented fail2ban on the image webserver, if you trigger mod_evasive 20 times a second you'll get banned for 10 minutes..
EDIT:
Thanks Radioactive.
The name sure threw me off on my idea of it though.
http://www.zdziarski.com/blog/?page_id=442AZD-A9S said:
mod_evasive? What is that?
I take it that a DoS was the cause of recent downtime then.
You'll probably need to tweak it now and then, some will still try to defeat counter measures.
You'll probably need to tweak it now and then, some will still try to defeat counter measures.
negative, old kernel was causing panics in the nic drivers....upgraded to latest ubuntu might of fixed it
bump, switched from ruby provided by Ubuntu to Ruby EE
let me know if you see any site issues
let me know if you see any site issues
tuned Ruby EE a bit more...let me know if you see any problems..
Some editing tools are now hidden by default. To turn them back on, go into settings and turn on "advanced editing". This is just to discourage people who push every random button they see from making annoying random changes.
Auto-propagating posts into pools is being phased out. It's too confusing and doesn't always make sense.
Added a few helpers to the post page; you can now change an X->Y parenting to Y->X in one step, and links to children are shown on parent posts.
You can now transfer a pool membership from a child to its parent. This helps replace the automatic mechanism that we used before. It just removes the post from the pool, and adds its parent in its place, with the same page number.
Added "detach parent from pool". This is for transitioning away the old pool mechanism. If you don't know what it's for, don't use it. This will go away once the transition is complete (it'll take a while).
Auto-propagating posts into pools is being phased out. It's too confusing and doesn't always make sense.
Added a few helpers to the post page; you can now change an X->Y parenting to Y->X in one step, and links to children are shown on parent posts.
You can now transfer a pool membership from a child to its parent. This helps replace the automatic mechanism that we used before. It just removes the post from the pool, and adds its parent in its place, with the same page number.
Added "detach parent from pool". This is for transitioning away the old pool mechanism. If you don't know what it's for, don't use it. This will go away once the transition is complete (it'll take a while).
You can now also change the page number of a post within a pool from the post page, instead of having to navigate to it in the pool order page.
Fixed "-pool:123" doesn't work in tag scripts.
Advanced: you can now "-pool:123:parent" as a tag script to remove posts from a pool, and add the parent post in their place, like "transfer to parent" does. Useful for batch replacing posts.
You can now search history by tags, pool names and descriptions and post source changes.
Tag results show additions and deletions; the rest just shows additions.
Tag results show additions and deletions; the rest just shows additions.
Note history is merged into history; the old note history page will go away eventually. It shows note position/size changes, can be undone like other changes, and note texts will be returned in history searches.
Added "user:name" searching for comments, linked from user/show.
It should no longer be possible for two people deleting the same post simultaneously to accidentally permanently delete it.
"Tag subscriptions" (favorite tags) are disabled for now. They don't scale well and are causing other background processes to take too long.
Added "user:name" searching for comments, linked from user/show.
It should no longer be possible for two people deleting the same post simultaneously to accidentally permanently delete it.
"Tag subscriptions" (favorite tags) are disabled for now. They don't scale well and are causing other background processes to take too long.
Removed the search form from the comments index. It's very rarely used and clutters up the screen; go to the comment search page when you want to search comments.
The top site navigation has been updated, giving dropdowns for each site section. Click-and-hold to open. You can also click and drag downwards to open immediately.
You can also see the most recent forum topics from the forum menu (helpful to see if that bold Forum menu is actually a topic you're interested in without having to navigate to the forum index).
This keeps access to the most common parts of the site quick: it still only takes one click to get to posts, comments, forums, etc. (That's why it's not a click-to-open menu, like Windows menus; those would take two clicks.) It's also not a hover-to-open menu, because those are awful--you move your mouse to the wrong spot and suddenly you've got an unwanted menu in your way.
The menu won't work on touchscreen devices that don't support dragging (smartphone browsers). You'll need to continue using the bottom navigation links for those. A few pages are also still only in the bottom links (eg. "Delete Artist" and other page-specific things).
Tested in FF3.6, Opera 10, IE7, IE8, Chrome 5, Safari PC 3. Usable in IE6 with some glitches. The top-level menu doesn't require JavaScript, so the site can still be navigated without scripting.
You can also see the most recent forum topics from the forum menu (helpful to see if that bold Forum menu is actually a topic you're interested in without having to navigate to the forum index).
This keeps access to the most common parts of the site quick: it still only takes one click to get to posts, comments, forums, etc. (That's why it's not a click-to-open menu, like Windows menus; those would take two clicks.) It's also not a hover-to-open menu, because those are awful--you move your mouse to the wrong spot and suddenly you've got an unwanted menu in your way.
The menu won't work on touchscreen devices that don't support dragging (smartphone browsers). You'll need to continue using the bottom navigation links for those. A few pages are also still only in the bottom links (eg. "Delete Artist" and other page-specific things).
Tested in FF3.6, Opera 10, IE7, IE8, Chrome 5, Safari PC 3. Usable in IE6 with some glitches. The top-level menu doesn't require JavaScript, so the site can still be navigated without scripting.
The pool search now searches pool descriptions, and uses a FTS search index like the comment search.
You can now use most of the site searches directly from the menu.
The site's up near 300mbit and it's not really sustainable. So, we'll probably be implementing some changes to reduce bandwidth use. A lot of bandwidth (in fact, probably more than half) is people blindly spidering the whole site, which is just a waste--almost none of them are likely to ever do anything with all that. A lot of people also download PNGs when they probably don't care about the difference, maybe from not noticing the high-res JPEG versions (which are unsuitable for editing but just fine for viewing).
I'll be experimenting with different things, some probably more noticable than others. I'll try to keep from getting in the way of normal, day-to-day use of the site, but keeping the site around is more important, so bear with us.
I'll be experimenting with different things, some probably more noticable than others. I'll try to keep from getting in the way of normal, day-to-day use of the site, but keeping the site around is more important, so bear with us.
site url's been changed to break previous links
Hopefully the site won't ever get back up to the same bandwidth usage as before the Google/URL changes.
not exactly site news, but there's a minecraft server running @ minecraft.imouto.org
You'll need to get the paid alpha version though
You'll need to get the paid alpha version though
Added something very experimental: automatic comment translation.
To turn it on, set your language in settings. Only a few languages are supported, since we translate all comments to each of those languages and I don't want to spam Google with dozens of translate requests per comment; for now I picked the most common languages on the site.
If you want certain languages to be untranslated, select them in the Secondary Languages box. For example, if your native language is Spanish and you understand English, you can set it to show all messages in Spanish, but to leave English ones alone.
Quotes are translated separately: if a message is in English with quotes in Chinese, and you've configured it to not translate Chinese, it'll translate the English and not the Chinese.
This is only currently implemented for comments, not forum posts, and it'll only work for new comments since we havn't generated translations for all the old ones.
Obviously, this is only as useful as the translations--and the most common language here besides English is Chinese, which happens to be a language that machine translation is still really bad at. Still, it's easier to read than Chinese if you can't read Chinese...
It's not turned on by default for now. This may change later on if it actually seems useful and after more testing.
To turn it on, set your language in settings. Only a few languages are supported, since we translate all comments to each of those languages and I don't want to spam Google with dozens of translate requests per comment; for now I picked the most common languages on the site.
If you want certain languages to be untranslated, select them in the Secondary Languages box. For example, if your native language is Spanish and you understand English, you can set it to show all messages in Spanish, but to leave English ones alone.
Quotes are translated separately: if a message is in English with quotes in Chinese, and you've configured it to not translate Chinese, it'll translate the English and not the Chinese.
This is only currently implemented for comments, not forum posts, and it'll only work for new comments since we havn't generated translations for all the old ones.
Obviously, this is only as useful as the translations--and the most common language here besides English is Chinese, which happens to be a language that machine translation is still really bad at. Still, it's easier to read than Chinese if you can't read Chinese...
It's not turned on by default for now. This may change later on if it actually seems useful and after more testing.
An older change I forgot to mention: when making /post/index API calls, if you filter by "pool:id" you'll get the pool sequence numbers in the results.
Pool searches now experimentally support simple quoted phrase matches. For example, compare:
http://oreno.imouto.org/pool?query=girls+girls+girls
http://oreno.imouto.org/pool?query=%22girls+girls+girls%22
order:date, order:name, order:updated and limit:N now work for pool searches.
http://oreno.imouto.org/pool?query=girls+girls+girls
http://oreno.imouto.org/pool?query=%22girls+girls+girls%22
order:date, order:name, order:updated and limit:N now work for pool searches.
Does order:updated work fine? The result is strange..petopeto said:
Pool searches now experimentally support simple quoted phrase matches. For example, compare:
http://oreno.imouto.org/pool?query=girls+girls+girls
http://oreno.imouto.org/pool?query=%22girls+girls+girls%22
order:date, order:name, order:updated and limit:N now work for pool searches.
The index display for parent posts, flagged posts, etc. is changed. This is partially because the borders are a pain for layout (some other things I've been playing around with), and partially because it's ugly and makes the thumbs harder to see properly. It'll probably be tweaked a bit more later.
Hey petopeto, how about making this "sticky"?
Also what does the colors next to the stars mean?
Here:
(Red Box highlight the colors)
Also what does the colors next to the stars mean?
Here:
(Red Box highlight the colors)
Answer in the post above yours:AZD-A9S said:
Also what does the colors next to the stars mean?
Colors are the same as before, except now they're little boxes instead of borders around the image.petopeto said:
The index display for parent posts, flagged posts, etc. is changed.
Green=parent post
Yellow=child post
Red=flagged for deletion
Blue=pending approval for restricted users (moe.imouto doesn't really use this one)
Personally, I like it a lot better the old way with borders.
admin2
basically....
I don't know :P
the IPKVM wasn't setup correctly so I couldn't get console access, but next time server dies I'll be able to see whats going on.