Live data from Hacker News

Exe.dev

exe.dev

211–220 of 316 posts

Re: Exe.dev

#211
post #193
post #144

Earlier quoted context omitted.

Come on guys, it literally says 'ssh exe.dev'

Yeah, and it really is not I would want to do, just like diving into unknown water that sparkles weird.. It's an instinct, can get past it but to get more info about the service... nah.

That's okay, you're not in the target audience is all.

Re: Exe.dev

#212

unlike others, i like the site and the initial prompt. Lost me at "verify email" though. Why get so creative, yet limit yourself to archaic "email". Why do *YOU* the provider need me to have an email or a phone? Look, mullvad can provide vpn services without email or all that nonsense. If you want people who will use ssh to order things, these are the same people that would get your service because you're not asking…

I run https://pico.sh where we don’t ask for email. Even on our website we instruct users to generate a token so if they do lose their key they can use it to recover their account.

People regularly lose their ssh keypair and also don’t generate a token. I think using email as a form of recovery is totally fine and regardless when you have to pay for the service you’re going to give up your email (and other personal info) via payment processor

Re: Exe.dev

#213
post #169
post #49

Earlier quoted context omitted.

Works fine on Firefox/Android here

https://blog.exe.dev/ I am not sure. I even tried Google Chrome This site can’t provide a secure connection blog.exe.dev sent an invalid response. ERR_SSL_PROTOCOL_ERROR https://i.imgur.com/HOwb7g3.jpeg also tried mozilla firefox on desktop Secure Connection Failed An error occurred during a connection to blog.exe.dev. SSL received a record that exceeded the maximum permissible length. Error code: SSL_ERROR_RX_RECORD…

try another network. i often get SSL errors due to false positives in my internet provider's "virus protection"

Re: Exe.dev

#214
Hmm, looking through how-exedev-works, it seems like what you call VM is more like a container, i.e. it doesn't run its own kernel?

Sort of a container which "feels like" a VM? Reminds me of Virtuozzo / OpenVZ VM approach which was popular ~20 years ago when RAM was expensive...

Re: Exe.dev

#216

The individual plan says: — $20/month — 25 VMs — 2 CPUs — 8GB RAM — 25GB disk — 100GB bandwidth Is this 2 CPUs/8GB RAM per VM (in other words, 50 CPUs/200GB RAM)? If so, this is an unbelievable bargain (too good to be true?); other cloud providers charge hundreds of dollars per month for an equivalent VM. If, OTOH, it's 2 CPUs/8GB total, Hetzner offers an equivalent VM for about $5/month (with much more disk and band…

No I apologize for the confusion (exe.dev person here). What is different about this service is you get dedicated resources that you share between your VMs. The initial allocation is conservative, we want to give people more (or drop the price). The goal is to reduce the marginal cost of creating a VM to zero. Instead of installing a container manager or using Unix users, just make another VM. (I will get a better ve…

Is rsync installed in the stock vm environment by default?

Asking for a friend…

Re: Exe.dev

#217
Interesting interface. Some feedback:

  - Email delay to Gmail inboxes for verifying an SSH key used via SSH via email is longer than the timeout of the "Waiting for verification email..." stage in the SSH key registration. Wait longer or provide a non-email way to authorize a new key. You could imagine a few ways to do this: Allow users to add/delete SSH keys from the website or exe.dev shell; create a bearer token/random string that I can generate from the exe.dev shell or website to associate a new SSH key; SSH key signatures (existing key signs new key); SSH CAs (like @cert-authority); etc.
  - SSH U2F/FIDO2 authentication support has become mainstream, and offers you a way to have homogeneous auth across web and SSH interfaces. Maybe consider unifying authN this way?
  - exe.dev ssh interface does not allow me to list SSH keys, only to delete them. Consider moving all authN/authZ functionality into an "auth" subcommand/submenu (like you have for "share") and support SSH pubkey CRUD in there.
  - You make some strong assumptions about email addresses that aren't true -- what happens on email address changes, lost email access, etc. This will become more important when you start billing (and possibly costly).
  - How do I manage persistent disks? Any way to attach them to a different VM after I'm done with them on the original one? Is there always a single PD per VM or can these be managed separately? What about data or database volumes? Can PDs be attached to one or multiple VMs at a time?
At what scale do you break even on fixed costs (wages, rents, etc.)?

Re: Exe.dev

#219
post #209
post #186

Earlier quoted context omitted.

Where did I say that, that wasn't a topic I just commented on the *entirety* of the content on the landing page. > The disk and sudo mentioned are good enough clues I mean, you do you and let's agree to disagree about a good landing page UX.

tbh maybe this service doesn't want you as a customer if you can't figure this out. it seems like you'd be an above-average support burden

You made me lol

Re: Exe.dev

#220

Earlier quoted context omitted.

Any plans to support non web stuff?

For non-web stuff you will need a static IP. We plan to support that in the near future: https://github.com/boldsoftware/exe.dev/issues/6

Could also support sni/sslh style stuff to support more protocols without static IP.
Post reply on HN