No.3
>>2Done. 4 images allowed per post.
No.4
>>3Support for webms (and maybe mp4s, although they weren't supported before) would be cool. Is the file size limit still 10MB? Whatever it is, it'd be rad to put it below the post box to tell people. Also youtube embeds, and whatever other old formats people would use that aren't currently supported.
If you want help and all that you could talk to undoall about it, although I figure you've probably already done that.
And thanks for bringing sushichan back to life, I've been missing it over the past few weeks.
No.5
>>4I bet one of the templates will let me put text below the post box. Embeds will be enabled soon.
No.6
>>5Embeds are enabled, and the text below the post form is back.
No.17
Are you going to code snow here?
No.18
this may be a menial request but, do we have word filters? It was a small touch, but it made sushichan cozy in its own way
No.19
Seisatsu I just wanted to say thank you very much first off,
secondly I think the best way to manage the site is a very hands off approach. deleting peoples posts, banning people, stuff like that should be done only when absolutely necessary.
it's also nice when the admin comes on to interact with the site userbase like this thread. Don't feel you have to but it's a really good thing!
No.28
>>17In due time, none will escape the cold embrace of snow.
>>18We don't have any currently and I don't know which ones were used in the past.
>>20Done.
No.29
>>28Not him but, it would be fun to bring those back, though the only ones I remember are
sushi roll - anon (also in the name field)
california roll - newfag
dragon roll - nigger
rainbow roll - faggot
No.38
ooh, adding to that - i think "friendly lady" was used in place of "bitch", was it not?
No.41
Great, someone who knows fuck all about how the site was has driving off the only mod left who did. undoall was right, the site should've stayed dead.
Fuck you, seisatsu you opportunistic cunt. Stop stealing other people's websites and try making yours less shitty, faggot.
Go ahead and ban me and delete this post, like I know you will.
No.45
>>41>who knows fuck all about how the site was has driving off the only mod left who didWhat's going on?
No.46
>>41>For the lack of a qualified oldfag to administrate and host the party for everyone this site should stay dead, instead of helping the only person who used his time to revive the site.Nah, you're just an elitist cunt who doesn't give a shit about the community.
No.47
>>41This makes me sad.
Fucking people who don't actually knows what is going on. Since this place got back up we've got nothing but fucking salty dudes wanting to impose themselves and then going "hurr durr Seisatsu is trying to impose himself".
I'm mad actually, how about you fuck off? You clearly don't care about the community and pretty much thing sushichan is like otherchan where you can just shit all over.
Seisatsu, btw, if this happens to be the same faggot who's been littering the site with his shit, you know who I mean, please ban him and also ban him from the circlejerk as well. Thanks
I appreciate Seisatsu's bringing back the site. He's been doing a fine job so far.
No.50
ITT: Ubuu
No.53
>>41So what you're saying is that you're uber buttmad that you can't impose your own controls on this site? Sorry, this isn't preschool, kiddo. Saying "fuck" eleventyone times doesn't help your case much either.
No.54
These kinds of people are going to follow me wherever I go, unfortunately. Try not to worry about it too much.
No.70
>>46>>For the lack of a qualified oldfag actually there are still "oldfags" on sushichan but yeah the dude was being a douche
No.71
Question: Should posts in /hell/ and /lewd/ appear in /kaitensushi/?
No.72
>>71I am leaning towards no myself, but am interested to hear what others think.
No.73
>>71That kind of posts can break the comfy atmosphere.
But I still would be inclined to say it's better to allow them to show up there.
No.74
>>72Same here, I would rather not see lewd and shock threads among other "normal" ones, it would break the confy vibe. Not that big of a deal but imho it would make more sense to put them aside of the news stream
No.75
>>71I personally don't see a problem, but I can see what
>>74 means.
How about, if possible, making them hidden by default, but make them toggle-able with a button, like the pic?
No.76
>>75Maybe. I suppose I'll leave them visible for now until there's some kind of consensus? I have to write custom code to do this.
On another note, I'm concerned that obviously uncomfy threads like this one
>>>/lounge/219 are starting to appear, and I'm not sure what I should be moving to /hell/ and what I should be deleting or banning, and what I should just leave alone.
Like, I want to say this user should know better, and a part of me in the back of my head even feels like this thread and ones like it are maybe an intentional attack on the userbase, since it's worded in such an inflammatory way that's practically guaranteed, even engineered to create negative drama and force my hand on moderation decisions. I may need to change or add some rules if this sort of thing keeps up? I'll watch it for a while and also see what people think. Discussion here
>>77 No.91
>>89Basically this.Just chill
No.104
My last post got too messy to work with after I tried to insert custom html so I deleted it.
There seem to be two popular opinions going on in the /yakuza/ discussions. One that threads shouldn't be moved from /lounge/ and that we should just fight uncomfy with comfy, and the other that all serious discussion should happen in /hell/ in the first place and lounge should just be random comfy stuff and light discussion.
I'm not sure it's really a good idea to say "anything goes, people can handle themselves" on /lounge/, because if it gets too uncomfy everyone will give up and leave. A constant flow of comfy users to drown out uncomfy users is far from guaranteed. No moderation at all will kill the site just as easily as over-moderation.
Also let's move the discussion about /lounge/ and comfiness to
>>77 since the threads are completely overlapping at this point and I'm just repeating myself in both places.