“History is written by the victors.” - what I immediately thought of.
- 0 Posts
- 28 Comments
Kayana@ttrpg.networkto Open Source@lemmy.ml•GravyScanner : a FOSS Android app that reveals installed apps involved in Gravy Analytics data breach8·5 months agoTrue, but at that point, every website I’ll ever visit and have visited in the past might be a threat, so that doesn’t really matter too much to me.
Kayana@ttrpg.networkto Open Source@lemmy.ml•GravyScanner : a FOSS Android app that reveals installed apps involved in Gravy Analytics data breach8·5 months agoI’ve got several hits, but none of them have permission to request my location. If I understand the README correctly, that should mean I’m safe, right?
If you want the magic explained, here’s a start: https://en.wikipedia.org/wiki/Lempel%E2%80%93Ziv%E2%80%93Welch
Huh, really? I thought there were slightly more women than men, but maybe that depends on the economies etc.
As for your second point, yes, exactly. They don’t reproduce. So it doesn’t matter if many men get one wife each, or if a few men get many wives each, the number of pregnancies won’t change, and the number of pregnancy-related deaths won’t change either. So (again), I don’t see how polygyny helps in this situation.
Edit: This first point was wrong, but the second point still stands.
Polygyny wouldn’t solve the aforementioned problem if we suppose that the birth rate of men and women is roughly the same. If one man has many wives, some of whom even die, then several other men won’t have any wives.
Kayana@ttrpg.networkto Technology@lemmy.world•ESET in Germany recommends installing Linux as alternative for older HW running Windows not supported by Windows 11English6·7 months agoHardly a surprise, since Windows 10 didn’t need new hardware to run. You could install it on anything.
Well, what problems are you trying to solve by having the classes all access each other’s data members? Why is that necessary?
Kayana@ttrpg.networkto Mildly Infuriating@lemmy.world•So now I have to PAY you to NOT store files on my device that I don't want?English7·10 months agoCookies required for the website to work (like that one) are totally fine and, in fact, they don’t even have to ask you about them - if they’re not used for tracking. So no, asking each time is definitely avoidable.
Kayana@ttrpg.networkto Games@lemmy.world•Alan Wake, Control developer agrees €15m convertible loan from TencentEnglish407·10 months agoNot only is that headline’s grammar exceptional(ly bad), for a moment I thought the developer of Control was named Alan Wake. Like, how did they manage to butcher that so badly?
There are pros to this:
If the person you blocked can’t see your posts, they can intuit that you’ve blocked them. Then, they might try and find you on other social media to harass you even further, or shift targets to someone else.
If they can see your posts, they have no idea they’ve been blocked, similar to Reddit’s shadow bans. This might make them think you’re just annoyed or rarely look at your DMs, making them invest even more time to uselessly try to contact you.
Of course, I can see the other side too, that you don’t want them to know about any (new) posts you’ve made; but it isn’t as one-sided as you seem to think it is.
Because you don’t need to have significant experience or rent a VPS in order to do that, and I can respect that. We don’t need to force FOSS developers to become proficient in everything.
What needs to happen is some kind of tool (ideally FOSS) that lets you spin up an actual forum with the same difficulty to set it up as Discord.
Kayana@ttrpg.networkto Mildly Interesting@lemmy.world•streetlamp post with cardinal directions118·11 months agoBut is the letter facing the direction, or are you looking in the direction if you’re looking at the letter? So, is East behind the camera or in front of it?
Because I didn’t know absurdism, I read the second one differently at first:
[The] nothing matters.
And I immediately had to think of this gem:
“But it doesn’t do anything!” - “No, it does nothing.”
Depending on the stuffing, I might actually rather take the seat, just because it’s got armrests.
Possible formula: Tax for n-th house = n-th Fibonacci number + 5 * max(0, n - 2). So low numbers like three get penalized by that linear part, and high numbers grow exponentially due to the Fibonacci number.
Kayana@ttrpg.networkto Games@lemmy.world•$843 million lawsuit against Valve already has its own website: "The Steam Claim" accuses the biggest store in PC gaming of "overcharging" playersEnglish42·1 year agoHuh, interesting… You know, I’ve never really wondered about Humble Bundle specifically, but you’re right, they seem to be selling your run-of-the-mill Steam keys, or at least you can activate them effortlessly in Steam. Maybe it’s a case of Steam themselves handing out keys (instead of the publishers) to increase user retention? I honestly don’t know, this is all just speculation.
I actually didn’t click on your link at first, because I assumed it would just show other stores where you could purchase the whole game instead of a key, so I’m sorry that you had to clarify that.
Kayana@ttrpg.networkto Games@lemmy.world•$843 million lawsuit against Valve already has its own website: "The Steam Claim" accuses the biggest store in PC gaming of "overcharging" playersEnglish61·1 year agoAs far as I know, they do - for Steam keys. If you’re selling your game through other stores, not just a Steam key, there aren’t any demands placed upon you. The OC might’ve been talking about that.
Kayana@ttrpg.networkto Canada@lemmy.ca•Toronto developers are getting desperate as no one is buying condos anymore12·1 year agoThat’s a point I didn’t actually think about, touché. Let’s go through this then:
Before Covid (in my country at least), there was this massive push for more homes, because the interest rates were so low. Everyone was building a house, because it was so very cheap (in interest at least, not necessarily in costs). At that point, wise developers might have decided to not take on any big new projects, focusing on finishing their current ones instead of trying to ride out this bubble.
Then Covid hit and the supply chains broke down. That was sudden and couldn’t be expected, I’ll give you that. But now, four years later, the main reason (in my opinion) for the low occupancy is the newfound interest for WFH, also resulting from Covid. Who needs an expensive condo in a crowded city if you can have a cheap flat in a small town instead?
So in this case, I’ll (partially) retract my prior opinion and instead state that while a crash could’ve been seen somewhere on the horizon, Covid with all its consequences certainly couldn’t have been foreseen.
I’m not familiar with the housing prices in Toronto compared to smaller cities in Canada, but perhaps those developers need to bite the bullet and lower their asking prices, because I’d imagine selling for less is still better than holding onto dead weight, praying for demand to go up again.
There are two different things mentioned here, which I feel I need to clarify:
First, what you said about merging / creating a PR with broken tests. Absolutely you shouldn’t do that, because you should only merge once the feature is finished. If a test doesn’t work, then either it’s testing for the wrong aspect and should be rewritten, or the functionality doesn’t work 100% yet, so the feature isn’t ready to get merged. Even if you’re waiting for some other feature to get ready, because you need to integrate it or something, you’re still waiting, so the feature isn’t ready.
At the same time, the OP’s point about tests being supposed to fail at first isn’t too far off the mark either, because that’s precisely how TDD works. If you’re applying that philosophy (which I personally condone), then that’s exactly what you do: Write the test first, checking for expected behaviour (which is taken from the specification), which will obviously fail, and only then write the code implementing that behaviour.
But, even then, that failing test should be contained to e.g. the feature branch you’re working on, never going in a PR while it’s still failing.
Once that feature has been merged, then yes, the test should never fail again, because that indicates a new change having sabotaged some area of that feature. Even if the new feature is considered “essential” or “high priority” while the old feature is not, ignoring the failure is one of the easiest ways to build up technical debt, so you should damn well fix that now.