Oscar J Carlton IV has written a couple of (useless, but harmless) Ruby classes for jyte users and groups.
By
Oscar J Carlton IV
on March 19, 2007
As usual, I didn't notice the existing project until after I got started. The only advantage mine has is the use of the secret "info" API, so that's something. By the time the APIs are fully fledged, I might know how to use them.
The two files are JyteUser.rb and JyteGroup.rb. Naturally, they both expire after 24 hours. If I had the pbwiki password, I might put it there...
Anyway, if you find it amusing or useful, great. As always, constructive comments are appreciated; I know it needs cleaning, and there are probably several Ruby-noobyisms that will make some of you cringe.
6
1
85.7% 14.3%
Embed Claim
Make a related claim
Discussion (8)
There's always something. I need like 8 clipboards.
The first one is the stuff before a Regexp pattern match, and the second is the stuff after. I think it's a Perlism. I believe $& is the text that matches.
Probably because I can't count @ signs.
I didn't want to use String#split, b/c the OpenIDs frequently contain colons, and I only wanted to split on either side of the colon.
The $`, etc, symbols are synonyms for match data; the pickaxe people said it was ok...
By the way, see if you can figure out why my group cred counter is so wrong...
I think I was thinking that two at signs made the variable private; I said it needed some work. What I was wanting to do was separate the implementation from the interface, but there's not much point with such a small class.
I don't know any Perl at all, and certainly didn't want to leave that impression.
The new JyteUser.rb, JyteGroup.rb, and TestJyte.rb. Now with rdoc comments. I'm debating moving them to RubyForge.
New features include contact list retrieval, group intersection tests, and average cred for each group.
I'm working on a cred visualization thingy for it now (probably in graphviz), and starting the RubyForge upload process. I had to pick a lame module name, b/c jyte was already taken, and I didn't think trying to merge with this project would've worked out in the short run at least, since I don't know what this will be when it's finished.
Anybody have any thoughts on what kind of license it should use?
Also, anybody who finds this stuff useful is welcome to work with me on it and certainly encouraged to give feedback or suggestions.
MIT license might be good, but at least LGPL or something allowing other people to jump on it. Though, you might want to protect it from someone using it to make a ton of money through your work. :)
I think it's either creative commons or ruby license, depending on which form it used. I really only need the minimum that lets people know I wrote it.