Re: [opensource-dev] Viewer changes for Premium changes

2020-02-27 Thread hw
So after stealing my money you make stuff more expensive for everyone and try to either get rid of the users that aren't signed up or force them to sign up so that you can steal their money, too. How about you finally fix other problems like the block list not being loaded and making use of

Re: [opensource-dev] Viewer changes for Premium changes

2020-02-27 Thread Henri Beauchamp
On Thu, 27 Feb 2020 12:44:31 -0800, Brian McGroarty wrote: > All else aside: In the future, if you notice something on aditi adversely > affects your viewer, please don't be shy about raising it on this list or > in a JIRA. An early heads up may be helpful to other viewer devs, or it > will make

Re: [opensource-dev] Viewer changes for Premium changes

2020-02-27 Thread Brian McGroarty
On Tue, Feb 25, 2020 at 12:17 PM Henri Beauchamp wrote: > Sadly, you used an LLSD sub-array into the LLSD map, and "old" viewers > (i.e. all viewers not based on LL's v3 viewer code for the XML RPC part) > do not know what to do with such an array (they can only deal with simple > key/value

Re: [opensource-dev] Viewer changes for Premium changes

2020-02-27 Thread Henri Beauchamp
On Thu, 27 Feb 2020 14:39:10 -0500, Oz Linden (Scott Lawrence) wrote: > That protocol works (and from time to time we employ it) when the change > is one that can be compatible, but that's not the case here. The account > levels are not an optional thing, and there never was any way we could >

Re: [opensource-dev] Viewer changes for Premium changes

2020-02-27 Thread Oz Linden (Scott Lawrence)
On 2020-02-27 12:37 , Henri Beauchamp wrote: 2.- Had you*simply* (this is really trivial, since this is how the viewers and login server already work !) respected the normal protocol, not sending any "account_level_benefits" related info to the viewers not requesting that option

Re: [opensource-dev] Viewer changes for Premium changes

2020-02-27 Thread Henri Beauchamp
On Thu, 27 Feb 2020 11:10:19 -0500, Oz Linden (Scott Lawrence) wrote: > The definition of LLSD and our open source implementations of it have > always included the possibility of arbitrary nesting in arrays and maps > (and we use it extensively internally without problems). We're not able > to

Re: [opensource-dev] Viewer changes for Premium changes

2020-02-27 Thread Oz Linden (Scott Lawrence)
On 2020-02-27 11:26 , Nathaniel Prugh wrote: Can you show me the links to announcement of new premium. Features like the plus? We have not yet announced the specific changes, just that some are coming including the new Premium Plus level.  Those should be coming pretty soon, but a search

Re: [opensource-dev] Viewer changes for Premium changes

2020-02-27 Thread Nathaniel Prugh
Sent from my iPhone On Feb 27, 2020, at 8:14 AM, Oz Linden (Scott Lawrence) wrote:  On 2020-02-25 16:10 , Nathaniel Prugh wrote: Where is announcement of those features in sl blog? So we know what new stuff coming soon etc? [..] The fact that we're making changes to Premium and

Re: [opensource-dev] Viewer changes for Premium changes

2020-02-27 Thread Oz Linden (Scott Lawrence)
On 2020-02-25 16:10 , Nathaniel Prugh wrote: Where is announcement of those features in sl blog? So we know what new stuff coming soon etc? We don't normally use the blogs for communicating code changes; that's what this list is for. The fact that we're making changes to Premium and

Re: [opensource-dev] Viewer changes for Premium changes

2020-02-27 Thread Oz Linden (Scott Lawrence)
On 2020-02-27 08:21 , Cinder Roxley wrote: On February 25, 2020 at 2:17:16 PM, Henri Beauchamp (sl...@hotmail.com ) wrote: On Tue, 25 Feb 2020 10:48:03 -0500, Oz Linden (Scott Lawrence) wrote: > Why are there changes? > > The viewer currently has some messages and

Re: [opensource-dev] Viewer changes for Premium changes

2020-02-27 Thread Cinder Roxley
On February 25, 2020 at 2:17:16 PM, Henri Beauchamp (sl...@hotmail.com) wrote: On Tue, 25 Feb 2020 10:48:03 -0500, Oz Linden (Scott Lawrence) wrote: > *As we mentioned at the last Third Party Viewer meeting, Oh yes, those meetings a non-English speaking developer cannot follow because they are