The actual requirement is not: a centralized console where macOS antivirus updates are pushed to all user devices.
We take security very seriously but this is not the way.
899 karma · joined July 26, 2010
We take security very seriously but this is not the way.
They want evidence of the antivirus updates for our macbooks being centrally managed by some tool (quote-unquote: WSUS). I get this is how some enterprises operate, but for our small shop we're talking a handful of macbooks that have access to even anything. And even so the people who operate those are contractually obligated to run a very tight ship (encrypted disks, auto updates (which includes XProtect, apple's native antivirus so to speak), 2FA on all services, etc), tunnelling on unprotected wifi, etc.
We sent evidence of all of this. But they really want centrally managed antivirus for our macbooks.
I wish we had an easier time talking about ideas with a little more detachment.
Could be changed tho, Nix leadership should brainstorm how to make this an attractive thing to sponsor. Feature name prominently on site, conferences, social media, even CLI(?).
While big tech is firing small tech is hiring. We are seeking a Senior-level Node.js Backend Developer to join our team and help us continue to scale, modernize, and improve our service. As a Node.js Backend Developer at Transloadit, you will have the opportunity to work on a variety of projects, including building and maintaining our API, improving our file processing pipeline, and open source.
Transloadit allows you to receive, transform, or deliver any file with our API without owning or managing infrastructure. We are bootstrapped and 100% free of Venture Capitalism. We believe in empowering our team members to create the circumstances and working hours that work for you. Check out our engineering blog to learn more about our company as well as real-world use cases with Transloadit's API.
Responsibilities:
* Develop and maintain our Node.js API
* Improve and optimize our file processing pipeline
* Collaborate with the rest of the team to identify and solve problems
* Write clean, maintainable, and efficient code
* Stay up-to-date with the latest industry trends and technologies
* Strong experience with Node.js
* Strong debugging skills
* Excellent communication skills (English) and the ability to work well in a remote team
* Willingness to be on call for incident response
Even for remote staff, there are many more human ways of informing someone they are out of a job than shooting an email. Am I the only one who feels that way? Is it actually better to get an email an process the blow in async? Genuinely curious as I didn’t see this comment yet.
React, Hooks, Node.js, TypeScript, SWR. Are these right up your alley? Transloadit is hiring a developer to work on our website (mostly front-end work, some back-end tinkering may not be ruled out). Remote, freelance, 32h+/week, $50/h. You'll be part of a highly skilled team and have plenty opportunity to work on our open source projects as well (uppy.io, tus.io). We're thin on process and management, it's mostly github issues & slack. That may not work for all, but well for some, so worth mentioning. We have an open, friendly & curious culture.
If you are interested please DM a tweet-sized motivation and any relevant links to @kvz
https://transloadit.com offers similar composable workflows in a single request, and supports more file types besides PDFs.
Disclosure, I am a founder :)
* excellent English
* Node.js & command line experience
* emphatic, patient, curious, helping others motivates you
* 100% remote
* $40/h
* 32h/week, flexible but ±4h overlap with CE(S)T office time
Transloadit is a file uploading and encoding service. Launched by three developers who met through open source in 2009, customers have been loving our API and top-notch support ever since. We're an open, remote, independent, small team, with a big footprint (or so I believe). Our engineers are changing how HTTP works (tus-v2), and wrote the number one open source file uploader (Uppy). We were the first to run Node.js in production, have shaped much of its early ecosystem (node-formidable, node-mysql), and employ a member of its Technical Steering Committee. GitHub partners with us to offer free transcoding services to students and teachers, and we partner with core contributors of FFmpeg, Nix, Prometheus and Jekyll intimately to advance the state of the art. Roughly 80% of our revenue is allocated towards open source, and we keep all of these efforts afloat with our commercial service: a REST API that developers integrate with to make light work of bulk importing, encoding, resizing, recognizing, rotating, or file thumbnailing – all fully automated. Our paying customers sign up, read docs, and integrate themselves, but, sometimes they run into issues, and this is where you would come in. You'll work closely with them, and our developers to ensure smooth onboarding, that any issues are filed and solved correctly and swiftly.
We're looking for someone with coding experience, but enjoys balancing that with a lot of human interaction (be it through text), helping them succeed, and chooses tech support as a career.
If this sounds interesting to you, please check out the full vacancy here: https://transloadit.com/blog/2022/01/job-support-engineer/ which also has information how to apply.
- better cli (previously was a myriad of shell scripts you’d just had to memorize, and would do the non-typical thing by default if you didn’t pass many arguments)
- flakes (will make nix more nix. Currently we need checkouts of entire nixpkgs to run two versions of the same software alongside, it is my understanding that with flakes this will become more easy and lightweight to pull off)
- markdown docs
This last one shouldn’t be understated I feel. Docs have always been a pain point with Nix to the point where insiders joke about it with an affection almost. I feel due to many core contributors having academic backgrounds and the generally steeper learning curve with Nix, they have been susceptible to embrace “quantifiably superior documentation formats”, blindspotting the effects of markdown being the lingua franca lowering the barrier to entry for people contributing fixes by so much—perhaps because this is less easy to quantify, and perhaps less easy to appreciate for folks that were okay to learn Nix in its current state the first place.
Anyway, thanks everyone for putting in the hard work, this will pave the way to a bright future for Nix I am sure.
Now some Ubuntu releases and issues and HN threads like these later, I’m ready to give it a go. Will be installing it this holiday
Tesla is a software company and probably has a lower chance of getting hit due to expertise and funds being poured into security (even tho not infallible as this post shows), but there’s a race to the bottom and soon enough Car companies that couldn’t pull of decent navigation will have some form of computer-controlled-steering as stockholders are looking at Tesla stock price and breathing down their necks.
I have been worrying about this for some time, even tho I am also a tech lover and Tesla driver. was thinking of writing a blog post about this, but seeing this comment, maybe it isn’t a new thought and everybody is already aware of this risk.
I think you are right about medical personel. But also: if you make everyone crash around rush hour, you take out a significant share of the working population. And how do you clean up the infrastructure to let trucks and ambulances through again. Not to mention the catastrophe of cars crashing into stores and pedestrians in city centers.
But this is (way) less than 1% of code and typically performance is not the problem with Node, even for our use case. ~Everything we build feels fast the first time. If on rare occasion it does not, it’s a matter of rearranging the building blocks, not swapping them out for something else entirely.