How does this work?

1. You are assigned a customizable public URL.

2. You click on a button to grant your browser read-only access to a folder on your device.

3. When someone visits your custom public URL they can see and download the contents of your shared folder.

How does this work, technically?

A WebSocket connection is established with Socket2.

When an authenticated HTTP request is received to your public URL it is split into frames and sent to your browser tab.

If you granted read-only access to the requested file, it is sent back to the Socket2 proxy through the same connection.

The response WebSocket frames are directly piped into the HTTP response.

Do I need to install anything?

No. You just need to keep this browser tab open and on top as long as you need your Static Web Server to be live.

Is there a file size limit?

No. You can share really large files.

How is this better than a file transfer app?

Firstly, your files remain on your device and can only be read by a person you trust.

Secondly, you can share static websites. How awesome is that?

How is this better than other Static Web Hosting?

With Socket2, your files stay on your device.

You don't need to wonder if some giant corporation actually deleted that repository you "deleted permanently".

How do I stop my Static Web Server?

Just close this tab. Really. It's that easy.

How do I improve my download speeds?

Here are some tips to improve your Static Web Server's performance:

- Keep this tab on top - so your browser doesn't throttle its JavaScript engine

- Uninstall addons that keep your browser busy

- Enable password protection so that unwanted requests don't reach your Server

How can I log in?

We're using Firebase for authentication so you can log in with either your Google account or any valid e-mail address.

Make sure to add [email protected] to your contacts list and never follow authentication links that don't point to our domain, auth.socket2.me.