I'm meaning to do a complete re-write of the WakabaMark code. With this re-write, I could support things like nested quotes and lists, and quoted lists, and such. The thing is, though, to accomplish this I'd have to make the code strip out the ">"s in front of quoted text. Now, personally, I like quotes to have ">" in front of them, but I could make a much more flexible text parser without them.
Anyone have any strong opinions on this subject?
">" is a widespread and now very intuitively known and used feature on most image boards. Personally, I could get used to not using it, but then again maybe the majority might not.
Well, you'd still USE it, you just wouldn't see it in the actual text afterwards. This is somewhat less intuitive than the current situation, which is what makes me somewhat reluctant to do it.
As long as the quoted text is still a different color, I don't think it'll be that much of an issue.
By the way, I think lists (as in <ul> and <ol>-style stuff, I presume?) are a rather unnecessary feature. I'd rather see you get code blocks working instead of that. :P
I'm working on code blocks, too. Part of the reason I want lists is that I'm meaning to reuse this code later for things like the wiki, where lists are more useful.
Good gravy, you're gonna write wiki software too?!? You're on a rampage!
Feature request: The ability to not use fucking CamelCase. I abhor CamelCase with a fury and a passion, but all too often it's a standard feature on wiki software. [[Braces]] like MediaWiki (Wikipedia's software) uses are much more elegant and result in a page which is much easier on the eyes.
Incidentally, what are you planning on calling it? And do "Wakaba" and "Kareha" mean anything?
I probably won't do anything from scratch, but I've already got my modified TiddlyWiki for the documentation running at http://wakaba.c3.cx/docs/docs.html. I'm meaning to modify it even more when I get some time. For instance, the base TiddlyWiki does not work at all without Javascript, and I've been meaning to make it at least readable without it.
"Wakaba" means "new leaves", and "Kareha" means "old leaves".
"Wakaba" is a take-off on "Futaba" (Literally "two leaves", means a small sprout - come to think of it, "moe" comes from the verb "to sprout" - I wonder if there's a connection there). "Kareha" is to go with "Wakaba", in two senses: New japanese drivers get a "Wakaba mark" to put on their cars, which I've used as a favicon both here and on iichan, while old drivers get a "Kareha mark", which is used as a favicon for the kareha boards.
Can "*" and "_" please be replaced by something used less often?
The only usage I've seen that collides with the WakabaMark usage is when people use * for emoting, like *looks like an idiot*. Personally I can't help but feel that this is not a big loss.
The parser tries to be intelligent about when to trigger the markup, so you can write 6*9=3*18 all you want, or c_code_function_name(), and it won't get parsed.
> The only usage I've seen that collides with the WakabaMark usage is when people use * for emoting
There's also AA that always breaks with it. :(
Well okay, >>11, with AA getting broken by Wakabamark, how about making a couple of characters in a group used to ignore all others in that section, and when its posted, both the mysterious characters are missing AND the AA is wakabamark-free.
I already suggested to implement something like a function that would get triggered by AA (or maybe sjis) in the EMail/Link field and turn off Wakabamark. This could be combined with sage (as it works right now, if sage appears anywhere in the EMail/Link field, the thread will not be bumped).
I've been meaning to implement this, but I always get distracted by something more shiny.
Partition to NOT have quoting with > as part of Wakabamark.
I would like to disable Wakabamark without having to do without the Futaba Channel-style way of quoting.
If I recall my own code correctly, disabling WakabaMark disables > quoting only in Kareha. This matches the behaviours of 0ch and Futaba, respectively - Futaba will make quote sections based on >, but 0ch won't.
I had an idea for autodetecting AA which worked by converting the post to US-ASCII and seeing if anything was lost. It's not a very robust method, though.
It fails as soon as you use any other language than English, which is sort of common around these parts... I was thinking that a better method would be to check for characters that are often used in AA but seldom elsewhere, but I haven't had the energy to figure out such a list of characters.
Having experienced Wakabamark for quite some time at Wakachan and 4-ch now, I think it's not as useful as it seemed. Most cases where it appears still are people who don't understand it and are trying to do something else (emoting, AA kopipe, etc.)...
The idea of a clean, elegant syntax of Wakabamark that is more or less the same as already widely accepted forms of Markup may be noble, but I really think some more complicated and less elegant approach like bbcode would have provided better results in usability on these kind of boards.
No, I still maintain BBcode is a usability nightmare. The only reason people know that is that they have been forced to learn it by other broken software. If I were to use some more explicit markup, I'd use a subset of HTML.
The only real problems I see are with AA (thus the discussion for autodetecting it), and with cut-and-paste, where Firefox has a tendency to insert spaces in front of text you paste, triggering code blocks. Some accidential triggerings of WakabaMark is exactly what I want - ideally, you should be able to use it without knowing it. The list parsing should work like that, for instance, but in practice it has some problems. I should maybe make it a bit more intelligent.
People fuck it up way too often. I really think this would work better as a Firefox extension. Enabling/disabling it in your browser would be much more convenient for me than waiting dozens of years until people get it right (which they won't).
I was thinking of a solution that would please most people, which is to add support for several different types of markup, and make it selectable one way or the other. I was thinking "no markup" (except for the default Futaba/0ch stuff), "WakabaMark", and "HTML", or rather a subset of HTML. This requires two things, though: A good place to put the GUI for it, and me actually writing some code.
Suggestions are welcome, and no, I wouldn't put in BBcode.
> A good place to put the GUI for it
Tools -> Extensions -> WakabaMark
Really, this seems to be the most convenient way for me to keep the ability for markup and not annoy the users all the time or forcing them to go out of their way to disable something that's built into the site itself.
Adding more and more options to the site seems to be leading to eventual design overkill. Which brings to mind: Stylesheet selection could also be outsourced to an extension. But meh...
The main point for me here is that the markdown should not take place on the side itself in that it actually writes the <em> tags into the HTML code.
I like how Thunderbird does this (although I know the analogy is slightly flawed), it only interprets the markdown. It doesn't automatically rewrite my markdown into some HTML characters and then sends the EMail as HTML or something.
>>24
Regarding that Thunderbird example... that's actually the "Quote Colors" extension that does this. Not as customizable as you would like (seems really like every software has its own standards for interpreting text as bold, italic, underlined, etc.), but pretty nifty anyway.
No, an extension is really out of the question. It's far too limiting, since many don't use Firefox, and few of those who do would be willing to install it.
Then ditch it. :(
Would it be that horrible to have a popup to select the formatting method?
I guess not. I just think all these kinky bonus features that transcend mere transfer of pure text and certain filetypes should be outsourced...
Maybe that's because I am still dreaming of a Kareha browser/FF extension.
A preview function? It seems odd to have your text changed mysteriously without any feedback whatsoever, especially for non-coders who are more familiar with the WYSIWYG model.
As for deleting messed up posts, well...apparently a group of people still don't know how to do that, or don't like cookies, or something.
Or post on 4-ch.net, which has disabled the ability to delete your own posts on most boards for some reason.
>>31
It's been disabled because some people deleted their posts for no apparent reason which made the discussions turn pretty incoherent for newcomers.
I agree that WakabaMark should probably be turned off by default. The motivation behind is good but at the moment it just doesn't seem practical.
I like WakabaMark but I wish it'd be a bit more predictable.
For example, only works for 15 or so characters. _ can be unpredictable across multiple sentences (or was that "?). Mixing italics and bold just doesn't work.
Gah.
^H only works for 15 or o characters.0123456789abcdefghijklmnopqrstuvwxyz
↑ successful test with 30
Also _ only works in one paragraph, using it over more than one will break it.
And mixing isn't supposed to work, I guess.
^H is really just a joke, and isn't really supposed to be very useful for anything.
Also, since I'm a semantic markup fag, * and ** don't mean "italic" and "bold", they mean "emphasis" and "strong emphasis", (<em> and <strong>). How they are rendered is entirely up the browser and/or stylesheet. Thus, mixing them doesn't really make sense.
Shouldn't that be left to the browser then?
If a poster wants to mix it, let them.
Is ^H more of a joke than Microsoft's Windows X POS XP OS?
Personally, I like the feature. :)
Wow, that is one stubborn spam bot. Check out the logs:
67.43.11.124 - - [31/Jan/2006:06:07:49 -0700] "GET /sup/kareha.pl/1100047195 HTTP/1.1" 200 31487 "http://wakaba.c3.cx/sup/kareha.pl/1100047195" "Mozilla/5.0"
62.171.194.10 - - [31/Jan/2006:06:07:53 -0700] "GET /sup/kareha.pl/1100047195 HTTP/1.0" 200 31487 "http://wakaba.c3.cx/sup/kareha.pl/1100047195" "Mozilla/5.0"
62.171.194.41 - - [31/Jan/2006:06:08:12 -0700] "POST /sup/kareha.pl HTTP/1.0" 200 202 "-" "Mozilla/5.0"
67.43.11.124 - - [31/Jan/2006:06:08:25 -0700] "GET /sup/kareha.pl/1100047195 HTTP/1.1" 200 31487 "http://google.com" "Mozilla/5.0"
67.43.11.124 - - [31/Jan/2006:08:10:17 -0700] "GET /sup/kareha.pl/1100047195 HTTP/1.1" 200 31487 "http://wakaba.c3.cx/sup/kareha.pl/1100047195" "Mozilla/5.0"
221.163.42.170 - - [31/Jan/2006:08:10:31 -0700] "GET /sup/kareha.pl/1100047195 HTTP/1.1" 200 31487 "http://wakaba.c3.cx/sup/kareha.pl/1100047195" "Mozilla/5.0"
221.163.42.170 - - [31/Jan/2006:08:10:39 -0700] "POST /sup/kareha.pl HTTP/1.1" 200 202 "-" "Mozilla/5.0"
67.43.11.124 - - [31/Jan/2006:08:10:53 -0700] "GET /sup/kareha.pl/1100047195 HTTP/1.1" 200 35522 "http://google.com" "Mozilla/5.0"Note that it tried to POST once, and failed, probably because spam.txt blocked it. Not to be deterred, it posted again, with completely randomzied data! Awesome plan!
strike
^H
Hmmm, is the do_wakabamark() function in http://wakaba.c3.cx/docs/docs.html
>>48
Shit, I just completely blanked out there,
is that function up to date with the current implementation of WakabaMark.
I think the Javascript one might actually be a bit more solid than the Perl one, but it doesn't have the stupid joke features.
test
Bitch why do you list as spam boards that actually may help sell your product?
You are just a punk no-good motherfucker.
Afraid to even list a Contact me section...lmao.
We are >>65's courtiers. We are sorry that our lord has posted such a stupid reply.
After the last war we had completely lost, our lord got mental illness. Everyday, he kidnaps girls from the village. Every night he gets drunk and tries to chop courtiers with his katana.
Now the lady of the house is ill in bed. The people in our country are suffering badly from famine. The neighboring Daimyos is taking advantage of this situation, they try to pass across the border and take over our land.
Quite a few of our fellow courtiers have intention to rise in rebellion.
We are now in dire straits. Our clan would be destroyed.
But, don't worry. We arranged that our Lord become a Buddhist priest.
In his way to the temple, our skilled assassin should take his life.
That is arranged perfectly. After that we will hail Master Monaminokami, the nephew of our lord, as our new lord. We, all courtiers, would do our best to serve this new lord with faith.
We apologize for any inconvenience our lord may have caused you.
Please wait for a while. Please forgive the evil deeds done by our lord.
>>63
lol, firefox, not working with this page
xml error... etc..