Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

DigitalOcean S-1

sec.gov

Post reply on HN
Print view View original

331–340 of 442 posts

Re: DigitalOcean S-1

#331

Post by indigodaddy »

LinuxBender wrote: post #330
indigodaddy wrote: post #296

Earlier quoted context omitted.

I find this extremely hard to believe. EDIT: Just to clarify, AWS has a lot of IPs, over 100 million [1]. Let’s just speculate that 1/50th might be in an overall pool for customer allocation. Do you really think the majority of 2M IPs would come back blacklisted in some form? I haven’t dug in to this to actually see if this is the case, but it would seem laughable to even begin to think that this might be the case..…

I think the wording should be changed. I would agree that all their EC2's and lightsail instances would be in the RBL/RSL's. AWS have an email service specifically for this use case.

I would be shocked if even that were true. Well, looks like I’ve got some homework for tonight.

Re: DigitalOcean S-1

#332

Post by ivraatiems »

robertlagrant wrote: post #293
ivraatiems wrote: post #255

Earlier quoted context omitted.

I moved to BuyVM, https://buyvm.net/ . I had already been using their services for a few years, I just expanded on what I already had. They are not as large an enterprise as DigitalOcean, by a long shot, but the upside of that is you can speak with the owner and his small staff personally and get personal service. They made me a very good deal. I also know from their Discord that they have some conservative political…

Not treating people differently based on their beliefs sounds like someone with leanings on either side, rather than extremists on either side.

Yeah. There are definitely people on their Discord I'd call extreme, but none of those people work for or speak for the company. They aren't people I would choose to associate with, but it's a free country.

I thought about it quite a bit, actually. But there is a line there and they haven't crossed it.

Re: DigitalOcean S-1

#333

Post by Bender »

indigodaddy wrote: post #331
LinuxBender wrote: post #330

Earlier quoted context omitted.

I think the wording should be changed. I would agree that all their EC2's and lightsail instances would be in the RBL/RSL's. AWS have an email service specifically for this use case.

I would be shocked if even that were true. Well, looks like I’ve got some homework for tonight.

They come and go get listed and delisted so you may find your own nodes to be hit and miss. That is for the well behaved RBL's and RSL's. Spamcop, Spamhaus, Uceprotect will expire nodes and networks after a period of no reported spam. There are a few others that will leave things listed for a long time. I am only basing my experience on those three. The less costly a VPS provider, the more often they get listed. Ramnode for example is almost always blocked. If you have long running nodes, it is unlikely you will find them blocked outside of Uceprotect level-2.

Re: DigitalOcean S-1

#334

Post by kevinoconnor7 »

cobaltoxide wrote: post #323
kevinoconnor7 wrote: post #228

Earlier quoted context omitted.

I remember interviewing with DO back in late 2014 and it was nuts! The entire interview process took ~3 months and it was clear that they were defining the process as they went. The entire process was basically: 1. initial call with recruiter 2. homework project 3. call with engineer to discuss said homework project 4. two phone screens with engineers 5. onsite interview with 6 engineers Finally I had was at the fina…

That interview process sounds completely standard.

Overall I don't think the total amount was excessive, or maybe just slightly. My experience has always been been technical phone screen or homework problem before onsite, but not both.

The real issue was how chaotic the process was. I had started out talking to an engineer that had picked up my application, but was handed off to recruiter only after the homework portion was done (said recruiter even mentioned that they had just been hired). The two technical phone screens also were two discrete steps (i.e. the second was only scheduled after the success of the first).

That was really the issue: neither I nor them knew how many more steps there were. It wasn't helped by having long periods of radio silence between each step either. But it was painfully obvious that they were scrambling to figure out how to scale their processes, so much so that it still stands out to me 6+ years later.

Re: DigitalOcean S-1

#335

Post by kevinoconnor7 »

mamurphy wrote: post #310
kevinoconnor7 wrote: post #228

Earlier quoted context omitted.

I remember interviewing with DO back in late 2014 and it was nuts! The entire interview process took ~3 months and it was clear that they were defining the process as they went. The entire process was basically: 1. initial call with recruiter 2. homework project 3. call with engineer to discuss said homework project 4. two phone screens with engineers 5. onsite interview with 6 engineers Finally I had was at the fina…

I was bored so I clicked on the key proof in your profile and it says it's been revoked.

oops! I rotated my private key a couple years back and never updated that. Fixed!

Re: DigitalOcean S-1

#336

Post by voltagex_ »

smarx007 wrote: post #277
vinger wrote: post #220

Earlier quoted context omitted.

Last time I provision on linode and do at the same time a created a ubuntu box. I found I had to setup a few additional things in linode. Linode never felt as polished which is fine. The one thing that made do better was they had a datacenter in my region. No one mentioned vultr killer $2.50 which is where I would go if I wanted a dev box to play around on.

I remember something being off in Vultr $2.50 offer which made me stop halfway during sign-up. Had to go to https://www.vultr.com/products/cloud-compute/ again to remind myself: $2.50 VPS does not come with an IPv4 address. At least today they openly mark it and I think 5 years ago you'd only find it after a few clicks.

This was an advantage to me at the time. My ISP (Internode) had enabled dual-stack v6, and a few of the other options I was looking at on LowEndBox came with a NATed v4 address. Here was Vultr offering an IP I could fully control, even point real domains to!

I don't know if this is still the case, but I also got no SSH logspam from bots trying to log in on a v6 host.

Re: DigitalOcean S-1

#337

Post by chrisweekly »

ksec wrote: post #324

Congrats to DO. Really like the direction DO is going. Which is something in between millions of small VPS firm and giant like AWS. It also forced Linode to React. And proved the space in Cloud Hosting exist, which company like Vultr and UpCloud are now joining. And I think their features are finally close to hitting the perfect spot. With all the essential like DBaS, Object Storage and K8s. They have also ( finally…

I'm a fan of DO too. In terms of "what's missing?", how about the equivalent of AWS Lambda@Edge or Cloudfront EdgeWorkers? ie, a NodeJS runtime as close to the end user as the nearest CDN edge.

Re: DigitalOcean S-1

#338

Post by voltagex_ »

sneak wrote: post #236
yte15 wrote: post #225

Earlier quoted context omitted.

Your issue was exactly, and I mean exactly, what I had in mind when I said “learning experiences” upthread. I followed it closely. Linode painfully learned the scrubbing lesson as well - and DO was in a worse position to learn it at the time, being forced to throw the scrub write load at SSDs that don’t like that type of load. That’s the real issue, honestly, that they probably started noticing SMART warnings from sc…

It's not tough to solve. The whole scrub thing was a red herring: you don't need to scrub anything to not leak data, you just thin provision. It's (mostly) fine if customer data stays on your disks after they delete. It's not fine to give it to the next customer because you don't know how disk abstraction works. My issue is mainly how they coped with it, which has nothing to do with their (at the time) technical inco…

What do you mean by "thin provision" here?

Re: DigitalOcean S-1

#339

Post by voltagex_ »

jandrese wrote: post #198
halfmatthalfcat wrote: post #10

I love DigitalOcean. The simplicity of their UI, friendly CLI tooling and (as a hosted k8s customer) the frequency of updates to their offerings. BUT: 1. Their web UI stability is terrible (constantly hangs and errors out) 2. Their hosted DB IOPS aren't competitive with other PaaS providers. There's also no way to scale DB size dynamically without upgrading to a new price tier which is overkill. 3. Their Kubernetes C…

5. Their IPv6 support is pants on head. https://www.digitalocean.com/docs/networking/ipv6/ Yes, you read that right, they assign a /124 if you enable IPv6. There is no provision for getting anything larger. All configuration is totally static as well. It's really incredible how botched the setup is, and it has been like this for years . If you're wondering if you're sharing the same /64 with an entire datacenter wort…

That's OK, OVH gives you a single IPv6 address with some VPS configurations.

Re: DigitalOcean S-1

#340

Post by VintageLight »

Ansil849 wrote: post #305
kevinoconnor7 wrote: post #228

Earlier quoted context omitted.

I remember interviewing with DO back in late 2014 and it was nuts! The entire interview process took ~3 months and it was clear that they were defining the process as they went. The entire process was basically: 1. initial call with recruiter 2. homework project 3. call with engineer to discuss said homework project 4. two phone screens with engineers 5. onsite interview with 6 engineers Finally I had was at the fina…

Not to hijack this sub-thread, but just a general question: how does one deal with unethical 'homework projects'? I've had a case during an application where I was given a 'homework project' that seemed to me very much not like a theoretical scenario, but more like the company wanting me to do free work for an actual real-world issue they had. Have people had situations where you suspected the same? How do you deal w…

Some people don't like whiteboarding or timed pair programming because it's not close to a real-work environment.

Some people don't like take-homes that replicate scenarios/projects because they think it's too close to real work and want to be paid instead!

There's no pleasing everyone with interviewing processes.

Post reply on HN