The last snapshot for the Trust flag viewer was back on 2024-05-27. Does this mean you stopped taking snapshots, or perhaps it's some glitch you might not be aware of?
I stopped doing automated updates years ago, and only run it manually once in a while. This just means I hadn't thought about it for a while. I'm running a full re-check of all Flags now. It should be done in about 8 hours. Let me know if anything fails. 
Topic: LoyceV's (Personal) Trust Flag viewer [daily updates] (NOW IN DESCENDING ORDER) (Read 3902 times)
November 02, 2024, 05:02:32 AM
November 02, 2024, 04:54:23 AM
Hello LoyceV, Sorry for bumping this topic after a long time. The last snapshot for the Trust flag viewer was back on 2024-05-27. Does this mean you stopped taking snapshots, or perhaps it's some glitch you might not be aware of?
June 25, 2020, 09:39:40 AM
The weekly DT update is a good example of how an update each week is sufficient.
Good point, I can keep weekly snapshots. But for now, it's still not working correctly, and I haven't had the time to figure it out exactly. 
June 24, 2020, 08:41:35 PM
I now have hundreds of daily snapshots, so you can see who supported which Flag when. Does anyone even use that, or can I just keep at most monthly snapshots?
I think your question has been answered through a lack of an answer - I don't feel that people place that great an importance on who did what, when to the minute. The weekly DT update is a good example of how an update each week is sufficient. The only people who would need such information on a minute by minute basis are those either trying to garner support for or against a fresh flag.
The novelty wears off after a while.
June 08, 2020, 02:58:50 PM
My Trust Flag viewer is currently (a bit) broken, it doesn't update all Flags anymore. I need some time to fix this.
Considering the large number (around 2000) of Flags, I'll also stop scraping all Flags daily, and instead scrape the older Flags less often.
I'll update here when it works properly again.
Question: should I keep all older records? I now have hundreds of daily snapshots, so you can see who supported which Flag when. Does anyone even use that, or can I just keep at most monthly snapshots?
Considering the large number (around 2000) of Flags, I'll also stop scraping all Flags daily, and instead scrape the older Flags less often.
I'll update here when it works properly again.
Question: should I keep all older records? I now have hundreds of daily snapshots, so you can see who supported which Flag when. Does anyone even use that, or can I just keep at most monthly snapshots?
February 07, 2020, 02:21:22 PM
Bumping this 
Please review a few Flags once in a while, if you can spare the time. It doesn't matter whether or not you're on DT (that might change depending on how others value your judgement).
Once in a while something fails scraping: if the file size is out of order, just skip that one. I only leave them in for the navigation to keep working (and never bothered to build in a check). Please review a few Flags once in a while, if you can spare the time. It doesn't matter whether or not you're on DT (that might change depending on how others value your judgement). January 24, 2020, 01:52:41 AM
Improvement:
New: (Support | Oppose)
Because of Flag spammers, I've added quick links to (Support | Oppose) Flags.
Because of Flag spammers, I've added quick links to (Support | Oppose) Flags.
January 22, 2020, 10:47:27 AM
Make sense 😉
There you go, have it your way:New: Descending order
Starting January 22, 2020, my Trust Flag viewer is now in descending order (newest Flags first).
Starting January 22, 2020, my Trust Flag viewer is now in descending order (newest Flags first).
Allow me to use this opportunity to promote Add comments to Flags on LoyceV's Trust Flag viewer. Example:
Quote
2020-01-22 Wed 13.07h
source: loyce.club
*** Steamtyme commented: Flag lacks proper reference.
*** dragonvslinux commented: Corrected reference: https://bitcointalksearch.org/topic/m.52774268
884 Insufficient support. Lauda flagged dragonvslinux (type 1, see why). Supported by Lauda, TheUltraElite. Opposed by nutildah, eddie13, Last of the V8s, Steamtyme, Timelord2067, dragonvslinux.
The comments should be under the Flags, but I messed up the BBCode when I changed the order. This should be fixed in the next version. source: loyce.club
*** Steamtyme commented: Flag lacks proper reference.
*** dragonvslinux commented: Corrected reference: https://bitcointalksearch.org/topic/m.52774268
884 Insufficient support. Lauda flagged dragonvslinux (type 1, see why). Supported by Lauda, TheUltraElite. Opposed by nutildah, eddie13, Last of the V8s, Steamtyme, Timelord2067, dragonvslinux.
January 21, 2020, 07:55:25 AM
I don't mind scrolling down, but the page gets slower to load now.
Quote
Re: LoyceV's (Personal) Trust Flag viewer [daily updates]
Make sense 😉 January 21, 2020, 06:43:48 AM
I wonder what took a too long to have this in mind for you. 😉
I don't mind scrolling down, but the page gets slower to load now. January 21, 2020, 06:39:38 AM
A descending order will be nice. That way we can start looking from the latest flag.
I'll think about it when the list gets much longer. January 20, 2020, 01:53:41 AM
A descending order will be nice. That way we can start looking from the latest flag.
I'll think about it when the list gets much longer. December 30, 2019, 06:53:33 AM
I could be wrong but early today when I imported data from loyce.club, I felt the speed is lower than before.
I don't think the current hosting is slower. However, I do notice downloads start "slow", then gain speed a bit later. As if the servers are still negotiating how fast their connection is:Code:
wget -O /dev/null http://loyce.club/Merit/merit.all.txt
--2019-12-30 06:48:15-- http://loyce.club/Merit/merit.all.txt
Resolving loyce.club (loyce.club)... 44.230.10.13
Connecting to loyce.club (loyce.club)|44.230.10.13|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 13339707 (13M) [text/plain]
Saving to: '/dev/null'
100%[============================================================================================================================================================>] 13,339,707 8.46MB/s in 1.5s
2019-12-30 06:48:17 (8.46 MB/s) - '/dev/null' saved [13339707/13339707]
--2019-12-30 06:48:15-- http://loyce.club/Merit/merit.all.txt
Resolving loyce.club (loyce.club)... 44.230.10.13
Connecting to loyce.club (loyce.club)|44.230.10.13|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 13339707 (13M) [text/plain]
Saving to: '/dev/null'
100%[============================================================================================================================================================>] 13,339,707 8.46MB/s in 1.5s
2019-12-30 06:48:17 (8.46 MB/s) - '/dev/null' saved [13339707/13339707]
I did notice directories with 10,000 files load a bit slower, maybe because I switched from Nginx to Apache. I could install Nginx, but I'm still not even done with restoring all services.
December 30, 2019, 06:41:49 AM
I could be wrong but early today when I imported data from loyce.club, I felt the speed is lower than before. Is it exactly what happened with your club?
December 30, 2019, 06:12:35 AM
Due to server changes, the banned-status in my Trust Flag viewer wasn't working in the last few updates. It'll be fixed in the next update.
October 17, 2019, 09:27:31 AM
At the risk of talking to myself a bit:
I have suggested before that I can allow users to add comments to my Trust Flag viewer, but haven't had any feedback to this.
I made this:New: Add comments to Trust Flags
You can now add comments to my Trust Flag viewer, see Post here to add comments to LoyceV's Trust Flag viewer.
You can now add comments to my Trust Flag viewer, see Post here to add comments to LoyceV's Trust Flag viewer.
October 17, 2019, 08:26:14 AM
Thanks for the clarification...
Neither do I - in part the reason not to support the flag.
Quote
~ is a duplicate of a previous (still active) flag
I don't really get why LFC_Bitcoin uses my topic on scammer BetKing.io as a reference topic for a Flag on game-protect. October 17, 2019, 05:46:44 AM
It's quite likely other flags have non valid reference links.
When I wrote about Flags that don't have a valid Reference link, I meant "not valid" from a webbrowser's perspective: The link doesn't exist (anymore).The description on my Trust Flag viewer is better: "Reference topic does not exist".
Many Flags have a Reference link with invalid content, but I can't highlight those without doing it manually.
I have suggested before that I can allow users to add comments to my Trust Flag viewer, but haven't had any feedback to this.
Quote
~ is a duplicate of a previous (still active) flag
I don't really get why LFC_Bitcoin uses my topic on scammer BetKing.io as a reference topic for a Flag on game-protect. October 16, 2019, 09:18:01 PM
Update: I'm now highlighting all Flags that don't have a valid Reference link:
To reduce scraping, I won't re-check all Reference topics each day, so there it could take a while to update after a Reference topic gets trashed.
These Flags are currenly involved:
Reference topic does not exist:
...
To reduce scraping, I won't re-check all Reference topics each day, so there it could take a while to update after a Reference topic gets trashed.
These Flags are currenly involved:
Reference topic does not exist:
...
I've referenced in these two threads that the reference threads were either not created by the flag creator, or, do not reference to the person who is the topic of the flag (hence are not valid reference threads)
https://bitcointalksearch.org/topic/100-of-quicksellers-flags-are-false-5165940
https://bitcointalksearch.org/topic/lauda-creating-flags-against-random-people-linked-to-threads-not-related-5161689 <-- this thread needs updating as the person involved has recommenced creating flags against users, however the flag recipient usually aren't the subject of the thread in most cases.
It's quite likely other flags have non valid reference links.
*edit*
Have just recalled this flag is a duplicate of a previous (still active) flag - essentially double dipping / double jeopardy... The creator of the second flag has modified their OP that many times (and even references the first flag) bullying anyone [1] [2] who opposes the flag they created.
October 12, 2019, 08:44:20 AM
For the first time, Flags have been removed! They'll show in the next update.
I've changed the wording: instead of "No such flag", my Trust Flag viewer now shows "This Flag has been deleted by the Bitcointalk forum administration".Currently:
Quote
Jump to: