> I'm curious about this point; if the only thing stored on the chain is a URL (including Drive/Imgur) then there's no possible way to actually preclude the content from changing right?
When you use something like IPFS the url is created from a hash of the file contents, so it is not possible to change the file without creating a new url.
VAERS is a voluntary reporting system, it does not include any deaths by bus. Nor does Sharyl Attkisson hawk miracle cures so you seem to be talking complete nonsense.
> Rug pulls have emerged as the go-to scam of the DeFi ecosystem, accounting for 37% of all cryptocurrency scam revenue in 2021
So 37% of $7.7 billion is $2.849 billion.
> All in all, rug pulls took in more than $2.8 billion worth of cryptocurrency from victims in 2021.
> It’s important to remember that not all rug pulls start as DeFi projects. In fact, the biggest rug pull of the year centered on Thodex... In all, users lost over $2 billion worth of cryptocurrency, which represents nearly 90% of all value stolen in rug pulls. However, all the other rug pulls in 2021 began as DeFi projects.
The graph shows $2.6 billion was lost with Thodex. So that leaves $0.249 billion that was lost in projects that were rug pulls that began as DeFi projects.
Ah yeak ok. I agree the formatting is a bit unusual. I guess the confusion is Chris did mention Axie but it was in the previous post which is paywalled.
The only time the sizes attribute is not needed when using srcset is when the rendered size of the image is fixed.
One example would be a logo that is less than 320px wide (so it fits even on mobile). In that case you can add x descriptors to give a higher quality logo on retina screens. e.g.
But if the image depends on the viewport width then 'srcset' (without x descriptors but with w descriptors) and in combination with 'sizes' is the way to go.
I've had this happen when uploading a highly optimized image (manually optimized with Squoosh) 2560px wide, then WP generating a 1920px wide version and the KB was larger. I believe I was using the free version of Smush at the time and had to change. Now using reSmush.it.
The browser doesn’t know the size at which the image will be rendered on the page until it has downloaded and parsed all the relevant CSS and JavaScript files. Shortly after the browser downloads the HTML, it requests CSS and JavaScript. But before the CSS and JavaScript is done loading, the browser starts downloading images. The only thing that the browser does know is the size of the viewport. If we give sizes based on screen width then the browser will know which image to use. The width doesn’t have to be expressed as a viewport width unit though. It can be any length including absolute and relative length. You can even use CSS calc() to do things like auto-calculate margins dynamically.
For your example I believe it would be done like so:
When you use something like IPFS the url is created from a hash of the file contents, so it is not possible to change the file without creating a new url.