In the United Kingdom, people just add a contact to their phone book called “ICE”. You can learn more here.

Good bot

For those not familiar with US retailers, the punchline is:

Nice! And MIT too. Perfect; I’ve given it a star now.

I agree. I don’t have the time but someone should point this out to the dev via an issue on GitHub.

So basically don’t use this in anything commercial because the phrase “feel free” is different to legally libre and gratis. I personally wouldn’t touch this until it’s released under a reputable license.

Shame they didn’t use a proper license when publishing.

I like to imagine there was a parade of ghosts but they’re all too skeptical to see them.

Love your posts and your little insights and review you share with the screenshots. Thanks for sharing!

Holy shit. This has been holding me back for so long with the engine as I generate basically everything procedurally (including meshes) during runtime.

Will this support 3D or just 2D as the video shows?

Edit: just read the PR and it mentions 3D throughout!

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.

I’d gladly take a single functioning system rather than wait another 12 years of my life for this Kickstarter project to deliver.

Next it’ll be 1000 star systems while we’re still waiting on Squadron 42.

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.