What's your point?

His point is that Ops time is more expensive than Dev time, they get paid more. The Dev teams should really fix their own bugs if they happen in the wee-small-hours.

Not just that (since there's a lot of situations you may not be able to actually fix bugs in the moment, just work around them), but it also aligns incentives and enforces lessons learned. If you know you're gonna be on the other end of that pager, maybe that hack won't see the light of day. For more senior folks, pattern recognition around how things were built and what issues they led to are incredibly valuable. Being able to tell a junior engineer no don't do it like that, we did that last time and it led to x y and z, could save the company a ton of money and pain.

If you're separated out from ops, what would ever drill that into you? Saying you're too busy for ops is just wild to me. That's some of the highest effort to reward work someone can do.

All they said is they want to keep work within contracted hours.

> waste my already precious *freetime* on fixing bugs in prod

It doesn't mean bugs cannot be raised, planned and addressed through the normal development process.

Also, abundance of bugs in production could indicate cutting costs on testing.

Surely that must be a politically motivated stance.

We need a p2p client side / federated search engine, with customisable white/blacklists and proper caching. Able to both work with results of other search engines and index specific websites itself.

Pi-hole does not solve the problem completely unfortunately; it's fairly trivial to bypass network DNS. In theory any software could manually call one of the public DNS ip's or just have a fallback hardcoded list of IPs.

Nothing solves the problem completely. Redirecting DNS at the router to a blocking DNS server goes a long way, but DNS over HTTPS is a tougher nut to crack.

I block all dns outbound on my home network. My resolver uses DNS over https to Cloudflare. I consider any DNS / udp 53 traffic outbound unauthorized or a leak that should be prevented. If I see a beacon to a particular DNS server externally, I’ll create a NAT to point to my resolver so I can manipulate the answers, if I deem it necessary.

That solves the first issue, what about the hardcoded IPs issue?

Can also trap reflected waves inside and focus them right in the middle

this is not reddit

> The amount of school activities missed

Has been more or less spread across population. If only a known subset is affected, those will become disadvantaged and possibly even discriminated during employment.

What do you suggest replacing it with?

Probably their usual greenwashing stuff like "100% recycled aluminum"

I meant from previous generation iPhones of the same form factor - it used exactly the same screen and camera

I suspect they mean "recycled" as in "we reuse existing assembly lines / stocks of parts" and not "we take apart old iphone 8s to make SEs". That doesnt seem feasible from a quality assurance POV

The only reason for the markup, is because they can, which they ensured in advance