[BPIP] Bitcointalk Public Information Project [Back in Action]

[logfiles]

I always thought that when a user is Nuked, this is similar to someone being permanently banned except that the whole post history is wiped off

Danielplease1 appears to have been nuked according to the modlog

Nuke user: N/A in topic #0 by member #3582292

But it's like BPIP.org does not record this type of ban. Is it bug?
https://bpip.org/Profile?id=3582292

[1714201894]

1714201894

[1714201894]

1714201894

[LoyceV]

I always thought that when a user is Nuked, this is similar to someone being permanently banned except that the whole post history is wiped off

Correct.

But it's like BPIP.org does not record this type of ban. Is it bug?

My guess: BPIP hasn't scraped modlog yet, and this user was Nuked only recently. If you check someone from the bottom of modlog, BPIP shows the profile was Nuked.

[ibminer]

But it's like BPIP.org does not record this type of ban. Is it bug?

Thank you.

My guess: BPIP hasn't scraped modlog yet, and this user was Nuked only recently. If you check someone from the bottom of modlog, BPIP shows the profile was Nuked.

I thought the same thing initially, but the modlog should normally be getting read every ~2-3 minutes, it looks like BPIP's modlog stopped updating on October 6th 21:24. Not quite sure why yet, but once it is corrected, it should catch everything back up.

[suchmoon]

I thought the same thing initially, but the modlog should normally be getting read every ~2-3 minutes, it looks like BPIP's modlog stopped updating on October 6th 21:24. Not quite sure why yet, but once it is corrected, it should catch everything back up.

Should be ok now. There was a thread with the same title that was deleted twice. This shouldn't be a problem since there were two different thread IDs. But for some reason the thread ID got truncated - I have to look into why. So both entries ended up like this:

"Prime-exchange.ru - oбмeнный пyнкт элeктpoнныx вaлют in topic #546"

And that's a problem because the parser gets confused and doesn't find where the new (since last parse) entries begin in the modlog.

I've changed it to ignore the thread deletes when it's looking for new entries. It's already ignoring post deletes because those are obviously not unique. Now it will re-parse everything back to the last nuke or ban. Should be more reliable. Probably not 100% - technically it's possible for someone to get banned twice in one week albeit very unlikely. I might need to add something like checking 3 consecutive entries instead of relying on one entry.

[paid2]

Bpip.org is down from my side

I tried to access it with Firefox and Chromium, same issue.

[ibminer]

Bpip.org is down from my side

I tried to access it with Firefox and Chromium, same issue.

All looks good from here, not seeing any issues. Did you receive an error?

[paid2]

All looks good from here, not seeing any issues. Did you receive an error?

No, nothing in particular, just that "this website is not reachable".

I've just tested it again and it's just loading endlessly. Still not working here, I will try with a VPN later to check


--EDIT--

Strange, still looks good for me. You could try a traceroute (or tracert) to bpip.org to see where the hops stop, they'll stop before reaching bpip.org due to firewalls or filters (under normal conditions), but it can sometimes give an idea how far the packets are getting. (assuming they are being dropped somewhere...)

Thank you ! I haven't even had time to test with traceroute, it's working normally again right now.

[ibminer]

No, nothing in particular, just that "this website is not reachable".

I've just tested it again and it's just loading endlessly. Still not working here, I will try with a VPN later to check

Strange, still looks good for me. You could try a traceroute (or tracert) to bpip.org to see where the hops stop, they'll stop before reaching bpip.org due to firewalls or filters (under normal conditions), but it can sometimes give an idea how far the packets are getting. (assuming they are being dropped somewhere...)

[logfiles]

I believe there are some bugs and inaccuracies with the DT Change log

First, I see some invisible member was getting selected into DT1


And then, I was offline for most part of last month, I never touched my trust list and then I see this

11/1/2023 9:45:18 PM    DT2 selection    logfiles DT2 no longer trusts 1miau DT2

11/1/2023 9:45:18 PM    DT2 selection    logfiles DT2 no longer trusts icopress DT2

My trust list hasn't been touched for a while - https://loyce.club/trust/2023-10-28_Sat_05.07h/1247226.html

This could mean it didn't happen to me alone, there could be some more incorrect changes in the log that we think.

[examplens]

And then, I was offline for most part of last month, I never touched my trust list and then I see this

11/1/2023 9:45:18 PM    DT2 selection    logfiles DT2 no longer trusts 1miau DT2

11/1/2023 9:45:18 PM    DT2 selection    logfiles DT2 no longer trusts icopress DT2

My trust list hasn't been touched for a while - https://loyce.club/trust/2023-10-28_Sat_05.07h/1247226.html

This could mean it didn't happen to me alone, there could be some more incorrect changes in the log that we think.

If I understood the bpip reporting correctly, what you mentioned appears after changing the status from DT2 to DT1 and vice versa.
This is a printout because in the meantime you and 1miau have become DT1, so there is no longer an equation logfiles DT2 no longer trusts 1miau DT2, now is more like logfiles DT1 trusts 1miau DT1
So, BPIP shows all the changes, and here the change happened due to the monthly DT reshuffle.

[logfiles]

If I understood the bpip reporting correctly, what you mentioned appears after changing the status from DT2 to DT1 and vice versa.
This is a printout because in the meantime you and 1miau have become DT1, so there is no longer an equation logfiles DT2 no longer trusts 1miau DT2, now is more like logfiles DT1 trusts 1miau DT1
So, BPIP shows all the changes, and here the change happened due to the monthly DT reshuffle.

Or probably a bug due to the month reshuffle?
Yeah, last month I was on DT1 and this month am on DT2, but the thing is I have so many other members on my trustlist and not just those two, so I would expect it to show others too... right?

[examplens]

Or probably a bug due to the month reshuffle?
Yeah, last month I was on DT1 and this month am on DT2, but the thing is I have so many other members on my trustlist and not just those two, so I would expect it to show others too... right?

I don't think it's a bug, just a showing of all changes. It confused me too, but then I saw that Jollygood dominates the log, but in fact, he has several thousand users on his distrust list. One of those pages for example https://bpip.org/TrustLog?pindex=5
I'm not sure how to check these changes for each user separately, nor is there an easy way to extract only the changes after the DT reshuffle. (manually only, I guess)

[LoyceV]

Or probably a bug due to the month reshuffle?

It's a feature, not a bug

Yeah, last month I was on DT1 and this month am on DT2, but the thing is I have so many other members on my trustlist and not just those two, so I would expect it to show others too... right?

Enter your username in the Report Options (tiny orange icon on the top right), and you'll see all of them. When 30 DT1-members are replaced at once, BPIP's DT Change Log dumps a lot of data all at once. Your own name will be spread over multiple pages.

[fillippone]

Or probably a bug due to the month reshuffle?

It's a feature, not a bug

Technically I have heard someone calling it a negative feature: the system is working as expected, following the programmer's logic. However, the programmer's logic is very different from user logic.
I would say that when the user has to adapt to programmers, and not the other way round, that is a bad UX choice.

[alani123]

When looking at the activity ranking it would be fun to have a column for "latest post " (to see when this member made their last post on the forum). Seeing if a member has posted in the last 2 weeks or not would help you get a picture if their activity is going to rank up in the next period or not. Also, I don't see why the hourglass indicating inactivity isn't shown next to usernames in this ranking. This page is where it's the most relevant.

[GazetaBitcoin]

It's a feature, not a bug

That still does not explain some glitches...

Look, for example, at the image posted by logfiles above:

Why does it show an invisible user which became part of DT...?

[Vod]

If the BPIP team is willing, I'd be willing to help redesign that DT change log.   It was one of the last things I was planning before the site transfer.

I had it simply comparing the changes.  Theymos' monthly "lottery" leads to entire trust lists being marked as changed.    The new version needs to not record changes when every person on a trust list is added or removed.

Of course, there are many ways to do this, seeing as BPIP already tracks DT membership.

[fillippone]

The new version needs to not record changes when every person on a trust list is added or removed.

Why not? Of course, the important information would be something like "fillippone wiped his Trust list" or "fillippone created his brand new Trust List". But I guess some sort of tracking of whole list creation/deletion might be of value.

[LoyceV]

Why not? Of course, the important information would be something like "fillippone wiped his Trust list" or "fillippone created his brand new Trust List".

I think Vod meant the current situation where DT1-changes "fake" wiping your Trust list. It should for instance say: "fillippone moved from DT1 to DT2", or "fillippone was excluded from DT1", without showing all entries on your Trust list as removed. Unless, of course, when you actually wipe your entire list: in that case it should be shown. My guess is this requires a lot more scraping than the current setup.

[examplens]

I think Vod meant the current situation where DT1-changes "fake" wiping your Trust list.

It can be said that that part is completely unnecessary, The DT strength page is more relevant for that. It should only have changes made by the user.
Although I would listen to Vod's proposal, maybe there is a more useful solution.