OVH annonce Olala mini 7A1B
OVH sa première famille de LLM. Premier représentant de cette famille, Olala mini 7A1B est un modèle compact bâti sur une architecture inédite.
Olala : le modèle innovant dans l’attention hybride
Olala mini repose sur une architecture de 7 milliards de paramètres (7B) avec un milliard activés répartis entre 256 experts par couche, l’attention hybride avec Differential-TPA et Mamba-3, au format BF16. Seule une fraction du modèle est sollicitée à chaque requête, ce qui le rend plus rapide et moins gourmand en mémoire. Conséquence directe: le modèle fonctionne sur un GPU doté d’un minimum de 8 Go de mémoire, il atteint 160 tokens par seconde sur une RTX A4500, et même sans GPU, sur un simple processeur, à 50 tokens par seconde. Sa fenêtre de contexte atteint aujourd’hui 32 000 tokens. Olala mini sera disponible en open source sur Hugging Face, sous licence Apache 2.0.
Entraîné avec l’aide publique européenne et en fonctionnement chez Qwant
Olala mini a été entraîné sur trois supercalculateurs publics européens, Jupiter, MeluXina et Jean Zay, équipés de GPU GH200, A100 et H100. Ce soutien, qui représente l’équivalent de 7 M€ en heures de calcul, a été déterminant, et OVH tient à en remercier les pouvoirs publics. L’initiative publique s’est révélée un succès à plus d’un titre : elle a fait émerger une équipe d’exception en intelligence artificielle et a donné naissance au Lab Agentique d’OVH: OVHai LLM. Olala mini est publié avec ses poids, son modèle de base pré-entraîné, son rapport technique et sa documentation de conformité à l’AI Act. Qwant l’a déjà adopté pour sa fonctionnalité de réponse flash, avec des gains significatifs : des réponses 20 % plus rapides et des coûts de fonctionnement divisés par trois par rapport au modèle précédemment utilisé.
En route vers la v1.1, puis la v2.0
Attendue d’ici la fin de l’année, la version 1.1 portera la fenêtre de contexte à 128 000 tokens et améliorera ses performances en raisonnement mathématique. Avec la version 2.0, OVHai LLM entend développer des modèles spécialisés dans trois domaines. D’abord, l’agentique pour les entreprises : à terme, Olala alimentera OVHai Workspace, dont la version chiffrée nécessitera des modèles capables de tourner en local, directement sur le poste de travail. Ensuite, le DevOps cloud, avec des déclinaisons adaptées aux développeurs, aux architectes et aux équipes d’exploitation qui assurent la continuité de service 24h/24. Enfin, la cybersécurité, dans ses volets défensif comme offensif. Olala v2.0 dépassera les 100 milliards de paramètres.
https://t.co/3QlWMzfpkk
I spent 6 years at Apple building Siri. This month Apple terminated my developer account.
What happened - this is my guess:
• One of my apps was running a remote-config A/B test on its onboarding screens
• I got an automated warning, so I removed the property and re-submitted the app
• Two days later the account was terminated under section 3.2(f)
My dad and I build and ship our apps together from this account and it’s one of the things that keeps us close even 6000 miles apart.
I've appealed and haven't heard back yet. I really believe this is a mistake, and if not I’d love to hear the issue and possibly be given the opportunity to fix it.
If anyone at Apple can get this in front of App Review or if you know somebody from that team, I'd be incredibly grateful 🙏
DMs open, happy to share case details with anyone at Apple who can help
@djraz369 How were you "submitting an app update every day" (or even 2–3 times a day) for the same app when Apple App Review typically takes 24–48 hours, and sometimes several days?
Interesting advice coming from someone who has experienced Apple account terminations himself.
You know firsthand how difficult this situation can be, yet you keep questioning developers who choose to protect their identity.
You've reportedly continued publishing through another company after your own terminations, so you understand how much is at stake.
I've shared my apps privately with trusted developers. Privacy isn't proof of guilt.
Instead of attacking developers asking for fair treatment, why not support meaningful human reviews and a transparent appeal process?
@tim_cook@AppleSupport@Apple
@erikgoinsHQ It is abhorrent for Apple to block competing stores and then arbitrarily refuse to carry perfectly fine and lawful third-party apps on their monopoly store.
Apple is playing games with the livelihoods of 1M developers and the freedom of access for 1B consumers.
This is what years of hard work looked like before Apple terminated my developer account.
$1,729 MRR. 136 active subscriptions. Real growth, built from zero.
No shortcuts. No overnight success. Just an indie developer working every day to build a career and a stable income.
Then Apple terminated my entire account under Section 3.2(f), citing a pattern of misleading or manipulative behavior, without clearly explaining which actions justified such a serious decision.
Apps that had been approved and live for months were suddenly part of a termination I still don't fully understand.
No meaningful human conversation. No clear guidance on what to fix. Just years of work and income put at risk.
I understand Apple needs to protect the App Store from fraud, but legitimate developers deserve transparency, a fair review, and an opportunity to correct mistakes.
I wasn't making millions. I was finally starting to make a living from something I built myself.
I'm not asking for special treatment. I'm asking Apple to review my case fairly and explain what I did wrong.
Section 3.2(f) should protect the App Store, not leave developers feeling powerless against decisions they can't understand or challenge.
I'm not giving up.
#BuildInPublic @AppleSupport@Apple@tim_cook@pbsIdentity
‼️ Apple suspended the developer account of PowerDirector maker CyberLink on 24 October. CyberLink's App Store page now lists zero apps.
Those apps made 14.69% of the Taiwanese firm's 2025 revenue.
CyberLink says Apple told it some products failed unspecified requirements. Apple has not said publicly which ones.
The company has appealed, and Taiwan's Ministry of Digital Affairs is helping. CyberLink warns the hit could last up to a year.
Chairman Jau Huang calls Apple high-handed on a monopoly platform. He says Apple ignored a friendly letter from CyberLink's lawyers.
This might be the scariest Halloween I’ve ever had.
Not because of ghosts, horror movies, or anything supernatural.
But because, after almost 10 years as an independent iOS developer, I might lose everything I’ve built.
On October 26, 2026, I received a Pending Termination Notice from Apple saying that app submissions from my account had “repeatedly violated the App Review Guidelines in an attempt to evade the review process” and that the violations remained unresolved after multiple resubmissions.
I’m trying to understand how my review history matches that conclusion.
Here is the full story.
I started learning Objective-C at the beginning of 2017.
At the time I had an iPhone 5c and simply wanted to build an app for myself because I couldn’t find anything in the App Store that worked the way I wanted.
For around 3–4 months I learned every day from documentation, videos and whatever resources I could find.
YouTube had far fewer good iOS development tutorials back then, and a lot of learning material was paid.
Eventually I reached the point where I thought: I can actually build this.
I still remember how amazing it felt writing some code and then seeing something I had created running on my own iPhone.
I released my first app on August 11, 2017.
That app is still maintained today.
It is written in Objective-C, which is becoming increasingly difficult to maintain, and one of my plans has been to finally rewrite it in Swift/SwiftUI.
That was the beginning of my journey as an independent developer.
I’ve never been a developer who releases dozens of apps every year.
I’ve started many ideas and abandoned many of them because somebody built something better, because I decided the idea wasn’t good enough, or simply because I no longer felt passionate about making it.
That is why the notice I received this week was so difficult to understand.
The app connected to the termination notice was first submitted as version 1.0 in April 2025.
During the initial review I had five rejections.
Unfortunately, App Store Connect no longer shows me enough detail to reconstruct every rejection from that period.
But from what I remember, they were mainly related to screenshots and App Store metadata.
One issue was that my screenshots were too marketing-oriented and did not show enough of the actual app experience.
I changed them.
Another rejection concerned content shown inside the screenshots.
One screenshot showed a man and woman kissing.
I replaced it with an image showing a marriage proposal.
That was rejected too.
As I remember, the reviewer cited the Objectionable Content guideline, explaining that the content could be considered objectionable by some users. The reviewer also referred me to screenshots attached to the rejection message, which pointed to the particular App Store screenshot I had been trying to correct.
I suspected that the title or wording displayed on that screenshot might also have contributed to the rejection.
So I changed the screenshot's text as well.
After making these adjustments, the app eventually passed review.
During those submissions I also made changes to the binary and uploaded new builds.
The important part is what happened afterwards.
Version 1.0.1 — approved April 28, 2025.
Version 1.0.2 — approved May 5, 2025.
Version 1.0.3 — approved May 27, 2025.
Version 1.0.4 — approved August 7, 2025.
Those four updates passed App Review without rejection.
Then more than one year passed.
I did not submit another update to this app.
And on October 26, 2026, I suddenly received a notice saying:
“App submissions from your account have repeatedly violated the App Review Guidelines in an attempt to evade the review process.”
It also says that after multiple resubmissions, violations described in previous correspondence remained unresolved.
That is the part I cannot reconcile with the history I can see.
After the initial review process in April 2025, Apple approved the app.
Then Apple approved four additional updates.
The last one was approved in August 2025.
As far as I can determine, none of my other apps have a history of repeatedly being rejected for the same unresolved issue either.
I have never intentionally tried to hide functionality from App Review.
I don’t use A/B testing to show reviewers a different paywall.
I don’t dynamically switch to a different paywall for review.
I don’t intentionally use dark patterns.
In this app, I have never shown a paywall during onboarding or immediately after onboarding. I also don't use promotional paywall screens that interrupt users after they enter the app.
Users are not forced to make a purchase just to get past onboarding. My intention has always been to provide a transparent experience where users can explore the app and understand its functionality without being pressured into purchasing.
My apps are not built around hard paywalls — I normally provide free functionality so users can actually use and evaluate the app.
I also regularly check my privacy policy and support pages to make sure they continue working, because I know broken or misleading links can themselves cause App Store problems.
The difficult part for me is that this is not just an app.
Independent development has been my work for almost a decade and is how I support myself and my family.
Almost ten years of work could potentially disappear because of a violation that, at least from the information currently available to me, I still do not understand.
I appealed approximately 30 minutes after receiving the notice.
Looking back, I probably should have waited until the next morning.
I received the message around midnight and didn’t sleep that night.
The appeal form also limits the response to 2,000 characters, so I had to repeatedly shorten what I wanted to explain.
The next day I realized there were things I could have explained much more clearly.
For now, I’m waiting for Apple’s response.
I hope Apple reviews the account manually and that this can be resolved.
P.S. I also want to clarify a few things about the app involved in this termination notice.
This was not an AI girlfriend / boyfriend app. Its name and icon did not imitate, copy, or attempt to resemble any other apps, brands, or popular services.
It was a simple AI image-to-video generator. Users could upload their own photos and generate AI videos from them. The app did not offer pre-made templates or similar content.
I also implemented safety checks for both uploaded images and text prompts before processing generation requests, with the intention of preventing NSFW or otherwise prohibited content.
Every new user received their first AI video generation completely free. I personally covered the cost of that generation, so users could try the app and see the results before deciding whether to spend any money.
After using their free generation, users could optionally purchase additional credits through Apple's In-App Purchase system. The app never offered subscriptions of any kind. There were no recurring payments or automatic renewals, only one-time purchases of credits when users wanted to generate more videos.
I also never actively promoted or advertised this app. I didn't create TikTok or Instagram accounts for it, run social media campaigns, or use paid advertising to attract users.
And importantly, Apple's stated reason for the Pending Termination Notice was not any of these issues. The notice specifically alleged repeated App Review Guideline violations, attempts to evade the review process, and unresolved violations after multiple resubmissions.
That is precisely what I am trying to understand, because the initial rejections were addressed, the app was approved, and all four subsequent updates passed review without rejection.
#Apple #AppleDeveloper #AppStore
@AppleSupport@Apple #IndieDev
#BuildInPublic
ANTHROPIC IS CRACKING DOWN ON VIDEO GAME REWRITES 🚨
Claude Code picked up a new rule around Oct 27, sent from Anthropic’s servers under a flag called "tengu_heron_brook". There’s no setting to turn it off.
The full rule: “Do build original games, games in a genre, and games from the user’s own designs and assets. Don’t build a recreation of a specific existing game, even if it is renamed or called original.”
Is this the end of game rewrites, modding and everything in between?
Hey @johnternus hope this gets through your filter.
Microsoft did something stupid like this when I worked there.
Steve Ballmer apologized to the company and fixed the problem.
He got my loyalty by doing so.
Hope you can pull inspiration to fix this problem from his leadership.