uponcoffee | 5 years ago | on: Show HN: Bunkerized-Nginx – Nginx Docker image secure by default
uponcoffee's comments
uponcoffee | 5 years ago | on: Show HN: Bunkerized-Nginx – Nginx Docker image secure by default
uponcoffee | 5 years ago | on: Combating abuse without backdoors
uponcoffee | 5 years ago | on: Proton 5.13: A Massive Update
uponcoffee | 5 years ago | on: Proton 5.13: A Massive Update
Succinctly, it's easier and cheaper to port games wholesale than it is to: build out yet another platform for developers to target, on board them, and on board consumers to this new console.
What steam has that consoles don't, are is massive preexisting library. The problem is it mainly targets windows. Their options for bringing this to the console market are either pay for windows licenses (which on top of hardware, would make them more expensive than the alternatives), or port in wholesale. Most console games get a pc (windows) port eventually.
So if they can get proton to a mature point, they'll be the defacto winner of the console wars.
uponcoffee | 5 years ago | on: Uninstall Nano Defender
As far as an NDA goes, that's signaling to the current open-source maintainer that something nefarious is afoot. How would an NDA work? The maintainer hands other their GH account for the new party to commit under? The extension suddenly goes closed source? The maintainer doesn't acknowledge the community at all and rubber stamps anything the new party wants to commit the repository?
It'd be far easier to publicly take over maintaince, do good for a month or so, then silently publish the malware. That was probably the best route here; the maintainer was going to donate most of the monry they received back to the Turkish developers if they did a good job) and they'd have passed the transitory wave of scrutiny from seasoned devs like gorhill.
uponcoffee | 5 years ago | on: Cloudflare One
Tailscale is ergonomic tunnel management//authentication. Which in itself is a great product, but it's not nearly as granular. Being able to restrict access based on identity provider, individual, etc is a must for a corporate solution.
One of Tailscale's selling points is the data isn't routed through their servers, just between peers. That's the opposite of Cloudflare; their value proposition is centralized granular control, no plumbing, just plug'n play.
uponcoffee | 5 years ago | on: Tables: Tracking work for teams
uponcoffee | 5 years ago | on: Tables: Tracking work for teams
uponcoffee | 5 years ago | on: Tables: Tracking work for teams
uponcoffee | 5 years ago | on: Tables: Tracking work for teams
Paraphrasing the video: Like sheets, but with structured data (columns define data types with relationships) and complex actions/triggers via bots.
Per your original comment, given Google's track record with customer performance//services being dead on arrival, I can imagine few here are interested in learning//migrating their workflow just to be locked out or migrating away not long after.
I'd link to the myriad of hn//twitter//medium posts used to get customer support through bad press, but I'm on mobile, I'll leave that as an exercise to the user.
uponcoffee | 5 years ago | on: How to Design, Build and Test Small Liquid-Fuel Rocket Engines (1967)
Simulating cooling channels//ablation for larger scale rockets is a major PTA though.
uponcoffee | 6 years ago | on: CDC declined to test new coronavirus patient for days, California hospital says
The point was that the cost of saving money is effectiveness.
Clearly, this isn't always the case, there is a difference between bloat/overpricing/unnecessary spending vs cut backs that hinder operation ability.
uponcoffee | 6 years ago | on: A billion medical images are exposed online
uponcoffee | 6 years ago | on: Nebraska farmers vote overwhelmingly for Right to Repair
They are incentized not to, new phones means profit for carriers and new hardware means profit for chip makers.
Maintaining old products costs money, not maintaining products saves money, planned obsolescence prints money
uponcoffee | 6 years ago | on: Brow.sh: Modem Text Browser That Supports CSS, JavaScript and Even WebGL
uponcoffee | 6 years ago | on: Cname cloaking, a disguise of third-party trackers
Even still filtering based on SNI will work for a long time yet. Yes, ESNI is on track to becoming to a standard but support for legacy devices/browsers means it to will rely on network tests for support - so it can also be disabled.
uponcoffee | 6 years ago | on: Deepfakes: MIT brings Nixon's Apollo disaster speech to life
True, but now they'll be able to drive any narrative with as much A/V 'evidence' as they want. Lies by omission or one sided reporting are dangerous in their own right, but challenging that is different from challenging fake evidence.
It's hard to say "It wasn't me" if you're on tape/film. You'd have to have experts argue over validity but the public doesn't have the attention span or trust to follow that. Deepfakes have the potential to be extremely damning/damaging to public image/reputation in a way that biased reporting never did.
uponcoffee | 6 years ago | on: Show HN: Workouts – Learn by doing real developer projects
uponcoffee | 6 years ago | on: New Catalyst Efficiently Produces Hydrogen from Seawater
The water cycle is self regulating, unlike other green house gases.
>> "However, water vapor does not control the Earth’s temperature, but is instead controlled by the temperature. This is because the temperature of the surrounding atmosphere limits the maximum amount of water vapor the atmosphere can contain."
The other non condensing gases, largely from man made sources, contribute to global warming and elevate the amount of water that can be vaporized per unit volume of air.
Cutting down on emissions by replacing oil based vehicles with electric/hydrogen fuel cell powered vehicles absolutely helps the environment. Cutting emission sources makes job of scrubbing the atmosphere of the green houses gases already present more achievable.
In regards to docker worldview, this project currently doesn't follow best practices.
And while I agree mostly with this statement:
> Surely all the complexity should be inside the container
The caveat being that complexity should be split up into separate concerns. Otherwise there's little difference between the host and container aside from an extra layer of abstraction.
For example, this repo should probably be split into several containers: cert management should probably be its own container, which a shared volume for certs); php should be rolled into its own container, and php files should reside there; logging shouldn't be handled at the container level; firewall concerns (namely fail2ban) probably should be handled at by the host, or in a container with appropriate permissions; etc