lemmyng

joined 1 year ago
[–] lemmyng@beehaw.org 2 points 1 year ago

Right?!! Consider this - if you replace the scroll wheel with two buttons, which one would you press to scroll down?

[–] lemmyng@beehaw.org 5 points 1 year ago

Betteridge's law of news headlines strikes again!

[–] lemmyng@beehaw.org 10 points 1 year ago (1 children)

Retaliate with Pakleds!

[–] lemmyng@beehaw.org 2 points 1 year ago (1 children)

Perhaps this will change your prospects.

[–] lemmyng@beehaw.org 17 points 1 year ago

The author of the site works for Brave. The results need to be taken with a grain of salt. Is is more private than Chrome? Absolutely. Is it the best browser for privacy? Ehhh...

[–] lemmyng@beehaw.org 21 points 1 year ago
[–] lemmyng@beehaw.org 2 points 1 year ago (1 children)

Here you go https://archive.is/6IMPP . Don't bother though - it's a vapid article built around a single anecdote.

[–] lemmyng@beehaw.org 1 points 1 year ago (1 children)

As in contract law, the solution is to eliminate overarching or vague promises. Instead of promising to "balance the budget", have them produce a budget plan. Instead of promising elections reform, promise election reform pilot programs. And let's not kid ourselves, election promises made in good faith are a rarity these days. It's time to make it harder to lie to the electorate.

[–] lemmyng@beehaw.org 3 points 1 year ago (6 children)

Punishing the breaking of election promises would be a start. Those are not ambiguous or unintentional, and it should be punishable as a breach of contract.

[–] lemmyng@beehaw.org 3 points 1 year ago

He refers to the fact that the web app does not have default access to your device sensors, microphone, storage, etc.

[–] lemmyng@beehaw.org 6 points 1 year ago* (last edited 1 year ago)

Good article for discussion.

Health checks is one situation where kubernetes really shines. It makes a clear distinction between readiness probes (when the pod is ready to start serving traffic), liveness probes (when the pod should be considered dead), and startup probes (when the pod has finished bootstrapping). Coupled with autoscaling it then becomes acceptable to have a pod stop serving new traffic when it's too busy, because other pods can be created in a short time to take the extra load.

Including backend checks in your application depends on its nature. I think the mistake that the article's author made was not to include the checks, but to have too big of a blast radius when the check fails.

 

In March 2023, Argo CD completed a refactor of the release process in order to provide a SLSA Level 3 provenance for container images and CLI binaries. The CNCF also commissioned a security audit of Argo CD which was conducted by ChainGuard. The audit found that Argo CD achieved SLSA Level 3 v0.1 across the source, build, and provenance sections.

The Argo Project will next rollout attestations to Argo Rollouts, then follow with the remaining projects. SLSA has recently announced the SLSA Version 1.0 specifications, which Argo plans to embrace.

 

The KBOM project provides an initial specification in JSON and has been constructed for extensibilty across various cloud service providers (CSPs) as well as DIY Kubernetes.

view more: next ›