Hey ! Dans Le Point de Polgara, on discute avec Olivier Guillo et @simkamil de l'organisation du Festival d'Rôles de Jeux qui se déroulera en septembre prochain à Senlis #jdr
https://t.co/B21lMSHA4y
https://t.co/SjtEWqPaRd
🌶 Un Ramen de plus en plus épicé, généré par chatGPT 🍜
(Je ne me lasse pas de ces prompts trouvés sur reddit)
@jermyland J'espère qu'ils sont moins chauds au Japon ! 👹👇👇
(1/10) 🍜🌶 Pour l'instant c'est tranquille et appétissant
Nouvelle vidéo 👉 Dark Vador contre la clope ! La nouvelle tendance pour arrêter de fumer : le laser anti tabac. Des cabinets de laser anti tabac ouvrent partout en France. Les prétentions sont, encore une fois, incroyables... Merci pour vos partages😘 https://t.co/ztxPjvbbp1
Google Play news: New accounts must test apps with 20+ people for 2+ weeks before applying for production access.
TLDR;
- Meant to stop fraud and abuse, ensure higher-quality apps in the store
- From 0 days (immediately publish) to 14+ days to get a new app into production
- Personal accounts only (hobbyists, students, semi-pro devs), not organization accounts (businesses)
- Hinting at slower app review times
My take:
This will irritate developers, but their reasoning is fair (combating abuse/fraudulent apps) and it's a good thing to push devs to test their apps more and with real users. Of course, some will find ways around this but that's to their app's detriment.
Like launching on the App Store, devs will need to plan their launches carefully to ensure wiggle room if the app is rejected. Thankfully, this doesn't affect business accounts, just hobbyists.
The mention of slower app review times is a bit concerning. The speed and ease of shipping new and updated Android apps has always been a pro over the Apple App Store processes. That said, check out @useappflow's Live Updates feature to bypass review times if needed!
Holy shit Insomnia actually just wipes all the data you had locally with the latest update if you refuse to sign in with an account 😳
Didn't think they could one up Postman's egregious user hostility, I'm almost impressed
@GGmilgram Énorme vidéo ! Ça m’a rappelé quand je faisais du TaiChiChuan… à l’époque je ne croyais pas au 1re degré à ces démos; mon raisonnement : mix subtil entre ancrage au sol, renvoyer la force de l’adversaire, + hypnotisé par son maître. Mon prof restait pragmatique sur le sujet.
Génial ! Justement je me sers souvent du blocage d’URL pour tester la robustesse des applis web, et je me disais « ça serait bien de pouvoir surcharger les réponses » ! Eh bien c’est pour bientôt !
🤩 [1/4] Coming soon in @ChromeDevTools - You can overrides API response (Fetch/XHR) and more!
Imagine you can mock APIs in frontend without waiting for the backend changes!
Not only that...
✨ @Angular v16.2 is out ✨
- afterRender and afterNextRender ♥️
- Binding inputs of NgComponentOutlet
- more Vite for the CLI 🚀
👉 Check out our blog post!
https://t.co/rIRAw30Njo
Exactly this.. this is the future we are going for.
it all becomes a bloated protocol to appear "professional".
The sender don't want it, the reader don't want it. but it is agreed upon in the domain of business that this is how you communicate...