Incidentally
My blog now supports the use of tripcodes and secure tripcodes by commenters. The tripcode algorithm should be less broken than Shiichan’s while still not really entirely not being broken. The secure tripcode algorithm is crap and probably not portable.
The source for the plugin is here.
(I don’t approve of tripfaggery any more than the next guy. However, I have too much free time.)
!IIIiIIIiiI said,
January 13th, 2009 at 4:28 pm
Neat. Now does it work right?
!IIIiIIIiiI said,
January 13th, 2009 at 4:29 pm
Sure does. Awesome.
Cairnarvon!Rmk.XarnE2 said,
January 13th, 2009 at 6:12 pm
It doesn’t escape <>”& and so on, because that’s the most inconsistent part across implementations, and I’m pretty sure it was a bug in whatever the first one to use it was.
Right now it just works as a filter on the displayed author name, so the uncoverted tripcode is stored in the database (which is another reason I advise against using secure tripcodes). I should really have it create its own space to store both fields separately, and convert the tripcodes when the comment is posted, but that requires more digging into the WordPress API than I feel like doing right now.
I’ll get around to it eventually.
(Actually, what I should really do is stop using WordPress.)
Edit: Okay, I’m doing it slightly differently now. Tripcodes are processed before they’re entered into the database, but because I don’t see an easy way for it to do it the right way, they’re stored in the name field as
name<>tripcode<>securetrip(because Shiichan tells us this is a great way of doing things). To prevent cheating, this has to happen after > and < are escaped, so I guess we’re basically doing things the same way as most imageboards now (though I think WordPress does retarded things with quotes and apostrophes).It’d take some testing (or some reading the WordPress source, which sounds painful) to work out the idiosyncracies, but we’re still less broken than Shiichan.
!AnONIx9q9. said,
January 14th, 2009 at 9:03 am
is this some trick to steal tripcodes?
Cairnarvon said,
January 14th, 2009 at 12:42 pm
I can’t see tripcodes with the current setup, and I’m far too apathetic about textboard drama to bother changing it just for that.
!WokonZwxw2 said,
January 21st, 2009 at 9:02 am
Sup gusy. I’m working on removing the name field
"GRUNNUR"!GJsUSsMAN. said,
January 21st, 2009 at 9:26 am
This is actually quite preferable to forum/blog registration, gravatar, and all that crap.
> though I think WordPress does retarded things with quotes and apostrophes
It wouldn’t be WordPress if it didn’t!
You can steal this tripcode if you like anyway.
Eksopl!LOLIyiNQUE said,
January 22nd, 2009 at 11:33 pm
Is this some sort of trick to steal FrozenVoid’s trip?
That would be awesome, actually.
But yeah, the problem with tripcodes is that they are only useful as a cross-site authentication method if you trust all the sites where you use them.
Paul Graham !LISPHymEeU said,
January 30th, 2009 at 1:23 am
Sup.
Anonymous said,
September 22nd, 2009 at 6:04 pm
I’ve come to investigate tripcodes. Looking, looking, looking… Ooh, a picture of a worm. I like worms.
test!.CzKQna1OU said,
July 3rd, 2010 at 1:15 pm
This is just a test dude. Cheers for this, it was exactly what I was looking for. I don’t believe in logins etc. for most users. This gives people the ability to be sure that, at least to a certain extent, they can be identified, and posts considered the same.