You can search for a user (user:name), then use a tag script to pool posts, eg. "pool:10". Hmm, I need to add "-pool:10" to remove from pool (would be very helpful when moving posts from the unsorted pools)...
By the way, curl -b 'login=user;pass_hash=md5;' is easier (as long as you're not on a shared machine for others to see the MD5 in process lists).
By the way, curl -b 'login=user;pass_hash=md5;' is easier (as long as you're not on a shared machine for others to see the MD5 in process lists).
cookies are way easier ;)By the way, curl -b 'login=user;pass_hash=md5;' is easier (as long as you're not on a shared machine for others to see the MD5 in process lists).
since you first need to process your sha1 ... or so hmmm
well , got a 1paged of ac... should be easiest for radio to go through all stuff :D
Wait. You are talking about importing the ac stuff directly into the site? I would prefer to use the list I got from MDGeist...
Most of the non-dupe stuff is not worth importing.
Most of the non-dupe stuff is not worth importing.
-b gives cookies; either way you have to get your cookies from your browser, but this way you don't need to create an extra file. Of course, I'm never typing whole curl commandlines, I just stick them in a file and copy and paste.
have fun copy and pasting 5000+ lines! ;)
edit
you dont have to tell me that btw
im the one who came up with this command ;)
i said it before and i say it again
batch importing many files into danboos sucks !
plain sucks!
period...
edit
you dont have to tell me that btw
im the one who came up with this command ;)
i said it before and i say it again
batch importing many files into danboos sucks !
plain sucks!
period...
Er, no, lots of people have come up with it, not just you. :)
No need to copy and paste anything, easy enough to script, though if anyone's thinking about batch importing 5000 files into moe, they need to, uh ... not ...
No need to copy and paste anything, easy enough to script, though if anyone's thinking about batch importing 5000 files into moe, they need to, uh ... not ...
you can ask shuugo how he migrated from his old board (a shimmie) to danboo software :D
Changed star trigger from 2000x2000 to 1500x1500
btw.
how come these pages into existance ?
http://moe.imouto.org/post?page=4
only 3 posts on 1 page ?
http://www.abload.de/image.php?img=fehler-danboxno.jpg
how come these pages into existance ?
http://moe.imouto.org/post?page=4
only 3 posts on 1 page ?
http://www.abload.de/image.php?img=fehler-danboxno.jpg
Deleted images. The site doesn't self-sort particularly very well.MDGeist said:
btw.
how come these pages into existance ?
http://moe.imouto.org/post?page=4
only 3 posts on 1 page ?
http://www.abload.de/image.php?img=fehler-danboxno.jpg
The new global blacklist extends to all Explicit, Loli & Shota (It did on mine)
You might want to flag that Explicit blocking is on by default?
You might want to flag that Explicit blocking is on by default?
The atom feed doesn't seem to update when images are deleted. You can still see the placeholders.
Is it just me?
Is it just me?
Blacklisting works for me. Try reloading a couple times to make sure you have the latest javascript...
No, what I meant was my blacklist had already been filled in to exclude Explicit, Loli & Shota. I've never put any exclusions in place...petopeto said:
Blacklisting works for me. Try reloading a couple times to make sure you have the latest javascript...
I'm assuming someone has applied a global change.
It excludes explicit loli and explicit shota by default.
It doesn't do this for anonymous users, though. Need to figure out how to handle that (maybe just force the default blacklist for them).
It doesn't do this for anonymous users, though. Need to figure out how to handle that (maybe just force the default blacklist for them).
Remember to do the same to registered users (apply the rules on local_config) before submitting the patch to danboorupetopeto said:
It excludes explicit loli and explicit shota by default.
It doesn't do this for anonymous users, though. Need to figure out how to handle that (maybe just force the default blacklist for them).
Not sure what you mean. There's a script to add the defaults, that's why everyone has them...
I wasn't seeing normal Explicit images until I removed the tags. Damn I should have written them down.It excludes explicit loli and explicit shota by default.
I assume by the lack of complaints it must have just been me.
But they can overwrite them right?petopeto said:
Not sure what you mean. There's a script to add the defaults, that's why everyone has them...
Yes, they're just defaults.
I may also (re?)-add a small "N posts hidden" thing, to make all of this more visible, and so we can get rid of the global notice.
Radio: you may have had the old javascripts, which would probably misbehave.
I may also (re?)-add a small "N posts hidden" thing, to make all of this more visible, and so we can get rid of the global notice.
Radio: you may have had the old javascripts, which would probably misbehave.
That's why this modification will never make to danbooru's trunk like it is now. albert doesn't have any interest in letting plain registered users see "loli" posts for example.petopeto said:
Yes, they're just defaults.
I may also (re?)-add a small "N posts hidden" thing, to make all of this more visible, and so we can get rid of the global notice.
Radio: you may have had the old javascripts, which would probably misbehave.
Blacklisting is independent of what users can see, you can still block loli's from normal users though config in CONFIG["can_see_post"]
blacklisting lets the user set additional images not to be shown.
blacklisting lets the user set additional images not to be shown.
Ah thanks for the information. The default filters that were applied confused me.admin2 said:
Blacklisting is independent of what users can see, you can still block loli's from normal users though config in CONFIG["can_see_post"]
blacklisting lets the user set additional images not to be shown.
I seen there's only (Vote Up) option now in post/show but comment/index has both options still.
Alias seems to be messed up. mahou_shoujo_lyrical_nanoha is getting turned into magical_girl_lyrical_nanoha and fate/stay_night is getting turned into fate_stay_night.
Yes, it has already been reportedvistigris said:
Alias seems to be messed up. mahou_shoujo_lyrical_nanoha is getting turned into magical_girl_lyrical_nanoha and fate/stay_night is getting turned into fate_stay_night.
http://trac.donmai.us/ticket/266
Waiting for fix
should be fixed now...
Say hi to another mirror server added
moe.imouto.org - serves all new content
saki.imouto.org - serves content older then 2 days
moe.e-n-m.net - serves all content older then a month (give or take)
moe.imouto.org - serves all new content
saki.imouto.org - serves content older then 2 days
moe.e-n-m.net - serves all content older then a month (give or take)
any ip routing yet?
(like europeans get more saki links than moe.e-n-m links ...)
(like europeans get more saki links than moe.e-n-m links ...)
admin2
example:
curl -b cookies.txt -d "post[tags]=akane_iro_ni_somaru_saka tagme pool:Akane_Iro_ni_Somaru_Saka_Official_Fanbook parent:18841&post[source]=urlgoeshere" http://moe.imouto.org/post/create.xml
although you probably know that already.