▲ | adrianwaj 4 days ago | ||||||||||||||||||||||
"One-time access links with no traceable sender" ... so people get anonymous messages while logged-in to this site? How does the sender know about the recipient in the first place? What would I put in my HN profile to get messages on the site? You have people's email addresses... isn't that a problem when saying "no traceable sender?" People will need anonymous email addresses. Why not have pass-phrase logins? I had this idea (linked in my 3rd most recent comment,) whereby what if I wanted to give someone some crypto via a set of keywords? Maybe you could turn this into some kind of PayPal for crypto. Perhaps think about a video demo for this site. Good luck anyway. | |||||||||||||||||||||||
▲ | chistev 4 days ago | parent [-] | ||||||||||||||||||||||
Yea, the email part was a problem I mentioned in the white paper. Problem was I couldn't think of a way to enforce plan limits while making the subscription model work. If usernames, then they could just abuse it by creating new usernames each time. But I understand you. Maybe if you have some suggestions? So regarding the sender and recipient, let's say I wanted to send you something. A message or a file, but wanted to maintain plausible deniability on if I sent it. I wanted a way of doing this, and the solution I came up with was that the link you receive publicly is not the link you land on to access the message or file. Anyone who lands on the publicly shared link, gets redirected to a new url each time. But even without the deniability angle, it could be a way of sharing files with one time links. The links work once. And there's password protection, if enabled. The implementation might not be perfect, but open to ideas, of course. On, and there's API feature for generating links, and uploading files - for what it might be worth. | |||||||||||||||||||||||
|