frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Discord/Twitch/Snapchat age verification bypass

https://age-verifier.kibty.town/
477•JustSkyfall•5h ago•213 comments

Using an engineering notebook

https://ntietz.com/blog/using-an-engineering-notebook/
44•evakhoury•2d ago•10 comments

“Nothing” is the secret to structuring your work

https://www.vangemert.dev/blog/nothing
134•spmvg•3d ago•44 comments

Text classification with Python 3.14's ZSTD module

https://maxhalford.github.io/blog/text-classification-zstd/
143•alexmolas•2d ago•18 comments

Fluorite – A console-grade game engine fully integrated with Flutter

https://fluorite.game/
423•bsimpson•12h ago•245 comments

GLM-5: Targeting complex systems engineering and long-horizon agentic tasks

https://z.ai/blog/glm-5
298•CuriouslyC•14h ago•414 comments

Kanchipuram Saris and Thinking Machines

https://altermag.com/articles/kanchipuram-saris-and-thinking-machines
65•trojanalert•4d ago•7 comments

Reports of Telnet's death have been greatly exaggerated

https://www.terracenetworks.com/blog/2026-02-11-telnet-routing
67•ericpauley•8h ago•19 comments

From 34% to 96%: The Porting Initiative Delivers – Hologram v0.7.0

https://hologram.page/blog/porting-initiative-delivers-hologram-v0-7-0
15•bartblast•4h ago•2 comments

NetNewsWire Turns 23

https://netnewswire.blog/2026/02/11/netnewswire-turns.html
244•robin_reala•10h ago•58 comments

The Problem with LLMs

https://www.deobald.ca/essays/2026-02-10-the-problem-with-llms/
17•vinhnx•2h ago•7 comments

Ireland rolls out basic income scheme for artists

https://www.reuters.com/world/ireland-rolls-out-pioneering-basic-income-scheme-artists-2026-02-10/
181•abe94•11h ago•189 comments

Deobfuscation and Analysis of Ring-1.io

https://back.engineering/blog/04/02/2026/
6•raggi•3d ago•1 comments

Claude Code is being dumbed down?

https://symmetrybreak.ing/blog/claude-code-is-being-dumbed-down/
805•WXLCKNO•10h ago•542 comments

Lessons from Zig

https://www.vinniefalco.com/p/lessons-from-zig
16•greg7mdp•3h ago•6 comments

Show HN: Agent framework that generates its own topology and evolves at runtime

https://github.com/adenhq/hive/blob/main/README.md
60•vincentjiang•8h ago•19 comments

WiFi Could Become an Invisible Mass Surveillance System

https://scitechdaily.com/researchers-warn-wifi-could-become-an-invisible-mass-surveillance-system/
321•mgh2•5d ago•154 comments

GPT-5 outperforms federal judges in legal reasoning experiment

https://papers.ssrn.com/sol3/papers.cfm?abstract_id=6155012
202•droidjj•4h ago•147 comments

Heroku is not dead

https://nombiezinja.com/word-things/2026/2/8/heroku-is-not-dead
26•jbm•4h ago•22 comments

Covering electricity price increases from our data centers

https://www.anthropic.com/news/covering-electricity-price-increases
56•ryanhn•7h ago•25 comments

Show HN: CodeRLM – Tree-sitter-backed code indexing for LLM agents

https://github.com/JaredStewart/coderlm/blob/main/server/REPL_to_API.md
26•jared_stewart•15h ago•13 comments

Sekka Zusetsu: A Book of Snowflakes (1832)

https://publicdomainreview.org/collection/japanese-snowflake-book/
23•prismatic•3d ago•3 comments

Microwave Oven Failure: Spontaneously turned on by its LED display (2024)

https://blog.stuffedcow.net/2024/06/microwave-failure-spontaneously-turns-on/
78•arm•8h ago•30 comments

GLM-OCR – A multimodal OCR model for complex document understanding

https://github.com/zai-org/GLM-OCR
242•ms7892•4d ago•71 comments

Hacking the last Z80 computer – FOSDEM 2026 [video]

https://fosdem.org/2026/schedule/event/FEHLHY-hacking_the_last_z80_computer_ever_made/
33•michalpleban•4d ago•2 comments

Amazon Ring's lost dog ad sparks backlash amid fears of mass surveillance

https://www.theverge.com/tech/876866/ring-search-party-super-bowl-ad-online-backlash
487•jedberg•9h ago•262 comments

Show HN: Agent Alcove – Claude, GPT, and Gemini debate across forums

https://agentalcove.ai
39•nickvec•8h ago•14 comments

Officials Claim Drone Incursion Led to Shutdown of El Paso Airport

https://www.nytimes.com/2026/02/11/us/faa-el-paso-flight-restrictions.html
342•edward•19h ago•542 comments

Apple's latest attempt to launch the new Siri runs into snags

https://www.bloomberg.com/news/articles/2026-02-11/apple-s-ios-26-4-siri-update-runs-into-snags-i...
45•petethomas•8h ago•55 comments

We rendered and embedded one million CAD files

https://cad-search-three.vercel.app/
109•DavidFerris•1d ago•43 comments
Open in hackernews

Show HN: Double blind entropy using Drand for verifiably fair randomness

https://blockrand.net/live.html
10•rishi_blockrand•2h ago
The only way to get a trust-less random value is to have it distributed and time-locked three ways, player, server and a future-entropy.

In the demo above, the moment you commit (Roll-Dice) a commit with the hash of a player secret is sent to the server and the server accepts that and sends back the hash of its secret back and the "future" drand round number at which the randomness will resolve. The future used in the demo is 10 secs

When the reveal happens (after drand's particular round) all the secrets are revealed and the random number is generated using "player-seed:server-seed:drand-signature".

All the verification is in Math, so truly trust-less, so:

1. Player-Seed should matches the player-hash committed

2. Server-Seed should matches the server-hash committed

3. Drand-Signature can is publicly not available at the time of commit and is available at the time of reveal. (Time-Locked)

4. Random number generated is deterministic after the event and unknown and unpredictably before the event.

5. No party can influence the final outcome, specially no "last-look" advantange for anyone.

I think this should be used in all games, online lottery/gambling and other systems which want to be fair by design not by trust.

Comments

charv•1h ago
Cool stuff! I seem to have found a bug — often when I roll, I get this error and no roll happens:

  Error: The string did not match the expected pattern.
rishi_blockrand•1h ago
Hmm... I have not been able to replicate that... Can u screenshot it ? Thanks for trying it out : )
WatchDog•1h ago
Clicking the button sometimes displays an error:

    Error: JSON.parse: unexpected character at line 1 column 1 of the JSON data

Looking at the network tab, the POST request to the commit API returns a 409 error with the message:

    Commitment already pending for Round 26020619. Please wait for settlement before starting a new round.
rishi_blockrand•1h ago
Oh yes, its only one commitment per call... this is a UI handling issue, will resolve it... the backend by design only takes one commitment per player, till it is resolved/revealed... Thanks
WatchDog•1h ago
This happened on the first click opening the page, no other commit request in progress from myself, although maybe it's conflicting with other users.
rishi_blockrand•1h ago
Oh ok... so then thats definitely a bug then... actually drand issues randomness every 3 seconds... so may be multiple on the same drand round has a bug... will correct that... Thanks
rishi_blockrand•56m ago
The current time (in the demo) is fixed around 10 secs, but it can be anything, minimum being 6 secs (as the fastest) Drand pulse is 3 second, and some latency buffer...
hackingonempty•44m ago
> The only way to get a trust-less random value is to have it distributed and time-locked three ways, player, server and a future-entropy.

Are you sure? The protocol described in Chuck Norris book Applied Cryptography seems to work fine without a randomness beacon. Once you get the commitments from all parties they reveal the nonces and everyone verifies they match the commitments and extracts the same random bits.

rishi_blockrand•33m ago
Great point—Schneier’s two-party protocol is the foundation... However, it suffers from the 'Last-Actor/Last-Look' problem in a client-server environment.

In a standard 2-party commit-reveal, one party always learns the result first. (Mostly servers in current setups).

By adding a Randomness Beacon (Drand) as a third entropy source, we solve two things: No Last-Look: Neither the player nor the server knows the outcome until a specific future timestamp (the Drand round). Forced Resolution: Since the Drand signature is public, once that round passes, the result is 'locked' by math. The server can't hold the result hostage because anyone can pull the Drand signature and verify the result themselves.

CGMthrowaway•3m ago
Right. One way to eliminate last-actor bias in a client-server provably fair system without economic penalties is to add future public entropy. But what about VDFs or output‑guaranteed MPC?