richba5tard

Other than that invision pb is nice though. Maybe needs some addional smilies. Or giphy integration.

Yeah that's weird. Invision PB sees this as "status updates" like twitter or facebook. I don't find an immediate option on how to turn it of from the feed. It's not like a PM but it's not really ment to show to everyone either.

Sadly I had to remove the content of the "news" section as this one hackers had infested with the crypto mining javascript, so comments on news is lost. All other content migrated just fine.

Forum migration is done, but hwbot engine integration with the invision pb api is a bit wonky. We are keeping an eye on it.

Ok, this will be included in rev7.1 as 76.19% voted in favor. ETA early march.

I'm on it -edit- i see websmile already configured the correct sockets.

Added

"stealing" points because you got a spectacular #1 spot is a different discussion than awarding minimal points beyond cutoff guys, please be on topic.

The algorithm is complex enough already. Stop making suggestions. j/k

Also interesting approach, although harder to properly implement and explain. Correct, but the app multiplier still stands. So apps which don't award full points, get less min points.

First suggested change for rev7.1 is to give minimum points to your best submissions, even if they are below the 90/50/75% cutoff compared to the best score. Min = minimum points if score above cutoff MinBC = minimum points if score below cutoff Reasoning: - people who are cooling with air/water now often receive 0 points, even if their submission was good air/watercooling - if there is a very large gap between wr and the others, very few people receive points - less incentive to submit mediocre overclocking results Suggestion: - min 2/2/0.5 bp/gl/hw points if > cutoff - min 1/1/0.2 points for any participation in the ranking < cutoff

When using a REST api, you client should specify which format it wants to use. This is typically done by adding the "Accept: application/json" or "Accept: */*" or "Accept: application/xml" header. If not specified, "Accept: */*" is implied (i can accept anything). The default behavior for "accept anything" was changed in rev7, but this change has been reverted. Nonetheless, it is more robust to add the header anyway.

We have removed the crypto hacks several times on this aging vbulletin 3 forum, but as vbulletin no longer provides security patches they always come back. We are currently implementing the invision pb API into the hwbot engine. Once done, we migrate the forums.

I found a way to mark json as primary media type, so json is returned instead of xml if you don't specify accept headers. I'm pushing the change to prod tomorrow morning.

Hi! The libraries used for the API have been updated, due to the old ones no longer being maintained. I've checked a few 3rd party apps but not all. The issue is likely because you don't explicitly mention application/json in your Accept header. Can you check? Thanks.

Revision 6 is more than 3 years old. It does not change that often.

Monthly hosting cost for hwbot is approx 1100 - 1200USD, mainly due to the massive database. The upgrade to a significantly faster database costs an additional 365$ monthly.

hwbot main server has been moved to an instance 4x as powerful as the previous one to temporarely solve the sluggishness. We can't keep running on this db server for ever, as the cost is higher than the budget we have.

The problem is rev6 of points does not scale. Each submission has impact on a global ranking, a hardware ranking, possible a custom competition ranking, team ranking, hardware masters, etc etc. One submission may cause 10000 updates of submissions in the same ranking, as the rev6 algorithm is based on your position within that ranking. Eg if there is a new #3, the points of #4 and lower (tens of thousands) need to be recalculated. Obviously this is especially bad during the last days of large competitions, where people sandbag and then submit top scores at roughly the same time. Rev7 solves this problem mostly by not taking your position into account, but based on % compared with the world record. Only if the WR changes, a total recalculation is required. There is a long ongoing discussion about this revision, and go-live date has been postponed multiple times, sadly. If you browse the dev version of hwbot (uat.hwbot.org), which runs on much lower end spec servers with the same database, you will notice the site is quite responsive. Rev7 will not solve all the problems, but it will run much smoother.

Feel free to make a pull request.

19 year old cpu put to very good use! congrats!

This will be picked up asap.

I encountered this improvement while grooming the 1800 tasks long HWBOT backlog. It has been dispatched to the developer, long overdue.

Java version will be displayed on HWBOT in next release (on the right bar as meta data), to be released for computex. To run as bash script, supply an output file name as parameter and it will not launch a UI. $ java -jar hwbotprime-0.8.3.jar output.hwbot --------- HWBOT Prime 0.8.3 ---------- Processor detected: Intel(R) Core(TM) i5-5257U CPU @ 2.70GHz Estimating speed... 4x 2,703.36MHz @ 62.0 C 8192 MB memory Running benchmark using 4 threads. Starting benchmark... Warm up phase: ..................................................................................................... done! Benchmark phase: ..................................................................................................... done! All done! Current CPU temperature: 63.0 C Score: 3242.43 saved to file output.hwbot.

Background for last stage: http://hwbotnews.s3.amazonaws.com/Competitions/1359-1366_GbtTargetOpenTarget/backgrounds/Target_Z170_1920x1080_6.jpg