irgeek

Maybe you could add support for Gitea? It’s a pretty handy way to slap an API in front of git and it’s much simpler to self host than GitLab.

You can add GitGuardian - https://careers.gitguardian.com/jobs

This definitely still works.

Certificates issued from AWS Certificate Manager are — and, I believe, always have been — free. AWS is definitely not rent-seeking on certificates.

I was just looking at your pricing page and the greyed-out-but-still-ticked items in the comparison lists are very confusing. Being greyed out makes it look like their not included, but there's still a tick, so maybe they're still included but less capable? Or available as an add-on? I can't tell what, exactly, you're trying to convey to potential customers.

While I understand the point you’re trying to convey, the commit history of this project stretches back to June 2013 so it’s a little unfair to imply it just “popped up” recently.

Cognito is a joke. It’s full of bugs, the hosted UI doesn’t support half the features and -- based on the change velocity I’ve seen over the last three years —- it is desperately under-resourced by AWS. The new releases always seem to be small changes (like adding a new OAuth provider) but never fixes for the major bugs.

To be fair, this is just how executable scripts work — it’s not a special yaml shebang, just a regular shebang for an executable that happens to take yaml files as it’s input. The underlying OS just invokes the command in the shebang and passes the file as the first parameter, exactly as it would if the shebang were for bash or python.

This is very cool. It looks much easier to use than the collection of Makefiles and build scripts I cobbled together in college.

One thing that’d make this even more awesome is the ability to drop in a data table and have it show up as a graph. The scripts I built in college allowed me to drop a CSV file into a directory and have it automatically turned into an EPS graph that I could use in LaTeX. It made for pretty easy, but very good looking reports.

Are read-only keys on the roadmap too? CI/CD pipelines don't really need write access in most cases.

These should absolutely be documented on the site!

When I looked at the CLI source I almost walked away. 112MB spread across 12k files from a developer I don't know is _way_ too scary to trust with access to my SSH private keys. Being able to manage it without that CLI tool, though, makes it something I might try out.

Assuming the GitHub issues are from the actual attacker -- and I see no reason to doubt they are -- this is very troubling:

https://github.com/matrix-org/matrix.org/issues/363

Compromise began well over a month ago

Yikes. That's a long time for a compromise to go unnoticed.

Other than porta-potties, are there any other situations where poop isn't flushed into the sewers?

Where, exactly, do you think the poop goes once it's flushed into the sewers?

Sewers are not magical portals into another realm that we can just dump poop into forever. The sewers run to sewage plants where the water is extracted and treated to be sent back into the water supply. The poop that's left over has to go somewhere...

Seems to be back up for me in AU.

In response, we implemented a shadow ban: On the surface, the attackers continued to receive a 200 HTTP response code, but behind the scenes we simply stopped sending document invitations after they exceeded the rate limit.

And right there they broke the service for legitimate users. Totally unacceptable collateral damage IMHO.

Something isn't right here. 80MB of pcap data with 138k packets captured, but over 5 million connections to googleapis.com. That's 36 connections per packet. Also, if you add up the number of packets in the destination port table and divide that into 80MB, it works out to 4 bytes per packet. Which is a bit surprising considering IPv4 has a 20 byte header on every packet.