snak

Most of the time,

between the keyboard and the chair

Is where the problem is.

What's the difference between those 4 checkpoints?

From the GitHub's README:

    sd-v1-1.ckpt: 237k steps at resolution 256x256 on laion2B-en. 194k steps at resolution 512x512 on laion-high-resolution (170M examples from LAION-5B with resolution >= 1024x1024).

    sd-v1-2.ckpt: Resumed from sd-v1-1.ckpt. 515k steps at resolution 512x512 on laion-aesthetics v2 5+ (a subset of laion2B-en with estimated aesthetics score > 5.0, and additionally filtered to images with an original size >= 512x512, and an estimated watermark probability < 0.5. The watermark estimate is from the LAION-5B metadata, the aesthetics score is estimated using the LAION-Aesthetics Predictor V2).

    sd-v1-3.ckpt: Resumed from sd-v1-2.ckpt. 195k steps at resolution 512x512 on "laion-aesthetics v2 5+" and 10% dropping of the text-conditioning to improve classifier-free guidance sampling.

    sd-v1-4.ckpt: Resumed from sd-v1-2.ckpt. 225k steps at resolution 512x512 on "laion-aesthetics v2 5+" and 10% dropping of the text-conditioning to improve classifier-free guidance sampling.

Wow, just checked and Pi 3 is over 100€, and Pi 4 over 200€.

What happened? I remember buying a Pi 3B+ in 2019 for less than 50€.

Apparently also known as the "Baader–Meinhof phenomenon".

Great video, thanks for sharing. I had the same feeling of my palms sweating during some of the shots.

It also sparked my interest for climbing, I'll give it a try for sure (with rope).

Agreed, I stopped reading after this sentence.

Excellent explanation, thanks for sharing!

Is there a known limit for the energy to hash ratio ?

At least "cryptos" in plural is clearly for crypto currencies (I don't think anyone uses "cryptographies").

Yes, the article mentions it:

What if I have ECC-capable DIMMs?

Previous work showed that due to the large number of bit flips in current DDR4 devices, ECC cannot provide complete protection against Rowhammer but makes exploitation harder.

FP abbreviation is probably not a good idea here, while talking of Floating Point and Fixed Point, a little bit confusing.

Performance degradation is noticeable with DEBUG level in production.

I'd say that comparison over-simplifies what Cloudflare does behind the scenes.

- Electricity costs

- 99.999999999% (eleven 9’s) of annual durability

- Speed of your HDD (around 200 MB/s?) vs speed of R2

...

Nice one, thanks for sharing.

Oh, just noticed the article is from 2017. Is there a newer one, related/similar to this one?

The Casssandra cluster mentioned (12 nodes, 1TB each) only handles text, as far as the article goes.

I don't necessarily agree with your point of view, but these two concepts were new and interesting to me. Posting their meanings for others that haven't heard of them either:

Phrenology

Pseudoscience which involves the measurement of bumps on the skull to predict mental traits.

The study of the conformation of the skull as indicative of mental faculties and traits of character.

Chesterton's fence

Principle that reforms should not be made until the reasoning behind the existing state of affairs is understood.

Just for clarity:

3.456 × 10^13

34 560 000 000 000

~35 long-scale, european billions (10^12)

~35000 short-scale, american/english billions (10^9)

The problem is people abuse of "var", and use it everywhere even when the type is not obvious from the right-hand expression/assignment. This is especially bad when reading code outside of an IDE, like in a GitHub PR, git/cli tools, etc...

From msdn/dotnet documentation:

The use of var helps simplify your code, but its use should be restricted to cases where it is required, or when it makes your code easier to read.

https://docs.microsoft.com/en-us/dotnet/csharp/programming-g...

Also, C# 9.0 introduces target-typed new expressions:

https://docs.microsoft.com/en-us/dotnet/csharp/language-refe...

Aside from the amusing programming error, the main problem with much of the "smart contract" activity today is that doing anything remotely interesting requires an oracle. An oracle is basically a server that reports the outcome of an event. And servers can be attacked in ways that systems like Ethereum can't.

Thank you! I've tried to put it into words before but I think this is as close to perfection as one can get while describing why smart contracts are not what people believe them to be.

That's amazing, the IDE itself and the shader preview running on a WebGL canvas. Thanks for sharing!

Can you expand on why it isn't a fiat currency?

I was wondering the same thing, there's nothing stopping the archaeologist from unwrap it it off-chain/offline/...?

Either we're missing something from the unwrapping process, or there's too much trust put into the archaeologist.

Not daily, but weekly:

1. Cloudflare Radar https://radar.cloudflare.com/

2. Cloudflare Blog https://blog.cloudflare.com/

3. GitHub Trending https://github.com/trending

I don't think that would benefit gamers at all.

Maybe it will offset the days it takes for a graphics card to pay itself by a few weeks? (e.g. previously RTX 3070 took x weeks to pay itself by mining 24/7, maybe it will change to x + 2 weeks?)

Gaming needs more resources to solve a problem whose difficulty is increased to produce better and more accurate images.

Mining needs more resources to solve a brute force problem whose difficulty is increased just for the sake of making the problem even harder to solve.

Yes, I do agree C# does have many constructs (Parallel For/ForEach/Invoke...) but there's many things to consider that are not designed with thread safety in mind (e.g. generic collections, List<T>, Dictionary<T>, etc... must be replaced by their System.Collections.Concurrent respectives) and many other risks that parallel computing poses.

  int x = 0;
  Parallel.For(0, 99999, z => {
    x++;
  });
  Console.WriteLine(x);

And that definetely does not match what oblio means with "have the programming language Do The Right Thing with no further hassle".

Thanks for sharing, even though it's from 2017 it was an interesting read.

Looks great, I'll give it a try. Thanks for sharing!

Thanks for sharing that parable. It reminds me of the times I've discussed about Kubernetes with colleagues.