|
Aster Lardner
Registered User
Join date: 14 Nov 2005
Posts: 72
|
04-12-2006 10:11
Tags
I was listening to radio Linden and Pathfinder's interview. He mentioned tags in profiles. I think this is an awesome idea, but I think it would be awesomer (is that a word?) if tags had two added features:
I think tags should be grouped or categorized. Or perhaps associated with other tags. There are many things like Geek Code, Bear Code, Furry Code, as well as various forms of WhatIz tags found in MUCKS that would only make sense in the context of other tags.
If Lidens added a textbox and database for tags, I think I ought to be able to enter something like this:
Furry, Narnia, Dragons, Snakes on a Plane, OMGWTFBOXONHEAD!11!!
Species{Polymorph, Lion, Dragon}
Geek3.1{GCS/SS d-(---)@>-pu s+:++ a-- C+++(++++) U--- P L-- E? W++>$ !N !o K--? w+ !O M-- V? PS++ PE- Y+ !PGP t+ !5 X++ R+* tv-- b+ DI-- !D G e++ h- r y---}
FurAffinty{FC1.Fv~ S$MA1++++++ S$^Other G$+ G$^ H$7-f W$400-fm T$4-f W$-f A$24 M$++ H$++ M$+ M$Seven_Elemental P$+++++ F$+++^++++ S$+ N$Aster}
WhatIsz1.33{yiffy homosexual male-only messy no-pain no-damage romantic inflatable innocent macro/micro shapeshifters transformation Muscle-lovin'}
WhatIszTF1.33{be-changed restrictive big males slow mythical djinn magical sexual morphic cows canine cervids equine feline wolves pachyderm reptile weird pig non-consenting plants size slave change-others}
I guess the main reason would be to separate people that live in PA from people that wear a PA. The idea is all tags within a certain delimiter (in this case “}”) get associated with another tag.
The second feature I'd like to see would be the ability to fetch a user's tags via LSL.
|
|
Argent Stonecutter
Emergency Mustelid
Join date: 20 Sep 2005
Posts: 20,263
|
Property lists.
04-12-2006 13:33
I want string llGetProp(key agent, string name);, as well as integer llSetProp(key agent, string name,string value,integer flags);. Flags would include PROP_PUBLIC, PROP_APPEND and PROP_REPLACE. If agent != llGetOwner() you can only read names that have PROP_PUBLIC set, you can only write names that have PROP_REPLACE or PROP_APPEND set... what you write will either replace or be appended to the property list. This would be useful for role playing, combat simulation, and social scripts. For example, you could have: integer allied(key agent) { string race = llGetProp(agent,"race"); if(race == "human" || race == "vulcan") return TRUE; if(race == "borg" && llGetProp(agent,"hive_id") == "") return TRUE; // freed borg if(race == "ferengi" && ((integer)llGetProp(agent,"latinum")) <= 0) return TRUE; // poor ferengi return FALSE; }
|
|
Aster Lardner
Registered User
Join date: 14 Nov 2005
Posts: 72
|
04-12-2006 14:02
That's a good idea... Each tag would have a list of properties. That makes more sense.
The way see it, There'd be a profile tab for tags. It'd just be a big textbox. Normally you'd just type in your intrests like so: Furry, INFP, Dragons, Laptops. When you save it it would parse the text and enter your key in a database under the groups "Furry", "INFP", "Dragons", and "Laptops". When other people pull up your profile they could click on these keywords and pull up a list of all people with that keyword tag. It's kind of a simple way to form a club without making an official guild-like group.
I also think you should be able to add properties/qualifiers/and what not. A XXX{Vanilla, Kissing} type tag would be stored as two tags: XXX[Vanilla] and XXX[Kissing]. That way I could do a search for people who are into XXX and are Vanilla without pulling up people who just think it's a nifty flavor.
Geek Codes, Furry Codes, Goth Codes, and whatever could be entered as qualifiers to their code tags. While not readable, if LSL is implimented we could script various encoders & decoders as well as do specialized searches.
It would also be nice to have "Public" and "Private" tags-- that way you don't fill public profiles with coding jibberish. If LSL is implimented, you should be able to pull up a list of tags, thier privacy flags, and then a list of properties for each tag...
|
|
grumble Loudon
A Little bit a lion
Join date: 30 Nov 2005
Posts: 612
|
04-12-2006 14:40
How about key llRequestAgentData(key id, DATA_ABOUT) key llRequestAgentData(key id, DATA_INFO) key llRequestAgentData(key id, DATA_MYNOTES) key llRequestAgentData(key id, DATA_IWANTTO) key llRequestAgentData(key id, DATA_SKILLS)
This would get the text from the profile that is alreddy public and you can then define a standard way to parse it.
|
|
Argent Stonecutter
Emergency Mustelid
Join date: 20 Sep 2005
Posts: 20,263
|
04-12-2006 15:35
I honestly don't see why tags should automatically go in the profile. Let's suppose you have a group of people involved in a D&S role playing group, and they want to have a "bdsm_role" tag containing (say) "sub", "dom", or "switch"... there's no reason this should be something people might chance upon in the profile, but it should be accessible from a scripted object.
Perhaps an additional property flag, PROP_PUBLISHED, would put it into the profile.
|
|
Aster Lardner
Registered User
Join date: 14 Nov 2005
Posts: 72
|
04-14-2006 09:50
Yea, I was think about it and properties don't really need to be in the the profile. The only reason I thought they should be is because it seemed like flicker/del.ico.us/facebook-like tags were something Linden labs were already thinking about in the far future... and would probably be easier to get implimented if you tag on to something they're already intrested in. Also, I think everyone would probably like to be able to view/edit thier own tags, and a tab on the profile page would be the best place for that. People could get paranoid if properties can be stored like invisible "cookies." I mean, look at the hubub about people collecting keys. >.<
Scripting-wise, your idea makes the most sense though and is a hell of a lot cleaner.
|