[-] Pifpafpouf@lemmy.ml 11 points 5 days ago

So layoffs are bad, but not doing layoffs is bad too?

[-] Pifpafpouf@lemmy.ml 15 points 3 weeks ago

A single nuclear warhead is not capable of ending life as we know it, where did you read that ?

[-] Pifpafpouf@lemmy.ml 2 points 3 weeks ago

Using the same argument, 10 is one symbol. It is the "ten" symbol.

I’m just pointing out that it makes no sense to say that this system allows writing any number as one symbol.

[-] Pifpafpouf@lemmy.ml 8 points 3 weeks ago

6 is 2 symbols though

[-] Pifpafpouf@lemmy.ml 29 points 4 months ago

Love how nobody got the joke

When DST ends you set your clock back 1 hour (or it does it automatically nowadays) in the middle of the night, gaining 1 hour of extra sleep

The joke here is that the guy did the same for Leap Day, setting his clock back 24 hours and gaining 24 hours of sleep, so when his boss called at 2pm he was in the middle of his ~32h night

[-] Pifpafpouf@lemmy.ml 9 points 5 months ago* (last edited 5 months ago)

A blockchain is only as secure as the amount of work (= processing power) that goes into it. Anyone with 51% of the processing power invested in a blockchain can attack it and essentially steal from other people. For cryptocurrencies it’s a problem that solves itself, because every person that possesses some of the cryptocurrency is incentivized to mine to keep it secure (and to earn some at the same time). The more your cryptocurrency is valuable, the more people will want to mine it and the more secure it will be.

For anything other than cryptocurrencies, you can’t incentivize a huge number of people to commit computing power to secure your blockchain. So you have to protect it some other way, for example only allowing you and some trusted people to write on it. But then it doesn’t really need to be a blockchain anymore, just a write-only database (which will perform better and occupy less space).

If it requires no work to generate a block at the end of your blockchain, any attacker can generate malicious ones.

[-] Pifpafpouf@lemmy.ml 5 points 7 months ago

They don’t though, they disable printing with the subscription’s cartridges. You can still buy other cartridges and it will work.

[-] Pifpafpouf@lemmy.ml 13 points 9 months ago

Good thing guns are banned (in civilized countries anyway) so terrorists can’t use them

[-] Pifpafpouf@lemmy.ml 15 points 9 months ago

If you never use medicine that was developed with the help of animal testing I guess you could. If you do use pretty much any kind of antibiotics though, or are unfortunately diabetic and have to use insulin, then it would be pretty hypocritical.

[-] Pifpafpouf@lemmy.ml 2 points 9 months ago

BG3 had a day-one patch, and is at its 6th hotfix now. Does it make it a broken game?

With the scale of modern AAA games it is inevitable, if a studio had to wait until every bug in a game the size of Starfield was fixed to release it, it would simply never release. You have to decide at some point that the game is in a releasable state, and at this moment you start printing discs, then you keep working on it and fixing bugs and that constitues the day-one patch. And don’t worry about the expansion, they started working on it long before the release.

[-] Pifpafpouf@lemmy.ml 4 points 9 months ago

A day-one patch is the day of the release, so it counts as included in the release in my books.

It doesn’t mean « they haven’t done enough testing before physical production », it means they took advantage of the inevitable several weeks or months between start of physical printing and release.

And of course a patch 1 year after release is fine. What I’m saying is that I prefer a broken game that is fixed on release day over a broken game that is fixed 1 year later.

[-] Pifpafpouf@lemmy.ml 12 points 9 months ago

What’s the problem with day-one patches? I’d much rather have a game with a day-one patch than a game that needs a patch 1 year after its release

Game + day-one patch is essentially the initial state of the game

1
submitted 10 months ago by Pifpafpouf@lemmy.ml to c/mlemapp@lemmy.ml

Hello, I would really appreciate being able to disable swipe gestures (for example to upvote/downvote or save). In Apollo iirc there was a settings switch for each swipe gesture, and disabling all of them enabled lateral swipes for navigation, from anywhere on the screen instead of just from the edge. Thanks

view more: next ›

Pifpafpouf

joined 1 year ago