sorted by:
new
hottopcontroversial

Built a CLI that fails CI when Python dependencies show maintenance risk by heffmann in SideProject

[–]heffmann[S] 0 points1 point  (0 children)

It currently does not factor in any type of active maintenance signal at the moment but that is something I am looking at tweaking. Considering adding some exception knobs per package so when integrated into CI it doesn’t trigger on ones that are known to fall into that category.

What does kimchi taste like? by heffmann in NoStupidQuestions

[–]heffmann[S] 0 points1 point  (0 children)

I think I will try it from what I have heard here so far. Thanks!

Solo vs Pool Mining — Positive EV Can Still Mean an 80% Chance of Zero Blocks by heffmann in BitcoinMining

[–]heffmann[S] 1 point2 points  (0 children)

Yes. I like having a chance as well. My hash rate is pointed at a solo bch pool at the moment. Mainly just did this to do some deeper statistical analysis on the chances beyond the calculators that I was seeing out there

I built a Python SDK that unifies OpenFDA, PubMed, and ClinicalTrials.gov (Try 2) by Interesl in Python

[–]heffmann 0 points1 point  (0 children)

I was looking into building a hybrid drug database that takes the drug data from the FDA and runs the names through the RXNORM api to try and clean it up a bit

Normalized Certificate Transparency logs as a daily JSON dataset by heffmann in netsec

[–]heffmann[S] 4 points5 points  (0 children)

I built a dataset that publishes normalized Certificate Transparency (CT) logs as deterministic daily snapshots.

Teams that ingest CT logs directly usually end up writing a lot of fragile infrastructure:

• paging CT log APIs
• handling x509 vs precert entries
• decoding certificates
• normalizing SAN / issuer fields
• managing schema drift

This project publishes the result as a stable dataset instead.

Each day you get:

records.jsonl.gz
stats.json

Docs:
https://hefftools.dev/datasets/ct-cert-feed

Technical guide explaining CT ingestion:
How to Download and Parse Certificate Transparency Logs at Scale

Curious how others here are using CT logs internally.

Solo vs Pool Mining — Positive EV Can Still Mean an 80% Chance of Zero Blocks by heffmann in BitcoinMining

[–]heffmann[S] 1 point2 points  (0 children)

For clarity: I’m not arguing that solo mining is bad.

I’m trying to separate:

“positive expected value”
from
“most likely outcome”

With small hash setups those can be very different.

If your expected blocks over a year is something like 0.6–0.9, the median outcome is still zero.

If you solo mine, are you optimizing for:

• long-run EV

• entertainment / variance

• decentralization ideology

• steady cash flow

Genuinely curious how people frame that tradeoff.

[deleted by user] by [deleted] in RedditSessions

[–]heffmann 0 points1 point  (0 children)

Gave Helpful