When I write a bot like this I generally prefer using browser automation (like puppeteer). This requires less reverse engineering and is often a lot simpler and faster to implement.

Browser automation is nice for some projects, but when I used it I felt limited by the speed and inability to integrate captcha solving.

Have you used selenium IDE browser extension? If you do a lot of browser automation it’s a life saver.

You can now link the takeout to another cloud provider (e.g. Dropbox or Microsoft OneDrive). And configure the takeout to take place every two month (for up to 6 times).

So you just need to configure the takeout once a year and you'll automatically receive a backup once every two month.

This is nice, thanks for pointing it out. It's a shame though you can't export to something like S3.

You can also just do a normal form post request into an invisible iframe that is generated by the attacker's javascript.

This is, as far as I know, only possible if you bought it online.

You're right. Here I shop only online, I haven't been in a store (other than grocery store) for at least 5 years. When I buy something online, they deliver it same day to my doorstep, so why would I not. You can (for a small fee) use their service to pick up returned items (or return them yourself at their service center with no charge)

Physical Apple Store purchases too - https://www.apple.com/legal/sales-support/sales-policies/ret...

Apple integrates their online store with their B&M locations so closely it really wouldn't make any sense for them to have different return policies.

But managing an IRC server cluster for 10.000+ users is no simple task.

Paying experts in their field (chat tools in this case) is most of the time the most reliable and cheapest variant. You must also include that Slack has plenty of features that are not available in IRC and mean the productivity is not as good.

Since when is running any service for a number of people something people compare with running google?

30 years ago, efnet was (apparently) 35k users.

Yes, it has a package registry feature for NPM and Maven:

Maven: https://docs.gitlab.com/ee/user/project/packages/maven_repos...

NPM: https://docs.gitlab.com/ee/user/project/packages/npm_registr...

GitLab released integrated packaging back in 2016 - starting with a Docker registry - and adding Maven and NPM in 2018. You can find our plans for adding further packaging capabilities on our public packaging roadmap https://about.gitlab.com/direction/package/

We are also embarking on making package management more secure and auditable for the users of packages with a Dependency Proxy https://about.gitlab.com/direction/package/dependency_proxy/ GitLab users will be able to block and delay packages that are suspect and trace where vulnerable packages were used. This will increase performance, cost efficiency, and the stability of your tests and deployments.

> GitLab released integrated packaging back in 2016 - starting with a Docker registry - and adding Maven and NPM in 2018.

No, first version with "NPM support" (see my other comment as why I don't consider it being "supported") was gitlab 11.7, end of january 2019. I was really looking forward to this and were following your verdaccio (an open source npm registry) thread closely. Development then made a 180 and chose to re-implement rudimentary support for npm on top of your current package abstraction instead.

Oops, you're correct that 11.7 was the first release, sorry for messing up the timeline.

The NPM support is basically not more than a proof of concept. It cannot be used for anything production-like. https://twitter.com/eatingfoodbrb/status/1101461965036244993

Hey. You can probably find my name in each of the zendesk comments/issues. Thiago posted a few for me. I have been very vocal about what I feel needs to be done through my sales leads (my client has a EEU subscription).

Ahh thank you. I don't really pay attention to either of those ecosystems so I hadn't realized it.

Did you try to upgrade using AWS database migration service?

Normally the operational status is automatically updated on outages. The past incidents part is managed manually.

Nearly everything. Old k8s version. No upgrade possible. Odd deployment process (not fully automated). Support is unable to help in a timely manner. First deployed cluster was directly broken (no DNS resolution).

We eyed on switching from kops to EKS. But immediately stepped down after experiencing so many issues.

There is ECS, works for me.

And now Fargate.

I wonder who is writing those status messages. as a customer this reads like "please wait, ETA to fix unknown" in 10 different ways.