Key Size Limit

[flyoffacliff]

I know we are limited to 10 keys per forum. But isn't there also a limit of 4MB per key or something? How do we know how much space a key is using?

[flyoffacliff]

Bump

[Peter]

Limit is 4k. To check how much space a key is using, just check the length of it, as it will be a string.

[flyoffacliff]

Dec 20, 2012 18:11:51 GMT -8 Peter said:

Limit is 4k. To check how much space a key is using, just check the length of it, as it will be a string.

You mean 4KB, or 4MB?

How?

I don't really know any coding.

[Chris]

Dec 21, 2012 9:56:24 GMT -8 flyoffacliff said:

Dec 20, 2012 18:11:51 GMT -8 Peter said:

Limit is 4k. To check how much space a key is using, just check the length of it, as it will be a string.

You mean 4KB, or 4MB?

How?

I don't really know any coding.

4k. either 4000 or 4096. I'm not sure which.

As for checking, if you have the key, typically you could enter this in a script:

alert(proboards.plugin.key.get("PLUGIN KEY HERE").length);

I believe that's right. Honestly, if you're not coding, I wouldn't worry about it.

[blueshead]

Chris.. Let me ask you another question.. We are limited to 10 keys which may or not be in a plug in that we install..

So..If we get 10 keys, which you say are only 4kb.. That means we can only after that use plug ins with out keys?

Since the keys are so small.. And we don't have a choice about the plug ins having keys or not.. We kinda get screwed..

I understand limiting the size and how many plug ins you can use.. But with the keys only being 4kb..This makes no sense..

Basically according to this.. If Every Plug Developer added a key.. We could only use 10 plug ins regardless if we are under our plug in space limit..

[Chris]

Right, and so plugin developers need to be smart.

1) Use the yootil library which lets you store settings in localStorage. This is in compliance with the EU cookie law AND removes the need for a key.
2) Reuse keys across plugins by the same developer. That is, if data needs to be stored across multiple plugins, I will make my codes share a key.

But the size (4kb) has nothing to do with needing more keys. So that's why I said it's best to just ignore it.

[blueshead]

Dec 30, 2012 14:23:03 GMT -8 Chris said:

Right, and so plugin developers need to be smart.

1) Use the yootil library which lets you store settings in localStorage. This is in compliance with the EU cookie law AND removes the need for a key.
2) Reuse keys across plugins by the same developer. That is, if data needs to be stored across multiple plugins, I will make my codes share a key.

But the size (4kb) has nothing to do with needing more keys. So that's why I said it's best to just ignore it.

Ok.. This gets Interesting.. I did a few weeks ago install the yootil library..and moved it up to the top of my plugs ins as said..

Library for plugin developers.

Important:

Move this above any plugins that require it.

If you are unsure, please visit support.proboards.com and ask.

Does by doing this I can ignore the 10 key limit?

And as I pointed out.. Why should we the Customer....Be penalized because of Keys? We have no choice if the plug in comes with a key..

[Chris]

Dec 30, 2012 15:00:37 GMT -8 blueshead said:

Dec 30, 2012 14:23:03 GMT -8 Chris said:

Right, and so plugin developers need to be smart.

1) Use the yootil library which lets you store settings in localStorage. This is in compliance with the EU cookie law AND removes the need for a key.
2) Reuse keys across plugins by the same developer. That is, if data needs to be stored across multiple plugins, I will make my codes share a key.

But the size (4kb) has nothing to do with needing more keys. So that's why I said it's best to just ignore it.

Ok.. This gets Interesting.. I did a few weeks ago install the yootil library..and moved it up to the top of my plugs ins as said..

Library for plugin developers.

Important:

Move this above any plugins that require it.

If you are unsure, please visit support.proboards.com and ask.

Does by doing this I can ignore the 10 key limit?

No. But, if a developer is being smart, they won't use a key for something trivial. If they need a key, they will have to use one. But this prevents them from wasting keys. It does not automatically improve anything; the developers themselves need to make sure they use Yootil.

[blueshead]

This is not good for us.. If every developer used a key.. We are limited to 10 plug ins unless we pay more..

[Chris]

Dec 30, 2012 15:13:20 GMT -8 blueshead said:

This is not good for us.. If every developer used a key.. We are limited to 10 plug ins unless we pay more..

Most plugins don't need keys though.

[blueshead]

Dec 30, 2012 15:25:04 GMT -8 Chris said:

Dec 30, 2012 15:13:20 GMT -8 blueshead said:

This is not good for us.. If every developer used a key.. We are limited to 10 plug ins unless we pay more..

Most plugins don't need keys though.

Yes.. But will they know that by using a key they will impact proboards customers?  Will you tell them this?

[Chris]

Dec 30, 2012 15:35:05 GMT -8 blueshead said:

Dec 30, 2012 15:25:04 GMT -8 Chris said:

Most plugins don't need keys though.

Yes.. But will they have an option to use a key without knowing how it will affect us?

I'm not sure what you mean... if a plugin requires a key, you'll have to use a key then. Plugins won't operate without keys.

If you don't want the key, then you'll need to just remove the plugin.

[blueshead]

I meant can you let developers of plug ins know if that if they use a key.. It will limit us.. The users, on how many plug ins we can use...

Also you just said this..  

Plugins won't operate without keys.

A lot of the plug ins I am trying do not have keys..

Basically it boils down to we can only use up to 10 plug ins with keys.. Not good.. Why should keys matter to us?  It should simply be about the size of the plug in and the space we can use..

[Chris]

Dec 30, 2012 16:12:40 GMT -8 blueshead said:

I meant can you let developers of plug ins know if that if they use a key.. It will limit us.. The users, on how many plug ins we can use...

Also you just said this..  

Plugins won't operate without keys.

A lot of the plug ins I am trying do not have keys..

Basically it boils down to we can only use up to 10 plug ins with keys.. Not good.. Why should keys matter to us?  It should simply be about the size of the plug in and the space we can use..

I think there's a misunderstanding on what keys are used for here.

So, plugins use keys to store data. For example, an RPG plugin would store the user's stats in a single key. So that plugin needs one. When I said "can not operate without keys," that means that RPG plugin can't be made without using a key... nowhere to store the data!

But not every plugin needs to store data. For example, in v4.5 terms, a plugin that removes the last post column on the main page... it doesn't need to store data, so it won't need a key.

Now, developers should not be arbitrarily using keys... it makes no sense to do that! Instead, they should only use them when absolutely necessary. For example, when I said you could have a setting? That shouldn't use a key. That should be stored in localStorage via yootil, thus preventing it from needing a key and wasting space.

Hope that clears some things up. Also, it's better for them to allot us keys than space... because the space is per-thread or per-user, the more active forum, the less space you'd have! By limiting the number of keys, we instead get more space for an active forum.