seanmcgregor

7 ms·

1.
by seanmcgregor 14y ago
(I am apparently posting too quickly) It is up to the individual user on what level of privacy is enough for them. I think this has great potential as a cross posting mechanism. I can't switch to Diaspora because of network effects. How do
2.
by seanmcgregor 14y ago
(let me take my Privly hat off and put on my Machine Learning Researcher hat) Facebook needs users far more than access to users' private communications. Their "like" button and the demographic data they collect is more valuable than crawli
3.
by seanmcgregor 14y ago
Nice! We'll standardize the URL structures so anyone can write their own extension to interface with the protocol, but we'd love to have more contributors on Privly. There are many components that we can carve up and work in parallel.
4.
by seanmcgregor 14y ago
Interesting, is it open source?
5.
by seanmcgregor 14y ago
Thanks, and with help, our implementation will monotonically increase in convincingness.
6.
by seanmcgregor 14y ago
This concept encompasses both hosted ciphertext (on some other network) and host page ciphertext. There are use cases to both, and development of the server/network does not inhibit the development of the extensions. The road map has a set
7.
by seanmcgregor 14y ago
Yep, in the long run something will leak out of our servers. The plan is only to store ciphertext.
8.
by seanmcgregor 14y ago
Our adoption model is to pass through a phase where content is separated into a key hosted by a site like Facebook (on the link), and the encrypted text on a content server like priv.ly. That way it is readable when they click the link, but
9.
by seanmcgregor 14y ago
The hosted server is how we plan on financing development since many users will want the level of privacy it can provide, but don't have the technical expertise to manage their own environment. Over time we want to push content into a netwo
10.
by seanmcgregor 14y ago
More details on the encryption element: http://www.kickstarter.com/projects/229630898/protect-your-c...
11.
by seanmcgregor 15y ago
They could ban the URLs, but not the IPs since the IPs come from the clients. Regardless, it is politically difficult for FB or other scrutinized companies to block a certain kind of hyperlink whose only purpose and use is to protect ones o
12.
by seanmcgregor 15y ago
Honestly, this is a huge and important question that we have thought about extensively. In the end it comes down to what people want to be public, and what they want to be private. The absence of a content search feature on Facebook is a go
13.
by seanmcgregor 15y ago
I cried a little when I used recaptcha (Google hosted), but I'll yank that once I have time to drop in a different captcha system. There are a few other hosted items, but none are from advertisers and none will last very long if I get more
14.
by seanmcgregor 15y ago
re crypto-experts: You are right on this, but we are going to stay away from implementing our own crypto libraries. Instead we will develop APIs for well supported libraries like PGP and package them for browser extensions. That is the prop