Introduction

Introduction

Imagine you have a file on your desktop. You click its context menu and select a function called "Secure Share…" A group of people you chose will quietly receive a copy of that file from you. Without anyone else ever being able to see what you are doing with what and with whom. Without anyone else ever knowing it happened. That's one of the things secushare is for.

Why are most of us still communicating between each other using e-mail that anyone can look into, or confide our private communications to corporations that, instead of respecting constitutional principles, make profit on it or stand tall to PRISM obligations from spook agencies.

Encrypted communications are still too complicated, never fully re-assuring and not exciting either. Even if you use them right, you still have little chance of hiding who you are talking to, who your social network is.

With secushare we're trying to provide something fun, useful and maybe even exciting, which as a side effect addresses many issues in privacy.

Most applications have become dependent on Internet servers, but it doesn't have to be in a way that the servers know everything about us. If we enable our laptops and phones to interact securely between each other, we can let servers be of help speeding things up, but without exposing our privacy to them.

secushare is a framework for social interaction over the Internet in a way as safe as currently feasible, or at least empowering you to choose a trade-off between safety and convenience yourself. We imagine a social platform equivalent to Facebook, but distributed and encrypted straight from your phone or desktop.

But our framework actually allows any software to make safe communications with people in your social circles, so we'll start with something simple like end-to-end encrypted chat, mail and maybe file exchange. But once that part works, we can create half a new Internet experience on top of such a protocol stack.

The reasons why something like secushare hasn't been done before are manyfold. It requires a profound understanding not only of the design of anonymous systems, but also on how to bring the scalability of cloud technology into non-commercial distributed networks. You still can do business over secushare, but neither secushare nor its users are the product.

As we researched in the 2011 paper and in further detail in the comparison, only some advanced anonymization and P2P file sharing applications have explored these levels of privacy. We examined several of them closely, and ultimately went with GNUnet.

Buzzwords to Dig Into

  • Anonymity - How to keep things for the intended people.
  • Answers - Some FAQs asked and answered.
  • Architecture - How does it stand tall?
  • Aspects - How different views of your profile are created.
  • Business - An authenticated Internet helps business.
  • Comparison - How do other tools compare.
  • Features - How many social networking services can we replace?
  • Introduction - What has led us here?
  • Protocol - Ingredients: efficiency and extensibility.
  • PubSub - The publish and subscribe paradigm revamped.
  • Rendezvous - How to get started when you know nobody.
  • Scalability - How to make applications work for billions.
  • Security - People be the gatekeepers to their devices.
  • Society - How secushare is not a threat to society.
  • Storage - How to keep devices in sync.
  • Threats - What if malware messes up your secushare identity?
  • Transparency - Should everything always be open for everyone to see?

How can you help?

  • You can express your support for us. (example)
  • You can help us get funding, help us with our communications, work out alliances or simply give us more visibility.
  • You can give us feedback if you think we are designing the perfect tool everyone has been waiting for, or if there's anything we overlooked.
  • If you're a web designer, you can help us get a cross-device user interface going as described in architecture.
  • If you're a graphics artist, you can spice us up.
  • If you're a lawyer.
  • If you're a C developer, talk to us to help us with the core service.
  • If you're a developer in whatever other technology you like, you can design or translate a wide choice of tools (see 'Native User Interfaces' in architecture for examples) to work on top of secushare.

P2P Compliance

secushare is supposed to fulfil the following requirements for true P2P:

Further Rambling

  • Censorship - We like ad-hoc mesh networks, too.
  • Channels - Structuring the flow of information.
  • Cheat Sheet on secushare.
  • Conspiracy - What if everyone is out to get you.
  • DSNP – not that interesting
  • Federation - Why the decentralized social web thing doesn't work.
  • HTTP – criticizing wrong protocol
  • Identity - How many can I be on secushare?
  • Like - How about a distributed Like button?
  • PGP - Reasons why you may want to use something else.
  • Privacy - If you have no secrets, you have no life.
  • Prototype - Current status of the prototype version.
  • Rights - You don't need a Bill Of Rights from us. You own us.
  • WebID – How does it make sense?
  • XMPP – Why XMPP isn't the way to go.
Top