fartsparkles @ fartsparkles @sh.itjust.works

Shine Get

---

Read more

Posts

0

Comments

517

Joined

2 yr. ago

I read complicated and dry books as that helps me. I’m reading a Roman history book and an old philosophy book at the moment that I barely make it through a handful or two of pages of either before I’m drowsy. But if I pick up a brilliant piece of literature, I’ll read until dawn with zero issue.

Wear goggles when you go swimming.

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!

Why does the embargo remain? What does the US gain from this? (I’m rather out of the loop)

Especially RAID 0.

Reference for the admission?

Spot on. Another thing to consider is weather. EVs perform worse in cold weather - lower ranger and slower charging. Some manufacturers are worse than others. Preconditioning while plugged in is super helpful in below freezing temperatures and use the heated seats and heated steering wheel instead of climate control if you can.

Just needs some research if you live somewhere where below freezing temperatures occur at times in a year. Absolutely not a reason to avoid EVs altogether, just know the limitations, what to expect, and how to best mitigate some of the limitations.

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.

What is up with the bird at the end?

What were the reasons?

Sleep

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 completely agree. She’s an icon of strength.

Technically they thought they might have introduced a bug that caused the delay / a regression and set about investigating it. Pretty sure it was a Microsoft developer too.

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.