bradleybuda

34 ms·

391.
by bradleybuda 14y ago
It turns out that there are very few services for which this is the case (imagine if you had to log back in to everything every time you switched wifi networks). Having said that, we have some innovative ideas for supporting the few service
392.
by bradleybuda 14y ago
Yes - by default your logins are only available to you, and they are only shared with the individuals that you explicitly add. We definitely want folks to be using the same tool for both team and individual passwords.
393.
by bradleybuda 14y ago
We think of Meldium as a tool for sharing accounts, not for just sharing passwords. While there are a lot of password managers out there, none of them are built for teams first. Meldium's browser extension makes passwords go away completely
394.
by bradleybuda 14y ago
Thanks for the suggestion Jason. Our free tier actually covers up to five users, so it works great for both individuals and small teams. We knew that Meldium would be useful for large companies, but we've been surprised to learn that even v
395.
Meldium (YC W13) Controls Your Team’s Shared App Passwords For You(techcrunch.com)
108 points by bradleybuda 14y ago|49 comments
396.
by bradleybuda 14y ago
There's a flip side to the problem - not only can startups not pay, but they might not even know that they should be talking to someone like Matasano. Many tech startups severely underestimate the security implications of what they're doing
397.
by bradleybuda 14y ago
We ended up using Ruby's SecureRandom.hex, which is 128 bits of the form "e7e12f9b82f71d90b678373c360e497c" - roughly equivalent to the 126 bits of randomness you get from a version 4 UUID.
398.
by bradleybuda 14y ago
You're absolutely right. It was 100% our fault that Meldium was broken - we didn't pay attention to the implementation, and we assumed that job IDs were random when they really weren't. I don't mean to cast any blame on UUIDs or resque-stat
399.
Be careful with your random tokens(blog.meldium.com)
46 points by bradleybuda 14y ago|30 comments
400.
Dangerous Curves(insidehighered.com)
3 points by bradleybuda 14y ago|1 comments
401.
by bradleybuda 14y ago
The sample sites look great on my Nexus 4 - nice to see a mobile experience that isn't iPhone-only. Great work guys!
402.
by bradleybuda 14y ago
Storing secrets in the environment is an excellent idea. Heroku highly encourages this approach, and it makes it much easier to give different levels of access to code and secure data. It also makes it easier to avoid accidentally copying
403.
by bradleybuda 14y ago
Unfortunately, it doesn't look like this patch works in Ruby 1.9, where YAML is actually the Psych module. Any Psych experts know how to make this 1.9-compatible?
404.
by bradleybuda 14y ago
This could be very useful - it's a purely client-side solution to remember which account you used to log in to a site the last time and multiplex accounts. My only initial complaint is that the UI is ugly and confusing, and it doesn't seem
405.
by bradleybuda 14y ago
This is Brad for Meldium. Thanks for the kind words Adrian. We enjoyed participating in Demo Day: it's quite an experience to have to handle a wide variety of product, business, and team questions in real time - Boris and I were kept on our
406.
by bradleybuda 15y ago
I'm in the advertising industry where I frequently find myself surrounded by this kind of jargon (the word "media" is a tell that you're about to get an avalanche of bullshit). I've found one trick for turning these conversations about abst
407.
by bradleybuda 15y ago
Fuck that.
408.
by bradleybuda 15y ago
N = 18