Their docs say that something like:

`def greet(name: String, greeting: String = "Hello"): String`

will work for kwargs with default values — https://type-ruby.github.io/docs/getting-started/understandi...

That example is for positional args with default values, according to the example usage: `greet("Alice")`. Can't find ruby-style keyword args example, with or without default values. maybe no kw args in t-ruby?

Or wait, found examples that claims to be keyword arguments, but you define them just the same? I'm confused. https://type-ruby.github.io/docs/learn/functions/optional-re...

I think they've missed a trick there, they could have used `|` like low-type does.

e.g.

  def greet(name: String | "Hello"): String

I know it's all subjective but I think that reads better and it's valid ruby.

To be honest low-type with a static analysis tool would be my favourite syntax for this.

https://github.com/low-rb/low_type

There's a pretty amazing documentary from Noclip that goes in to a bit more depth on how they built the world and how they were able to model the physical attributes of each plane more accurately with than previous versions — https://www.youtube.com/watch?v=0w7q1ZFfsxs

Noclip had a fantastic mini-series for Hitman

Why not use your knowledge of these exposed secrets for good? You know which repo they're coming from, it'd be super simple to let the owner know rather than potentially costing them time and money.

It also seems as though the only use of this site is to capitalise on other people's mistakes? It looks like you're just handing over leaked data to people who will definitely abuse it, which seems to go against your core business of preventing data leaks?

Would it be considered spamming to pull the email address of the commits and send them an automated email?

Well, you don't need to send an email necessarily, a GitHub issue with a guide on how to include sensitive data in a public repo would probably suffice.

I suspect it would be easy to secure GitHub's cooperation in this, but almost certainly not for money or via a black box.

Would it be against the GitHub terms of service to do such an email?

Yet if people don't know the risk exists, they'll continue being ignorant and fucking up. Awareness is a good thing.

This isn't awareness though. This is like telling a specific set of people about all the houses near by that have their front door key under the mat. You only become aware of the issue when it is too late.