Add Black Screen screensaver 1.1

[simmel]

If there’s a checkbox you can’t complete for any reason, that's okay, just explain in detail why you weren’t able to do so.

After making all changes to the cask:

• brew cask audit --download {{cask_file}} is error-free.
• brew cask style --fix {{cask_file}} reports no offenses.
• The commit message includes the cask’s name and version.
• sha256 was updated, but version remained the same.
  Post a link to a public confirmation by the developer.:

Additionally, if adding a new cask:

• Named the cask according to the token reference.
• brew cask install {{cask_file}} worked successfully.
• brew cask uninstall {{cask_file}} worked successfully.
• Checked there are no open pull requests for the same cask.
• Checked the cask was not already refused in closed issues.
• Checked the cask is submitted to the correct repo.

[vitorgalvao]

• sha256 was updated, but version remained the same.
  [Post a link to a public confirmation by the developer.][version-checksum]:

Could you please explain what was unclear, there?

[simmel]

sha256 was updated, but version remained the same.
Post a link to a public confirmation by the developer.:

That could mean so many things.

1. When was sha256 was updated supposed to happen?

• When I ran any of the previously mentioned commands?
• When I updated/added it myself, as in this case?

2. Who is the developer?

• Creator of the application?
• The person adding/updating the cask, me in this case?

I never updated the sha256 in this case, I just added it.
So I shouldn't have clicked that?
Should that be moved to a new headline, like:

Additionally, if updating an existing cask:
[ ] sha256 was updated, but version remained the same.

That would make it clearer to me, at least.
🤷‍♂️

[vitorgalvao]

@simmel Thank you for the feedback. See #33692. Clearer?

[simmel]

No problem @vitorgalvao! I added another comment on that PR :)