DevKage retweeted
Today is Flame's 9th birthday! 🥳🥳
A contributor opened a PR with an easter egg to our website, see if you can find it...
In other news, Flame v2 is getting closer and closer to stable.
DevKage retweeted
After 7 years we moved Flame's examples to @widgetbook_io! We should have done this sooner... 😅
Check the examples out at: examples.flame-engine.org
DevKage retweeted
In Flame v2 you'll be able to have Flutter widgets as parts of the Flame component tree, with working priority (z-index) and everything! 😃
DevKage retweeted
Are you using Supabase + Flutter?
V3 of the supabase_flutter SDK is now in beta and we would love feedback.
The new v3 version has full type safety and lots of other goodies. 😎
If you're interested in participating in a feedback group you'll also get some swag. 😏
DevKage retweeted
Indian telecom Reliance is sabotaging access to Telegram for millions of users OUTSIDE India (including the UAE) via a rogue method called BGP hijacking.
The sabotage seems intentional, as Reliance has ignored multiple reports.
This may be part of a competitive war, as Reliance is partially owned by Meta — the company behind WhatsApp.
Network operators are advised to reject unauthorized BGP announcements from Reliance (AS18101) to prevent route hijacks and ensure stable Internet access for their users.
Such abuse of global Internet routing is alarming. I wouldn’t be surprised if Reliance/WhatsApp were also behind the recent lobbying effort to ban Telegram in India.
DevKage retweeted
India’s IT ministry banned Telegram for one week because some users shared leaked exam questions.
This punishes 150M+ ordinary Telegram users in India — not the insiders who leaked the exam materials.
And the ban hasn't stopped anything. The leaks just moved to other apps.
Statement : Shutting down Telegram is a band aid solution and is a disproportionate answer to exam fraud
The Internet Freedom Foundation objects to the directions announced today in the National Testing Agency's press release on action against the Telegram platform. On the NTA's recommendation, the Ministry of Electronics and Information Technology has, under Section 69A of the Information Technology Act, 2000, restricted access to the whole of Telegram in India until 22 June 2026, and has separately ordered the platform to switch off message-editing for every Indian user until 30 June 2026. This is a blunt, nationwide measure aimed at the conduct of rampant fraud rackets, and on the Government's own admission is constitutionally incompatible.
At the outset it is important to note that Section 69A and the Blocking Rules of 2009 framed under it allow the Government to block access to specific “information” on a computer resource. They do not extend to switching off an entire intermediary, still less to ordering a company to redesign its product by removing a feature for a whole country. In Shreya Singhal v Union of India, the Supreme Court upheld Section 69A because it is narrow and hedged with procedural safeguards. Reading it to authorise shutting down a platform that lakhs use is an overbroad restriction by the NTAs own admission. For the message-editing direction the release identifies no source of power at all. If one exists, the order must say so.
The release argues against itself
A restriction on access has to be the least intrusive measure that achieves its aim as per the constitutional test of proportionality laid down in Justice K.S. Puttaswamy v. Union of India (2017) and applied in Anuradha Bhasin v. Union of India (2020). The NTA's own narration shows the block fails its nodal agency, the release says, “has secured the prompt take-down of a substantial number of Telegram channels, groups and bots”, and this targeted work “is the reason the harm caused by these rackets has been contained to the extent it has”. If channel level takedown contained the harm, the case for a blanket block collapses and hence the Government has reached for a heavier tool while conceding that a lighter one was working. The collateral cost sits on the record too as noted in the press release. The block, the NTA accepts, “affects lakhs of citizens who use the Telegram platform for legitimate personal, educational, professional and informational purposes”. The release also says there is "no such paper available outside the secured examination chain" and that “the security of the examination is unaffected by the action taken”. If the exam is secure and no leak exists, what is being suppressed is rumour, and rumour cannot justify closing a platform when specific blocking and criminal prosecution remain available.
Students use of Telegram
The block of telegram is reactive and ineffective and will punish ordinary users instead of addressing the systemic source of exam leaks. This blocking comes in the final days of NEET preparation, when thousands of students depend on Telegram for study groups, doubt-clearing, and shared resources. Also, it is important to consider that the source of exam papers leak will occur from inside the system, among insiders and across the printing and logistics chain, with the platform being the most downstream channel for distribution. Hence, switching off Telegram, is merely a deflection from the repeated failures that will continue while media attention is directed towards this Telegram ban.
Lack of transparency
At present only a press release from the NTA has been provided, which recommended the block but the reasoned order of MeitY, the authority that issued it, has not been released. The Anuradha Bhasin decision requires that orders restricting access be published so they can be tested in court. Here the order, and the reasoning of the committee behind it, stay out of view, and we do not know whether Telegram was heard at all. An announcement of a block is no substitute for an order the affected party can challenge.
Blunt to enforce and very easy to evade
Usually, app-level blocks run through IS-level DNS and IP filtering. They are over inclusive, sweeping in lawful use, yet simple to evade as a determined exam leak racket moves to a VPN or a mirror within minutes while ordinary users lose the service for a week.
We ask the Government to:
1) Publish the MeitY Section 69A order and the NTA recommendation behind it, with reasons;
2) State the legal basis for the message editing direction, or withdraw it;
3) Confirm whether Telegram was given a hearing under the Blocking Rules, and place the committee's record before any court that hears a challenge; and
4) Lift the platform-wide restriction and rely on the targeted takedowns the NTA itself credits with containing the harm.
We emphasise that the NEET (UG) 2026 re-examination is worth protecting and it concerns the future of lakhs of aspirants. It requires securing the entire process of examination rather than reaching for purported band aid solutions that instead cause more harm. The State cannot switch off a service used by lakhs to answer the wrongdoing of a few, and cannot do it through an order no one affected is allowed to read. On its own facts, the Government has done both.
New Delhi, 16 June 2026.
DevKage retweeted
“What’s the point of 3D graphics without 3D physics?”
That’s the question me & @luanpotter27 kept asking ourselves.
So... we are building a whole new set of packages to bring 3D physics into the Flutter💙 & Flame🔥 ecosystem!
PS: keep an eye on the Flame Engine's GitHub 👀
DevKage retweeted
Split screen 3D games natively in Flutter? No problem for Flame3D! With the same API that you already know and love from Flame🔥
Maybe I should submit a talk to @FlutterNFriends on how we have made all of this possible and teach others how they can build their own 3D games
DevKage retweeted
Don't miss out on the FlameJam that starts this Friday, we have amazing prizes! 😍
For example a @FlutterNFriends ticket, an amazing modular console device (Comet) from @mecha_systems and of course Dashes! 💙
We have a new prize for the winning team of the #FlameJam2026, a @mecha_systems Comet device, and it can of course run Flutter & Flame! 🔥
"Open Modular Linux handheld designed for dreamers, tinkerers and builders." 😍
#FlameJam2026 just escalated 🔥
We have a new prize for the winning team of the #FlameJam2026, a @mecha_systems Comet device, and it can of course run Flutter & Flame! 🔥
"Open Modular Linux handheld designed for dreamers, tinkerers and builders." 😍
DevKage retweeted
Flame reached 2500 closed PRs today! 🥳
PS. Don't miss our game jam in a few weeks, no previous experience needed.
DevKage retweeted
Join Alba on another unforgettable journey and discover how she and Neva first met in the new DLC, arriving on February 19!
*Available for €2.99 on Xbox Series, PS4, PS5, Switch, Steam, and Mac App Store.
DevKage retweeted
Hey Flutter folks, It's time for FlameJam 2026! 🥳
Join us between 6-15th of March and create your very own game (link in the comments).
No previous experience is needed.
If you are interested in sponsoring prizes for the gamejam, please reach out😊
DevKage retweeted
This, my ladies and gentlemen, is
Build With Flutter.
#FlutterDev #Flutter #Dart #DartLang #GameDev #MathPorn #3dmodeling
Wouldn't be possible with huge inspiration and ground work from - @algebrandon @_eseidel @wolfenrain @SuprDeclarative @spydon @filiphracek @craig_labenz
DevKage retweeted
Love to see 3D in the Flutter space!
This, my ladies and gentlemen, is
Build With Flutter.
#FlutterDev #Flutter #Dart #DartLang #GameDev #MathPorn #3dmodeling
Wouldn't be possible with huge inspiration and ground work from - @algebrandon @_eseidel @wolfenrain @SuprDeclarative @spydon @filiphracek @craig_labenz
DevKage retweeted
Pretty disappointed in both @humble and especially in @GirlsWhoCode. Please teach girls how to code, don't push them into generative AI. That won't build their skills. Prioritize foundational programming skills and awaken their interest. "Tired of long days writing code"???
DevKage retweeted
Update 7 Released for Mesh2Motion! 🎉
✨ 20+ new animations available
✨ Root motion support for animations
✨ New head/body separation option for human
✨ Mirror animations options
Release notes: mesh2motion.org/news
Try it out: app.mesh2motion.org
Would love feedback






















