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.

Well, I've used paste bins before. How about one with an email address input that'll invite whoever is meant to view it?

So instead of sending someone an image in an email, you send them a ClosedLink, they can view it once, and you avoid having to send them the image as an attachment?

Some screenshots would be nice.

Are you expecting a lot of signups? As plan B, maybe aim to get a grant from the Oasis Protocol Foundation - they're all about privacy - and quiz them on what to do next.