The Legendary Next Update (365)
300 Name: Anonymous : 2005-10-23 23:06 ID:Heaven
Seconded. This'll go a long way to resolving headaches with WakabaMark and SJIS art, and there really isn't anything egregious about its current implementation into the mode_message template (nothing compared to putting it in a separate area, for example)
Going back to the CSS selector: since switching styles is not inherently supported in all browser GUIs, how about having a third party create extensions for those browsers and freeing up the real estate on the actual page? The selector to me seems out of place with the rest of the layout, simply because it's only there for the purpose of presentation, not the actual page content. How many people out there change styles from board defaults on a regular basis because of readability preferences?
107 Name: dhcp125.engglab.ualberta.ca 2005-10-17 17:28 ID:Heaven
fusianasan + sage test
179 Post deleted by user.
286 Name: Anonymous : 2005-10-23 19:13 ID:Heaven
> The error page in mode_message should more closely resemble that of 0ch (complete with "ERROR!" title).
Signed. And the style selector on the error page is pretty useless.
47 Name: Anonymous 2005-10-14 22:48 ID:1l2MEdqn
>>46
Well, I haven't checked to see exactly where the ban functionality exists in Kareha, but my idea is something along the lines of: (1) encrypting the offender's IP, (2) writing it to a bans.txt list, and (3) writing a parameter next to the IP specifying the time when the ban should be lifted. Of course, you also need underlying code to check bans.txt every time a user tries to post or reply, and also to remove a ban entry at its specified time.
194 Name: Anonymous 2005-10-20 12:12 ID:Heaven
> Why?
I am not the user who initiated this parition but I find them to be triggered far too often.
> On another note, why have I seen partition instead of petition multiple times?
An old imageboard meme. Don't ask!
188 Name: Anonymous 2005-10-20 11:10 ID:Heaven
> partition to kill secure tripcodes
signed
> add functionality for multiple uploads in one post.
I think this was decided against before.
116 Name: dmpk2k!hinhT6kz2E 2005-10-18 03:53 ID:Heaven
What does "fusianasan" mean?
269 Name: !WAHa.06x36 : 2005-10-23 15:11 ID:Heaven
> Can't this be somewhere else but the post form?
No, because that would be immensely useless and annoying, because nobody would know it's there, and even if they did, they'd have to go somewhere else every time they wanted to post something using a different markup.
171 Name: Shii the Metal Idol 2005-10-19 20:51 ID:z/kxsMjQ
>>170
But my good man, sage means down.
> Also, how is Kahera unrivaled when there are still large sites that are not running it? Shiichan is still on world4ch, Thorn on parts of wakachan for example.
These are temporary problems because the webmasters of both sites are too stubborn to upgrade.
296 Name: !WAHa.06x36 : 2005-10-23 20:44 ID:Heaven
Should be fixed now.
140 Name: Anonymous 2005-10-18 20:03 ID:Heaven
>>137
I also noticed that you removed the CSS selector in individual thread views. Personally, it seems both the Admin options and Style selector are a bit of a hindrance to the overall layout. Don't get me wrong -- I think the drop-in Style capability is fantastic-- but it just doesn't seem to play nice with the current 2ch page design.
The thing is, don't most or all major browsers these days allow users to change CSS styles from within the application itself? I know Firefox does, at least. Maybe the selector isn't really necessary.
342 Name: !WAHa.06x36 : 2005-10-27 09:31 ID:SjmelPTB
I don't see any inconsistencies in >>341 except for the rounded corners.
280 Name: Anonymous : 2005-10-23 18:15 ID:Heaven
Hmmm, I just noticed you still allow <a> tags, which would let posters use inline links. Are you gonna keep that?
9 Name: test 2005-10-12 20:46 ID:Heaven
> Reintroduction of "Marked for deletion (old)"
I actually don't like that, and think wakaba should no longer use the futaba style of dropping threads by default. Why not use the least-popular option instead? If a thread is in demand, let it live.
350 Name: Anonymous : 2005-10-28 03:57 ID:Heaven
> Does the CSS selector -really- get in your way?
> Is having the More options thing really ruining your experience,
Yes and yes and I already stated why.
I am sure you know this but text markup takes place on a whole different level than identification/bumping issues. Your comment about pgp signatures is very funny but I will not honour it with a comment.
74 Name: Anonymous 2005-10-17 08:29 ID:Heaven
> To more closely resemble the 2ch look, how about prefixing thread title headers in the main board page with a 【position:postcount】thingie?
2channel does not do this either by default. It can make browsing a bit more convenient (and I suspect dedicated 2channel browsers to insert & read these in some kind of standardized way) but I don't think that's reason enough to impose it on users by default.
> Of course, this could get screwy if you're using reverse order and out-of-order posts in the URL, so I dunno how well it could be implemented.
Personally, I find the reverse order listing, as well as the random order listing, to be a bit silly & useless. The only useful bonus feature here seems to be the comma range seperator, but it seems even in that case there is not much benefit to it (saves 1-3 links in the average case that it is needed, which is rare to begin with).
> The "First 100" link should also be removed from the bottom of individual thread pages, and there should be a link to to thread-list included below the reply box of each previewed thread on the front page.
signed
> In order for the CSS selector not to take over the entire header, how about turning it into a drop-down menu?
This was proposed before (long time ago) and it is hereby also signed.
> and would something like this work (given that all boards share the same root directory)?
That's a tricky bit and I think it was decided against because it would be too much work to properly maintain such a function at the time when 4chan implemented it.
64 Name: &height=16)
2005-10-17 05:03 ID:gBva8ggI
Ah, there was an XHTML error in the cutesy capcode, and of Safari won't handle XHTML correctly and die on errors. Gah. Fixed.
177 Name: dmpk2k!hinhT6kz2E 2005-10-20 02:33 ID:Heaven
What does Thorn have to do with Kareha? Thorn's counterpart is Wakaba.
Anyway, the version of Shiichan on world4ch is bust. It's not a case of feature versus feature here, Shiichan simply doesn't work. It's not worth comparing until it doesn't break regularly.
If Shii were still working on it might be different, but Shiichan is effectively a dead project which incidentally has a closed and broken version working on world4ch.
297 Name: Anonymous : 2005-10-23 20:52 ID:Heaven
How about appending an estimated (at the time of thread creation) time of pruning to the first post's header, if pruning-by-age is enabled?
180 Name: Anonymous 2005-10-20 06:32 ID:Heaven
>>178
There will always be pranksters around. This is probably a good example on what matters to trust tripcoders more than anonymous contributors.
Trivia: Here is a list of 2ch kopipe to fool people into using fusianasan:
http://ansitu.xrea.jp/guidance/?fusianasan
222 Name: Anonymous 2005-10-21 16:19 ID:Heaven
>>220
I meant only using the extra post for autoclose situations where the thread has exceeded the defined postcount limit in config.pl. As for the implementation, couldn't you just have Kareha use post_stuff() and (somehow) replace the timestamp with "Over XXXX Thread"?
137 Name: 2005-10-18 19:23 ID:gBva8ggI
Removed it when redesigning the page head, haven't figured out quite what to do about it yet. It needs to be changed, but to what, I'm not yet sure.
282 Name: !WAHa.06x36 : 2005-10-23 18:24 ID:Heaven
I'm not sure. On the one hand, people expect that to work. On the other hand, it can be a bit annoying. On the third hand, it's not all that annoying anyway.
18 Name: !WAHa.06x36 2005-10-13 10:11 ID:gBva8ggI
What browser are you using? I think I've tracked down the problem, and it's most likely a browser bug. The ancient Firebird (not fox, even) version I tested at work had the same bug (character set issues in the escape() and unescape() functions). It looks like your browser also doesn't follow the spec for how they are supposed to work.