Free online tools for devs & data nerds. Text + file utilities, no sign-up, nothing leaves your browser. New ones are shipping constantly.
Free tools at →
Joined November 2018
- Tweets409
- Following73
- Followers59
- Likes3.9K
All Over Tools retweeted
Thailand, I am inside you again 😏🇹🇭
> sun is shining ☀️
> coffee is bussing ☕️
> locals are smiling 😊
> 4 month apartment leased 🏡
I’m telling you, move to Thailand, whatever it takes.
All Over Tools retweeted
Qwen 4 vs Kimi-K3.1
The quality of these models is getting ridiculous Both are showing serious potential
And they will be a lot cheaper than Openai and anthropic models
All Over Tools retweeted
GTC Dev Community Berlin Recap: From Open Models to Physical AI xitter.cf/i/broadcasts/1DxleVyYn…
All Over Tools retweeted
pr4th4mā māt4 // 0 1 ☯️ ♾️
f1rst f1re. f1rst th0ught. 100% l0aded.
sh3 w4s n3ver l0st, 0nly w41ting 🌅
4sat0 mā s4d gam4ya ▓▒░
All Over Tools retweeted
European airfares will see their ‘biggest increase in history’ in 2027, Ryanair CEO Michael O'Leary predicted this week, with airlines largely unhedged against higher jet fuel costs. Joanna Plucinska explains reut.rs/4sj9U1y
All Over Tools retweeted
Ruby 4.0.8 is out with an Onigmo regex overflow fix that looks like the root cause here.
github.com/ruby/ruby/release…
🚨 CRITICAL: GitLab flaw (CVSS 10.0) affects 12 years of releases.
CVE-2026-110264 could allow unauthenticated remote code execution on self-managed servers.
Read - thehackernews.com/2026/10/cr…
All Over Tools retweeted
Railway emailed: an unauthorized party may have accessed and decrypted customer environment variables.
If anything is hosted there, here’s a checklist for today:
• List every secret in your Railway variables. API keys, tokens, DB URLs, passwords. Every project.
• Revoke each one at the provider. Deleting it from the Railway dashboard doesn’t undo exposure.
• Make new keys with a spend cap. A leak should cost a limit, not a surprise bill.
• Check usage and logs from the last week for anything you didn’t run.
• Turn on 2FA on Railway, GitHub, cloud and AI accounts.
• Remove old OAuth apps and integrations you don’t use.
• Delete stale services, like forgotten test projects.
• Hold off adding new keys back until Railway says it’s contained. A separate host works in the meantime.
• Go slow. Rushing is how a second key leaks.
Going forward: mark keys as Secret on every host, one key per app, rotate every few months.
An urgent notice from the Railway team
blog.railway.com/p/security-…
All Over Tools retweeted
Extremely timely
What to do when your cloud provider is breached, from a former cyber insurance adjuster:
If your provider just disclosed a breach, you have to assume you've been exposed.
And every instinct you have about what to do next is probably wrong. So here's what you should actually do:
When you first hear about the hack, even if you doubt you were exposed, you need to get on it. Right away.
I don't care if you're on a date, or at your son's college graduation.
Get to a computer and start rotating every secret…everything. When someone asks later how fast you responded, you want the answer to be "immediately," with timestamps to prove it.
You're going to want to put as little in writing as possible. I get the instinct.
Do the opposite.
Document everything, obsessively. If your provider has locked things down and you can't rotate something yet, write that down too, with the time you tried. If you're using agents to investigate (and you should be, spread wide across everything), keep every trace and make them write down everything they find.
This will feel wrong in your soul. Do it anyway. If this ever turns into a claim, if you can show you did everything you were supposed to, minute by minute, you will survive.
You might tell yourself it's just names and emails and nobody cares. But this is wrong. All customer data counts.
I've watched companies lose millions just because someone could see data they shouldn't have.
You're going to want to wait for your provider to finish investigating before communicating with your own customers. Don't.
Figure out what information may have been exposed, even if you’re not sure yet who it belongs to, and what obligations you have under your contracts / applicable law. Your cloud provider’s investigation doesn’t change the fact that you have your own obligations to meet. And learning about a deadline after you’ve missed it is a very expensive lesson.
Bookmark this. I hope you never need it, but with everything happening lately, there's a real chance you will.
All Over Tools retweeted
This is the most serious 48 hours in cybersecurity history.
"Black October" they're calling it
It seems every *hour* there's a new incident, that in a typical year, would be one of the biggest incidents of the *entire year*
SUMMARY OF THE LAST 48 HOURS:
YEAR-LEVEL INCIDENTS (In a typical year, these would be among the biggest incidents of the year):
1. PHP2Shell: a hole in the software behind ~70% of websites. Governments took sites offline.
2. eMudhra: the master keys that prove websites are real were cracked. One was the number 4.
3. California: data on every public school student since 2023 stolen, including disability status
4. Railway: hackers stole customers' secret keys from a hosting platform used by millions of developers
5. Zeabur: 321,810 accounts breached. The company is shutting down.
6. LiteLLM: an AI tool downloaded 3.4 million times a day was poisoned with a password stealer
7. GitLab: a 10-out-of-10 severity hole in every version since 2014
8. Cairn: criminals used an AI hacking tool to break into 100+ companies
9. Ahold Delhaize: hackers knocked the owner of Food Lion and Stop & Shop offline
10. Onamae: malware planted on up to 26,739 customer servers in Japan
MONTH-LEVEL INCIDENTS (In a typical month, these would be among the biggest incidents):
11. Signal: a bug could leave your mic and camera on after you hang up
12. NGINX: 3 critical holes in software running ~1/3 of websites
13. HTTP/3: a single connection can crash 7 of the 10 web server types tested
14. Plex: hackers breaking into home media servers
15. SafePay ransomware: FBI warns it has hit 600+ critical infrastructure organizations
16. Palo Alto: ransomware gangs breaking in through company firewalls
17. Bullhorn: platform used by 10,000+ companies knocked offline
18. Medi-Cal: 970,000 patients' data stolen
19. WordPress: hackers stole a plugin maker's keys and used them to plant backdoors on websites
20. AOMEI: backup software's update server handed out a backdoor
21. Meta Muse: Meta's AI agent exposed users' personal and business secrets
22. Tor: 333 relays hijacked to steal logins
23. TiDB Cloud: database company's cloud breached
Also serious:
24. State Bank of India: India's biggest bank confirms a data breach
25. OVHcloud: hackers slipped a password stealer into a cloud company's official tool
26. Siemens: a software hole being used to spread malware
27. North Korea: state hackers launch a new attack campaign on South Korea
All Over Tools retweeted
99.99% uptime = down for < 9 minutes a year
99.9% uptime = down for < 9 hours a year
A 9 hour outage caps you to 2 nines of reliability for the year.
All Over Tools retweeted
I just added notifications to bring players back whenever something happens in the game 👀
All Over Tools retweeted
I asked Gemini 4 Argon to build the Shore Temple in Blender. The temple is approximately 1,300 years old, and the entire project took close to 16 hours. Even this video, including the music, was created by Gemini 4 Argon.
All Over Tools retweeted
Some government websites in Europe and elsewhere went offline after vulnerabilities in PHP, a widely used programming language, were uncovered using AI. Cybersecurity Reporter Raphael Satter explains why reut.rs/4jyVubl
All Over Tools retweeted
Lots of excitement last week about finally understanding neural networks, thanks to @nickcammarata's essay.
Nick revisited early research he helped produce and found patterns he had missed.
And the reaction was: oh yes, neural networks are clean, we can see through them now.
There are indeed some fascinating findings. But is it all so clear?
As always, I want to see the whole picture. @nabla_theta's response asks whether these explanations can survive tougher tests.
Here are both sides, and what we still need to investigate: youtube.com/watch?v=VYzjtj-1…