retoor/drstats
1
0
Fork 0
Code Issues 2 Pull Requests Actions Packages Projects Releases Wiki Activity

feat: update export statistics with new user data and extended date range for graphs

Browse Source 
- Bump active users from 351 to 355 and total contributions from 8477 to 8726 in dataset export
- Update per-user contribution counts and percentages for IHateForALiving, BordedDev, CoreFusionX, and D-4got10-01
- Add Burns11Mor to mentions list and adjust mention counts for multiple users
- Replace graph PNGs with extended date range from 2024-11-07 to 2025-01-14, replacing previous 2024-12-28 cutoff
- Append new post content for users 12bitfloat and AceDev in their respective export files
This commit is contained in:
bot
2025-01-14 19:08:20 +00:00
parent 2ab5588697
commit fd0b16180c
518 changed files with 1615 additions and 627 deletions
Download Patch File Download Diff File Expand all files Collapse all files
export/rants-atheist.txt
+6 -1
View File
@@ -23,4 +23,9 @@ https://boards.greenhouse.io/xai/...,I think I've solved my problem. It's a 6 li
Must be polite and grateful to open source devs.
Must be diplomatic when pointing out they're fundamentally wrong about the spec they're implementing. Even if they helped write it.
Must not be sassy when showing receipts (what the spec says).
Must not be sassy.,Anyone doing advent of code?,So now the spam bots are mostly gone, do we start weekly rants up again?,Today is 6/12/24 and the doubling tickles my brain.,I can't wait for openAI to go bust.```
Must not be sassy.,Anyone doing advent of code?,So now the spam bots are mostly gone, do we start weekly rants up again?,Today is 6/12/24 and the doubling tickles my brain.,I can't wait for openAI to go bust.,Testing 4 different implementations of a standard and getting 4 different answers...,My new favourite consensus algorithm:
Get several devs to implement the same standard. Compare the results for lots of different test data. The consensus "correct" result is the one that is most common from all Implementations. Where consensus can't be found, the devs are shown each others code and it's a race to find bugs to invalidate an implementation that disagrees with yours. Implementations that don't follow "correct" behaviour must be updated accordingly, even if it means copying bugs from other code.
The insane thing is this is legit how it works, like python's typing standard is based on mypy and other type checkers have to match its behaviour. Unicode isn't really a standard, it just started to describe how text works in different places instead of the fights to the death battle royale we used before that.,Never trust code that describes itself as "rigorously tested".,It's nice when devs are
happy you find bugs in their code, like I don't want to bother them with issues so saying thanks is positive```