Sergio Regueira

Software Engineer at @Auth0. @YCombinator Alumni (S21). Co-Founder of @arengu. Passionate about engineering and technology.

[Miguel Carranza @elwatto]

https://t.co/8Gm3doCH6K

[Anthropic @AnthropicAI]

The US government, citing national security authorities, has issued an export control directive to suspend all access to Fable 5 and Mythos 5 by any foreign national, whether inside or outside the United States, including foreign national Anthropic employees.

The net effect of this order is that we must abruptly disable Fable 5 and Mythos 5 for all our customers to ensure compliance.

Access to all other Claude models is not affected.

We apologize for this disruption to our customers. We believe this is a misunderstanding and are working to restore access as soon as possible.

Read our full statement: https://t.co/bwn0sximKZ

[Miguel Carranza @elwatto]

Many such cases. Monoliths acquired for billions, while startups with 1,000 users worry they won’t scale without the latest architecture preached by some random conference tech influencer. Just be pragmatic. Use the right tool for the problem and the stage.

[slash1s @slash1sol]

a guy made $36,900 on Polymarket weather bet.

with a hairdryer.

> he figured out the platform was pulling data from a single unguarded sensor near a Paris airport runway.
> bought YES on temperature targets.
walked up to the thermometer.
> plugged in a hairdryer.
> collected his winnings.
> ran.

he entered the trade with $2,000 at a price of 5 cents and exited with a profit of nearly $37,000.

the meteorological service launched an investigation.
the sensor now has a security guard.

security is at the thermometer.
the guy is gone.

his profile: https://t.co/CuvcrBVPqV

his wallet: 0x1838cca016850ac7185a9b149fe7d0bd2d6629b4

copy him via tg with https://t.co/5aAg87o8ji here: https://t.co/lvnjNl1rCg

don't lose him.

[James Cowling @jamesacowling]

Time for a big systems advice thread!

In distributed systems there's no magic "push everything to prod at once" button. Every service gets pushed independently and nodes within a service get updated incrementally. If you mess up forwards/backwards compatibility you can fail irrecoverably.

So how to avoid this?

1/5: Decouple data and code changes. Never push out a release that changes how data is stored at the same time as the code that uses this new data. If there's a bug and you need to roll back to the old version of your code it won't be able to handle the new data in the new format. Instead push out a release that first changes the data in a way that’s compatible with both the old and new code (e.g., optional fields etc), when that’s stable push out the new code that uses it, then when that’s stable you can change the data to remove backwards compatibility. This is known as a “migration” in the database world and yes it’s annoying, but yes you need to do it.

[Josh Kale @JoshKale]

This is big... Anthropic just announced a model so powerful they won't release it to the public out of fear over the damage it will cause 😨

Claude Mythos Preview found thousands of zero-day exploits in every major operating system and web browser...

The numbers are hard to believe:
> $50 to find a 27-year-old bug in OpenBSD, one of the most security-hardened operating systems ever built

> Under $1,000 to find AND build a fully working remote code execution exploit on FreeBSD that grants unauthenticated root access from anywhere on the internet

> Under $2,000 to chain together multiple Linux kernel vulnerabilities into a complete privilege escalation exploit

For context: these are the kinds of findings that previously required elite security researchers working for weeks.
Anthropic engineers with no formal security training asked Mythos to find exploits overnight. They woke up to working code the next morning.

The results were so impressive Anthropic assembled Apple, Google, Microsoft, Amazon, NVIDIA, and seven other organizations into Project Glasswing:

A $100M defensive coalition. They're not releasing this model publicly. Instead, they're racing to patch the world's infrastructure before models like this proliferate.

[flavio @flaviocopes]

How Axios was compromised 🤯

[Larsen Cundric @larsencc]

The gap between "works in a demo" and "works at scale" is about 4,000 commits.

[Fabien Butz @f_butz]

@arpit_bhayani 800 million users. one primary.

meanwhile startups debate which database will scale before they have 10 users.

[Dmitrii Kovanikov @ChShersh]

22
80
443
3000
5432
8000
8080

[Ghost St Badmus @commando_skiipz]

401

403

429

500

[EU–INC @euinc_petition]

President Ursula von der Leyen officially announced the EU–INC today at Davos!

A single legal entity for all European founders to grow massive companies in Europe. Online incorporation in 48 hours. No more bureaucratic mess across European borders.

All of you made this happen!

[gaut @0xgaut]

realizing you don’t need to know how to code to build good ideas anymore but you have no good ideas

[Ben Eater @beneater]

Anyone else out there vibe circuit-building?

[James McDonald @jamesm]

When you toggle the lights, the entire page dims to create a more immersive sense of the lighting

Such a great design detail 💡

[Miguel Carranza @elwatto]

Biggest hack for managers who miss the instant dopamine of shipping software: weekly updates. They build discipline, accountability, and visibility. They force you to reprioritize.

You actually ship something every week, and it feels great to reflect on the progress made.

[dennis hegstad @dennishegstad]

“Good morning. Your payment has been declined”

[Igor Babuschkin @ibab]

A common mistake that AI companies make nowadays is to not give their engineers enough time and mental calm to do their best work. Constant deadlines, pressure and distractions from daily AI news are poison for writing good code and systems that scale well. That’s why most AI APIs and products have reliability issues.

A good company culture that mixes excellence with focus and enough rest leads to faster and better results. The best example of how to do it well is the early Google culture from 1998 which resulted in one of the largest scale and most reliable services on the web in just a few short years. Founders should copy some of the strategies that Larry and Sergey used. They are still underrated IMO despite their huge reputation.

[leroysmer @Leroysmer]

Aquí os dejo un avance de mi último video, usando la Inteligencia Artificial para enseñar de una forma más divertida!

Espero que os guste, tenéis el video completo en el tuit citado.

Powered by: Nano banana + Veo3.1

[Branko @brankopetric00]

CTO asked to reduce S3 costs. We were spending $4,200 monthly on storage.

Implemented lifecycle policies:
- Move to Glacier after 90 days
- Delete after 2 years

Cost dropped to $980 per month. Saved $3,220 monthly. DevOps team got praised in all-hands meeting.

Three months later, customer needed a file from 120 days ago. Normal retrieval: 3-5 hours. Expedited: $150 for one file.

Turns out those "old files" weren't old. They were:
- Compliance records customers accessed quarterly
- Historical reports used for annual comparisons

Spent $2,400 in Glacier retrieval fees over 6 months. Wiped out all savings.

Lesson: Know why data exists before deciding how long to keep it. Cheap storage that's inaccessible isn't cheap.