kichik

Fargate, just like ECS, doesn't natively scale to zero. You can set the minimum number of instances to zero for both, but there is no native mechanism to scale it back to one when traffic arrives. And especially not one that would hold the connection until the container is ready. Not saying it's impossible... Just not native. And it would require extra resources. So the price won't scale to zero without something like Lambda in front of it.

No, not really. You can attach auto scaling to it. But it doesn't scale as fast. And it's not very straightforward to scale to zero. And you have to maintain all of it yourself.

The scaling part. You don't need to do anything. It just runs as many instances of the Lambda as needed for you.

Don't you have to submit plans to the city for approval? You might be able to get the data from that angle. Some cities let you pull the plans for a fee.

Nice chain and write-up. I don't know that I would call eval() on user input, hard coded secrets, and leaked credentials small or harmless. All of those are scary on their own.

Invoke-WebRequest is also very slow if you forget to disable the progress bar with $ProgressPreference = 'SilentlyContinue'

PowerShell has some "interesting" design choices...

The echo server will have no knowledge on how to construct the string to be signed.

You are indeed misunderstanding me. I am talking about returning the entire string to be signed. Not the result of the signature.

You can save the expected string to a file, save your string to a file, and run diff on a hexdump of both. Even without hexdump, you should see the difference between "\n" and "\\n" in properly escaped output.

Not exactly the point of this article, but it would be cool if APIs like this can return the expected signed string for debugging. It would have to be properly limited for security. But if the API is expecting non-standard signatures, it could help developers with better debugging tools.

Wasn't ninja invented by a Google employee?

From MSN:

> The largest net seller in January was Canada. The U.K. was the largest buyer in January, after having been the largest net seller in December. Norway and Japan were the second and third largest net buyers in January, respectively, Goldman said in a note.

They might be looking for some open-source fame. The contribution to their resume is more important than the contribution to the project.

You can ask for larger zip files. The maximum is 50GB. It uses zip64 which most modern systems should support. So still 6 files in your case, but at least not 50.

Google Takeout can also run on a schedule. You can do a monthly backup and they will email you when it's ready.

Keep reading down the thread. He's not trying to hide it that much.

https://x.com/paulg/status/1847333998554447948

Those are the first two paragraphs of the article. Verbatim. Can't get more in context than that.

The texts he sent are in the PDF.

You can still charge $80 for the proprietary plastic shell.

Yeah he loves that stuff.

https://github.com/kichik/nsis/blob/b4f28a7071dcd0bf3bcdb766...

Sorry, clone might not be the right word here. Foobar2000 was created out of spite because the creator didn't like what Winamp was doing. I vaguely recall something about bitrate limits and ogg support? It was so long ago and on IRC so no history saved. So it's a replacement?

Edit: some more context here:

https://forums.winamp.com/forum/developer-center/winamp-deve...

https://www.reddit.com/r/software/comments/lqu9u/a_brief_his...

That's a funny name considering it was the Winamp creator's nickname and Foobar2000 itself is a Winamp clone.

And their local DNS servers crash with heavy usage.

For anyone as confused as me by the title, "California Forever" is a company that wanted to build an utopian city. Backed by billionaires according to the article.

> if I could keep this up and convert 10-20% of waitlist users

$5000/mo for 10% of the list. Unless he factored in the list growing further.

The website has pricing and it does say $500/mo for the pro version. So maybe 100 was a typo and he had 1000 on the waitlist.

It's not a cure. It's a crutch. And it doesn't even train you for a real relationship because it's so accommodating. It never stands up for itself and has no real needs.

We need a "dumb it down for the non-lawyers" on every article that mentions courts. ELIANAL. I always try to ask my lawyer friends, but they are sadly not very good at dumbing it down.

but my server will:

  - require direct source code access
  - require go build tools
  - require maintaining GitHub auth
  - require upgrading build tools over time
  - not be trivial to rebuild on failure

I think for Google and Apple this is more of an agreed upon API to replace the multiple "login with X" buttons. Instead of having "Login with Google", "Login with Apple", "Login with Facebook", and "Login with GitHub", there is just one login button that uses your ecosystem of choice. That's the part that should make the process simple for users. Less choice.

In other words, it's to help you easily login to everything else. But your main account would still be protected by a password. Otherwise you wouldn't be able to replace a lost device.

Back in the day it was common to use <form action="mail to:me@domain.com">. Then the spammers came along. My poor 10MB ISP mailbox couldn't take it.