I thought everyone decided “jfgi” in online discourse was a toxic years ago. It’s the same attitude as :
chemtrails make you sick!
How so?
go do your own research
If you’re going report on something, provide a little more information than just “no”. It’s more helpful, better for the community, and in 5 years time when the facts are different, there’ll still be a reference of what was factual in the past.
Let’s not get carried away.
If you ignore the mildly abusive familial relationship. Sure.
Yes, because my imported car tunes to a foreign radio station that doesn’t exist when you first turn it on, the “source” button cycles through all 27 of the pre-programmed foreign radio stations then moves onto digital radio then CD and then Bluetooth, but picks my wife’s phone first, and needs to fai before allowing you to move onto the next phone.
Honestly, I just drive in silence most of the time.
Because:
Agreed.
Resilio sync works better. But the “sync identity” thing is broken, and configuring it declaratively is hard.
But 100% agree. Would love a virtual file system solution. Ideally one which you can use to fill available disk space and ensure you always have a minimum number of copies.
Mozilla, because:
It never gets read, but your account gets a “does not follow instructions” counter added to it.
The staff then laugh about you on their smoke break.
Hips that make a Pixar mom jealous.
If I were building it, I’d do the watermarking on the individual assets & textures.
Your asset pipeline would publish these to the solution, which would pack it up ready for distribution.
Except, each beta tester logs into the game and the publishing system gives them a personalised set of assets with a unique noise filter thrown over the top.
Mr leaky beta player publishes a video or screenshot of the gameplay, and then the studio can just reverse the noise algorithm to get their unique ID.
Absolutely terrible for large scale content delivery. But for a small closed beta, probably not an issue.
Come April, NZ will be charging EVs road user charges using the same price-per-kilometre mechanism diesel (diesel not have a fuel levy) vehicles use.
I was expecting some sort of “Ai discovers new bug in 30 year old software”… cool I’m excited.
Then they were talking about how the bug was persistent, and I’m more intrigued “is the bug some weird emergent behaviour corrupting state somewhere?”
Nope, just another example of a shit in shit out data model.