[feature] publishing from dat-desktop

[max-mapper]

Based on our call the other night, open to changes but this is what we felt like was an acceptable tradeoff of features vs shipping things quickly

V1 Desktop Publish Flow

1. User installs desktop app, opens it, signs up for account
2. They can create a dat, it creates it locally, including a keypair
3. Nothing happens on a server until they 'publish', at that point it hits our dat-push endpoint and they see their data uploading to our google server
4. Then when the push completes, they update their auth0 user account profile to have that dat listed as published
5. They can also pick a short/pretty url for that dat when they create/publish it in the desktop app then we someone goes to that short url, the server looks up the profile corresponding to that short url, gets the dat from the profile, and uses hyperdrive to fetch metadata and render the dat.land page view for that dat
6. If they delete their app and lose their key they wont be able to update the dat for now

[yoshuawuyts]

Sounds good; seems like it's completely in line with what we discussed in Berlin

[okdistribute]

Sounds Good. We don't have a design for "pushing to a dat endpoint and see the data uploading to our Google server"

[okdistribute]

cc @Kriesse what do you think about the 'pushing to a dat endpoint'? Should we make an issue for that in dat.land-roadmap with a 'design needed' tag for some point later? The functionality isn't there yet but at some point we'll probably want to talk about how the design would work. For now it could just be a simple button that is like 'backup' but i wonder what other implications this might have down the road for user stories

[yoshuawuyts]

Depends on login & register (https://github.com/datproject/dat-desktop/issues/134, https://github.com/datproject/dat-desktop/issues/135)