stophecom

5 ms·

1.
by stophecom 1y ago
I'd recommend the following options. Both platforms offer enterprise solutions, but also provide free starter plans: https://www.storyblok.com/ https://www.datocms.com/ From own experience, the develop
2.
by stophecom 4y ago
No, unfortunately not at this point. I got often issues with bigger files in Chrome for some reason. (network error) But Firefox worked. I try to improve the stability in the meanwhile.
3.
How to Securely Share a File(blog.stophe.com)
4 points by stophecom 4y ago|0 comments
4.
by stophecom 4y ago
Was about to say. Domain is great. I created scrt.link some time ago, which does the same thing as well :)
5.
Show HN: Sharrr – Pretty secure file transfer(sharrr.com)
7 points by stophecom 4y ago|2 comments
6.
by stophecom 4y ago
Well, fair questions. So as mentioned in the footer. The service is powered by scrt.link, which encrypts the url on the client. That means br3f never knows what link you intend to redirect to. Read more on https://scrt.link/
7.
One-Time URL Redirects(br3f.com)
2 points by stophecom 4y ago|3 comments
8.
by stophecom 4y ago
With br3f you can create disguised and disposable redirect links. Use it whenever you have to share a sensitive URL in a chat or email.
9.
Scrt.link vs. One-Time Secret(blog.stophe.com)
1 points by stophecom 5y ago|0 comments
10.
by stophecom 5y ago
> If you want to quickly commit something really small and trivial in master/a branch/a PR without having to do the whole stash/checkout/pull/change/commit/push rigmarole (like if you're in the mid
11.
by stophecom 5y ago
Issue is resolved. Using DELETE request now, which feels a bit more accurate. Blocking crawlers is no longer needed, which also benefits page speed! Thanks again for the input. C.
12.
by stophecom 5y ago
Thanks again for all the feedback. Short update: I'm using DELETE now, since it feels a bit more accurate. As a side effect, the page is way more responsive. :) Have fun sharing secrets. C.
13.
by stophecom 5y ago
Yes, this is a joke. Not sure it's a good one to earn trust ;). C.
14.
by stophecom 5y ago
Oh wow :) Do you know, by any chance, what type of filter/firewall your institution is using? I'd be interested in the reasoning behind the flagging/blocking. C.
15.
by stophecom 5y ago
> email security services do click on links before delivering to the client's email inbox True. This may be a problem. Like mentioned, common bots are being blocked currently, plus, I will be testing POST instead of GET requests (Si
16.
by stophecom 5y ago
The part of the URL holding the encryption key is not sent to the server. https://stackoverflow.com/questions/14462218/is-the-url-frag... Don't take my word for it :) You can check all code that runs in your
17.
by stophecom 5y ago
Not exactly. Sure, if your email is compromised someone could access the secret link, and ultimately your password. But now, you will know that someone else had access to your password, since the link won't work for you anymore. This
18.
by stophecom 5y ago
Very good point! Thank you. I'll look into this.
19.
by stophecom 5y ago
It is done entirely on the client. You can check the source code. Read more on scrt.link/security.
20.
by stophecom 5y ago
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. S
21.
by stophecom 5y ago
Thanks for the feedback. Much appreciated - I'll look into the consistence naming issue. > Features like delete after N visits or by X date might be useful too. Indeed this is an often seen feature. I'll consider it. About the
22.
by stophecom 5y ago
Good question! Bot traffic from common apps/services is beeing blocked. But let me know if you run into a problem. C.
23.
Why I created scrt.link(blog.stophe.com)
29 points by stophecom 5y ago|40 comments
24.
How to Share Secrets Online(scrt.link)
3 points by stophecom 5y ago|0 comments