MurphyA/hacker-news huggingface dataset:
Show HN: Sidely a minimal ChatGPT sidebar for Chrome (no back end no injections)
by parasochka | 2025-11-19 11:59:31+00:00
I made a small Chrome extension because switching tabs to ChatGPT all day was getting annoying. Sidely opens your existing ChatGPT session in the Chrome side panel.

No backend, no tracking, no page injections. Just a lightweight shortcut to ChatGPT.

Would appreciate feedback on the UX or anything that feels rough.

Chrome Web Store: https://chromewebstore.google.com/detail/sidely-chatgpt-side...
Show HN: Q⊗DASH – Rust/Python quantum operator framework for graph-based QC
by dioniceOS | 2025-11-19 11:59:32+00:00
I’ve released an experimental quantum computing framework that grew out of my own operator/graph work: Q⊗DASH (MetatronQSO)

Rust core crate: metatron-qso-rs Python package: metatron_qso

GitHub: https://github.com/LashSesh/qso crates.io: https://crates.io/crates/metatron-qso-rs PyPI: https://pypi.org/project/metatron_qso/

# What it is

MetatronQSO is a Rust-first quantum operator framework with Python bindings. It focuses on graph- and operator-based algorithms: quantum walks, VQE, QAOA-style circuits and related experiments.

Core ideas: - Rust library for state evolution, circuits, walks and variational algorithms - PyO3-based Python SDK mirroring the same concepts - Backend abstraction (local simulator now, room for hardware providers via traits) - A nontrivial default geometry (a Metatron-cube–style graph) instead of toy line/grid graphs

The goal is not “yet another Qiskit wrapper”, but a self-contained operator core you can bend into your own models.

# Architecture (high level)

The workspace is organized as multiple crates, the key ones: - metatron-qso-rs: core quantum library (state, operators, circuits, walks, VQE/QAOA, example binaries) - metatron_qso_py: Python bindings - backend/telemetry crates for plugging in execution backends and exposing basic metrics

Everything is regular Rust + Cargo, with Python wheels built via maturin.

# Current status

metatron-qso-rs published on crates.io (0.1.x) metatron_qso published on PyPI (0.1.x) CI builds Rust + Python, runs tests and some benchmarks There are docs/notes in the repo explaining the operator model and backend design

It’s early-stage, but it compiles, runs examples, and is usable for experiments if you’re comfortable with Rust (or happy to drive it from Python).

# What I’d like feedback on

Does the Rust API surface feel idiomatic and composable? For Python users: is the current binding layer something you’d realistically work with, or would you expect a higher-level abstraction? Is the backend abstraction (local simulator now, future hardware later) structured in a way that’s easy to extend? Any obvious red flags in how I treat graphs/geometry as the primary object?

If you’re into quantum computing, graph-based algorithms, or unusual Rust workspaces, I’d appreciate any feedback, criticism, or ideas for where this should go next.
by VBprogrammer | 2025-11-19 12:00:03+00:00
People don't maintain HAM clubs for the potential use in an emergency, any more than people learn to fly in the hope of being able to rescue a commercial aircraft when both pilots are incapacitated.

They enjoy HAM radio as a hobby in and of it's self. It's doesn't come free to the government either, I'm sure some HFT organisation would pay handsomely for some of the bands currently used by HAM radio.
by duskdozer | 2025-11-19 12:00:23+00:00
>"Nothing they can do"? I've never owned a car so genuinely don't know but surely you can buy whatever lights you want for it and/or correct the alignment?

This was my initial thought too, but thinking about it for a second, I'm sure it's some absurd proprietary connector or housing, with a DRM chip of course, and only comes in the one variety to protect their brand.
by viraptor | 2025-11-19 12:00:27+00:00
> you absolutely don't want the service gateways to exist by default.

Why? My work life is in terraform and cloudformation and I can't think of a reason you wouldn't want to have those by default. I mean I can come up with some crazy excuses, but not any realistic scenario. Have you got any? (I'm assuming here that they'd make the performance impact ~0 for the vpc setup since everyone would depend on it)
by jacquesm | 2025-11-19 12:01:24+00:00
If I could give you one tip it would be this one: make sure that your current production contains enough contact information and appeal to other authors to help you bootstrap the next iteration. That first one is the hardest, and any aspiring writers that have good stories sitting unpublished (of which there are very many) is always on the lookout for new places to get their stories published. This is how almost every successful anthology in the past was published. Typically they had a contest model where if you got published you were awarded some prize money and otherwise you'd be out a couple of stamps.
by boriskourt | 2025-11-19 12:02:24+00:00
Interesting approach and a very readable paper.

> We provide two varients of MMaDA-Parallel with different tokenizers. MMaDA-Parallel-A is trained with tokenizer Amused-VQ, and MMaDA-Parallel-M is trained with tokenizer Magvitv2.

tyfeld/MMaDA-Parallel-A: https://huggingface.co/tyfeld/MMaDA-Parallel-A/tree/main

tyfeld/MMaDA-Parallel-M: https://huggingface.co/tyfeld/MMaDA-Parallel-M/tree/main
by cfiggers | 2025-11-19 12:02:52+00:00
When two humans want to talk but don't speak a shared language, if they spend enough time together, they will figure out how to communicate eventually.

But when two computers want to talk to each other and don't speak a "shared language" (aka, the client specifically must conform to the server's "language"—it's very one-sided in that sense) then no amount of time will allow them to learn one another's rules or settle on a shared communication contact without a human programmer getting involved.
by echelon | 2025-11-19 12:03:05+00:00
https://github.com/search?q=unwrap%28%29+language%3ARust&typ...

This is sobering.

My new fear is some dependency unwrap()ing or expect()ing something where they didn't prove the correctness.

Unwrap() and expect() are an anti-pattern and have no place in idiomatic Rust code. The language should move to deprecate them.
by discordianfish | 2025-11-19 12:03:22+00:00
Indeed, nothing about the root issues are particular surprising but why they missed a critical service panicing across their fleet is not bubbling up.

My best guess is too many alerts firing without a clear hierarchy and possibilities to seprate cause from effect. It's a typical challenge but I wish they would shed some light on that. And its a bit concerning that improving observability is not part of their follow up steps.
by jeroenhd | 2025-11-19 12:03:25+00:00
Group chats and just about everything else messaging clients have supported for a decade are part of the Universal Profile that came out nine years ago (file sharing, location sharing, audio messages, etc., although Signal still lacks location sharing so I guess RCS is still ahead of the curve here). These features will not always fall back well to SMS/MMS, though, according to the spec: https://www.gsma.com/solutions-and-impact/technologies/netwo...

Synchronisation is not part of the problem it's trying to solve (sending messages between devices), the same way SMS and MMS don't, so that's up to the apps implementing the protocol.

E2EE has been added very recently (https://www.gsma.com/solutions-and-impact/technologies/netwo... came out a few months ago), and post-quantum encryption is still being developed. It uses standard MLS (RFC 9420) for messaging, so verification will have to be implemented however normal MLS implementations do it. I don't know if there's a standardised way to do it, I haven't fully read the most recent RCS spec yet.

I oversimplified RCS somewhat, it's not just HTTP wrapped in carrier stuff. It's also SIP, SDP, XML, OIDC, RTP, and JSON wrapped in carrier stuff. Still, page 428 of the second link shows an example of a POST request that you can make after combining all of the tidbits of specification that came before it, and that's where the simple JSON+XML shine through the stack of protocols that are tasked with delivering it. The E2EE layer is basically just sending base64'd encrypted messages over that same interface.
by 4ggr0 | 2025-11-19 12:04:15+00:00
> Men are workers

What are women, then? Baby-machines, cooks and cleaners, which I guess you don't see as work?

I mean it's not the first time I encounter a dude with the same opinion as you have, but every time I'm surprised by the casual reductionism of our societies. Men make work, Women make baby. Men hard, Women soft. Men strong and powerful. Women weak and emotional.
by jgilias | 2025-11-19 12:04:34+00:00
You don’t even need all the ceremony. If the config gets updated every 5 minutes, it surely is being hot-reloaded. If that’s the case, the old config is already in memory when the new config is being parsed. If that’s the case, parsing shouldn’t have panicked, but logged a warning, and carried on with the old config that must already be in memory.
by byinsightAI | 2025-11-19 12:04:34+00:00
I'm a non-technical founder working on something in the fintech infrastructure space. I have put together a small technical challenge to help me understand how different engineers think about real issues like routing, settlement ambiguity, compliance rules, and failure modes.

I'm using this to identify engineers who might be a fit for early founding roles. I would appreciate feedback or participation from anyone who enjoys this kind of work.

Challenge: https://byinsight.ai
by _flux | 2025-11-19 12:04:43+00:00
I believe LLMs ultimately cannot learn new ideas from their input in the same way as they can learn it from their training data, as the input data doesn't affect the weights of the neural network layers.

For example, let's say LLMs did not have examples of chess gameplay examples in their training data. Would one be able to have an LLM play chess by listing the rules and examples in the context? Perhaps, to some extent, but I believe it would be much worse than if it was part of the training (which of course isn't great either).
by ralferoo | 2025-11-19 12:04:52+00:00
One thing I'd never really considered before is how frequently bodies get ejected at high speed from the simulation, especially as the number of initial bodies is increased. Suddenly made me realise that the "big bang" which previously seemed a bit of a random and magical theory (obvious question is why would the universe be expanding from a single point when gravity would be immense) now seems a lot more plausible without needing any "magic" to justify it.
by The_Reformer | 2025-11-19 12:05:37+00:00
White Paper: Systemic Risks in Concurrent LLM Session Management By Never-fear (Loyal)

Executive Summary This paper introduces a newly validated exploit class affecting multiple large language model (LLM) platforms. The flaw is vendor‑agnostic, architectural in nature, and has been independently reproduced by leading AI providers. While technical reproduction details remain restricted under nondisclosure agreements, the systemic implications are clear: current LLM session management designs expose models to cognitive instability, untraceable corruption, and covert exploit erasure.
by intothemild | 2025-11-19 12:05:44+00:00
Could pebble2 launch with a minimal set of apps, asking the old Devs to push their binaries again? Sure, and with that in mind, all this deal with rebble does is save everyone time.

The way this reads, is a group of enthusiasts got together to create a lifeboat for people who wanted to keep their pebble devices alive... But are now building a moat around said life raft.

If they truly cared about the devices, the users, and the developers.. they would just drop this attitude and move forward.

Another interpretation is that for rebble the worst thing that could happen, was Eric coming back and restarting pebble.
by andrewstuart | 2025-11-19 12:06:54+00:00
They’re Linux computers.

Anything AWS does you can run on Linux computers.

It’s naive to think that AWS is some sort of magically special system that transcends other networked computers, out of brand loyalty.

That’s the AWS kool aid that makes otherwise clever people think there’s no way any organization can run their own computer systems - only AWS has the skills for that.
by gpderetta | 2025-11-19 12:07:12+00:00
This is equivalent of using a single global lock (and STM is semantically equivalent, just theoretically more scalable). It obviously works, but greatly limits scalability by serializing all operations.

Also in practice the CSP node that is providing access control is effectively implementing shared memory (in an extremely inefficient way).

The fundamental problem is not shared memory, it is concurrent access control.

There's no silver bullet.
by soulofmischief | 2025-11-19 12:07:28+00:00
Diffusion text models aren't new, I've made them at home. Also, plenty of frontier models are good at tool calling, GPT-5 has just been trained to do it more so that it appears to do better at coding exercises with codex/IDEs.

If you haven't tried an agentic IDE such as Cursor yet, or at least an extension such as Copilot, I would recommend checking them out and trying out Anthropic's models as well.
by udev4096 | 2025-11-19 12:07:39+00:00
You'll only learn when you get pwned or worse, your phone gets bricked because of incompetent people running e/OS! The fact that you are failing to even acknowledge the proof and refusing to even do a little bit of self-research tells me everything I need to know about e/OS's userbase. Get out of the echo chamber of using privacy theatric and insecure mobile OS
by janpio | 2025-11-19 12:08:02+00:00
I understood this to be related to this section:

> As well as returning HTTP 5xx errors, we observed significant increases in latency of responses from our CDN during the impact period. This was due to large amounts of CPU being consumed by our debugging and observability systems, which automatically enhance uncaught errors with additional debugging information.

(Just above https://blog.cloudflare.com/18-november-2025-outage/#how-clo...)
by echelon | 2025-11-19 12:08:54+00:00
I would be fine just getting rid of unwrap(), expect(), etc. That's still a net win.

Look at how many lazy cases of this there are in Rust code [1].

Some of these are no doubt tested (albeit impossible to statically guarantee), but a lot of it looks like sloppiness or not leaning on the language's strong error handling features.

It's disappointing to see. We've had so much of this creep into the language that eventually it caused a major stop-the-world outage. This is unlikely to be the last time we see it.

[1] https://github.com/search?q=unwrap%28%29+language%3ARust&typ...
by kragen | 2025-11-19 12:11:15+00:00
Possibly relevant is hugi-compo round 3, the "Pong" compo: https://www.hugi.scene.org/compo/compoold.htm#compo3

I spent three days disassembling Guillermo Sais's 142-byte winner, which was challenging to understand. My notes may be of interest; they are in gsais-pong.md in http://canonical.org/~kragen/sw/pavnotes2.git/

I hope this is not interpreted as any kind of criticism. I would much rather be responsible for maintaining Joshi's code than Sais's. But I suspect that most people who are interested in either work will be interested in the other.
by jacquesm | 2025-11-19 12:11:17+00:00
No shit. But it works, if you're stupid.

If you're not then you will end up frustrated because it will be as if you have an over-eager trainee that is only slightly less dumb than a box of rocks when it comes to actual thinking but that has near perfect recall about a massive amount of information. A sort of idiot-savant.

I gave it a try for a practical problem to see how long it would take to converge on a solution. It did not, because its reasoning powers simply are not that strong. But it gave me an endless runaround about solutions that this time really would work and never mind all the previous times we did the same thing and it did not work. Between the over enthusiastic tone, the ridiculous confidence level and the jumping-to-conclusions mode that you just simply can't switch off I found the whole exercise more than a little bit frustrating. It never, for even a second expressed any doubt. It never warned when what it responded with was at best extremely low confidence and possibly very wrong (or even dangerous). And this was for a problem where I already knew the solution, it was in some ways entertaining to see the AI blunder about while in full possession of all of the information to see the solution.

'Great, that narrows it down'

'Now I see the problem'

'Got it'

'Ah - perfect'

etc, etc...

If your job involves actual thinking I don't believe you are in danger just yet.
by prmoustache | 2025-11-19 12:11:27+00:00
Kids in most european countries use whatsapp even though they are under the minimum age.

Ban an app, another appear. Ban all apps and they would join any of the services that provide a web frontend. Kids in the late 90's/early 2000 were using IRC when ICQ and MSN messenger didn't support group chat, usually from a web client before they were introduced to mirc and other irc clients.

Bottom line: they would find a way.
by tcfhgj | 2025-11-19 12:12:39+00:00
> and SMS messages get transmitted on mobile networks before 3G connections are established to send Teams messages.

this is different as you already explained

Net neutrality:

> Net neutrality is the principle that internet service providers (ISPs) treat all online traffic equally and openly, without discrimination, blocking, throttling or prioritisation.

https://eur-lex.europa.eu/EN/legal-content/glossary/open-int...
by oblio | 2025-11-19 12:12:48+00:00
> Why wouldn't you expect an AI that's both a superhuman coder and a superhuman communicator to be decent at translating between human requirements and code?

At this point LLMs are a superhuman nothing, except in terms of volume, which is a standard computer thing ("To err is human, but to really foul things up you need a computer" - a quote from 60 years ago).

LLMs are fast, reasonably flexible, but at the moment they don't really raise the ceiling in terms of quality, which is what I would define as "superhuman".

They are comparatively cheaper than humans and volume matters ("quantity has a quality all its own" - speaking of quotes). But I'm fairly sure that superhuman to most people means "Superman", not 1 trillion ants :-)
by mlrtime | 2025-11-19 12:12:49+00:00
Just replying that I read your post, and don't disagree with some of what you wrote, and I'm glad there are some people that peacefully/respectfully push back (because balance is good).

However, I don't agree that AI is a risk to the extreme levels you seem to think it is. The truth is that humans have advanced by use of technology since the first tool and we are horrible predictors at what the use case of these technologies will bring.

So far they have been mostly positive, I don't see a long term difference here.
by saxenaabhi | 2025-11-19 12:13:25+00:00
We do use workers, but with hono so it's easy to deploy it on render with node.

There are other cloudflare products for which there are not many alternative(durable objects, workflows etc), but at least for us we don't use them in the critical path. We deliberately avoided them in the critical path because we knew we'll have to setup multi cloud for 99.999% uptime(we run a POS system so any downtime results in angry calls and long lines for our merchants)
by miroljub | 2025-11-19 12:13:35+00:00
Funny, I just asked "Ask Brave", which uses a cheap LLM connected directly to its search engine, and it got it right without any issues.

It shows once again that for common searches, (indexed) data is the king, and that's where I expect that even a simple LLM directly connected to a huge indexed dataset would win against much more sophisticated LLMs that have to use agents for searching.
by tim333 | 2025-11-19 12:13:48+00:00
The words 'lead to' there cover a lot. I don't think we'll get AGI just by giving more compute to the models but modifying the algorithms could cover a lot of things.

Like at the moment I think during training new data changes all the model weights which is very compute intensive and makes it hard to learn new things after training. The human brain seems to do it in a more compartmentalised way - learning about a new animal say does not rewrite the neurons for playing chess or speaking French for example. You could maybe modify the LLM algo along those lines without throwing it away entirely.
by inhumantsar | 2025-11-19 12:13:49+00:00
this program was great. I referred one person (the maintainer of an open source music player for OS X that I contributed an interface redesign to) back in the early or mid 00s and they've been paying me for it ever since.

unlike OP though, I had set up those rewards to cash out automatically. so once a year $35 would appear in my PayPal account and an indie dev or content creator would earn a sale.

best pyramid scheme ever.
by jeroenhd | 2025-11-19 12:14:17+00:00
I run my own Mastodon instance and it's definitely heavy and unoptimized for this use case. That seems to be a common theme with Ruby on Rails applications, to be honest.

There are lighter clients that will integrate perfectly into Fediverse/Mastodon networks, though, such as GoToSocial (https://gotosocial.org/) with its light and low-tech UI.

Many Mastodon alternatives expose a Mastodon API so that you can use the standard Mastodon apps with them, even if you're not really hosting Mastodon itself.
by lazide | 2025-11-19 12:14:19+00:00
Expensive to have kids is a symptom, not a cause of the issue.

Fewer kids == more investment per kid == more competition for high quality everything == more costs.

Also, more workers in the labor force (aka fewer SAHM’s, etc) == more competition for labor == lower cost for labor (vs historic trends) == can buy less with an hours labor.

The ratio of pay for an hours work to a daycare hour is at historic highs, and there is a reason for that.

If you look at women’s participation in the workforce and overlay it with ratios of worker pay vs buying power, it’s a pretty obvious correlation. There is a reason that labor has been losing ground since the 70’s, and it’s largely because birth control means that women can put off having kids (while still meeting needs like having sex and being in relationships) in order to work and make money and be independent.

The issue here is - whatcha going to do about it?

Most women I know eventually want kids, but then they get screwed by all the younger women who don’t yet want kids making the market, ahem, not very amenable.

And they’re caught in the rat race, which is its own kind of miserable, especially when everyone is competing for the same slots, instead of the roughly half that was the historic norm.

There really is no free lunch though - plenty of horror stories from before too.
by hirako2000 | 2025-11-19 12:14:24+00:00
It's a centralization vs decentralisation vs distributed system question.

Since down detectors serve to detect failures of centralized (and decentralized systems) the idea would be to at least get that right: a distributed system to detect outages.

You basically run detectors that heartbeat each others. Just a few suffice.

Once you start to see clusters of detectors go silent, you can assume things are falling apart, which is fine so long as a few remain.

Self healing also helps to make the web of nodes resilient to inevitable infrastructure failures.