Template talk:SL-hCard
I think there might be ongoing issues about including the uuid in the template, given that providing it to all users could promote serious abuse. Whilst leaving it at a default value of 00000000-0000-0000-0000-000000000000 is certainly one option, complete removal from the template might be a better one. --Alison Wheels 07:37, 9 January 2007 (PST)
- I removed it, uploading a picture is maybe the better way as long as the Wiki-configuration is not changed. But using the UUID would be the easier way. --Anders Nordberg 08:31, 9 January 2007 (PST)
- If you check the SL History Wiki, you'll see it works perfectly fine. No idea why it doesn't work here.
- The way the SLOpenID avatar caching thing works (the little project I made as a workaround for not being able to resize external images in the wikipedia) setting the default to NULL_KEY wouldn't really work. You'd just have (in theory, once I get around to it) the MISSING IMAGE texture displayed. Which wouldn't be nice :-P
- The other reason, btw, that the caching service was created was because of Linden Lab's odd decision with regards to the size and aspect ratio of the web-based avatar profile photo.
- SignpostMarv Martin 10:09, 9 January 2007 (PST)
- See Bug 2. I IMed Pathfinder if he maybe activate external images. No answer yet, until then I put the slopenid-link back into the template --Anders Nordberg 11:20, 9 January 2007 (PST)
- My issue wasn't that the uuid wasn't picking up the image, but that by making public an avatar's uuid it would make it very simple for someone to utilise some greifing LSL code directed at that avatar. --Alison Wheels 13:33, 9 January 2007 (PST)
- Hopefully it'll soon be a optional value without messing up the profile. But anyways, the UUID isn't a big secret but I agree it should be treated as optional and personal data--Anders Nordberg 14:02, 9 January 2007 (PST)
- That's what the ParserFunctions are needed for :-)
- Do bear in mind that there won't be a way to automatically fetch the UUID unless Linden Lab provide one.
- There is little or no danger in your UUID being accessible
- Chances are, your UUID is already available to the public through W-Hat's name2key database
- SignpostMarv Martin 14:09, 9 January 2007 (PST)
- My issue wasn't that the uuid wasn't picking up the image, but that by making public an avatar's uuid it would make it very simple for someone to utilise some greifing LSL code directed at that avatar. --Alison Wheels 13:33, 9 January 2007 (PST)
- See Bug 2. I IMed Pathfinder if he maybe activate external images. No answer yet, until then I put the slopenid-link back into the template --Anders Nordberg 11:20, 9 January 2007 (PST)