Dorian @Statickzz_

me developing godlike reaction speed to ping the enemy ward before my teammates for +5 gold:

Minimax H3 Max has generates video faster than you can watch it so I hooked it to a twitch livestream! Now you can watch infinite interdimensional cable - link to the stream below

@nnnllllaaaaa C'comme le chicken rouge du 129 peut etre

this goes unbelievably hard wtf

@elliot_sror @TiboInShape Il a un très bon cardio il a déjà partagé des courses sur son compte pour le coup

Which model should you run on the iPhone 17 Pro? Announcing our new intelligence and inference testing for small models on mobile devices: independent measurement of how capable small models are in typical on-device tasks, and how they perform on popular phones - in partnership with @liquidai We have partnered with @liquidai to deliver mobile device inference benchmarking, covering a range of models in 4-bit or lower precision on the iPhone 17 Pro and Galaxy S26 Ultra We’re publishing our phone-scale intelligence evaluation results in combination with @liquidai's inference performance benchmarks to give users and developers a holistic view of how small models are performing on phones Inference benchmarking is conducted in a controlled environment using Liquid AI’s inference benchmarking software, which Artificial Analysis has examined and is open-sourced on Liquid AI’s GitHub. Results cover end-to-end generation time, output speed, peak memory usage and other metrics. The inference benchmarking app, ‘Pipette’, is available to download for free on iOS and Android, allowing users to test a variety of models on their own devices We are ranking phone-scale model intelligence based on each model’s average score in five evaluations chosen for the task-based work these models do in practice: BFCL, IFBench, AA-Omniscience, GPQA Diamond and MATH-500. These evaluations are run by Artificial Analysis using our independent methodology. By default, we limit models to 16K context on each of these evaluations, representing the lack of memory space for significant KV cache on mobile devices. This leads to some intelligent but verbose models dipping in relative score - they were not designed for the constraints that phone memory imposes on token use We are defining our portable device category as including models that fit within 8 GB of memory after quantization, including KV cache, at 8K context We expect both the intelligence and inference benchmarks to evolve over time, as new models, devices, inference frameworks and quantization techniques are released. Our pages will remain up to date with these new additions Initial results: ➤ Nanbeige4.2-3B and LFM2.5-2.6B share the top average evaluation score at 63 (with a 16K context limit), ahead of Ornith-1.0-9B at 62 and Qwen3.5 9B (Reasoning) at 61. LFM2.5-2.6B achieves its score more efficiently: on an iPhone 17 Pro it answers a standard 1,024-token prompt in 8.0s using 2.3 GB of memory, against 21.4s and 4.0 GB for Nanbeige4.2-3B and 25+ seconds and 6.9 GB for the two 9B models ➤ The 16K context limit shapes the leaderboard: as an example, Qwen3.5 9B (Reasoning) spends 74.5M output tokens across one pass of the benchmark set, hitting the 16K limit on 29% of its generations and landing in fourth place overall. With the limit raised to 64K, Ling 3.0 Tiny takes first place with a score of 66, ahead of Nanbeige4.2-3B (65), Qwen3.5 9B (Reasoning, 64), and LFM2.5 2.6B (64). But a 64K window does not fit in mobile phone memory, and at 55 output tokens/s on an iPhone, generating 64K tokens could mean a 20+ minute wait and a lot of battery use. This is why our primary results are capped at 16K, but we're also publishing a set of results capped at 64K, and another capped at one minute of generation time ➤ The speed-intelligence Pareto frontier is short: six models are unbeaten on both intelligence and speed on an iPhone 17 Pro: LFM2.5-230M (27 at 0.9s), MiniCPM5-1B (45 at 2.9s), LFM2.5-8B-A1B (58 at 5.7s), Ling 3.0 Tiny (59 at 5.7s), LFM2.5-2.6B (63 at 8.0s) and Nanbeige4.2-3B (63 at 21.4s). LFM2.5-8B-A1B and Ling 3.0 Tiny are mixture-of-experts models that activate ~1B parameters per token, which is how they answer in under 6s with 8B-class weights ➤ Leading models have opposite strengths: Nanbeige4.2-3B is the most balanced (76% on BFCL, 96% on MATH-500, 67% on GPQA Diamond); Qwen3.5 9B (Non-reasoning) is the strongest tool caller (77% on BFCL) and scientific reasoner (79% on GPQA Diamond); LFM2.5-2.6B follows instructions best of any model measured on the iPhone (59% on IFBench), clears 90% on MATH-500 and hallucinates far less on AA-Omniscience (79% non-hallucination, against 33% for Nanbeige4.2-3B and 24% for Qwen3.5 9B (Reasoning)) More details below in thread ⬇️

@aniketjart @usecrayon looks cool!

@Sdotsol @123321mario En revanche, vu l'état du site, je peux t'assurer qu'il n'a aucune base technique. 2/2

@Sdotsol @123321mario Oui tu as raison, le problème du terme "vibecoding" qu'utilise l'OP, c'est qu'il englobe à la fois des devs compétents qui n'écrivent plus une seule ligne de code à la main, et d'autres qui n'y connaissent absolument rien. 1/2

@Pioustone3 @Foxyte17 Commencer quelque part, ça veut dire apprendre les bases. Si je ne connais rien à la plomberie, je ne vais pas vendre des tuyaux percés aux gens. Il n'y a aucune jalousie à pointer du travail bâclé et non conforme, mais ravi de voir que la médiocrité a trouvé son public : toi !

@Sdotsol @123321mario Exactement, mais pour conduire un engin de chantier, il faut un permis et savoir lire un plan. L'IA décuple la vitesse, mais sans les fondamentaux, elle décuple surtout les erreurs

@123321mario Merci, j'en ai ras le cul de voir passé son site de merde vibecodé à la fois sur le design mais aussi toutes les fonctionnalités

JUST IN: LinkedIn users are scrubbing “DEI” mentions from their profiles at historic rates.

@nnnllllaaaaa 10h56 c'est le pire tweet que j'ai lu ojd pour l'instant

@seblatombe La honte!

I can make you see colours that don’t exist!

🚨 ALERTE – PIRATAGE MASSIF DE L’ÉDUCATION NATIONALE Des millions d’élèves, enseignants et personnels seraient concernés. Après la DGFiP, le même hacker revendique 43 Go de données, soit près de 346 millions de lignes couvrant plus de 20 ans. Noms, prénoms, dates de naissance, adresses, téléphones, e-mails, données scolaires, affectations, grades et informations administratives seraient exposés.

@Pvblitoz la cam de fin de game me termine

@yunspizz @Joordangue Sam mérite une chance