Jyte should have a "Subject" search which searches creds, tags, and interests
By
Vynce
on April 17, 2007
Results for 'Foo' could include separate lists of each of the following:
- Tags:
- Claims tagged Foo
- Authors of Foo claims
- Commenters on Foo claims
- Proficient voters on Foo claims
- Creds:
- Givers of Foo cred
- Receivers of Foo cred
- Interests:
- Users interested in Foo
- Groups interested in Foo
Agreed
Disagreed
|
|
17
0
100.0% 0.0%
Embed Claim
Make a related claim
This claim was inspired by
Similar claims
- 24-1 Interests should be able to be co-related with varying strengths, and thence there should be fascinating emergent properties.
- 18-0 There should be a single underlying object ("Subjects"?) used for implementing Creds, Interests, and Tags.
- 20-0 Jyte's Search function should follow the same multiword quoting semantics that its tag and cred parser do
- 30-0 Jyte should autosuggest creds based on the interests of both creditor and credited
- 17-0 "Tagged" is higher relevance than "comments match"
Discussion (9)
well, we don't have user or, as fr as i can tell, group search yet.
We should put together a systematic map of all the available query parameters and sorting options. Sort of an Advanced Beginners' Guide.
An Intermediate's Guide? For after the initial addiction sets in and you want to play around more. First, let me get you hooked, then some others will pull out the harder stuff. :)
I've been meaning to ask, Rachel, why you linked to the claims in your guide the old fashioned way instead of embedding them. I realize that longer claims can be truncated (although I haven't checked this lately).
Because I don't know how to embed them. If you'd like to tell me how, I'll consider doing it that way, but my HTML skills are minimal.
I know how to organize and present information, at least in theory, and how to aim a document to require less frequent updating, but not so much with how to design information layouts or code presentations for information.
to the left of the "make a related claim" link there is a pile of HTML you can copy-and-paste to embed that claim in another document.
well, to the left for most of us. i'll help you find it, if you like.
might be another useful thing to put in the guide, i suppose.
Okay, now I need to figure out whether the upsides of embedding the claims is worth the downsides of decreased accessibility of the document.
It sounds like I can get a decent compromise by specifying the sizes as they do but setting scrolling to auto.
Whenever you start adding complex HTML like this, you run the risk of breaking usability for people.
Isn't there a way to add subtext, like what pops up when you hover over photos? I think it helps with search engines, too.
CTTOI, that could be built into the embedded claimframe, unless I don't know what I'm talking about.
Quite possibly, as I said, not my area of expertise. Plus, I doubt that'd be that helpful for many scenarios. Nor do I have a screenreader to test usability of some other issues. (I have a text-to-speech reader, but that's not quite the same thing.)