Parts of “Rift of the Necrodancer”
Parts of “Rift of the Necrodancer”
Using tools to break the encryption for backup purposes is legal in the US, but distributing tools to do so is not legal because the tools can be used for non-backup purposes.
I definitely remember hearing that term in the 90’s.
If you get ghosted, it only proves that that person is emotionally immature and wasn’t ready for a relationship anyway, so they did you a favor by outing themself.
This is not useful now, nor will something like this ever be useful.
The damage was not the actual pricing (which was cheaper than Unreal), the reason people are going to leave for Unreal/Godot and never come back is the loss of trust. Nobody wants to be chained down to a company that’s willing to pull the rug out like this.
Except Unreal already had the same kind of pricing structure that Unity is trying to move towards, that’s why Unity thought they could get away with it.
If you think they had impenetrable security before this, I’ve got some bad news for you…
Any time a gaming company does something stupid, leave it to gamers to out-stupid the company and prove that they deserved to get shit on in the first place
This is the entire point of PowerShell
Semantic versioning. Moving from v2.3 to v2.4 shouldn’t require major changes, but moving to v3.0 can.
I’ve heard that enabling CloudFlare DDoS protection on Lemmy breaks federation due to the amount of ActivityPub traffic.
Sounds like the heuristic is taking multiple samples only uses them if they are within some consistency threshold, to hedge against the cases where the field has random data.
The reason it only fails rarely and randomly is because it only happens when multiple actually random timestamps happen to line up around the same time.
Sort of like how several applications (cough git cough) have failure modes when two different files happen to have the same hash.
Turns out developers are bad at statistics and probabilities and don’t understand the birthday paradox.
You need to get a cert from Let’s Encrypt (using certbot), then look up directions for configuring nginx to use the cert files generated by certbot.
The only way to change someone’s core values is to show them the error of their ways WITHIN their own current value system.
If you can manage to find some purchase there you might have a chance, but it’s more likely that you will not find it.
I don’t think that last part is entirely accurate. The reason the weak gravity causes tides is actually because it’s acting over the entire ocean all at once.
It turns out that the ocean is a bit heavy… when you add up the entire mass of all of the water, this imparts quite a substantial bit of potential energy. This can be seen as a “bulge” outward in the moon’s direction, making the planet look a little “squished”.
If the planet were perfectly smooth, this probably would be fairly stable as the bulge wrapped around the planet… however, because we have continents and the sea floor, this movement of water crashes into the land and causes ripple effects with a huge amount of kinetic energy.
I don’t think it would take more that a few years for this process to ramp up to our current level of tides, if there were some way of doing such a ramp up in a controlled way.
You could try Morning Brew
There are only 3 hard problems in programming:
0: Cache invalidation
2: Race conditions
1: Naming things
3: Off-by-one errors
I only use the Subscriptions feed, and use an extension that blocks recommendations and shorts.
Additionally, before watching any video I’ll check the channel page to see if YouTube is hiding any of that person’s videos from me (which they do even on the Subscriptions feed sometimes).
Fuck the algorithm.
If you’re branching logic due to the existence or non-existence of a field rather than the value of a field (or treating undefined different from null), I’m going to say you’re the one doing something wrong, not the Java dev.
These two things SHOULD be treated the same by anybody in most cases, with the possible exception of rejecting the later due to schema mismatch (i.e. when a “name” field should never be defined, regardless of the value).