quave

Patched Node.js (24.22.1) images for Meteor 3.5.3 while we wait for an official Meteor release Node.js released security fixes on October 21 for Node 22, 24 and 26: nodejs.org/en/blog/vulnerabi… They fix four high-severity issues, including: - a Brotli decoder out-of-bounds write that can lead to remote code execution; - TLS certificate hostname-verification bypasses. The fixed versions are 22.23.4, 24.22.1 and 26.12.1. Meteor bundles its own Node. Meteor 3.5.3 ships Node 24.15.0, which is affected, and there's no Meteor release with the patched Node yet. At Quave we maintain the zcloudws/meteor-node-runtime and zcloudws/meteor-node-mongodb-runtime Docker images. We know a lot of Meteor developers use them outside Quave ONE, in their own Kubernetes clusters, VMs or CI. So we published patched versions for everyone, not only our customers. What changed These are the same images, with only the node binary replaced by the official Node.js 24.22.1 build: - The build checks the Node.js release signature against the official nodejs/release-keys and checks the binary's SHA256. - npm, MongoDB tools and the startup scripts are untouched. - Node stays on major version 24, so native npm modules keep working without a rebuild. New tags zcloudws/meteor-node-mongodb-runtime:3.5.3-node24.22.1 zcloudws/meteor-node-mongodb-runtime:3.5.3-node24.22.1-with-tools zcloudws/meteor-node-mongodb-runtime:3.5.3-node24.22.1-with-tools-ffmpeg zcloudws/meteor-node-runtime:3.5.3-node24.22.1 zcloudws/meteor-node-runtime:3.5.3-node24.22.1-with-tools zcloudws/meteor-node-runtime:3.5.3-node24.22.1-with-tools-ffmpeg How to use Change the FROM of your runtime stage: before: FROM zcloudws/meteor-node-mongodb-runtime:3.5.3-with-tools after: FROM zcloudws/meteor-node-mongodb-runtime:3.5.3-node24.22.1-with-tools You can confirm with node -v inside the container. The regular 3.5.3 tags are unchanged. They still match exactly what Meteor ships, which is what Meteor's tests run on. These hotfix tags only bridge the gap until Meteor releases with the patched Node; when it does, update Meteor as usual and go back to the regular tags. Other Meteor versions Right now we published 3.5.3 only. If you need another version (for example 3.4.x or 3.3.x, which use Node 22), open an issue in the repo and we'll publish it. The build scripts are in the same repo under meteor-tools/node-hotfix/ if you want to check how the images are built, or build them yourself: github.com/zcloud-ws/zcloud-… We already run Quave ONE in production on these images.

Onboarded a new team last week. First thing I asked: how do you monitor your apps? Answer: We don't 8 months in production. No alerts. No metrics dashboards We deployed them on Quave ONE. Monitoring was already running. They didn't have to configure anything CPU, memory, request rate, error tracking, latency - all there by default This is how it should work

Real Example of Claude Usage for My Personal Project Binge Watch: Fix Notifications for Auto-Skipped Videos > BTW, I didn't type any of this. I used @WisprFlow. > Use it, otherwise you'll be too lazy to type and will have bad prompts and bad responses due to laziness. First prompt: > Right now, what is happening is that I have two features that are not working well together: 1. Auto skip configuration (e.g., to skip short videos) 2. Notification So if I'm skipping automatically something, of course I don't want to be notified by that because I'm skipping it completely. We should only notify after the skip process has run. Analyze both codes and ask questions to me if you have any doubts. Second round: ⏺ Analysis Complete I've found the issue! Here's what's happening: Current Flow: 1. Auto-skip logic (videoService.js:88-93): When a video is detected as a short AND autoSkipShorts is enabled, it sets the status to SKIPPED 2. Notification logic (videoService.js:108-109): All new videos (including auto-skipped ones) are added to newVideosForEmail 3. Email/Notification sending (videoService.js:254-295): All videos in newVideosForEmail get notifications sent, regardless of their skip status The Problem: The auto-skip filtering happens before adding to the notification queue, but the video is still added to newVideosForEmail regardless of whether it was auto-skipped. This means skipped videos still trigger notifications. Questions for you: 1. Notification scope: Should we prevent notifications for ALL auto-skipped videos, or only for specific types (like shorts)? 2. Existing skipped videos: Should we also prevent notifications for videos that were manually skipped by users, or only auto-skipped ones? 3. Batching impact: When we filter out skipped videos, should we still send batch notifications for the remaining videos, or does this change how you want batching to work? The fix would be to filter newVideosForEmail to exclude videos with status === VideoStatus.SKIPPED before the notification logic runs around line 254. ⏺ Update Todos ⎿  ☒ Find auto skip configuration implementation ☒ Find notification system implementation ☒ Analyze interaction between skip and notification features ☒ Identify where notifications should be prevented for skipped content > Ok, I will reply one by one: 1. Yes for all skipped videos. 2. Doesn't make sense to be possible to prevent a notification for a video that is skipped because the video is already there, so it was already notified. Only for all to skip it once. 3. It doesn't change anything about the batching notification system for the other videos. And it worked. Whole conversation on the next tweet.

We have special positions for senior developers and tech leads that require deep knowledge of Node.js and MongoDB or React and Tailwind. If you only know back-end but not front-end, you need to be willing to learn, and vice-versa. Here at Quave, we believe all developers should be able to build a feature from back-end to front-end and handle all the details when consuming designs from designers. So it's really important to be good at both back-end and front-end. But if you're great in one of those areas, we're willing to wait for you to step up in the other areas. You will work with top talent around the world. We really have amazing people working with us, as human beings and also as technical individuals. Our work environment is challenging but friendly where we encourage people to study a lot, to deliver a lot, but to keep working the same hours to have a life and to enjoy friends and family. We don't provide empty feedback or fake compliments. We tell the truth looking for everyone to step up along the way. Our goal is to be better than ourselves at the organization level and also individual level. We are not in a war, we are not in a fight, we are doing our best and improving daily. Our north star metric is how much we learn. Our standard process is to do the code challenge first, and then we talk to you if you do well or provide feedback if you don't. But I'll open an exception here: if you want to talk to us first, you should write a really good cover letter and send it to our hiring email that you can find in the first comment. It needs to be a personalized letter for Quave, so read our website, read our job descriptions so you start to understand how we think. To wrap up: we have a ton of opportunities with AI everywhere, starting from the tools we use daily to the features themselves that use AI. We look for people with high QUAlity and VElocity. I don't think you will want to leave us but if you do after some time working with us you will be much better prepared for this new way of coding and creating digital products. > Please help to spread the word, mark your friends on the comments ;)

You are no longer required to use Meteor.js in our code challenge. Meteor.js remains our recommended stack and setup, but you can now customize it while respecting certain restrictions. Please refer to our updated README: github.com/quavedev/code-cha…

✨ Tech Lead and Senior Developer positions at @quaveDev Mention the best developers you know in the comment, please 🙏🏻 We have great opportunities available, and we are looking for talent. TL;DR: If you can't code using MongoDB, Node.js and React, this job isn't for you. Meteor isn't a deal-breaker as it's based on Node.js and JavaScript. We'll guide you in learning Meteor packages and problem-solving approaches later if necessary. You should be able to quickly build simple apps with MongoDB, Node.js, and React. We're looking for highly productive coders who can deliver working code much faster than average. You must be fluent in Portuguese and comfortable with English. While you'll have 6 months to improve your English communication skills, you'll eventually need to handle English-speaking clients independently. Also, you should be able to produce great code much faster than average. Plus, you should shine in environments where the current codebase is not good or even in different languages and frameworks that you are not familiar with. You should be productive with AI tools for developers like Cursor, Claude and more. We don't work coding like in 2022, we believe in the power of AI to make us more productive and help us deliver great results because we know how to use the tools to achieve that. We use our intelligence to extract the most of AI tools. If this doesn't describe you, please don't apply. Our tech leads code daily and are hands-on most of the time. We want to maintain this profile for our leaders. Our senior developers spend most of their time coding while helping the team deliver great results. If you are this fast coder, please go to our website footer and click "Careers - Open Positions!"

Quave Cloud: Tailored to You Perfect for businesses spending $2k+ monthly Uncover the perks of Quave Cloud Custom👇🏻

zCloud will be renamed to Quave Cloud. A natural evolution of our brand, keeping everything you love Why? Quave is our company (11 years old) and has always been the entity behind zCloud. We want to leverage our established brand and unify everything under one name. Nothing will change - the team remains the same, we're still profitable, and we continue to operate independently without investors. The only changes are to our branding and name. This transition will happen in the next few days. However, it won't affect your apps or any configuration URLs you currently use. We'll update our website and app, but all old links will continue to work or redirect to the new ones, so there's nothing you need to worry about. Here's a quick story: zCloud was initially red and yellow. The name wasn't my idea - it was Edimar's. He had already created the name, logo, and a basic version of zCloud. When we decided to make it a Quave product, we reviewed almost everything from scratch. Until then, it had been Edimar's hobby project to explore ways to offer fair deals for companies and developers running on any cloud, anywhere in the world. As many of you know, Edimar is my partner at zCloud and our Principal DevOps and Business Partner. Though we're retiring his suggested name, it's important to share this history of why we've been called zCloud until now! I want to thank Edimar for his amazing effort here - it's clearly paying off as zCloud grows by double-digit percentages every month. We're thrilled, and this rebranding is something we've wanted to do for months. Now is the perfect time, as it would become more challenging to change at a larger scale. This long message is really just to share this exciting news - we're thrilled about zCloud's current state and even more excited about its future. You should celebrate with us, as you're part of this journey. If you'd like to share a message, testimonial, or write a case study with us, please reach out - we'd love to hear from you! Have a great weekend and enjoy time with your loved ones. Below you can see our first official logo, our first headline and our first logo idea.

Are you using LLM for complex reasoning or math problems? Be careful. Watch this video and read both papers youtu.be/tTG_a0KPJAc?si=NEB5…

Quick reminder of a great founder playbook: 1. Get in the weeds 2. Question everything 3. Constant urgency 4. Motivate talented people And a quick piece of advice for leaders: your job is to do the hard and uncomfortable part

Amazing to partner with @MervinPraison in this video. He published the agent to answer the calls for you on @zcloudws If you are looking for a place to host your AI solution, get in touch

At @QuaveDev, we judge code challenges on merit alone When reviewing submissions, we: • Don't look at names • Don't check resumes • Don't browse LinkedIn profiles Our focus? The code itself and the UI delivered. That's it Great code is our primary filter. If your submission shows technical excellence, you will likely move forward to an interview. There, you can showcase your other qualities We believe in giving everyone a fair shot based on their work. Your code speaks first, and it speaks loudest

New use case for @WisprAI unlocked today When reviewing code challenge submissions, I use Flow to dictate my impressions into our feedback spreadsheet. Later, I dictate my final feedback and paste it into Raycast AI to polish the English before sending it to the candidate. This approach gives specific, genuine, and personal feedback without wasting time typing. I'm just speaking it.

At @quaveDev, our beliefs shape our work culture: • Reliability is vital for everyone • No babysitters, no traditional managers – we have leaders • Flexible work hours and locations • Family-friendly environment • Focus on results, not timesheets • Share interests and hobbies with colleagues • Continuous learning and growth • Positive, cheerful workplace • Small, tight-knit teams (2-4 people) We believe these principles create a better work experience for all. They allow us to deliver great results while enjoying what we do. I always say: "If you are at Quave you are reliable, never question yourself. When we ask something to you, that is really what we want to know, no hidden messages" Do you feel everyone trusts you in your work?

📢 Feedback wanted on zCloud Enterprise! 🚀 We've updated our Enterprise plan page and need your input. Here's a quick overview: 🔹 Fixed license pricing: $400/mo for up to 25GB RAM, $700/mo for up to 100GB RAM 🔹 Provider flexibility: Pick your cloud provider or let us suggest 🔹 Cost optimization: Use your cloud credits or special deals 🔹 Full DevOps management 🔹 Support for code and DevOps 🔹 Advanced monitoring (Grafana and Prometheus) 🔹 User-friendly interface with rollback and config history 💡 Goal: Top-tier PaaS features at 70-90% less than Heroku, Vercel, or Meteor Cloud. We've included a case study on our Paris 2024 Olympics work! 🙏 Your feedback please: 1. Is the value clear? 2. What features should we add? 3. Does the pricing work for enterprise clients? 4. Anything confusing? BTW, we've been selling this privately for a while. It's a great deal, but harder to explain on a page than in a call where we know the company's specific needs. Your insights will help improve our offering. Don't hold back - all feedback welcome. Thanks!

Am I crazy to expect Tech Leads to code every single day? I've added this to our tech lead position to avoid wasting time on interviews: If you can't code using MongoDB, Node.js and React, this job isn't for you. Meteor isn't a deal-breaker as it's based on Node.js and JavaScript. We'll guide you in learning Meteor packages and problem-solving approaches later. For now, you should be able to quickly build simple apps with MongoDB, Node.js, and React. We're looking for highly productive coders who can deliver working code much faster than average. If this doesn't describe you, please don't apply for this position. Our tech leads code daily and are hands-on most of the time. We want to maintain this profile for our leaders. If you are this fast coder, keep reading it!

I was all set to go to the Olympic Games with my wife in Tokyo But something huge happened... pandemic! We lost all our tickets. A year later, same story: Olympic Games without spectators This year in Paris, we didn't plan to go, but at least zCloud was part of the event somehow ALLOHOUSTON and zCloud joined forces to create a special cloud setup for the Paris 2024 Olympics. Their goal was to ensure smooth operations for companies operating in Paris, France, during the event zCloud built a custom cloud region in Paris using OVH Cloud. This setup made the apps run fast and kept data secure within France, which was ideal for this major event ALLOHOUSTON developed two main tools: "joptimiz.green" for vehicle and activity registration and control and "Itineriz" for traffic rules and for computing the best available route given the event constraints. These apps needed to handle users in real-time zCloud handled the easy deployment process, offering the same experience for all regions, both public and private. This let the ALLOHOUSTON team focus fully on the apps. Meanwhile, zCloud took care of all DevOps tasks, including setting up custom machines for the apps zCloud seamlessly enabled high availability and horizontal scaling for these tools. As a result, 45,800 vehicles were registered and validated by Joptimiz, and the tools received more than 150,000 visits