Readit NewsDeleted Comment
ldoughty commented on Kodak ran a nuclear device in its basement for decades popularmechanics.com/scie... · Posted by u/cainxinth
Ok but what about when it’s night time or cloudy?
Molten salt solar power doesn't care. It remains hot.
Advancements in solar also are improving with clouds.
Also, you know, batteries. When someone makes it cost effective to install a device to sell your car battery power on the grid we'll also have a better time managing the grid during spikes... Would be nice if that also did home battery backup in blackouts... 70 kWh would get me through most of the ones I've experienced.
> I love the idea of keeping my finances private
I'd love that too, but I'm not sure it's even feasible or possible, at least in the EU country where I live. I, like most people (I think?) need to file taxes each year, and those include my new positions, or what positions have disappeared, including how much I have in savings. And, the only way for me to keep savings without losing money, is to keep it in a bank, so it's again not private.
Feels like "private finance" been dead for a long time, unless you start using cryptocurrencies specifically for privacy, like zcash, otherwise you'll be having non-private data at least somewhere.
What you describe sounds more like keeping your assets a secret... and if you feel defeated because the government can know, how do you feel about hiring an accountant? Or executing stock trades? You can't keep those activities a secret from those agents working for you. You would probably expect them to keep their privileged information about you _private_ though, right?
And I think that's what the parent post is talking about. Today's companies make you agree to 3 50-page documents which they can update at any time and your continued use after such silent updates constitutes consent.. and at some point they will sell your financial status/well-being to people for profit. So the more you feed them the more of your data that is being easily sold.
We ultimately probably can't stop that, but we can make it more difficult. Many apps like this would take your information and sell it.. having an option that lets you track your own finances without becoming a product is nice.
I saw the keyboard to be operated by the left hand only and here is my (totally personal and somewhoat adjacent) problem with it.
My left hand is the one which has suffered the most the many hours of using a keyboard over the last +-25 years. While the right hand has the occasional break from the keyboard when using the mouse, the left hand is constantly glued to the keyboard.
It also has a much tougher job - all the cmd, ctrl, alt and shift + combinations are mostly done using the left hand - e.g. on Mac you cannot cmd+shift+ select text with the arrows - you must use the left hand - so it ends up doing so much more work.
I wonder if there are other people with the same problem. My right hand never hurts after many hours of computer work - but the left hand does. It hurts even now that I am typing and I haven't even spent more than an hour doing it.
They started with the left hand as requested, but made right hand version as well.
I wish these were also commercially available... I'd love to pay for one of these... I know it's open sources, but I don't know the language nor do I have the skills to construct one myself.
ldoughty commented on Avoid 2:00 and 3:00 am cron jobs (2013) endpointdev.com/blog/2013... · Posted by u/pera
I try to avoid crons at the top of the hour, partly because of this... but also because (in shared / serverless infrastructure) I assume a lot more people are setting their crons for 'on the hour' so there's more resource contention... I also aim for 'after 4am' where I can as well, or 'before midnight', to avoid this whole range.
ldoughty commented on Migrating from AWS to Hetzner digitalsociety.coop/posts... · Posted by u/pingoo101010
This implies cloud infrastructure experts are cheaper than bare metal Linux/networking/etc experts. Probably in most smaller organizations, you have the people writing the code manage the infra, so it's an "invisible cost", but ime, it's easy to outgrow this and need someone to keep cloud costs in check within a couple of years, assuming you are growing as fast as an average start-up.
I think it's completely different ballparks to compare the skill sets...
It is cheaper/easier for me to hire cloud infrastructure _capable_ people easier and cheaper than a server _expert_. And a capable serverless cloud person is MUCH cheaper and easier to find.
You don't need to have 15 years of a Linux experience to read a JSON/YAML blob about setting up a secure static website.. of you need to figure out how to set up an S3 bucket and upload files... And another bucket for logging... And you have to go out of your way now to not be multi-az and to expose it to public read... I find most people can do this with minimal supervision and experience as long as they understand the syntax and can read the docs.
The equivalent to set up a safe and secure server is a MUCH higher bar. What operating system will they pick? Will it be sized correctly? How are application logs offloaded? What are the firewall rules? What is the authentication / ssh setup? Why did we not do LDAP integration? What malware defense was installed? In the event of compromise, do we have backups? Did you setup an instance to gather offloaded system logs? What is the company policy going to be if this machine goes down at 3am? Do we have a backup? Did we configure fail over?
I'm not trying to bash bare metal. I came from that space. I lead a team in the middle of nowhere (by comparison to most folks here) that doesn't have a huge pool of people with the skills for bare metal.. but LOTS of people that can do competent severless with just one highly technical supervisor.
This lets us higher competent coders which are easier to find, and they can be reasonably expected to have or learn secure coding practices... When they need to interact with new serverless stuff, our technical person gets involved to do the templating necessary, and most minor changes are easy for coders to do (e.g. a line of JSON/YAML to toggle a feature)
I don't buy it either, because Apples GPTK works similar as Proton - they have a DX12-to-Metal Layer that works quite well - if it works. And their GPTK is based on wine, just as proton. It is more other annoyances like lack of steam support. There are patched version of steam circulating that run in GPTK though (offline mode) but that is where everything gets finnicky and brittle. It is mostly community efforts, and I think gaming could be way better on Apple if they embrace the Proton-approach that they started with GPTK.
Apple collects no money from Steam sales, so they don't see a reason to support it.
You don't buy Apple to use your computer they way you want to use it. You buy it to use it the way they tell you to. E.g. "you're holding it wrong" fiasco.
In some ways this is good for general consumers (and even developers, with limited config comes less unpredictablilty)... However this generally is bad for power users or "niche" users like Mac gamers.
It’s a terrifying experiment in hollowing out the civil service. At some point a critical mass of Federal workers may be lost which brings the entire machinery of the Federal Government to a standstill.
It’s also not clear how to recover from something like this.
The point is that they don't want it to recover. This is evidence that the US Government can't be trusted to provide the service themselves, and those functions should be privatized / contracted out instead... like how our Defense budget is so small thanks to us paying government contractors for everything we need, like $5,000 screwdrivers and $7,500 toilet seats installed by $300/hour Mechanic Specialist II's.
I was frustrated that (because my posts are less frequent) changes in Hugo and my local machine could lead to changes in what is generated.
So I attached a web hook from my websites GitHub repo to trigger an AWS Lambda which, on merge to main, automatically pulled in the repo + version locked Hugo + themes. It then did the static site build in-lambda and uploaded the result to the S3 bucket that backs my website.
This created a setup that now I can publish to my website from any machine with the ability to edit my git repo. I found it a wonderful mix of WordPress-like ability to edit my site anywhere along with assurance that there's nothing that can technically fail* (well, the failure would likely, ultimately block the deploy, but I made copies of my dependencies where I could, so very unlikely).
But really the main thing I love is not maintaining really anything here... I go months without any concern that the website functions... Unlike every WordPress or similar site I help my friends run.