> 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.

That was the bigger problem, IMO, in that even once PDO existed and the MySQL extension was "fixed" to have prepared statements, so much of the documentation still did it wrong.

And yet similar classes of bugs still pops up today, even with what I would've assumed to be safe defaults? I'm guessing its non-standard databases or DB clients or something?

This case is more just a pure lack of sanitisation, but it's fascinating to see in 2025 still :)

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.

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.

>you don't really need to whip out curl when you have the RPC service's definition

Following up a "how do I experiment with this in my workflow" with "oh you don't need to" is not the greatest look. There is a vast portion of programming bugs that stem from someone misunderstanding what a given API does, so the ability to quickly self-verify that one is doing things right is essential.

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