Re: [opensource-dev] V2.X & V1.X support on the same machine
On Thu, 5 Aug 2010 20:57:54 -0400, Marc Adored wrote: > On Thu, Aug 5, 2010 at 8:43 PM, Bunny Halberd wrote: >> Am I accidently filtering part of this list? This is not the first >> message I've gotten that seems completely out of context... >> >> - Bunny > > I'm with you Bunny the last few messages haven't made hardly any sense > at all. I know it has something to do with some card games, MOAP and > apple but what do they all have in common and is it relevant to > opensource-dev? (not a personal reply to you: just my feelings on this) I'm fine with them. In the past months this mailing list has been filled with lots of messages that were much more off-topic (I argue these ones are actually in-topic, if a bit cryptic), AND those were full of hate. These ones seem full of passion, instead, and the list is not being overloaded. Have a look to Dzonatas'work. If you can, read sources as he suggested (I can't, unfortunately). By the way, one can check if she got all list messages through the archives, that can be found by following the links in the footer. Opensource Obscure ___ Policies and (un)subscribe information available here: http://wiki.secondlife.com/wiki/OpenSource-Dev Please read the policies before posting to keep unmoderated posting privileges
[opensource-dev] Testers requested for V2 patch
I've written a very simple patch and would like a few people to test and/or comment on it: http://jira.secondlife.com/browse/VWR-17801 This fixes a minor menu error in Viewer 2. Thanks, -jonathan ___ Policies and (un)subscribe information available here: http://wiki.secondlife.com/wiki/OpenSource-Dev Please read the policies before posting to keep unmoderated posting privileges
Re: [opensource-dev] V2.X & V1.X support on the same machine
Opensource Obscure wrote: > By the way, one can check if she got all list messages > through the archives, that can be found by following > the links in the footer. > > Opensource Obscure > I would also suggest to read Google's policy and term and conditions very carefully. If anybody can disagree, then I ask for your reply, but I think LL screwed over by themselves (not important to use who made who)... it is important to fix the issue. They've had an adult grid that is suppose to be fast, easy,... and fun. They've had an teen grid that is suppose to be ... easy... fast... clean? Where is the family grid? I wouldn't doubt Google had on their minds to someone increase LL's revenue by a billion US$ over time, yet I can see that doesn't even match their protocol right now. They could bring back gambling, banks, stock market, and so on... and just get rid of one idea that makes almost next dumbest nominate idea ever next to disposable baby plastic water bottles. Sincerely, ___ Life -- --- https://twitter.com/Dzonatas_Sol --- Web Development, Software Engineering, Virtual Reality, Consultant ___ Policies and (un)subscribe information available here: http://wiki.secondlife.com/wiki/OpenSource-Dev Please read the policies before posting to keep unmoderated posting privileges
[opensource-dev] Fixing the Assets
Here is the proposal, as a routine. The written logical explanation in English with normalized words defeats the purpose of the routine for every reason that supports it. "Got to put a face on it:" Store timestamp by UUID. Keep secondary UUID to XOR with every second. Doesn't matter if timestamp of UUID changes within that second, as long as one of the two changes. That's a new "second". Do that again for the new "minute" based on 60 new seconds. The hour is optional, as there are several more value to consider to make a new "hour". And so on, until you have decided on a new "timestamped UUID". Store the original assets by Asset UUID or new timestamped UUID. Don't transmit the original timestamp of the asset... only transmit the the newer created unique value. The client-side can then create assets by that newer value, which would then create its own timestamp on the client side. I think LL can figure out the rest... Save yourself! -- --- https://twitter.com/Dzonatas_Sol --- Web Development, Software Engineering, Virtual Reality, Consultant ___ Policies and (un)subscribe information available here: http://wiki.secondlife.com/wiki/OpenSource-Dev Please read the policies before posting to keep unmoderated posting privileges
Re: [opensource-dev] Fixing the Assets
If Linden Labs implements this much and Google thinks it is "clean", then maybe I'll smile again and show how to do folded execution... and how to earn the money. US open source "no-engine"ers aren't fools. We love magic, however. Dzonatas Sol wrote: > Here is the proposal, as a routine. The written logical explanation in > English with normalized words defeats the purpose of the routine for > every reason that supports it. > > "Got to put a face on it:" > > Store timestamp by UUID. > Keep secondary UUID to XOR with every second. > Doesn't matter if timestamp of UUID changes within that second, as > long as one of the two changes. > > That's a new "second". > > Do that again for the new "minute" based on 60 new seconds. > > The hour is optional, as there are several more value to consider to > make a new "hour". > > And so on, until you have decided on a new "timestamped UUID". > > Store the original assets by Asset UUID or new timestamped UUID. > > Don't transmit the original timestamp of the asset... only transmit > the the newer created unique value. > > The client-side can then create assets by that newer value, which > would then create its own timestamp on the client side. > > I think LL can figure out the rest... > > Save yourself! > -- --- https://twitter.com/Dzonatas_Sol --- Web Development, Software Engineering, Virtual Reality, Consultant ___ Policies and (un)subscribe information available here: http://wiki.secondlife.com/wiki/OpenSource-Dev Please read the policies before posting to keep unmoderated posting privileges
