Live data from Hacker News

DigitalOcean acquires Paperspace (YC W15) for $111M in cash

finance.yahoo.com

91–98 of 98 posts

Re: DigitalOcean acquires Paperspace (YC W15) for $111M in cash

#91

Earlier quoted context omitted.

too vague! who locked you out? why did you get the hammer?

I have no idea tbh. Never got an email abt it. Saw the charges after a while (my miss) wanted to log back into my account to cancel - couldn’t because account was locked. The thing that annoyed me most is: they knew the account was locked and I could not used it and still charged me.

1. which company, DO or PS?

2. what kind of project were you running there?

3. CC chargebacks are a thing, do you have receipts.

Re: DigitalOcean acquires Paperspace (YC W15) for $111M in cash

#92

Earlier quoted context omitted.

I have no idea tbh. Never got an email abt it. Saw the charges after a while (my miss) wanted to log back into my account to cancel - couldn’t because account was locked. The thing that annoyed me most is: they knew the account was locked and I could not used it and still charged me.

1. which company, DO or PS? 2. what kind of project were you running there? 3. CC chargebacks are a thing, do you have receipts.

Paperspace; just tinkering around… Yeah, CC chargebacks work for 3 months or so here in Europe

Re: DigitalOcean acquires Paperspace (YC W15) for $111M in cash

#93

Paperspace gives free access to Graphcore IPU nodes (with 4 IPUs each), which is pretty neat. Theoretically that is way more throughput than a Colab T4 instance. ... But in practice, I tore my hair out trying to port an actual Stable Diffusion web UI, until I hit a wall. I needed to upgrade the "Poplar SDK" or something beyond the ancient Python 3.8 version to get things working, but the download was behind some kind…

You can download their SDK without a login from their website here: https://www.graphcore.ai/downloads

Re: DigitalOcean acquires Paperspace (YC W15) for $111M in cash

#94

Earlier quoted context omitted.

1. which company, DO or PS? 2. what kind of project were you running there? 3. CC chargebacks are a thing, do you have receipts.

Paperspace; just tinkering around… Yeah, CC chargebacks work for 3 months or so here in Europe

tinkering around got your account locked?

could that have been triggered by content moderation?

Re: DigitalOcean acquires Paperspace (YC W15) for $111M in cash

#95
post #47

Earlier quoted context omitted.

Hi Dillon - congrats on the offer! I adore your product. Quick question though - how sure are you DO won't be interfering with the product and the current team will continue doing its job? Alternatively, would you like DO to take a dominant role in running the product?

Stop dreaming. The acquirer does whatever they want with what they've bought.

The acquirer does whatever they want with what they've bought.

The acquirer does whatever is specified in the purchase agreement and contract.

Buying a business isn't like buying bananas in a store.

Re: DigitalOcean acquires Paperspace (YC W15) for $111M in cash

#96

Earlier quoted context omitted.

Paperspace; just tinkering around… Yeah, CC chargebacks work for 3 months or so here in Europe

tinkering around got your account locked? could that have been triggered by content moderation?

No, I don’t think so. It’s been like a few years since I tried them (2019?). I think it was running some example notebooks - but again, too long ago…

Back to the important questions: 1) Why no user support and explanation? 2) Why lock out users and keep charging them? 3) Why not give them the full refund for the period that Paperspace KNEW I could not access my account but just the 3 months I could do myself by CC chargebacks?

Why do I need to justify myself here? What part of this “we lock you out and charge you” is proper behavior? @mewmew07?

Re: DigitalOcean acquires Paperspace (YC W15) for $111M in cash

#97

Earlier quoted context omitted.

tinkering around got your account locked? could that have been triggered by content moderation?

No, I don’t think so. It’s been like a few years since I tried them (2019?). I think it was running some example notebooks - but again, too long ago… Back to the important questions: 1) Why no user support and explanation? 2) Why lock out users and keep charging them? 3) Why not give them the full refund for the period that Paperspace KNEW I could not access my account but just the 3 months I could do myself by CC ch…

locking and still charging is not proper; if you read my previous replies you'll notice they're focused on why the lockout happened

1) locking out for TOS breach very often happens without feedback, as does automatic flagging systems - no feedback on TOS breach is sometimes done when the effort to provide an explanation would expose the systems internals or considered unnecessary effort, think spam, system resource abuse, content 2) can only come up with technical reasons for that, neither serve as justification 3) see point 2

> Why do I need to justify myself here?

you don't need to

Re: DigitalOcean acquires Paperspace (YC W15) for $111M in cash

#98

I’m surprised by this. Digital Ocean is in no position to be splurging on new revenue streams. They’re underwater and making a loss [0]. They’ve got growing revenue but falling profits and they’ve got more debt than assets. They may want to raise their droplet prices, or issue more stock and then refocus on making their business profitable. [0] valustox.com/DOCN

I worked there relatively recently.

DigitalOcean is organizationally incapable of making anything in-house anymore.

I want to blame leadership - and to be clear, leadership sucks - but the problems are pervasive through every layer of the organization.

The only significant launches in the last 4-5 years have all been acquisitions or built by partner companies and whitelabeled.

Every system and every team has massively circular dependencies on one another , so it's just a massive circle of "we can't move until they move".

The tech debt is insane. Everything is slowed down by terribly-run and massively underfunded internal "platforms" teams for kubernetes, CI/CD, various internal databases, etc.

If you want to build something useful you basically have to ignore upper management and do it in secret until it's done and so integral to the systems that they have no choice but to allow you to support it.

Asking leadership outright to invest in minor maintenance for systems the entire company depends on is never approved.

The bar for engineering practices, code quality, and system design quality is comically low.

All the systems are massively distributed, but there is no understanding of distributed systems issues.

I was told multiple times that "CAP theorem doesn't apply here" and gaslit that an asynchronously replicated MySQL instance that sometimes spiked to multi-minute replication lag to the read replicas should just be used as if it were completely consistent between master and read replicas.

Tons of stuff was just run as singletons with hand-rolled in-memory rate limiting to avoid having to understand distributed locking or semaphores. These systems inevitably start falling over a few months after creation, but you're not allowed to evolve it into a correct system, you just have to support that garbage forever.

Brain drain everywhere due to low salaries. Even engineers barely capable of committing working code were getting fat raises to leave.

Post reply on HN