DigitalOcean

It would be great to have a managed pub/sub & queue available, you already have Kafka but is expensive and overkill for some cases (like a simple email queue), having a queue linkable to a function would be great

Please add support for logging in with passkeys (webauthn). This is far more secure and easier than using username/password and 2FA. Thanks!

I have been using Digitalocean for years (8+) and I am a strong advocate. But what happened to the support? I have now tried 2 times over several weeks to get support for at Managed Database and every time I get an answer it seems to be about something else but my question. I might not be the best at English, but it seems that the tickets gets answered to fast. And without reading more than the first 2 words. Give me an option to talk to professional support - I would gladly pay for it. But giving an illusion about having support is the way people loose confidence in a company.

Authenticator support with 2fa is a huge pain. Always have to go find my phone, often times I have to charge it before logging in. (I use iCloud Keychain.) Would really love to see passkeys made available so we can safely disable Authenticator 2fa.

I have had a great experience with Managed Databases and would like to know if Digital Ocean will be offering Managed Email services in the near future.I have read the Digital Ocean guide that essentially discourages you from creating and attempting to manage an email server, which is not easy task.I alone would switch 12 domains over almost imediately after it was available.This is the only thing that I still use my shared hosting for; custom domain email address.This could bring a lot of new users to the site which is a win for everyone.Thank you for taking the time to read.

Alerts for volume block storage when the storage usage exceeds a limit.

Make login by passkeys possible for project dashboards. Current two-step authentication by SMS is not safe.

When PersistentVolumeClaim is created using Digitalocean's custom StorageClass, it automatically creates the volumes (which is great) but assigns them random names (such as pvc-1c63892a-4319-444b-8880-960ca612d1d6). Initially I created the volumes manually through the Digitalocean interface and then assign those volumes by ID to a VolumeClaim; the problem with this is that if the node was deleted or recycled, the reassignment of the volume to the new node had to be manual. Anyway, the great of my initial approach was that the billing was very clear: in the details you could see the consumption generated by each volume with a descriptive name.

I have been learning java through your website. Content is really good. I request you to add dark theme to it.

Dear DO, I love how you can use the doctl to show how many API calls you have left before the next hourly refresh! its great that it can be output as json so we have can automation and try to ensure we arent ratelimiting. But it would be great if you can show the Remaining Per MINUTE as well :). Since thats easier to trip over. I know you've updated doctl to retry a few times and sleep enough to not cause much disruption to the customer when the do accidental hit the 250 per minute rate limit, thanks for that. I love DO so much. You guys are always so thoughtful. LMK if you think adding a Per Minute API Call Remaining is something you would consider returning in a header or the cli! You can see many people want this feature! https://github.com/kubernetes-sigs/external-dns/issues/4572