allset_

Many drink vending machines also have a place to deposit empty bottles for recycling.

The headline alone makes this clear.

https://www.imdb.com/title/tt0057012/

Your ISP can snoop on upstream requests. It is likely less private than Quad9 or similar services where you can mix requests with a large crowd.

Large companies use more than one language.

> Removed 17532 outdated packages, in an effort to keep the package set maintainable and secure.

Thanks for this! I appreciate the acknowledgement that more software in nixpkgs is not necessarily better.

Presumably, not paying out for these bugs which often take weeks of research to find.

Maybe they don't have any openings at this time.

Even then, that's only immutable for the workflow config. Many workflows then go on to pull in mutable inputs downstream (eg: default to "latest" version).

If only they offered dedicated in the US.

No.

DNS literally would not work if they did that.

I can only comment about the one I work for, but yes. It's also discussed publicly to some degree.

https://cloud.google.com/blog/products/storage-data-transfer...

Cloud Flare supports ECH. https://developers.cloudflare.com/ssl/edge-certificates/ech/

> AFAIK the proprietary server can glean your IP, your phone number, who you talk to, and when you talk to them. This type of metadata is valuable information.

To the best of my knowledge, so can matrix.org or whatever servers you connect and federate to. This is required to route messages between users. What is your point?

OK now do a small hatchback.

No.

And every tutorial you could find on how to use PHP with a database was a tutorial on how to add SQL injection to your site.

The underlying library that does most of the work is MIT.

https://github.com/landlock-lsm/go-landlock

Which you should absolutely do when the company storing your seed phrase gets hacked.

Which is why Neocities has a free tier which doesn't even have ads.

>your code

3P code is a thing

>why

Sometimes there are edge cases with nil pointers that testing missed.

>automatically restart

What about all of the other requests in flight? Letting those fail because one request hit an edge case isn't great for a production service with high throughput.

You can also phrase it a little more gently.

"I plan to start on this on X date, let me know if you have any concerns."

And send a reminder so that you're giving them multiple chances to respond.

As the linked docs mention, grpcurl is a thing if you want to use it.

Server reflection exists (https://grpc.io/docs/guides/reflection/), but you don't really need to whip out curl when you have the RPC service's definition. It tells you everything you need to know about what to send and what you will receive, so you can just start writing type-safe code.

Phone apps can have their own UI layout, font size, etc. though. No reason to force that on desktop users.

Or are hosting non-public services and want TLS certs that all my devices trust automatically, like me.

They do proxy your traffic if it can't set up direct connections, and it's still free.

https://tailscale.com/kb/1232/derp-servers

Cheap, safe to drink bottled water was my reason for making the daily pilgrimage while backpacking through Thailand.

I suspect that what you receive is determined client-side in software, and with some reverse engineering, you could force it to send you whatever quality you want (as long as your subscription allows for that quality level).

> - Files ending with "_unix.go", "_linux.go", "_windows.go" etc. will only be compiled when compiling for the specified platform. The exact list of platform is very hard to find in documentation.

Sure, you won't find it in the Go 101 guides, but it is well documented in the "go build" CLI reference in the official Go docs site. See https://pkg.go.dev/cmd/go#hdr-Build_constraints and https://pkg.go.dev/internal/platform.