fyn.fyi works inside ChatGPT via MCP. We also partner with Plaid and cost 190 LESS per month.
English
threehundobaud
8 posts
Alright — time to come out of stealth.
This week OpenAI launched ChatGPT Personal Finance: $200/mo, US-only, answers when you ask.
We've quietly been building the better version.
Meet fyn.fyi — $9.99/mo, free tier, Android too, and it reaches out before you ask.
$190/mo less. fyn.fyi/compare/chatgpt
English
@IntCyberDigest That's it. Full sending everything to PHP.
English
‼️🚨 UPDATE: The TanStack npm attack is now a full campaign.
'Mini' Shai-Hulud has hit:
- OpenSearch
- Mistral AI
- Guardrails AI
-UiPath
- Squawk packages across npm and PyPI
The malware specifically targets AI developer tooling. It hooks into Claude Code (.claude/settings.json) and VS Code (.vscode/tasks.json) to re-execute on every tool event, long after the infected package is gone. npm uninstall does not fix this.
International Cyber Digest@IntCyberDigest
‼️🚨 BREAKING: A new npm supply-chain attack uses a dead-man's switch. The payload plants a watcher on your machine that nukes your home directory the second you revoke the GitHub token it stole from you. The compromise happened today, across 42 official tanstack npm packages, 84 malicious versions in total. tanstack/react-router alone pulls more than 12 million weekly downloads. The attacker forked TanStack's repository and pushed a single hidden commit. From there, they tricked TanStack's own release system into signing the malicious packages as if they were the real thing. To npm, and to anyone checking the cryptographic proof of origin (SLSA provenance), the poisoned versions looked 100% legitimate. Maintainer Tanner Linsley confirmed the whole team had 2FA enabled. It didn't matter. This is the first documented npm worm in history that ships with a valid, signed certificate of authenticity, the same one defenders rely on to know a package wasn't tampered with.
English
@brian_armstrong TLDR; The scrum masters are shipping features.
English
We experienced an outage at Coinbase last night, which is never acceptable. The root cause was a room overheating in an AWS datacenter when multiple chillers failed. We design our services to be redundant to downtime in any one AWS Availability Zone (AZ), and most of our systems worked this way last night, but not all.
Our centralized exchange did not. Exchanges have unique architectures that optimize for latency and co-location of clients. It is possible to make exchanges resistant to AZ failures, but this can introduce latency delays that are not desirable along with breaking customer co-location. Given this incident, we'll revisit these tradeoffs to ensure we're giving you the best possible venue to trade. At a minimum, the duration of an outage should be able to be reduced considerably when an AZ move is needed.
Thank you to the AWS and Coinbase teams for working through the night to mitigate the issue. We’ll share the detailed technical summary once it's ready.
English
@TheAhmadOsman Honest take though. WSL2 is probably 1% penalty versus Omarchy with a laminated shortcut card taped to your monitor like a true neckbeard.
English
@theo I think they nerfed 4.6 over the past few weeks to make the benchmarks look more favorable for 4.7. Imagine what it looked like before....
English
@claudeai Now all of a sudden this makes sense. Opus 4.6 sucks for the duration of fresh benchmarking to hype improvement comparison with their 4.7 model.
When was this benchmarked?
English
@andrewc_actual @UnslothAI Will check it out soon. Thanks!
English
@UnslothAI neat! this is on my todo list for this weekend. Already using the unsloth Q4 for 122b with great results so far
English
Qwen3.5 is now updated with improved tool-calling & coding performance!
Run Qwen3.5-35B-A3B on 22GB RAM.
See improvements via Claude Code, Codex.
We also benchmarked GGUFs & removed MXFP4 layers from 3 quants.
GGUFs: huggingface.co/unsloth/Qwen3.…
Analysis: unsloth.ai/docs/models/qw…
English