Live data from Hacker News

Why I created scrt.link

blog.stophe.com

31–40 of 43 posts

Re: Why I created scrt.link

#31

Earlier quoted context omitted.

No, it expires after they view it.

Yes, this is a nice solution, but email security services do click on links before delivering to the client's email inbox. As such, you may need to set the link expiry click number to greater than 1. And then you lose the security due to being ephemeral. Of course, you can log the IP addresses of the clickers, but still you have the leak.

In practice this has not been a problem. It's like saying you can't put unsubscribe links in emails because a bot will click on it... You just simply design the software so that doesn't happen.

Like I said, I've used a similar service that only allows you to view the secret once and I've used it dozens of times with no problems.

Re: Why I created scrt.link

#34

I’m always wary of consumer services that specifically target secrecy and encryption. How many of those “lockbox” photo apps are just syphons into the developer’s server? “We’ll encrypt the file, trust us.” This message can only come from an already-trusted party. Mozilla had an identical service to this except it was for files (Firefox Send) and that one I could trust.

Thanks for the feedback. Appreciate it. I believe you can earn the necessary trust by being transparent. For this kind of service two things are essential: - Open source software: Let everyone review your code - Encryption in the browser. Sensitive information should never leave the browser in plaintext. I'm considering file transfer - but there are some challenges to meet :) C.

I don’t think you can do anything to early my trust personally other than sticking some big brand name in your domain. Anything you say or put on your website still comes from some random server on the web.

Re: Why I created scrt.link

#35

I’m always wary of consumer services that specifically target secrecy and encryption. How many of those “lockbox” photo apps are just syphons into the developer’s server? “We’ll encrypt the file, trust us.” This message can only come from an already-trusted party. Mozilla had an identical service to this except it was for files (Firefox Send) and that one I could trust.

If I wrote something like this, I'd try to be as transparent as I could be as to who I was, and how you could contact me. Hopefully that would create some small level of trust. -- As an aside, I know you are trying to be funny, but your username is tad offensive.

Regarding the name, search Scunthorpe on YouTube

Re: Why I created scrt.link

#36
I've used onetimesecret for a long time, so good to see alternatives and I like the sensible pricing structure here. This has me confused though:

  *Secrets*
  created: 1,179 | viewed: 960 | compromised: 0
Is the number of compromised secrets a joke?

Re: Why I created scrt.link

#37

Earlier quoted context omitted.

Yes, this is a nice solution, but email security services do click on links before delivering to the client's email inbox. As such, you may need to set the link expiry click number to greater than 1. And then you lose the security due to being ephemeral. Of course, you can log the IP addresses of the clickers, but still you have the leak.

In practice this has not been a problem. It's like saying you can't put unsubscribe links in emails because a bot will click on it... You just simply design the software so that doesn't happen. Like I said, I've used a similar service that only allows you to view the secret once and I've used it dozens of times with no problems.

> you just simply design the software so that doesn't happen.

How do you go about doing that? disregard security service clicks based on IP address blacklists, user agent sniffing, etc?

Re: Why I created scrt.link

#38

I've used onetimesecret for a long time, so good to see alternatives and I like the sensible pricing structure here. This has me confused though: *Secrets* created: 1,179 | viewed: 960 | compromised: 0 Is the number of compromised secrets a joke?

Yes, this is a joke. Not sure it's a good one to earn trust ;). C.

Re: Why I created scrt.link

#39

Earlier quoted context omitted.

In practice this has not been a problem. It's like saying you can't put unsubscribe links in emails because a bot will click on it... You just simply design the software so that doesn't happen. Like I said, I've used a similar service that only allows you to view the secret once and I've used it dozens of times with no problems.

> you just simply design the software so that doesn't happen. How do you go about doing that? disregard security service clicks based on IP address blacklists, user agent sniffing, etc?

Nope you just use a POST request...

Re: Why I created scrt.link

#40

Earlier quoted context omitted.

> you just simply design the software so that doesn't happen. How do you go about doing that? disregard security service clicks based on IP address blacklists, user agent sniffing, etc?

Nope you just use a POST request...

How does a legitimate user clicking on a link inside an email generate a POST request?
Post reply on HN