Hacker Newsnew | past | comments | ask | show | jobs | submit | nerder92's commentslogin

Nice catch, but god terrible write-up. Please take the time to write it yourself even if you think you will do worse in explaining it than the LLM. It’s so off-putting to read that. Share your prompt or raw article notes even, it will much enjoyable to read than this


I've got rage baited a bit today on Twitter, so much so, that I've ended up writing this mini-essay on the matter.

I'd love to hear other people opinions on this piece, it's my first long form article so I'd appriciate some feedback!

Thanks!


> META Total Annual Revenue in 2025: $200.97 billion (up from $164.50 billion in 2024).

They literally don’t care.


And while they paid a reasonable amount of tax in 2025, that was a one off. They normally pay 3-5%.


Let's hope for the best. It's time we finally acknowledge dopamine addiction and the regulate this on minors!


In which way this is different from PowerSync?


Both use local SQLite and keep the backend authoritative. The main difference is that PowerSync mostly handles downstream replication and gives you an upload queue; your API still owns the write semantics. Syncular specifies the whole round trip. Durable commits, auth scopes, conflicts, replay, revocation and bootstrap. Syncular also goes further up the stack: schemas plus SQL/SYQL generate typed queries for TS, Swift, Kotlin, Dart and Rust, and blobs, CRDT/encrypted columns and windowed sync are built into the protocol.

In my separate benchmark harness, Syncular currently does considerably better than the tested PowerSync setup. For example, 100k bootstrap is ~0.57s vs ~6.5s and offline replay ~35ms vs ~5.1s. Those are early results from one environment, though, not a universal claim (https://github.com/bkniffler/offline-sync-bench).

I've used PowerSync in the past with a huge initial bootstrap sync and was very frustrated by the performance back then (ca 1 year ago), which was one of the reasons to create my own library.

PowerSync is much more mature today obviously and still a great and proven tool.


Hey PowerSyncer here :)

Firstly, it's awesome that you are using @sqlite.org/sqlite-wasm for your client-side SQLite database. We really like wa-sqlite ourselves.

We're currently implementing this proposal https://github.com/orgs/powersync-ja/discussions/376, which will speedup the sync throughput a lot - this was a natural next step for us as we have users with massive datasets (syncing a million plus rows).

Sidebar: What has your experience with OPFS+SQLite been like on sqlite-wasm? We have seen our fair share of issues on Safari/web kit.


Hey, nice, looks like I’ll have to rerun the benchmarks soon!

sqlite-wasm with opfs-sahpool has mostly behaved. No OPFS in private mode, storage may be evicted, handles can’t be passed to workers, and webviews may close them when backgrounded.

We open SQLite inside one dedicated worker and proxy other tabs through it, so that avoids some of the mess. Tauri uses native SQLite.



Is this inspired by antirez work on ds4?

Amazing job!


Antirez is the number one!thanks really thanks!


Antirez has a GLM 5.2 branch now in dwarfstar: https://github.com/antirez/ds4/tree/glm5.2

It heavily utilizes ssd streaming from my understanding and I think he mentioned getting some semi usable speeds on a 128gb m5 mbp.



Thanks, macroexpanded, and another one...

Daisugi, the Japanese technique of growing trees out of other trees (2020) - https://news.ycombinator.com/item?id=37759366 - Oct 2023 (102 comments)

Daisugi, the 600-year-old Japanese technique of growing trees out of other trees - https://news.ycombinator.com/item?id=26941631 - April 2021 (171 comments)


This is extremely naive and I’ll invite to try and built something like this and compare it with Fin performance


They didn't say Fin was valueless, they said it would become so in the future. 10 years from now i bet they're right.

Fin is a short term play and that's fine.


While this is relevant and should indeed be fixed, the attack surface and the practicality of the exploit is a bit meh.

The user needs to do 3 things for this to be actually be phished:

1. Receive money from somebody they don’t known with a weird description 2. Proactively ask the agent for such transaction 3. Click the link the agent provide

While this of course can happen on scale, doesn’t seems so critical in practice


Thanks for chiming in.

I agree this is not a one-click account takeover.

But I think point 2 is broader than that. The user does not need to ask about the malicious transaction specifically. Any normal question that makes the agent fetch recent transactions could bring the attacker-controlled text into the LLM context.


People already click suspicious emails that ask them to login. At a high number of attempts, some chickens will be caught. However, people are now weary of emails since there is a lot of phishing there. On the other hand, the AI assistant env. could be considered "safe" by users because it's stuff coming from the bank. So they are more likely to fall for it. (honestly, unless you are a dev and aware of prompt injection, I don't see why the users wouldn't fall for it).


Unless I missed it they didn't provide any proof of this actually working. Really seems like a thing veiled advert for their product


This is similar to scam where people are sent messages about bad transaction with a fake link to the bank to verify it. Some attackers have gotten Paypal to send notifications that have the link. People are supposed to check the source and go directly to bank, and this will bypass that.


Depending on how much access the AI agent has, there are worse things to inject it with than a link.


I think the critical part is that it launders an arbitrary URL as trustworthy. The alternative is “Don’t trust anything our bot says at face value, please.”

I think a better criticism is allowing arbitrary text (including URLs) in a transaction description.


SEPA transfer fields need to follow a standard. I think it's fine, we shouldn't put more control and censorship there (try to put Daesh membership fee if you want to get your account locked...)

However a chatbot should absolutely not be able to display arbitrary and clickable links outside a pretty tight whitelist (like, the bank FAQ).


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: