HN user

sam_perez

21 karma
Posts2
Comments23
View on HN
Eyechat 2 years ago

Lol no not generally ;)

Just did not expect to be gazing into the windows of someone's soul immediately. The widescreen monitor may have contributed.

Eyechat 2 years ago

Clicking on the link without knowing what it was ahead of time was jarring, even not actively participating.

Beautiful.

----------------------------

This controller is intentionally written in a very verbose style. You will notice:

1. Every 'if' statement has a matching 'else' (exception: simple error checks for a client API call)

2. Things that may seem obvious are commented explicitly We call this style 'space shuttle style'. Space shuttle style is meant to ensure that every branch and condition is considered and accounted for - the same way code is written at NASA for applications like the space shuttle.

----------------------------

^^^^

This bit reminds me of exhaustive checks in typescript code. I try to use them all the time.

https://www.typescriptlang.org/docs/handbook/2/narrowing.htm...

Yeah, this does seem like an odd middle ground.

But I suppose it's more about what you're tracking? For example, instead of tracking reference counts to variable, they're tracking reference counts to each scope. Then, if a scope has no more references, the variables it owns are cleaned up.

That's really cool. One of the benefits of the JS ecosystem is the ability to step through code and crack open your dependencies. Not sure if this would directly make this possible when running your projects/tests, but it at least sounds like a step in that direction.

Hi HN!

I want to share a service we’ve been working on called 2Secured and ask for feedback. It's a tool to send sensitive information using end-to-end encryption.

Here's a link to our landing page: https://2secured.link/

I’ve worked at several companies where the standard for sending or receiving secrets inside and outside the company (passwords, api credentials, documents, ...) was to send/receive them in an email or in slack. Secrets not only lived in their final destination, but were also persisted in many different third party communication services in clear text. It was a common practice and a compliance nightmare.

2Secured ensures that the secrets you send and collect remain private and secure. We’ve abstracted away the pipes for sending and collecting secrets, allowing you to collect and send e2ee data with simple secure links, user friendly customizable forms, and in the future, easy integrations with your backends via SDKs and APIs. We’re also layering in features such as customizable link expiration and email confirmation to view the secrets.

You can share confidential documents, personal data, and other sensitive information without worrying about leaving plain text secrets in intermediate services. You also don’t have to worry about implementing your own internal tools or pages for fulfilling common data requests from clients or partners. It's made for companies or professionals who need handle private information regularly, such as legal documents, medical records, financial data, API keys, pass-phrases, etc.

Has anybody else come across this issue in any of the organizations you've worked in? How have you approached solving the problem?

Please ask any questions or share your experiences! Any feedback on the tool would be greatly appreciated!

Cheers!