inherit
217348
0
Jul 27, 2022 7:26:44 GMT -8
Lynx
5,780
January 2015
msg
|
Post by Lynx on Mar 28, 2016 20:09:54 GMT -8
Thanks for all the info on this but there is no way to make it a set of newest members unless u make it just the Newest Member As P̌̓aͧś̀t̀u͒le͆o͂2̀3̃̓ stated above, it will end up being newest member s - plural. Once the plugin gets installed, it will have to populate the key - of which it will do as each member / new registrant logs on. It will get their user ID and the date they registered. The plugin cannot do this until a person logs on, as it has no way to go through that database. Once a member logs on, they get added, thus adding to the population of the database for it to sort. Each person will only get added once, but in order for me to legitimately set the key, there will be a popup letting them know their registration date has been added - to which all they do is click OK and they won't see the popup again. You will be able to set this for however many recent members you want to show (from 1 to 100 - at least, initially to 100). So, if you set it for 5, then there will need to be at least 5 members / new registrants since the plugin was installed to have your list of 5. The "accuracy" I was referring to is this: If you have 5 veteran members log on as the first 5 to populate the list, they will be the ones who show as "most recent" - until someone else logs on with a newer registration date. I can only grab a person's registration date when that person logs on - I can't just grab all of them from 1 logon. If you've got any questions, please feel free to ask.
|
|
inherit
201984
0
Sept 11, 2023 1:23:07 GMT -8
P̌̓aͧś̀t̀u͒le͆o͂2̀3̃̓
Using My Talents Elsewhere
3,314
November 2013
pastuleo23
|
Post by P̌̓aͧś̀t̀u͒le͆o͂2̀3̃̓ on Mar 28, 2016 21:24:06 GMT -8
I also want to note that if you are adding recent members via popup and push. You can calculate the oldest registered date in the key and only update the key when you get a "newer" member. Therefore the popup won't even show for most users. I'm saying don't append every member by default. Also there might be an instance where there are 6 or 7 members pushed to the key at once. That's fine if you just display the first 5 in the array. And next time you add a new member, just pop the extras to keep the data amount in the key low. Unless you want to manage the entire database of members and names with no apparent purpose. (which is what will happen if each member saves to the key) Right now, I'm just looking for it to work properly - and to keep my head from exploding from trying to figure out how to do everything at once. Once I've got it working, then I can look into having it check for oldest registration date - that's what updates are for. Right? There will, initially, be a limit of 50 stored. Why so high? Only until enough people use it and give feedback on how many they set it for (5, 10, 12, ...) so I can get a fairly accurate idea of what's being used as a "maximum". Once I know no one is going over a certain amount, then I can drop the max limit down. I'v seen some places that actually list their most 20 recent members - so I don't want to have it too small to start with. Also, since this will be able to be placed where the owner wants it, it could conceivably end up in Brian's sidebar redux and have it list the most recent 10, 15, 20 or more recent members - especially for forums that may be getting new members frequently. If they got 10 new members in 1 day, and the max was only at 5, the "first" 5 would no longer "count" ... so to speak. I'm going for a big picture first, then deal with narrowing it down - if that makes sense. I have no intentions of managing the entire database - that would probably slow the plugin down if there were thousands of entries it had to check first. Since, I believe, a super key can hold 32kB of data, and (going really high) 6 bytes for user ID (of which is possible here on support) and 10 (I think) bytes for the timestamp, even if I go on a value of 20 bytes per entry, setting an initial max of 50, or even 100, would keep it well clear of key limit. And with today's speeds, even 100 entries won't take long to process. Doing it that way would maintain flexibility for the end user to change the number of most recent at any time - up or down - for various needs, and still have a small database that would be current (once populated). Just my thoughts on it. How are you going to manage 50 members max without accidentally overwriting the oldest registration? Perhaps im confused. Also you can cut data by cutting off the last three 0s of the timestamp and adding them back at runtime. However in this case would not be necessary
|
|
inherit
217348
0
Jul 27, 2022 7:26:44 GMT -8
Lynx
5,780
January 2015
msg
|
Post by Lynx on Mar 28, 2016 21:29:50 GMT -8
Via a sort so the oldest registration (populated) would be at index 0 - the sort would be done before a shift was done to remove that entry to make room for the push.
|
|
inherit
201984
0
Sept 11, 2023 1:23:07 GMT -8
P̌̓aͧś̀t̀u͒le͆o͂2̀3̃̓
Using My Talents Elsewhere
3,314
November 2013
pastuleo23
|
Post by P̌̓aͧś̀t̀u͒le͆o͂2̀3̃̓ on Mar 28, 2016 23:53:38 GMT -8
Via a sort so the oldest registration (populated) would be at index 0 - the sort would be done before a shift was done to remove that entry to make room for the push. That would be cool if it existed. You can sort the local copy of the key all you want. But you cannot sort the key on the server. Unless you just set the key which overwrites everything Which would be bad since a lot of users will be accessing the same data at once. Then again, unless I'm still missing something?
|
|
inherit
217348
0
Jul 27, 2022 7:26:44 GMT -8
Lynx
5,780
January 2015
msg
|
Post by Lynx on Mar 29, 2016 10:49:54 GMT -8
Okay. I concede defeat. If anyone else wants this - go for it.
|
|
inherit
201984
0
Sept 11, 2023 1:23:07 GMT -8
P̌̓aͧś̀t̀u͒le͆o͂2̀3̃̓
Using My Talents Elsewhere
3,314
November 2013
pastuleo23
|
Post by P̌̓aͧś̀t̀u͒le͆o͂2̀3̃̓ on Mar 29, 2016 15:20:28 GMT -8
Okay. I concede defeat. If anyone else wants this - go for it. Of all the keys. The forum key is NOT the one you want to tackle.
|
|
inherit
217348
0
Jul 27, 2022 7:26:44 GMT -8
Lynx
5,780
January 2015
msg
|
Post by Lynx on Mar 29, 2016 15:34:20 GMT -8
Of all the keys. The forum key is NOT the one you want to tackle. That is easily remedied - I'll just stick to keyless plugins.
|
|
inherit
201984
0
Sept 11, 2023 1:23:07 GMT -8
P̌̓aͧś̀t̀u͒le͆o͂2̀3̃̓
Using My Talents Elsewhere
3,314
November 2013
pastuleo23
|
Post by P̌̓aͧś̀t̀u͒le͆o͂2̀3̃̓ on Mar 29, 2016 16:41:13 GMT -8
Of all the keys. The forum key is NOT the one you want to tackle. That is easily remedied - I'll just stick to keyless plugins. You just need to update one of your plugins to use a private user key instead of using cookies and storage.
|
|
inherit
217348
0
Jul 27, 2022 7:26:44 GMT -8
Lynx
5,780
January 2015
msg
|
Post by Lynx on Mar 29, 2016 17:14:25 GMT -8
That is easily remedied - I'll just stick to keyless plugins. You just need to update one of your plugins to use a private user key instead of using cookies and storage. The only plugin that even uses storage is also the least-used plugin. Given that, it's probably not worth my time (or anyone else's) to update it. There is simply no demand for it - just take a look at its support thread.
|
|