Update:
Reload the page in about an hour to use the top-navigation-bar.
The easiest way to find the right profile, is through BPIP. For instance, for mine, go to Profile for LoyceV - BPIP.org, then click Trust list viewer for: LoyceV.
Topic: [130 weeks] [Updated Jul 10] LoyceV's Trust list viewer - Create your own! - page 21. (Read 23583 times)
February 29, 2020, 03:50:35 AM
February 22, 2020, 03:35:09 AM
Update:
Give it an hour for the top-navigation-bar to show up, and ~7 hours to completely update navigation for older weeks.
Give it an hour for the top-navigation-bar to show up, and ~7 hours to completely update navigation for older weeks.
February 15, 2020, 02:16:39 AM
This update is not ready yet:
But I have plans today, and didn't want to keep you guys waiting for your Saturday morning newspaper. If all goes well, the above link will work in about an hour.
The top navigation bar should be updated in the hours after that. If it doesn't work, complain to LoyceMobile, who can't help you at all
But I have plans today, and didn't want to keep you guys waiting for your Saturday morning newspaper. If all goes well, the above link will work in about an hour.
The top navigation bar should be updated in the hours after that. If it doesn't work, complain to LoyceMobile, who can't help you at all
February 08, 2020, 03:07:13 AM
I think you mistyped or forgot to change something.
You caught a rare moment: I accidentally ran my update too early (before theymos' data dump), so it used last week's data and (for the first time) used my fully automated update. So I removed the 2020-02-08_Sat_01.13h from the server again, but forgot about bots using latestversion.txt.Update:
It'll take about 1 hour to update the top-navigation bar for this week, and from there my update will work backwards updating the navigation for previous weeks. This will take about 7 hours. Until then, if the latest page (week 56) isn't available yet: go to week 56 first, and continue from there.
February 08, 2020, 02:52:19 AM
Hi @LoyceV, I found some minor problems here. As I told you that I am playing to code some bot based on your Trust list viewer, I just recently discovered this.
But in your index here: http://loyce.club/trust/
The latest one is 2020-02-01_Sat_05.15h/.
The path 2020-02-08_Sat_01.13h/ not yet existing.
I think you mistyped or forgot to change something.
Code:
http://loyce.club/trust/latestversion.txt
[b]content[/b] http://loyce.club/trust/2020-02-08_Sat_01.13h/
But in your index here: http://loyce.club/trust/
The latest one is 2020-02-01_Sat_05.15h/.
The path 2020-02-08_Sat_01.13h/ not yet existing.
I think you mistyped or forgot to change something.
February 01, 2020, 05:57:22 AM
I may not have explained myself properly, what I was meaning is when I'm looking at other people's trust pages, it'd be nice to see at a glance who the black-banned UID's are that either support or oppose any given user.
I got what you meant 
I just don't think it's worth adding.I found a bug:
Quote
Trust list for: SlipstreamStore (Trust: awaiting update) (0 Merit earned) (Trust list) (BPIP) (created 2020-02-01_Sat_05.15h)
Back to index
SlipstreamStore Trusts these users' judgement:
-
SlipstreamStore Distrusts these users' judgement:
-
SlipstreamStore's judgement is Trusted by:
-
~SlipstreamStore's judgement is Distrusted by:
-
Source: LoyceV's Trust list viewer.
Get your own Trust list in BBCode at loyce.club/trust.
Back to index
SlipstreamStore Trusts these users' judgement:
-
SlipstreamStore Distrusts these users' judgement:
-
SlipstreamStore's judgement is Trusted by:
-
~SlipstreamStore's judgement is Distrusted by:
-
Source: LoyceV's Trust list viewer.
Get your own Trust list in BBCode at loyce.club/trust.
From the data dump:
Code:
SlipstreamStore->theslimmyguy
It's a Newbie without posts, so I'm not going to fix this now. I've added an alert in case this happens again in the future.
February 01, 2020, 05:40:54 AM
I may not have explained myself properly, what I was meaning is when I'm looking at other people's trust pages, it'd be nice to see at a glance who the black-banned UID's are that either support or oppose any given user.
Thanks for reading.
Thanks for reading.
February 01, 2020, 03:36:31 AM
I don't know how heavily your site is used, but my guess is 95%+ of your HTML files are never accessed by anyone. If someone accesses a particular page n times, your server would need to generate the HTML n times.
I know I should switch to some database, and it's been suggested many times, but I simply don't have the time to learn how to do it and change everything. I don't really mind the 6 hours computation time, because it doesn't take much of my time. Currently, my Merit data analysis takes much more processing time, and that would be the next thing to make more manageable, but there too, I need the time.Meanwhile, I just started another project dealing with 50 million files, for which I'm taking a slightly different approach. And I have another project I want to start. It would probably be good to start using a database at least for new projects, but realistically, it probably won't happen.
Let's see how long it takes for the navigation bar to update 
It's done already, not bad The previous weeks will be updated in the coming hours. February 01, 2020, 03:08:19 AM
I've finished re-writing the code for the top-navigation-bar. It now "only" takes 6 hours to update instead of 2 days, and from now on the required processing power only increases at a linear instead of exponential rate.
This is much longer than it should. You should consider using jinja templates versus having millions of individual files, each with their own HTML. This would result in your server/computer generating the HTML at the time a user accesses a page instead of when you update your data. It would also mean you can update your data ~instantly. I don't know how heavily your site is used, but my guess is 95%+ of your HTML files are never accessed by anyone. If someone accesses a particular page n times, your server would need to generate the HTML n times. I think most likely, this will result in total less processing time, but even if not the case, the computational power required to generate one HTML page is nominal, so you will likely not ever have a backlog of things to compute.
February 01, 2020, 02:29:33 AM
Apologies if this has been asked before, is there any chance those users who have been black-baned from voting be shown in a different colour such as grey please?
My Trust list viewer isn't meant to see DT1-votes, so I'm not going to add a blacklist for DT1-voting.It is included though on my DT1-election: Rank up pipeline: All known blacklisted users don't count for voting (see that topic for the list).
Let's see how long it takes for the navigation bar to update
February 01, 2020, 12:02:22 AM
Apologies if this has been asked before, is there any chance those users who have been black-baned from voting be shown in a different colour such as grey please?
Some of the H8 conglomerate of shill/sockpuppets are on the list as trusting me, but given their votes are meaningless, can they be greyed out if possible? (Even if their profile is clicked on so it doesn't turn purple).
Thanks.
Some of the H8 conglomerate of shill/sockpuppets are on the list as trusting me, but given their votes are meaningless, can they be greyed out if possible? (Even if their profile is clicked on so it doesn't turn purple).
Thanks.
January 29, 2020, 06:37:48 AM
I've finished re-writing the code for the top-navigation-bar. It now "only" takes 6 hours to update instead of 2 days, and from now on the required processing power only increases at a linear instead of exponential rate.
Out of this 6 hours, 2 hours is for updating the newest version, the remaining 4 hours is for updating the older weeks. This should make it easier to quickly browse the latest Trust list viewer.
It's kind of a dirty code now, so please let me know if anything goes wrong with the navigation bar. So far, I haven't found any bugs.
Out of this 6 hours, 2 hours is for updating the newest version, the remaining 4 hours is for updating the older weeks. This should make it easier to quickly browse the latest Trust list viewer.
It's kind of a dirty code now, so please let me know if anything goes wrong with the navigation bar. So far, I haven't found any bugs.
January 25, 2020, 08:04:35 AM
Looks like everyone's favourite feline is back in the game.
January 25, 2020, 06:46:32 AM
Update:
It was updated hours ago, but I forgot to post here.
I'm working on improving the performance of updating the navigation bar on top. This has been on my Todo since I created it, and every week it takes exponentially more processing power to complete. I worked on this past week, but needed this week's new data for further testing. If all goes well, next week the navigation bar should be updated on Saturday morning.
It was updated hours ago, but I forgot to post here.
I'm working on improving the performance of updating the navigation bar on top. This has been on my Todo since I created it, and every week it takes exponentially more processing power to complete. I worked on this past week, but needed this week's new data for further testing. If all goes well, next week the navigation bar should be updated on Saturday morning.
January 18, 2020, 03:19:29 AM
Update:
I expect the navigation bar at the top to be updated either Sunday evening or Monday morning. Until then, you'll have to navigate to the above URL because you can't go to the last page from older pages (I noticed the update is sometimes overlooked because of this).
I now have a full year of Trust list history
I noticed a minor inaccuracy: one username wasn't on my DT1-list because of a name change. This problem existed last week already.
I'm not going to update this now, it'll be fixed next week.
I expect the navigation bar at the top to be updated either Sunday evening or Monday morning. Until then, you'll have to navigate to the above URL because you can't go to the last page from older pages (I noticed the update is sometimes overlooked because of this).
I now have a full year of Trust list history
I noticed a minor inaccuracy: one username wasn't on my DT1-list because of a name change. This problem existed last week already.
I'm not going to update this now, it'll be fixed next week.
January 15, 2020, 10:31:30 AM
My only problem is that the squiggly ("~") at the beginning of the username is used in the trustlist maintenance to indicate distrust of a member, so in that regard, it seems potentially confusing to the system to be using that squiggly.. at least in the beginning of the username...that seems to be why TMAN is redflagging ~DefaultTrust. Another reason, of course, is that sometimes members will bolster their trustlist by either including or excluding defaulttrust from their trust list, so having that "~DefaultTrust" as a username could inadvertently cause members to trust that member when they had not intended to do so.
It is very simple:
Excluding or including account ~DefaultTrust won't do anything to "default trust", however, I won't recommend including them, your trust network page will freeze because of things mentioned by LoyceV.
January 14, 2020, 12:33:27 PM
Historical note-
The squiggle is called a tilde, and it comes from the Medieval Latin word titulus. This means "stroke over an abridged word to indicate missing letters". Find out more here - https://www.etymonline.com/word/tilde
Stroke over an abridged poster to indicate missing content sounds about right to me.
The squiggle is called a tilde, and it comes from the Medieval Latin word titulus. This means "stroke over an abridged word to indicate missing letters". Find out more here - https://www.etymonline.com/word/tilde
Stroke over an abridged poster to indicate missing content sounds about right to me.
January 14, 2020, 12:31:03 PM
Kind reminder and request: please stay on topic in my topic
I don't mind someone spamming his own Trust list, as long as he doesn't pollute the rest.
~DefaultTrust's Trust list now looks like this:
For new usernames, I think ~ just slipped through. But there's not really a problem, I just tested it, and adding "~DefaultTrust" to your Trust list means excluding DefaultTrust, and doesn't mean including ~DefaultTrust.
To exclude ~DefaultTrust, use:
LoyceV add this: show the raw Trust list for blacklisted users, this shouldn't be a loophole to hide their Trust list from my viewer!
This is done I don't mind someone spamming his own Trust list, as long as he doesn't pollute the rest.~DefaultTrust's Trust list now looks like this:
Couldn't the forum software disallow the creation of usernames with such character, at least minimally as the first character? Anyone know?
I know it got more restricted at some point, some older usernames have much weirder characters than "~" in them. It's a pain to deal with, but since the username is used to login, it can't just be changed either.For new usernames, I think ~ just slipped through. But there's not really a problem, I just tested it, and adding "~DefaultTrust" to your Trust list means excluding DefaultTrust, and doesn't mean including ~DefaultTrust.
To exclude ~DefaultTrust, use:
Code:
~~DefaultTrust
The only reason I haven't excluded him yet is because he's not important enough. I don't think he'll ever reach DT2, so his Trust list abuse is not a problem. 
January 14, 2020, 12:24:52 PM
I may still be a newbie at heart but just curious tho
I suggest you read about trust before you comment.
the user set up the name as a way to game the system - trying to get the whole of default trust excluded from the trust list of anyone who added that user to their trust list
the user did this intentionally to act in a nefarious manner
please read up about it all then come back and apologise to me
thanks
January 14, 2020, 12:20:07 PM
do you have a trust list?
Not yet
do you know how default trust works?
Not really rocket science. I can say I have a slight grasp of what's happening and why (or I may be delusional, I have been known to be wrong before)
Still... what does default trust, trust network, depth, inclusions, exclusions, DT user changes etc have to do with NEGATIVE FEEDBACK FOR THE GUY'S USERNAME ?
I may still be a newbie at heart but just curious tho
The trust system will not be fooled by such a pity excuse for "grey" hacking.
... then come back and apologise to me
As I mentioned before, I have been known to be wrong before, so if I really am in this case and the root of all this is nefarious and not curiosity, as I assume, then will surely do !
Jump to: