xorcist

Investors gets ruined on PPAs all the time. With renewables, there's usually some sort of wind turbine or solar park attached, so after declaring bankrupcy the new owners can settle out of court and continue production.

Here there's realistically no way to continue electricity production so the assets will likely be chopped up and sold, if possible. Nobody owns anyone anything and Microsoft doesn't have to pay a dime. They won't get their power of course, but there's no downside for them.

These types articles where a PPA contract is confused with an investment is really common, mostly for nuclear and renewables, but that doesn't make them any more true. Microsoft hasn't invested anything, likely because they know this is (pardon the pun) hot air.

Most proprietary software ships as tgz files which you can just unpack and run.

A few ships with "installers", which are mostly just bash scripts with the tgz embedded.

Simple enough.

Interviewing is Hard(tm). I accept all the problem with live coding the article mentions but I still do it, at least a little bit.

What's the alternative? Take home problems come with their own problems, and select for people with no family and lots of time. Going by general vibe alone also works, kind of. But we're going to work together, so having something that at least faintly resembles work is kind of useful.

The leetcode type problems are useless however, fully agree on that. But a trivial loop with conditional, perhaps iterating over a list of lines shouldn't be that bad, especially if you get help with the syntax.

SECUSO is a shining beacon in the Android app space! Thank you for all your work.

One wishes smartphones was less of a moving target so that the maintenance burden was reasonable. Recompiling all your Windows software every year would seem beyond silly, but here we are.

These types of guides are hard because they don't really have a good target group. Those who best need them are the least likely to use them. There are many like it, and they all go into lots of technical details. Some of it is really specialized.

For example, a large part of this document is IDS-related. There are long parts on AIDE, fail2ban etc. But all these tools do is provide a lot of data. You still need to make useful use of that data. That requires you to actually understand this stuff. That's not a five minute job. Whereas changing to the Mozilla recommended cryptos is trivial. As a beginner who might want to read these tutorials, you won't know the difference.

Some recommendations are a bit exclusive, too. If you run the other run, you likely won't need fail2ban. Just as most people use chrony instead of ntpd these days. And there's nothing on mandatory access control, such as SELinux, rbac or AppArmor or the various eBPF based things that has dominated Linux for the past decade.

Perhaps more useful would be a paragraph or two about how access control works on Linux and the tools to use them, just so you know what you're aiming for. The old school way of deploying server applications on unix is to give every application a unique uid and if possible run them in a chroot. That's trivial and will go a long way, systemd will already have configuration options for it.

Will his customers trust him a second time though?

Yeah, I realize that was dangerously close to ragebait territory, sorry about that.

It's just that I saw it as an opportunity to glimpse into the reasoning made and I couldn't find myself with a charitable interpretation that didn't include something very similar to that statement, so why not pop it out there to find out more what the person disagrees with?

Feel free to ignore the question, it probably won't change anyone's view anyway.

There was also the epic quote about how keeping out all the C++ programmers was enough of a reason.

Which is funny, because you can see the truth to it. With C++ comes endless debates. No technical reason really, but a social one, and so far the Rust culture seems to be closer to C in that regard.

I am sure the "as a user, I should see relative timestamps" ticket was closed fast though! Another job well done!

The ones that did lost in the marketplace against the competitor which was more plug-and-play.

True story.

Flatpaks are a potential security disaster where people learn to install software of questionable provenance, not much different from other desktop operating systems where users learn to click past the warning to install binaries found on random web pages.

The whole point of NixOS is to make packages a special case of configuration. Running nix elsewhere doesn't do that and for configuration there are more mature tools. It would be like using Ansible(/Salt/Puppet or other similar tools) without any of the upside those have. Don't be afraid to use those tools though, they're great.

It depends on which type of ground you build on. The Nordics are mostly granite and have a relatively big problem with radon gas, or at least enough that people in general care about it. Continental Europe is dominated by limestome which hasn't got the same problem.

Phrabricator lives on in Phorge, which is seeing active contributions.

I haven't used Phorge, but Phrabricator is easily my favourite tool among the source code portals. The code review system actually works and does not make me tear my hair out. I am completely at a loss why the commercial side of it seemingly failed after all those years, when products such as Bitbucket and Gitlab seem to do well.

Those apps generally distribute keys, and E2E is if no help unless you validate those keys out of band. Do you, really?

Then there are all the ways, both white and varying shades of gray, of installing software in the end devices. That's your primary threat right there.

That's not a revenue stream at any cell phone carrier I've seen. They do what they are legally obliged to do, and while they do get paid for it, it's a fraction of the actual cost of providing the data. The state tends to drive the hell of a bargain. The service providers, such as Facebook, Google and Apple though, that's entirely different.

To clarify: When you get an NSL, not only is it impossible to refuse and stay in business, it is also impossible to talk about it. That's the scary bit.

I prefer to keep my in-process extensions to a minimum. Is it possible to do the same thing with uBlock rules?

For the past decade or so, I have used Conversations on mobile and Gajim on desktop. Seems to work fine with a minimum of work. What am I missing?

Remember that their main criticism of XMPP was there is just too many protocols extensions and proposals!

Turns out that maybe it was for good reasons.

Very easy to set up (without the Docker nonsense, it's just a binary that is trivial to build), but the real work was in maintaining it. After the third case of database table inconsistencies from joining large public rooms (or perhaps from upgrading it, or a combination) I regretfully had to give up on it. It was time consuming to find out the table structure being used and how to manually correct the data so that it would start again. People were generally helpful on irc but it's just not fun work and feels a bit unnecessary.

That's a real issue with several real life examples, but not really related to the issue of climate change or climate alarmism, is it?

There's been plenty of extended circles around political interests that has lined their pockets in matters of alcohol and drug prevention, abuse prevention and health care, but very few people seem to be taking the local step to actually, alcohol are good for you and anyone that says otherwise should be labelled alcohol alarmists. It's pretty unique to climate research.

I seem to remember that there were was a enormous backlash against CFC bans, and lots of talk about how it would lead to the spread of preventable illness and economic disaster, but it never reached nearly the same levels of anti scientific discourse as we see today.

Make your 5.4" screen phone with:

- a 3.5mm jack

- fingerprint sensor on the back

and it's an immediate buy for me, (almost, but not really) regardless of price!

The Pixel 4 had a 5.6" screen and it feels like the local maxima of mobile phone design. Ran GrapheneOS perfectly too.

> main drivers of the climate change alarm industry

This is clearly dog whistle langauge and not intended to be taken literally, but it is starting to be a common trope and it makes me very curious as to how this industry operates? What's their main source of income, who benefits from it, and how? And what is the supposed goal of it?

Raising the alarm about a conceieved threat could be a way to raise money for more research, which might indirectly benefit those scientists. But we haven't really seen a corresponding massive increase in scientists employed, and even if we did, they would have to find some way to leak money through publicly funded research to their own private enterprises because so far no one has suggested that we pay scientific researchers too much. The way to combat that would be to demand more transparency from universities, but they're already pretty good about that.

It also doesn't match very well what those scientists are actually saying. Which is mostly that the basic science is indisputable since the past century and more research is not required but action. Had the climate scientists been siphoning public money through alarmists schemes, wouldn't they rather say that things are very dire but "don't touch! We need much more expensive research before we can give any concrete advice"?

Since 1967 the second has a physical defintion:

https://en.wikipedia.org/wiki/Second#Atomic_definition

Blender Game Engine lives on in UP-BGE:

https://upbge.org/

It's very capable and easier to use for beginners than Godot.

The problem here isn't that the parser was updated. The parser and writer did what they did for a reason, that made sense historically but wasn't what the submodule system expected. The submodule system is a bit "tacked on" to the git design and it's not the first time that particular abstraction cracks.

Every file format is underspecified in some way when you use it on enough platforms and protocols, unless the format is actually a reference implementation, and we've had enough problems with those. There's a reason IETF usually demands two independent implementations.

Similar problems can affect case insensitive filesystems, or when moving data between different locales which affect UTF-8 normalization. It's not surprising that an almost identical CVE was just one year ago.

Be careful what you wish for. They could have used yaml instead of ini for the config format, and we would have had more security issues over the years, not less.

> You can give a quick explanation in terms they understand, which makes your job sound easy

This is always the right answer. It is the only answer that respects the listener and contains a seed to further conversation.

> I make equipment for high energy physics machines

> I have yet to figure out a way to tell people what my business is in a way that is even slightly accessible.

You ... just did? In a remarkable short, concise, and very accessible way. I can ask as many follow up questions as I want and we might even have an engaging conversation. Sounds interesting!

> the whole of paleo-anthropology "knew" that humans couldn't boil things until the invention of pottery

Is that really true? That sounds unlikely when there are so many contemporary counterexamples. If you have an interest in cooking, there are several traditional meals where cooking is done in other ways. Especially so for indigenous people who have little access to metals or clay. For example on Borneo the traditional way to cook rice over fire is inside bamboo stalks. As long as the water doesn't boil off, you can cook in almost any vessel.