| # | Time | Name | Subject | Comment | Host | |
| 1246 | 03/02 02:02 | AT_DA | | I'm going to Shrev...I'm going to Shreveport March 4-7, may peek in here and there if I start running out of cash. | ###.###.###.### | |
| Reply to thread | |
| 458 | |
| 1245 | 03/01 19:40 | kanria | Watchmen ... | Please? Some users...Please?
Some users in /co/ have asked for it and it seems like a good idea to
keep "omg watchmen movie" posts in [mostly] one thread. | ###.###.###.### | |
| File (KB) | |
| 1235954417714.jpg (44.13KB) | |
| 1244 | 02/18 02:52 | Kobra | | Moved into a new c...Moved
into a new condo, so i won't be able to watch any of my boards.
HOPEFULLY i'll have it back tomorrow (feb 18), but if I don't, just keep
an eye on /gif/, /x/, /sp/, and ESPECIALLY /v/.
thank you, fellow janitor brethren. | ###.###.###.### | |
| Reply to thread | |
| 458 | |
| 1243 | 02/15 23:04 | AT_DA | | >>1242 Seen this...>>1242 Seen
this in /d/ lately as well. I fail to see the use in mass dumping links
especially when they fail to even add descriptions or previews... | ###.###.###.### | |
| Reply to thread | |
| 1207 | |
| 1242 | 02/15 14:00 | ssddr | | To use the thread ...To
use the thread for a common theme here, Id like to request a sticky
for /h/. Can we remind people that posing a single image, with a
rapidshare link is not acceptable? There has been an increasingly large
number of people trying to use /h/ to whore up files they've uploaded to
rapidshare, or advertise their shitty site. /h/ is an imageboard, not a
linkdump and i think some people just aren't clear on that. | ###.###.###.### | |
| Reply to thread | |
| 1207 | |
| 1241 | 01/13 20:58 | Liska | | I recently got a j...I
recently got a job and haven't been around as much; as such, /s/ and
/hc/ has been under constant referral link attack (i.e. i come home to
find 8 pages full of referral links with no other images). Until the
month is over and i'm released from my assignment, can someone please
keep an out on both boards to make sure that there's actually content in
there? Thanks :) | ###.###.###.### | |
| Reply to thread | |
| 458 | |
| 1240 | 12/21 21:52 | Dhomochev... | | Going to be away a...Going
to be away a fair amount for about the next week or so. If someone
could keep a close eye on /co/ (we've been getting a lot of trolling and
porn in the evenings) and /h/ and /x/, that'd be neat. | ###.###.###.### | |
| Reply to thread | |
| 458 | |
| 1239 | 12/19 16:23 | Zorpheus | | Update on this: M...Update on this:
Many of my issues were fixed simply by upgrading to Firefox 3. This probably won't work for everyone, but it's worth a try. | ###.###.###.### | |
| Reply to thread | |
| 681 | |
| 1238 | 12/13 05:02 | Liska | | >>1236 another ad...>>1236
another
add on: that posting peoples personal information, such as email, phone
number, social security number (!!!) and IP address are NOT ALLOWED!! | ###.###.###.### | |
| Reply to thread | |
| 1207 | |
| 1237 | 12/13 02:46 | Dhomochev... | | >>1236 We could d...>>1236
We
could do with a reminder to go to /r/ in /h/ as well. Lots of people
have been forgetting that one, usually resulting in me having to delete
half the board. | ###.###.###.### | |
| Reply to thread | |
| 1207 | |
| 1236 | 12/12 16:48 | Liska | | >>1235 and also a...>>1235
and
also a nice little reminder that /s/ is not /r/, jailbait is still
underage and isn't allowed, and a warning to those anonymous' pretending
to be board moderators that they are not.
been having some board troll issues. Can you tell? :) | ###.###.###.### | |
| Reply to thread | |
| 1207 | |
| 1235 | 12/12 16:41 | Liska | | >>1207 thread hij...>>1207
thread hijack :)
is
it possible to get a temporary sticky in /s/ for a week or two
reminding users that it's not a board for hardcore content, and they
need to go over to /hc/ if that's what they're looking for?
I'm
having a lot of issues lately with people make requests in /s/ with
hardcore content, it's getting very annoying, and is pretty much counter
productive to the board itself because the majority of what's being
posted is fairly low-quality.
thanks :) | ###.###.###.### | |
| Reply to thread | |
| 1207 | |
| 1234 | 12/09 22:52 | kanria | | I will be leaving ...I will be leaving Saturday the 13th and won't be home until January 4th. Someone pls keep an eye on /u/ and /co/ for me | ###.###.###.### | |
| Reply to thread | |
| 458 | |
| 1233 | 11/26 11:19 | kanria | | I will be leaving ...I will be leaving today for a trip and won't be back until Sunday, so I won't be able to watch /co/ and /u/ | ###.###.###.### | |
| Reply to thread | |
| 458 | |
| 1232 | 11/21 02:45 | Liska | | >>1231 any luck o...>>1231
any
luck on getting this fixed in the future? I can't delete/ban request/do
anything from my janitor extension at the moment and have taken to just
deleting violating threads manually. I checked my passwords, logged
out, logged back in, doublechecked all my settings, etc. | ###.###.###.### | |
| Reply to thread | |
| 681 | |
| 1231 | 11/19 20:11 | Katsu | | There are a lot of...There
are a lot of the same issues that pop up for me too. Ban request will
have an error saying that it failed because perhaps it wasn't reported.
Deletions via the extension will say that the post/image did not delete
for both cases when it has succeeded and failed. I usually have to
refresh the page to make sure that it is deleted.
I know that this is nothing new. But I wanted some more effort to be put forth to getting these errors corrected. | ###.###.###.### | |
| Reply to thread | |
| 681 | |
| 1230 | 11/18 17:50 | moot | | >>1227 >My fellow ...>>1227 >My fellow janitor brethren need to calm down on the request ban button in my opinion.
YEP. | ###.###.###.### | |
| Reply to thread | |
| 1214 | |
| 1229 | 11/18 10:30 | Katsu | | Just letting you g...Just
letting you guys know that I'm not going to be around as much as usual
since I am at a national conference for the American Institute of
Chemical Engineers doing some presentations. It's only going to last a
couple of days but you never know what's going to happen. I'll be back
Friday.
Take care of /c/, /p/ and /trv/ during the day, but I
should be able to still janitor at night. (I just hate to see reports
accumulate.) | ###.###.###.### | |
| Reply to thread | |
| 458 | |
| 1227 | 11/17 22:25 | Kobra | | >>1223 >Flag the b...>>1223 >Flag the board and delete the spam.
Yeah,
I cringe when I see 600 ban requests on one IP. My fellow janitor
brethren need to calm down on the request ban button in my opinion. | ###.###.###.### | |
| Reply to thread | |
| 1214 | |
| 1226 | 11/17 06:31 | Dhomochev... | | >>1225 This has h...>>1225
This
has happened a lot to me today, to the point where I can't delete
anything without an error coming up saying that the post was not
reported. And on the odd occasion where that doesn't happen, the thread
remains there anyway. | ###.###.###.### | |
| Reply to thread | |
| 681 | |
| 1225 | 11/16 16:40 | Liska | | >>1224 I am havin...>>1224
I
am having the same issues, so it isn't just you. Firefox did a force
upgrade on my browser so i'm not sure if that is what it was, or if it
was something else. | ###.###.###.### | |
| Reply to thread | |
| 681 | |
| 1224 | 11/16 16:37 | Zorpheus | | Perhaps it is just...Perhaps
it is just me, but the extension seems... broken. I can't delete or
ban-request on the fly anymore, getting failure messages about 90% of
the time I try to do so. The Reports list lets me do everything fine,
but I can't use the buttons while actually browsing. Is this due to the
server issues we're having? | ###.###.###.### | |
| Reply to thread | |
| 681 | |
| 1223 | 11/08 20:24 | moot | | >>1222 >Even then,...>>1222 >Even
then, though, ban requesting isn't an ideal way to deal with an
invasion since it depends too heavily on mods actually looking at the
ban requests. If they're not, ban requesting would be no better at
stopping an invasion than deleting would be. >Janitors just aren't
equipped to deal with invasions and the like, and I'm not sure we're
meant to be. Getting the attention of someone who IS equipped to deal
with it is about the most effective strategy we have.
Ding ding ding!
Flag
the board and delete the spam. Stop issuing tons ban requests--it does
absolutely nothing if nobody is active, except flood the queue with
junk. The only persons equipped to address a large-scale flood are
MrVacBob and myself.
>>1216 >I get the feeling it's
probably the same people doing it over and over again, since it's
usually the same types of threads, so anything to stop them for a few
minutes would be greatly appreciated.
What? The vast majority of
these floods are done by bots/"viruses". The mods, for the most part,
are just as ineffective against these types of attacks. | ###.###.###.### | |
| Reply to thread | |
| 1214 | |
| 1222 | 11/08 01:45 | ryukaiser | | >>1221 Even then, ...>>1221 Even
then, though, ban requesting isn't an ideal way to deal with an
invasion since it depends too heavily on mods actually looking at the
ban requests. If they're not, ban requesting would be no better at
stopping an invasion than deleting would be.
Janitors just aren't
equipped to deal with invasions and the like, and I'm not sure we're
meant to be. Getting the attention of someone who IS equipped to deal
with it is about the most effective strategy we have. | ###.###.###.### | |
| Reply to thread | |
| 1214 | |
| 1221 | 11/07 22:49 | Katsu | | >>1220 I am sugges...>>1220 I
am suggesting that a feature be implemented so I can ban request UNIQUE
IPs and thus not just "ban requesting every post of an invasion." | ###.###.###.### | |
| Reply to thread | |
| 1214 | |
| 1220 | 11/07 18:55 | ryukaiser | | >>1219 What you sh...>>1219 What
you should be doing in the case of a spammer like that is to get the
attention of a mod. Janitors are not properly equipped to deal with that
kind of situation. Ban requesting every single post of an invasion
doesn't help anything. | ###.###.###.### | |
| Reply to thread | |
| 1214 | |
| 1219 | 11/07 15:30 | Katsu | | >>1218 Though this...>>1218 Though
this is true, sometimes it is difficult to tell whether or not a
spammer is from the same IP. It is quicker to ban request the poster
(and have that post removed) via the extension than to report the post,
and distinguish it is as a unique IP address.
I think what also
should be added is a mass report function. It should be much like how
you can delete multiple posts using the password box on the bottom. As
far as I know, reports can only be done for one post at a time even if
multiple posts are selected. It will only select the first post that is
selected and bring up a confirmation window for that particular post.
Having this feature would be helpful for me personally and would streamline my workflow during heavy posting periods. | ###.###.###.### | |
| Reply to thread | |
| 1214 | |
| 1218 | 11/07 13:28 | ryukaiser | | You shouldn't be b...You shouldn't be ban requesting the same IP that many times to begin with. If an IP already has a ban request on it, you really don't need to make another. The fact that people ban request the same IP 55 times is one of the reasons that the ban requests keep getting so backlogged.
If
someone's spamming or invading, ban requesting him that many more times
isn't going to get you help any faster- in fact, it'll probably just
make it slower. Yelling for a mod in IRC is really the only effective
way to deal with something that needs such immediate attention. | ###.###.###.### | |
| Reply to thread | |
| 1214 | |
| 1217 | 11/06 18:03 | Liska | | Agreed, this would...Agreed, this would be awesome.
>>1214 | ###.###.###.### | |
| Reply to thread | |
| 1214 | |
| 1216 | 11/06 16:58 | Dhomochev... | | Agreed. We've bee...Agreed.
We've been getting a lot of crapfloods and sagebombs in /co/ of late.
I get the feeling it's probably the same people doing it over and over
again, since it's usually the same types of threads, so anything to stop
them for a few minutes would be greatly appreciated. | ###.###.###.### | |
| Reply to thread | |
| 1214 | |