The Legendary Next Update (365)

167 Name:   2005-10-19 18:55 ID:gBva8ggI [Del]

Oh:

> Getting back to inconsequential nitpicking: I find the "___ image replies omitted" phrase to be a bit redundant, and for one it confuses me as to whether or not those image replies are separate from text-only replies. How about simply calling it "images"?

Yes, that's a great idea, which is why I've always done just that. You're thinking of 4chan.

285 Name: !WAHa.06x36 : 2005-10-23 18:38 ID:Heaven [Del]

>>284

HTML mode handles >> references, but not URLs because I've been too lazy to figure out a regexp that would handle that correctly. Also, yes, newlines are converted to <br /> intentionally. This matches how most sites that accept HTML markup work.

126 Name: Anonymous 2005-10-18 08:04 ID:Heaven [Del]

One of the things I did when I modified and restructured the order of functions in post_stuff() was add specific error messages for each non-comment field. Would this be considered superfluous?

37 Name: Anonymous 2005-10-14 13:32 ID:Heaven [Del]

Oops, forgot to link the first point to my original thread: http://wakaba.c3.cx/sup/kareha.pl/1127326007

Oh, and see if dmpk2k is willing to port over the proxy detection and load-balancing/distributed server cluster functions to Kareha. Those would be neat.

73 Name: Anonymous 2005-10-17 08:21 ID:Heaven [Del]

>>71
forgot to add that turning the CSS selector and Admin functions into drop-down menus and moving them to the right side of board and thread title headers would remove that top bar entirely on the front page.

171 Name: Shii the Metal Idol 2005-10-19 20:51 ID:z/kxsMjQ [Del]

>>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.

215 Name: 214 2005-10-21 15:03 ID:Heaven [Del]

Whoops, sorry. I read "close" instead of "permasage".
Permasage on filesize seems pretty silly, yes.

147 Name: Anonymous 2005-10-19 07:35 ID:Heaven [Del]

> Red, bold thread filesizes displayed near the bottom of subpages?

I support this, especially if thread-closing by filesize should be implemented.

208 Name: Anonymous 2005-10-21 13:46 ID:cRmds2wO [Del]

Recapping, here are the things I'd like to see in the final release:

  • better configuration of date and time (with optional timezone offsets), parsing certain characters for individual elements (ie, yyyy/MM/dd(D) hh:mm:ss -5:00:00) and also accepting numerical inputs for fixed dates and times (Eternal September)
  • config.pl parameter to permasage after a certain thread filesize/total number of characters has been reached
  • change the no-ID-on-email option to no-ID-on-sage
  • no EMAIL_ID parameter (most if not everyone uses "Heaven" anyway, and if they really want to change it they can easily find the string in kareha.pl)

Some nitpicky template adjustments to mode_message in order to more closely resemble 0ch (see http://f17.aaa.livedoor.jp/~zerotest/jikken and http://0ch.mine.nu/jikken):

  • multi-page links (1-, 101-, 201-, etc) at the top of subpages
  • red, bold thread filesize indicator near the bottom of subpages
  • "read all later posts" link just below the filesize indicator
  • non-bolded post numbers
  • colons before dates
  • colons before names (thread subpages only)
  • colons after thread position number in main page thread list
  • smaller and (at least for Pseud0ch) black and bolded title in "Create new thread" box

348 Name: Anonymous : 2005-10-27 17:17 ID:Heaven [Del]

I notice some weirdness with the CSS changes sometimes. For example, the first post on a -100 page will sometimes have the first character of the post enlarged. >>2 looks something like
\
/>2 until it is mouse-overed or you change the CSS, but then it goes back to large again on refresh. Also can happen with lowercase letters. Some of the field labels also change size from refreshing in a certain CSS versus just switching to it.

>It's all a design & layout question. I'd like to have the interface reduced to what is absolutely neccessary, esp. since I do not think many people really want to even bother or bother very often with the whole markup question.

Why have a name field or link field? For the majority of posts they are not used, or only used for sage. As stated earlier, they are not even needed for the bare minimum of usage. You want to prove it is you posting? Use a gpg signature or something and a third-party extension, it is just fluff that is not needed at all!

I'm all for having a system that is easy to modify to the end-user's wants and needs. However, there are going to be plenty of users that are not hardcore enough to make or use such options. Therefore, the normal functionality should be pretty usable.

People seem to pop-up whenever something that would change the interface to shout it down. They seem to fear any change and normally give no reason other than it would clutter things up or some nonsense. Does the CSS selector -really- get in your way? It is probably a whole ten pixels! Is having the More options thing really ruining your experience, or are you just against it on some principle? Personally, I would move it below the comment text-area or something, as now the tab amounts between the main fields has changed.

218 Name: Anonymous 2005-10-21 15:22 ID:Heaven [Del]

>>209

>> More information on the all threads page, date of the last post? file size?

Well, I had already proposed the filesize indicator in >>208, but optimally I would actually prefer that subback resemble the one in 0ch (ie, same as the main page thread list, but without CSS).

And single-post links don't include the thread's first post anyway, so there's no need for >>n. Quoting an entire post is not wise either.

>>211

>Isn't this essentially the same as saying "Please don't talk so much?"

In a sense, yes. Just like the postcount limit could be interpreted as "Please don't talk so long".

>what

main page -- 161 Name:◆WAHa.06x36:2005/10/21(Fri) 14:44 ID:Heaven
subpage -- 4 :◆WAHa.06x36:2005/10/21 14:44 ID:Heaven

Question: does Kareha have a 1001th post message like "Name: 1001:Over 1000 Thread" for when a thread exceeds its postcount limit?

225 Name: 214 2005-10-21 17:05 ID:Heaven [Del]

Okay then, for starters, how about the closing message to exactly look like a post (although it's sad it won't be accesable with >>1001)?

308 Name: Anonymous : 2005-10-24 15:37 ID:hjzD4Li4 [Del]

Why not make None or Text Art the default? That way you don't surprise people.

Also, can you make >> links into anchors('#') when you're on the reply/entire thread page, especially in Wakaba? Currently when you click the link it just reloads the page with a different highlight, which is not all that helpful.

151 Name: Anonymous 2005-10-19 08:57 ID:Heaven [Del]

You may want to consider releasing Kareha & Wakaba under some sort of license at this point, just to make sure that the scripts always stay free for people to use.

http://en.wikipedia.org/wiki/Free_software_license
http://en.wikipedia.org/wiki/Software_License_Types#Free_software_licenses
http://en.wikipedia.org/wiki/Copyleft

26 Name: Anonymous 2005-10-14 00:38 ID:Heaven [Del]

| stays |

243 Name:   2005-10-22 10:54 ID:Heaven [Del]

If you want to have a look at what the code actually does to dig out flaws, here is the current version:

sub sanitize_html($%)
{
my ($html,%tags)=@_;
my (@stack,$clean);
my $entity_re=qr/&(?!\#[0-9]+;|\#x[0-9a-fA-F]+;|amp;)/;

while($html=~/(?:([^<]+)|<([^<>]*)>?)/g)
{
my ($text,$tag)=($1,$2);

if($text)
{
$text=~s/$entity_re/&amp;/g;
$text=~s/>/&gt;/g;
$clean.=$text;
}
else
{
if($tag=~m!^\s*(/?)\s*([a-z0-9_:\-\.]+)(?:\s+(.*?)|)\s*(/?)\s*$!si)
{
my ($closing,$name,$args,$implicit)=($1,lc($2),$3,$4);

if($tags{$name})
{
if($closing)
{
if(grep { $_ eq $name } @stack)
{
my $entry;

do {
$entry=pop @stack;
$clean.="</$entry>";
} until $entry eq $name;
}
}
else
{
my %args;

$args=~s/\s/ /sg;

while($args=~/([a-z0-9_:\-\.]+)(?:\s*=\s*(?:'([^']*?)'|"([^"]*?)"|['"]?([^'" ]*))|)/gi)
{
my ($arg,$value)=(lc($1),defined($2)?$2:defined($3)?$3:$4);
$value=$arg unless defined($value);

my $type=$tags{$name}{args}{$arg};

if($type)
{
my $passes=1;

if($type=~/url/i) { $passes=0 unless $value=~/(?:^$protocol_re:|^[^:]+$)/ }
if($type=~/number/i) { $passes=0 unless $value=~/^[0-9]+$/ }

if($passes)
{
$value=~s/$entity_re/&amp;/g;

if($value=~/"/) { $value="'$value'" }
else { $value="\"$value\"" }

$args{$arg}=$value;
}
}
}

my $cleanargs=join " ",map { "$_=$args{$_}" } keys %args;

$implicit="/" if($tags{$name}{empty});

push @stack,$name unless $implicit;

$clean.="<$name";
$clean.=" $cleanargs" if $cleanargs;
$clean.=" $implicit" if $implicit;
$clean.=">";
}
}
}
}
}

my $entry;
while($entry=pop @stack) { $clean.="</$entry>" }

return $clean;
}

142 Name: Anonymous 2005-10-18 22:44 ID:Heaven [Del]

The Futaba template is missing the "No File" checkbox next to the File field in the Post New Thread area.

124 Name: Anonymous 2005-10-18 07:43 ID:9mxxoE2M [Del]

>>123
signed

252 Name: Anonymous 2005-10-22 13:11 ID:Heaven [Del]

Plus if you were to allow those tags in HTML, you should do the same for WakabaMark (which actually takes its cue from Markdown, so I don't see why it has a different name).

248 Name: 214 2005-10-22 12:23 ID:Heaven [Del]

It's also more markup when even the existing one isn't working as well as it should.

160 Name: Anonymous 2005-10-19 14:51 ID:Heaven [Del]

>>157
So the functions need to be hardcoded to a post element one way or another? If I wanted to, let's say, create a template for gazo-box or Shiichan (both use checkboxes for sage), I'd need to slightly modify kareha.pl to check that new checkbox input instead of the Link string input?

An interesting limitation. Thanks for explaining.

About permasaging/deleting after a certain thread filesize is reached: would this be the same as a limit on the total number of characters in a thread? Or would we also include WakabaMark formatting, hyperlinks (including navigation), name/date/title headers, reply boxes, and non-Unicode characters in the formula?

>>158
Chances are that most if not all major/fundamental changes made to Kareha's core scripts will clash with the philosophy of most people here (including WAHa), and they won't care for them anyway. There really aren't all that many big-bang end-user features left to be implemented in Kareha before it loses its minimalist charm.

P.S. Reminder for >>85

14 Name: !WAHa.06x36 2005-10-13 04:30 ID:gBva8ggI [Del]

I've been meaning to change some of the defaults away from Futaba-style to saner behaviours. Any suggestions for what to change are welcome. So far:

  • Pruning set to furthest-back instead of oldest.
  • Size limit instead of post number limit, maybe?
  • I'll add thread closing to Kareha, but I was thinking of setting the default behaviour to never permasage or close threads.

340 Name: Anonymous : 2005-10-27 08:57 ID:Heaven (Image: 1010x554 png, 80 kb) [Del]

src/1130425040482.png: 1010x554, 80 kb

>>336
IMO minimalist web applications like Kareha should only focus on core content/functionality and leave the inconsequential presentation options up to browser extensions so that each user can tweak them to his whim. That's why I was pushing to offload the CSS selector to an extension.

>>337
Here's a better example, I think. Even if we can't remove the excessive side borders, is there a way to at least have rounded corners?

On formatting options: I think >>338 fails to understand that leaving the formatting options up to each individual user is a good thing by all means. Besides, they are absolutely necessary to the interface and core functionality, just like the Name and URL fields are. Preview functionality, on the other hand, should be implemented in an extension.

I think the issue that people have with the formatting options is that we don't have a Japanese counterpart to blindly model it after. Since we're going at this on our own, nobody is quite sure how it should be done. I'd like to see how it turns out on mode_image (if you feel the need to include it at all). :)

153 Name: Anonymous 2005-10-19 13:16 ID:Heaven [Del]

>>152
What does that even mean? Does that mean nobody can come along and claim some sort of authorshop/copyright on Kareha or a slightly modified version of Kareha?

185 Name: Anonymous 2005-10-20 09:52 ID:Heaven [Del]

>>184
If people are going to decide to use custom names for paramaters, then there isn't much you can do about it anyway, or is there?

137 Name:   2005-10-18 19:23 ID:gBva8ggI [Del]

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.

123 Name: Anonymous 2005-10-18 07:27 ID:Heaven [Del]

Some semantical nitpicking: "replies" should probably be changed to "posts", since >>1 is not really a reply, which makes >>100 the 99th reply to a thread, thus contradicting the "First 100 replies" thing. Same goes for "Next 100 replies" and "Last 50 replies".

133 Name: c-24-91-21-117.hsd1.ma.comcast.net 2005-10-18 17:36 ID:z/kxsMjQ [Del]

test2. looks good!

249 Name:   2005-10-22 12:43 ID:Heaven [Del]

>>247

Well, you have your chance to try and abuse it over on the test page. Although the list of allowed tags there doesn't exactly match what would be allowed here.

Also, the point is to make the type of markup selectable, so you can pick WakabaMark or HTML or none at all.

154 Name: Anonymous 2005-10-19 13:28 ID:1l2MEdqn [Del]

>>148

>5) Seperation of sage et al from the email field to something else...

This is kinda what I had pushed for earlier in >>52. I think that separating the sage (aka, "don't bump"), fusianasan (aka, "show IP"), and ID:Heaven (aka, "no ID") functions from any particular post elements in the main scripts would be ideal for implementing Kareha in systems where inputting a certain string to trigger these functions is not intuitive (ie, every board outside of the 2ch/Futaba family). These trigger strings (S_DONTBUMP, S_SHOWIP, S_NOID) and their assignment to a certain form field input could be instead implemented individually in each template.

>2) Have the string to sage and fusianasan defined as a constant in config
>3) A specific string for ID:Heaven instead of anything in the email field

As I mentioned above, this would better work if they could be modified within each template in the list of string variable definitions.

>4) Cookie preferences such as "Don't use expanding textarea" which leaves it small or big.. or another option for that choice as well; an option to not save Name/Email automatically; anything else that is useful?

I like this one, as far as saving name and e-mail inputs go. I occasionally browse 4-ch at school, and it'd be nice for just an option to clear cookies when you're done and don't want anyone else to use your name, e-mail, and deletion password.

What the hell is RENZOKU?

P.S. >>151 is RMS

This thread has been closed. You cannot post in this thread any longer.