I’m sure they thought about it but did the non-dickish move and didn’t steal Kitboga’s character.

This is how you celebrate and maintain a legacy but well loved game. I still remember booting the game up for the first time on release day (after hours and hours of downloading haha, boy did Steam suck but look at where it is now).

What CEO would publicly acknowledge they did a shoddy job and missed a huge profit opportunity, putting their job on the line.

They still totally dropped the ball on this one. Especially since the big thing they did do is fuck mods by updating the engine and fucked Fallout London in the process. Muppets.

It’s clearly appealing to children and it’s not quite the holidays yet. I’m sure it’s on a fair few presents lists though.

Why anyone would downvote this is beyond me. More than ever, we need to strengthen regulations across the board when it comes to knowingly spreading misinformation, failing to do due diligence if you’re in a position of power and spreading unverified information, privacy and right to be forgotten with AI, and so much more.

Good bot

Valve have something up their sleeves to contend with Quest.

I think you mean “ChatGPT just hallucinated some garbage (again)”.

You missed out the bit where your joke is funny.

Yup. I’ve been boycotting Nintendo and EA for the past twenty years. EA due to the destruction of countless talented studios (Origin, Bullfrog, Westwood, Pandemic) and Nintendo when they were caught by the EU doing anti-competitive price fixing (which they still seem to be doing today).

I have missed out on nothing. A game is just a game; a piece of multimedia content to entertain. There are countless astonishing games out there; missing out on a few doesn’t harm you.

People really need to learn to vote with their wallets. And no, I don’t think sailing the high seas and yarharhar legal questionability is acceptable. You don’t need to play the game. There is nothing that important you’re missing out on for the “cultural zeitgeist”.

Piracy still increases the fandom and increases sales (contrary to what IP owners will tell you). So piracy is still supporting these organisations and feeding into their success.

Vote with your wallets. Don’t support business practices and businesses you don’t believe in. Give your time and money to those that deserve it.

This website ruled during lockdowns. Cannot recommend this enough!

Especially RAID 0.

Reference for the admission?

And it’s made by a Bitwarden developer.

They highlighted it was a bug and said it would be fixed very soon after it was flagged. It was addressed in a matter of days. You can build the server with the /p:DefineConstants=“OSS” flag still and you can build the clients with the bitwarden_license folder deleted again (now they’ve fixed it).

I don’t understand why you’re throwing FUD about this. Building without the Bitwarden Licensed code has been possible for years and those components under that license have been enterprise focused (such as SSO). The client is still GPL and the server is still AGPL.

This has been the way for years.

Cool. They got that sorted nice and quickly.

Edit:

I don’t get why people think they’re suddenly doing stuff under a different license to subvert the open nature of the project. They’ve been totally transparent on what isn’t part of the GPL/AGPL licensed code for years.

SSO, the password health service, organisation auth requests, member access report blah blah have been enterprise features under the Bitwarden License for ages and they architected the projects in a clear and transparent way to build without those features since they added them.

Truth right here. I’ve been privileged to travel the world and curries are hands down the most flavourful dishes this planet has to offer.

Thank you for the smug response however I did indeed read the article and going from 13 months to 10 days is not a trend but a complete rearchitecture of how certificates are managed.

You have no idea how many orgs have to do this manually as their systems won’t enable it to be automated. Following a KBA once a year is fine for most (yet they still forget and websites break for a few days; this literally happened to NVD of all things a few weeks ago).

This change is a 36x increase in effort with no consideration for those who can’t renew and apply certs programmatically / through automation.

Smells like Apple knows something but can’t say anything. What reason would they want lifespans cut so short other than they know of an attack vector that means more than 10 days isn’t safe?

AFAIK they’re not a CA that sells certs so this can’t be some money making scheme. And they’ll be very aware how unpopular 10 day lifespans would be to services that suck and require manual download and upload every time you renew.

This is actually why I use macOS at work - I wasn’t able to get a Linux box approved by IT but they happily support macOS and I get to use basically all the same software I do on Linux.