Hacker Newsnew | past | comments | ask | show | jobs | submit | leetrout's commentslogin

As a recurring kidney stone sufferer I am very thankful for fentanyl for my lithotripsy procedures. I hope we continue to make progress on effective pain medications and don't knee-jerk take them away.

I just keep thinking about SGI and, to an extent, Sun. Couple missteps and a couple innovations in the commodity direction and it will start having a negative effect.

I posted an "Ask HN" around this a while back. I think we will see a lot more of it and we will be hurting legitimate users. I like your temp ban idea but I doubt they would give reasons why.

https://news.ycombinator.com/item?id=40784126


> give reasons why

Because it'll be an LLM guided bot handing out bans, so no one will actually KNOW why.


IMO the worst part about canonical having a tight grip on it.

Reinventing the build chain every other year is miserable too.


It says VSM is automatically disabled... so I would assume not.

> Nested virtualization is supported only on 8th generation Intel-based instance types (c8i, m8i, r8i, and their flex variants). When nested virtualization is enabled, Virtual Secure Mode (VSM) is automatically disabled for the instance.

> made lots of coasters

Haha we would leave the room and avoid walking near the computer when the burner was running. Thanks for bringing back a memory :)


lol, we also did that. And we a Cyrix chip so our computer was pretty slow (but fast for the time) and you had to shut down absolutely everything, even the screensaver, that damn thing coming on is probably responsible for at least 100 coasters haha. Any sort of PC stutter and you were presented with that damn buffer underrun error message.

I was like 12 or 13 and wanted to install linux, like slackware 2.0 or some shit lol. But I didn't know about iso's, just FTP. So I was trying to download every single file from a unpacked linux distro on a ftp site with a 14.4k modem. Then I'd burn them and try to install. I think it took me nearly 500 cds before I got a working install. The install would get like 60% and die on some corrupt package/file, I'd redownload that file, burn it again, run the install... 61% crash, repeat... I did get that sucker installed though. insanity lmao


Ignore the competition. Dont ignore their customers.


If they don't have customers you won't either.


If they don't have customers, they aren't competition.


You might think they are competition though.

Or they might have a single customer - which because they treat well and charge a fair price you won't be able to get away from them.


Any chance you would consider avoiding the SSO tax and making it available for all tiers?


SSO (Google, Microsoft, GitHub) is available on all tiers. Custom OIDC provider support is even available in our ~MIT~ (Apache2) licensed community edition if you self host Distr. Even TOTP MFA is available for all users and part of the community edition.

How can we improve in reducing SSO tax?


Starter package does not show SSO as being available. Thanks for clarifying https://distr.sh/pricing/

I see Apache 2 licensed code in your GitHub but not MIT. Is there another repo or that's what you were referring to?


Custom SSO integrations often require specific development and are therefore not available in our beginner tier.

Oh my bad. Our repository[1] is obviously Apache2.0 licensed, not MIT. Thanks for pointing that out.

[1] https://github.com/distr-sh/distr


It's Patagucci, thank you.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: