frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Big Tech vs. OpenClaw

https://www.jakequist.com/thoughts/big-tech-vs-openclaw/
1•headalgorithm•2m ago•0 comments

Show HN: Orcha – Run multiple AI coding agents in parallel, locally

https://orcha.nl
1•buildingwdavid•2m ago•0 comments

Anofox Forecast

https://anofox.com/docs/forecast/
1•marklit•2m ago•0 comments

Ask HN: How do you figure out where data lives across 100 microservices?

1•doodledood•2m ago•0 comments

Motus: A Unified Latent Action World Model

https://arxiv.org/abs/2512.13030
1•mnming•2m ago•0 comments

Rotten Tomatoes Desperately Claims 'Impossible' Rating for 'Melania' Is Real

https://www.thedailybeast.com/obsessed/rotten-tomatoes-desperately-claims-impossible-rating-for-m...
1•juujian•4m ago•0 comments

The protein denitrosylase SCoR2 regulates lipogenesis and fat storage [pdf]

https://www.science.org/doi/10.1126/scisignal.adv0660
1•thunderbong•6m ago•0 comments

Los Alamos Primer

https://blog.szczepan.org/blog/los-alamos-primer/
1•alkyon•8m ago•0 comments

NewASM Virtual Machine

https://github.com/bracesoftware/newasm
1•DEntisT_•10m ago•0 comments

Terminal-Bench 2.0 Leaderboard

https://www.tbench.ai/leaderboard/terminal-bench/2.0
1•tosh•11m ago•0 comments

I vibe coded a BBS bank with a real working ledger

https://mini-ledger.exe.xyz/
1•simonvc•11m ago•1 comments

The Path to Mojo 1.0

https://www.modular.com/blog/the-path-to-mojo-1-0
1•tosh•14m ago•0 comments

Show HN: I'm 75, building an OSS Virtual Protest Protocol for digital activism

https://github.com/voice-of-japan/Virtual-Protest-Protocol/blob/main/README.md
4•sakanakana00•17m ago•0 comments

Show HN: I built Divvy to split restaurant bills from a photo

https://divvyai.app/
3•pieterdy•19m ago•0 comments

Hot Reloading in Rust? Subsecond and Dioxus to the Rescue

https://codethoughts.io/posts/2026-02-07-rust-hot-reloading/
3•Tehnix•20m ago•1 comments

Skim – vibe review your PRs

https://github.com/Haizzz/skim
2•haizzz•21m ago•1 comments

Show HN: Open-source AI assistant for interview reasoning

https://github.com/evinjohnn/natively-cluely-ai-assistant
4•Nive11•22m ago•6 comments

Tech Edge: A Living Playbook for America's Technology Long Game

https://csis-website-prod.s3.amazonaws.com/s3fs-public/2026-01/260120_EST_Tech_Edge_0.pdf?Version...
2•hunglee2•25m ago•0 comments

Golden Cross vs. Death Cross: Crypto Trading Guide

https://chartscout.io/golden-cross-vs-death-cross-crypto-trading-guide
2•chartscout•28m ago•0 comments

Hoot: Scheme on WebAssembly

https://www.spritely.institute/hoot/
3•AlexeyBrin•31m ago•0 comments

What the longevity experts don't tell you

https://machielreyneke.com/blog/longevity-lessons/
2•machielrey•32m ago•1 comments

Monzo wrongly denied refunds to fraud and scam victims

https://www.theguardian.com/money/2026/feb/07/monzo-natwest-hsbc-refunds-fraud-scam-fos-ombudsman
3•tablets•37m ago•1 comments

They were drawn to Korea with dreams of K-pop stardom – but then let down

https://www.bbc.com/news/articles/cvgnq9rwyqno
2•breve•39m ago•0 comments

Show HN: AI-Powered Merchant Intelligence

https://nodee.co
1•jjkirsch•41m ago•0 comments

Bash parallel tasks and error handling

https://github.com/themattrix/bash-concurrent
2•pastage•41m ago•0 comments

Let's compile Quake like it's 1997

https://fabiensanglard.net/compile_like_1997/index.html
2•billiob•42m ago•0 comments

Reverse Engineering Medium.com's Editor: How Copy, Paste, and Images Work

https://app.writtte.com/read/gP0H6W5
2•birdculture•47m ago•0 comments

Go 1.22, SQLite, and Next.js: The "Boring" Back End

https://mohammedeabdelaziz.github.io/articles/go-next-pt-2
1•mohammede•53m ago•0 comments

Laibach the Whistleblowers [video]

https://www.youtube.com/watch?v=c6Mx2mxpaCY
1•KnuthIsGod•55m ago•1 comments

Slop News - The Front Page right now but it's only Slop

https://slop-news.pages.dev/slop-news
1•keepamovin•59m ago•1 comments
Open in hackernews

Bring true randomness to Spotify with Fisher-Yates shuffle

https://github.com/vuciv/true-random-shuffle
20•Elliott-Diy•4mo ago

Comments

mg•4mo ago
There also is a random button on the Music-Map that jumps to a random band:

https://www.music-map.com/info

From running the music discovery websites Gnoosic and the Music-Map for years now, and doing a lot of experiments, my experience is that the chance of someone liking a truly randomly selected band is very low. Less than 10%. But hey, trying 20 random bands and finding one interesting one can be worth it.

dehrmann•4mo ago
I can't seem to find the blog post, but you generally don't want true randomness because you don't want artists to cluster. You also almost never hear two songs by the same artist play consecutively on the radio.
lycos•4mo ago
Always reminds me of the time Apple introduces "Smart Shuffle" in iTunes in 2005 which "which lets the user change the “randomness” of shuffled songs".

https://www.apple.com/newsroom/2005/09/07Apple-Introduces-iT...

mcmoor•4mo ago
This is always brought up whenever Spotify shuffle is mentioned, but current Spotify shuffle is much worse than this. For me it consistently only plays a handful of songs in my dozens of songs playlist and all others are always shoved way behind in the queue.

My prime conjecture now is that there's some kind of caching reason where it's more advantageous for their CDN if those handful of songs are the only ones that're played. Funnily this also happens in my offline playlist, but I guess this is just because the same algorithm is also used there.

bob1029•4mo ago
> My prime conjecture now is that there's some kind of caching reason where it's more advantageous for their CDN if those handful of songs are the only ones that're played.

It's far more sinister than this. It has to do with royalties. They've got some secret algorithm that will even cut your account off from specific content if it's expensive and you consume it too frequently.

I find no issues listening to pop cult shit 24/7/365, but when I want to listen to some obscure opera more than 3 times it inevitably starts to fade out like a ghost.

owisd•4mo ago
Announcing it Steve Jobs quipped “We’re making it less random to make it feel more random.”
aarond0623•4mo ago
Ironically, I'm pretty sure you're thinking of this article by a Spotify engineer that has since been taken down:

https://web.archive.org/web/20230410041435/https://engineeri...

EDIT:

> We noticed some users complaining about our shuffling algorithm playing a few songs from the same artist right after each other.

...

> Since the Spotify service launched, we used Fisher-Yates shuffle to generate a perfectly random shuffling of a playlist.

...

> The algorithm is now rolled out to everyone using our desktop client and other clients will follow soon.

Everything old is new again.

dehrmann•4mo ago
> this article

That's the one! Thank you!

atoav•4mo ago
That's the question. And the answer is that different people prefer different things. I for example vastly prefer to listen to a full releases, that would be "shuffle by album", others want it to be as non-repetitive as possible while staying in a genre, yet others would want to stay in a certain time period of music, but shuffle between genres occasionally, etc.

Shuffling music on a per song basis is an interesting problem, with the ideal solution being something a top class DJ would do, e.g. matching one characteristic of the two tracks (e.g. Tempo), but updating another (e.g. Timbre).

But even with that implemented, not everybody likes the same thing. E.g. I love to hear new music that I don't know yet, but as a DJ my experience has been that many people like to hear music they know. Meaning app developers have to make the right choices available and those choices are under the hood far more complex than how you can sort a list of tracks by artists.

lylejantzi3rd•4mo ago
> And the answer is that different people prefer different things.

Exactly. There is no winning here.

When I was in college, I built a system for the college radio station that plays music while there are no DJs on the air. What I enjoyed most is keeping track of what songs played when (which we needed to do anyway for FCC compliance) so that we never play the same song twice until every song was played. This "felt" more random even though it wasn't.

Some people didn't like it. They wanted to hear a smaller subset of songs more often (the equivalent of putting a playlist on random). We solved that by letting users request songs through the website.

I wonder if there's a way to solve this by adding a setting called "repetitiveness". It's a value between 1 and 100. 1 is the least repetitive "play all songs once before repeating any" and 100 is "play the same sequence of songs every time."