delano

13 ms·

91.
by delano 15y ago
The relevant quote from Scoble: By the way, PR people should take lessons from Denis. He not only drove a few hours to see me in Davos, but he taught me to sled, which was one of the highlights of my trip to the World Economic Forum. Of co
92.
by delano 15y ago
I didn't know what NFC meant. I couldn't find an answer on the site so I had to search for it on Google (it stands for Near-Field Communication).
93.
by delano 15y ago
http://lamsonproject.org/
94.
by delano 15y ago
Yep, good eye. It's not an ideal approach but using KEYS is the only option for a non-specific tool. The right solution is to have something similar build into redis-cli (see antirez's link above).
95.
by delano 15y ago
actually it is possible to build both features in the RDB -> JSON dump (filter by key pattern, type, single DB, and so forth). But that would be much faster. Absolutely, that would be awesome and definitely a lot faster. feature requ
96.
by delano 15y ago
Salvatore, thanks for taking a look. or add this feature to redis-cli, so that it is able to translate RDB files into JSON and the other way around. Absolutely, that would be fantastic. I'm not a C guy so I wrote something quickly in Ruby
97.
Redis-dump: Backup and restore Redis with JSON(github.com)
33 points by delano 15y ago|8 comments
98.
by delano 15y ago
Sent you an email. Let me know if you need anything else.
99.
by delano 15y ago
We're only displaying it for people coming from HN. This should work: https://onetimesecret.com/pricing (If not, delete the sessid cookie for onetimesecret.com.)
100.
by delano 15y ago
Ya, that's a great question. We've thought a lot about backups. We delete secrets immediately after they're viewed which presents an interesting problem with regards to keeping backups. We're probably going to take a route similar to Wikipe
101.
by delano 15y ago
For tech people, we've had the most questions regarding our API (password resets, one-time pads, custom encryption) and also the ability to have custom installs that are separate from the multi-tenant instance (e.g. we now have a paid plan
102.
by delano 15y ago
We totally thought the usecases were going to be pretty limited but as it's turned out we've been getting a lot of great feedback from outside of the tech community too. Drew Carey of all people retweeted it: https://twitter.com/DrewFromTV
103.
by delano 15y ago
Clickable link: https://onetimesecret.com/ (The previous post for our alpha: https://news.ycombinator.com/item?id=3207489 )
104.
Thanks HN: we just launched the One-Time Secret beta based on your feedback
30 points by delano 15y ago|19 comments
105.
by delano 15y ago
Let's just say we're all in agreeance.
106.
by delano 15y ago
No we don't keep any identifying information so we have no way to contact people. We only display a message on the private URI page to the effect of, "Message was received 30 minutes ago".
107.
by delano 15y ago
Cool. I hadn't seen that. I like the way they handle the password.
108.
by delano 15y ago
What happens?
109.
by delano 15y ago
Cached by the browser?
110.
by delano 15y ago
You guys raise an interesting case we hadn't thought about yet. Devil's advocate: how would that be better than the algorithmic approaches (weak, medium, strong indicators implemented in javascript etc).
111.
by delano 15y ago
Nothing is entirely secure. We're two guys with no ulterior motives that take all reasonable precautions to keep the data safe. For most people that's not only enough, it's much better than having their passwords stored in their email archi
112.
by delano 15y ago
You raise some great usecases. We have an option to require a password to view the secret but that doesn't directly solve the cases you bring up. We're considering changing the basic UX to require a click to display the secret (the click wi
113.
by delano 15y ago
We don't have an API yet, but we will soon.
114.
by delano 15y ago
Ah, you raise a good point. We monitor and track only the homepage. We don't mention this explicitly and it would be a good idea to remove from other pages to avoid confusion. Fixed.
115.
by delano 15y ago
Nice idea. Seems like a no-brainer for one of the "More Options".
116.
by delano 15y ago
That's an interesting idea. We could offer that as an option: "Convert this text to an image".
117.
by delano 15y ago
Here's our privacy policy: we don't care to know your secrets. That's tongue and cheek obviously b/c you do raise a good point. Do you have any examples we could base one on?
118.
by delano 15y ago
There's an option to require a password before displaying the secret.
119.
by delano 15y ago
My grandfather wouldn't know what to do with an encrypted ZIP file. A lot of my friends wouldn't either.
120.
by delano 15y ago
Thanks. jsonifier.com looks cool btw.

More ›